Brandon Watson on ChevronWP7.Updater’s “non-serviceable state”: it is not FUD

Reading time icon 2 min. read

Readers help support MSPoweruser. When you make a purchase using links on our site, we may earn an affiliate commission. Tooltip Icon

Read the affiliate disclosure page to find out how can you help MSPoweruser effortlessly and without spending any money. Read more

fudIn this week’s Windows Phone Radio official Microsoft podcast the hosts Brian Seitz and Matt Akers, joined later by Brandon Watson, spoke of the issues surrounding updates and Windows Phone 7.

First, trying to take some heat of AT&T, they explained the “testing phase” was interactive, and that the delay may be that the carrier has send the update back to Microsoft for further development, which then required further testing.  This does not of course explain why the same phones on other carriers have been successfully updated already.

Next Brandon Watson confirmed that the issue of Chevronwp7.Updater putting phones in a “non-upgradable” state was real.

“The net result is that it [the updater tool] was putting phones in a state where they couldn’t be updated from us [Microsoft]. They could be updated, but beyond that, they would not be updatable.”

Microsoft is apparently looking at ways to reverse this situation without users having to send their phones back to the carrier. He insisted this is definitely not FUD, this is a real concern for Windows Phone users.

Lastly, trying to douse the flames of anticipation for MIX11, he notes that the event is primarily for developers, to let them know what’s next.  Expectations are running high at the moment for a massive update which will address many missing pieces in the Windows Phone 7 puzzle.

Read much more at WindowsPhoneMetro here.

More about the topics: nodo, update, windows phone 7