“Given the importance that Microsoft’s smartphone platform should have—not to mention the uphill struggle it faces against the iPhone and Android juggernauts—one would have thought that the company would make sure that delivery of the first patch was rock solid and reliable,” Peter Bright reports for Ars Technica.
“After all, robust, universal patching is one of the big advantages of Microsoft’s platform over Google’s Android. Microsoft’s locked down hardware requirements, in conjunction with its centralized patch distribution and offical (albeit carefully-worded) statements to say that all devices would be ‘eligible’ for updates, should have given Microsoft an almost Apple-like patch process: uniform availability, regardless of carrier, regardless of OEM, regardless of model,” Bright reports. “And because every phone is running the same software, well, it should all just work, shouldn’t it?”
Bright reports, “Alas not. Monday, Microsoft started rolling out the first update to Windows Phone 7… Sounds simple. Except it doesn’t actually work… The updates are failing to install in two ways. For lucky individuals, the process merely hangs on step seven (out of ten); rebooting the phone resurrects it, albeit without the upgrade. For a minority of unlucky users, the process fails at step six, and corrupts the phone’s firmware. What’s worse is that for some of them it appears to be bricking the phone completely, rendering it useless.”
Read more in the delightful full article here.
MacDailyNews Take: Wholly expected incompetence; a fish rots from the bald head down and Microsoft was rotten to start with.
[Thanks to MacDailyNews Readers too numerous to mention individually for the heads up.]