imageMicrosoft as finally come forward to explain what went wrong with the update, who is impacted and where things are headed. IA few noteworthy items: everyone will get the update but it may be days or even months before this happens…ugh. Here it is in full, with a few items highlighted in red by me:

It’s been roughly 48 hours since we hit the send button on our first Windows Phone software update. The rooms around me are buzzing with folks monitoring the rollout, sifting carefully through incoming phone health data (from customers who provide it) and pouring over the anecdotal update reports you’ve been posting around the web.

You’ve said loud and clear that you want to be kept in the loop. So here’s what we’ve learned so far.

Contrary to some of the gloomy headlines out there, our preliminary internal data paints a very different picture about update progress:

  • 90 percent of people who’ve received an update notification have installed the new software patch successfully. (So when your turn to download it arrives, chances are good this will be a non-event.)
  • Of the 10 percent who did experience a problem, nearly half failed for two basic reasons—a bad Internet connection or insufficient computer storage space. Luckily, both are easy to fix.

Has the update process has gone perfectly? No—but few large-scale software updates ever do, and the engineering team here was prepared. Of course, when it’s your phone that’s having a problem—or you’re the one waiting—it’s still aggravating. That’s why we’re committed to learning from our first update and improving the process. We know we have work to do, and we won’t be satisfied until you are.

As the teams here continue to monitor the ongoing update, I’ll report back if there are any other noteworthy developments. Meanwhile, let me address a few other questions I’ve been seeing, here and elsewhere.

Q: I’ve read there are problems updating Samsung phones. Is this true?

A: We’ve identified a technical issue with the Windows Phone update process that impacts a small number of Samsung phones. We’re working to correct the problem as quickly as possible. But as a precaution, we’ve briefly suspended updates to Samsung phones. We are continuing to update other Windows Phone models as scheduled.

Q: How can I make the update go more smoothly when my turn comes?

A: Given what we’ve learned so far, the best way to prepare for your update is to make sure your computer has an Internet connection and plenty of disk space before you begin. Why? Because before updating your phone, the Zune software and Windows Phone 7 Connector for Mac attempt to back up your phone data as a precaution. For more details, see Make room on my computer for phone updates.

Q: If I have questions or a problem with the update, where can I get help?

A: This troubleshooter addresses several update-related error messages. Another great source for troubleshooting info is the Windows Phone forum on Microsoft Answers. Finally, see our complete set of Phone update articles on the Windows Phone website.

Q: Can every Windows Phone receive this update?

A: Yes. All Windows Phone 7 devices are eligible for updates.

Q: Can I get this update “over the air” via my carrier’s cellular network?

A: No. The only way to update your phone is to connect it to your computer and update it via either the Zune software or the Windows Phone 7 Connector for Mac. (Only the update notification is sent over the air to your phone.)

Q: I don’t live in the U.S. Will the update process work differently where I am?

A: No. Everyone with a Windows Phone 7 in a supported market will receive a notification when new updates become available, and will have to update their phones by connecting it to their computer and running either the Zune software or the Windows Phone 7 Connector for Mac.

Q: I still haven’t received an update notification yet. When can I expect it?

A: It’s hard to predict because it depends on many factors. It could be days—or even weeks—before you’re able to update your phone.

Q: Why can the process take so long?

A: The simple truth is that the smartphone world is complex, and even a small update like this requires a coordinated effort by multiple companies to pull off.

Another reason is that Microsoft and the carriers we’ve partnered with around the world need time to test phone updates to make sure they meet our joint quality, performance, and reliability standards. Testing schedules can vary, and that affects when you’ll be able to download an update.

We’re working closely with our worldwide partners to determine update delivery schedules and also looking for ways to improve the process.

Q: What happens if I don’t update my phone?

A: Even if you skip this update, you’ll still eventually receive it. The patch will simply be bundled together with our next update.

7 COMMENTS

  1. Wait a minute, if it may take weeks or even months to get this update, and if it will be bundled with the next update for those that skip it, then does that mean it may also take weeks or months to get No-Do?

  2. @D-Money: I’d agree with your interpretation. They need to make sure that updates don’t bric phones and only then will Samsung devices get updates.

  3. “Ok i figured out a way to get my Omnia 7 running again after the C101002e restoration error.

    Here are the steps i followed. This will probably not work for branded phones. Follow these steps at your own risk!

    1. Check if the phone is capable of getting into the ‘download mode’. To do this: Turn off the phone (or remove > replace battery), then turn it back on by pressing the power/camera/VolumeUP buttons simultaneously. When the phone turns on, release the power button. If the phone shows the yellow triangle with exclamation and a “download mode” message, your phone is capable of getting into the ‘download mode’, and you can proceed to step 2.

    2. Download the following files (be warned: multiupload.com is loaded with huge ad’s/pop-ups)

    – Firmware I8700XXJK1 ## 2010 November CSC_Cetus_Europe_I8700XENJK1: http://www.multiupload.com/OGUYF4F3VA (rar-file password: samfirmware.com)

    – Samsung WP7 Flash Program: http://www.multiupload.com/3OE4SYAGQA

    – Samsung Mobile USB Drivers V5.2: http://www.multiupload.com/GH391NDSY1

    – Flash Guide (English): http://www.multiupload.com/FDRJ3WDZQ7

    3. Unrar / install downloaded files

    4. Make sure the phone is disconnected from computer and turned off

    5. Reboot computer for the drivers to complete install.

    6. Start Samsung WP7 Flash Program.

    7. Turn on the phone in ‘download mode’ and then connect it to the computer

    8. Drag the 4 files from the unpacked firmware rar-file to the Samsung WP7 Flash Program dialog screen. The application will place each file in the correct field.

    9. When the phone is recognized you can use the ‘Start’ button to start the flashing process.DO NOT INTERUPT THIS PROCESS!

    10. When the flashing is done (aprox. 15min.) the phone will automatically reboot and show the welcome screen.

    Note: For more information about flashing the firmware to your Omnia 7 see the the flash guide you downloaded as well

    (Source/credits for downloads: http://www.samfirmware.com/WEBPROTECT-i8700.htm – registration required)

    As stubborn as i am i tried to apply the update again, and it worked! :-)”

    All credit goes to SConijn

  4. This is really pissing me off. I’ve stood faithfully by MSFT and WP7 for months now, eagerly yet patiently awaiting the “early Q1” copy/paste update that has already gotten pushed to late Q1. Now I may be facing a sometime-in-Q2 update for frigging copy and paste? I am very irked right about now. This is kcuffing demoralizing.

  5. Hmmm – that leaves me and my family in the last 5 unmentioned percent that can’t update our phones. I am not impressed!!
    I think that a 5% failure is a big time failure in itself and my guess is, that it’s 10-100 times more than MS suspected. If a “large-scale software update” for Windows XP/Win7 had a failrate of 5%, then I suspect that heads would roll.
    It’s embarrassing, Microsoft! Stop fooling around and start delivering – now please!

  6. […] problem, 8007054B4 specifically, with some official pre-update update his people issued in February. Eric, if you […]

Comments are closed.