Grrrr!!! My Windows Phone NoDo update failed! Error Code 800705B4. Now what?!?

How many of you received your notice that the Windows Phone “NoDo” update is available to you yesterday? If you did, I am putting up this post to share my experience and a tip for you in the event you encounter a similar experience as me.

Yesterday, like many other AT&T subscribers, I received the notification I have been eagerly waiting for that the Windows Phone “NoDo” update is now available for my Samsung Focus. First reaction? “Yay!” Of course, like so many of us these days, I decided to wait until things slowed down a little (lunchtime) to go ahead and do the update to my phone.
After going through the proper steps and completing them to perform the update, instead of receiving the new experience I was so looking forward to, I received the following screen:

What?? Error?? Ok, fine. Most logical next step? Let’s try that again. Sure enough, after going through the steps again, I received the same Error Code 800705B4 notification telling me my update did not successfully complete. Next logical step? Bing of course! Sure enough, a quick query brought up this write-up. Not only does this write-up do a great job of walking people through how to perform the update itself, but the part that I found VERY useful is the section called, “You receive an error while you are updating.”

Inside this section, it has a table listing a collection of possible Error Codes you may see while attempting an update. What’s really nice about it is that you can click on any of the Error Codes listed and it will take you directly to the steps to utilize in order to attempt to address the issue you are facing.
Sure enough, I clicked on the 800705B4 link in the chart and was promptly brought to the suggested steps to complete my Windows Phone update. Upon using these suggested resolution steps (and I didn’t even need all of them as the second suggestion worked for me), I was greeted with the following screen:

Woohoo! I am now up and running on the latest Windows Phone update for my Samsung Focus and absolutely love it!

As noted above, I hope this post and the included link to the support document for potential Windows Phone Error Codes is helpful to any of you that happen to encounter one of them while performing your updates. Even with the Error Code I received and performing the steps to resolve it, the entire update process still went very quickly and I was up and running in a very short time.

I hope you too are enjoying the latest updates to your Windows Phone the fantastic experience that Windows Phone provides. Also, if you haven’t checked it out yet, I have a bunch of links and resources included in my Windows Phone 7 information and resources - Everything you love, easier and faster post that may also be of use to you.

Did you find this information helpful? If so, you may want to make sure you are utilizing all of the areas I share information online, such as: my Facebook page, my Twitter account, my LinkedIn account, and my blog.

Tweet this:

Thank you and have a wonderful day,

Eric Ligman – Follow me on TWITTER, LinkedIn, and RSS and see “What I’m thinking”
Director, Worldwide Partner Experience
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights

Bookmark on: MSDN , TechNet, and Expression

Technorati Tags: Microsoft,Windows Phone,NoDo,updates,800705B4,error,error code,Eric Ligman,Samsung Focus,AT&T,KB,support,800704C7,80072F05,80181196,801811A5,801881E4,80072FA8,80181197,801811A8,801881CC,80072EE2,8018000E,80181198,801811C5,801881CD,80072EE7,80180033,8018119C,801812C1,C1010007,80072EFF,80180080,801811A3,801812DD,C101002E

del.icio.us Tags: Microsoft,Windows Phone,NoDo,updates,800705B4,error,error code,Eric Ligman,Samsung Focus,AT&T,KB,support,800704C7,80072F05,80181196,801811A5,801881E4,80072FA8,80181197,801811A8,801881CC,80072EE2,8018000E,80181198,801811C5,801881CD,80072EE7,80180033,8018119C,801812C1,C1010007,80072EFF,80180080,801811A3,801812DD,C101002E

Comments

• Anonymous
  April 20, 2011
  Hate to say this but glad its not me my update worked fine

• Anonymous
  April 20, 2011
  My update worked great today, however, this is a very helpful post who might be frustrated...  Hopefully they find it.

• Anonymous
  April 21, 2011
  Very help information. It did not fix my problem but the troubleshooting page you linked to did mention the Windows Phone Support Tool. I ran that and then tried to update and it went smoothly :) Thanks for the post! A note to anybody running the support tool, it really does take a minute before your phone is recognized and you can click Recover...wait until Zune appears, close it, then recover.

• Anonymous
  April 21, 2011
  @ Kyle - Thanks for the feedback and glad it helped you out. Also, great call out on the Windows Phone Support Tool delay in your comment. As noted in my blog, I too had to go to the second step, which was the Windows Phone Support Tool. I definitely means "may take a few minutes" when it says that about recognizing the phone being connected. Definitely have patience and wait for Zune software to start up, then close the Zune software and continue from there. Eric