Windows Phone 7: Will NoDo show? Has Mango gone soft?
This week, Microsoft released a “fixed” version of its first software update for Windows Phone 7 that was designed to alleviate problems reported by a number of Samsung users. However, the Samsung WP7 fix doesn't seem to install correctly for a number of users.
Context & Ripple Effects
The trouble began on February 21, when Microsoft started rolling out its pre-NoDo maintenance update for Windows Phone 7; within days, install failures concentrated on Samsung handsets, as the February 23 post on update woes documented. This week's "fixed" version of that same update was meant to close the chapter — instead, per confirmed reports, it too fails to install correctly for a number of Samsung users.
The stakes are bigger than one patch: this small pre-update exists to prepare devices for NoDo, the first genuine feature release (copy and paste included) since Windows Phone 7 launched. A prerequisite patch that cannot reliably reach the devices it targets leaves Microsoft debugging its over-the-air delivery mechanism in public, before the update that actually matters has shipped.
First-order effects
- Owners of affected Samsung Windows Phone 7 devices are stranded between a broken original update and a fix that will not install, unable to take the step that precedes NoDo.
- Microsoft is forced to iterate patches publicly, handset by handset, rather than pushing the NoDo feature update on its intended schedule.
Second-order effects
- Samsung absorbs the reputational cost, as failed installs attach to its Windows Phone hardware specifically — a drag on the very devices carrying Microsoft's platform into the market.
- Rival phone makers gain a retail talking point: an OS whose first maintenance update struggles to install invites buyers to weigh update track records alongside spec sheets.
Third-order effects
- If delivery reliability is not stabilized before the larger Mango release, Microsoft's strategy of closing the gap with iOS and Android through rapid updates stalls — an echo of the earlier episode in which Windows Mobile 7 derailed entirely.
- The episode points toward over-the-air update infrastructure being treated as core platform plumbing rather than an afterthought, with botched rollouts treated as platform-level failures rather than OEM quirks.
The trend: Smartphone platform competition is increasingly fought over software-delivery reliability, where a botched update does brand damage no feature roadmap can immediately offset.