Despite Microsoft's assurances that it had "fixed" a buggy Windows Phone 7 patch that bricked a "small number" of Samsung phones, some users are still complaining that they can't update their handsets.
Dozens of annoyed Samsung Omnia 7 owners are lighting up Microsoft's "Answers" support site with tales of failed updates and a new error code: 800705B4.
"Did the install and finished with Error Code 800705B4 and no update," wrote one user. "Followed the web help. No help. 2nd fail at update. Anyone have any ideas?"
Windows Phone support staffers suggested that Samsung handset owners try deleting files off their phones to clear out more storage space—or, failing that, remove the batteries from the devices, put them back in, and restart.
But several Samsung users, understandably testy after nearly two weeks of dealing with the glitchy update, were growing impatient.
"Tried it and guessed what? It FAILED," wrote one annoyed user. "Now what?!"
To be fair, it's not clear how many Windows Phone users are still having trouble with the "cursed" patch (as WMPoweruser puts it), which was originally released last Monday. Microsoft later pulledthe Samsung version of the patch after getting hit with complains of stalled updates and bricked phones.
A Microsoft rep blogged last week that 9 out of 10 Windows Phone users had no trouble with the update. A few days later, he followed up with news that engineers had "pinpointed and fixed" the problem and had redeployed the patch.
I'm sure I wasn't alone in thinking that would be the end of it ... but apparently not. The good news, at least, is that the 800705B4 error doesn't seem to be resulting in any more bricked handsets.
In any case, a Microsoft rep tweeted on the official Windows Phone support Twitter feed that engineers are—again—"looking into" the latest update problems.
The patch in question is the very first for Windows Phone 7, Microsoft's top-to-bottom revamp of its long-in-the-tooth Windows Mobile platform.