Microsoft support staff admits NoDo was supposed to go live on March 7

There has been a lot of talk about NoDo the past few days as many wonder when it will actually ship out to end users.  Neowin originally locked down March 8 as the launch day, but it's worth noting that our source did say March 8 in "Australia/NZ" which would mean it would indeed launch on the 7th March in the rest of the world.

The information comes from the Microsoft Support Forums (via Wpcentral) where a forum moderator admitted that NoDo was scheduled for the 7th. The moderator states

You are right, the NoDo update was suppose to be released on March 7th, but it has been postponed. We don't know a date yet, but Microsoft will push the update soon.

It is widely believed, but not confirmed, that Microsoft held off on the update after the issues with its pre-NoDo update that resulted in 10% of its userbase devices failing to complete the update or becoming unusable. Because of this, they have held off on the launch of NoDo to ensure that it goes as smooth as possible. Microsoft does not want to be known for pushing faulty updates, it has a lot riding on the success of NoDo. 

Microsoft France posted up earlier today that NoDo will ship out later this month. While and exact date has not been pinned down, some suggest March 21st as the potential day, Neowin is not able to confirm this date at this time.  

Report a problem with article
Previous Story

Mozilla announces Firefox 4 Release Candidate

Next Story

Microsoft attacks the font size of Apple's App Store brief

38 Comments

Commenting is disabled on this article.

You know... with WP7 you can say "when it will be released?" but with android you have to say "i hope this will be released for my phone".

Worst written news article I have read in a long time. I had to read the comments to figure out that the "NoDo" update is related to cellular phones.

Mr Byte said,
Worst written news article I have read in a long time. I had to read the comments to figure out that the "NoDo" update is related to cellular phones.

+1
'Assuming' stuff is crazy. At least a mention of Windows Phone 7 (WP7) should have been there.

"...update that resulted in 10% of its userbase devices becoming unusable."

Not true. 10% of the devices failed to update for various reasons. (Insufficient disk space on the computer, faulty internet connection, etc). Only about half of those were failed Samsung updates. And then only a few devices became truly bricked (Meaning, no way for the user to restore the phone). I hate that just because it's Microsoft it's okay to spread lies.

I agree and I updated the article to reflect this. Truth be told, only half of that 10% was estimated to have their phones bricked, and in most cases this was also to do with faulty connections and too little battery power.

Neobond said,
I agree and I updated the article to reflect this. Truth be told, only half of that 10% was estimated to have their phones bricked, and in most cases this was also to do with faulty connections and too little battery power.
You cant really blame MS for this but people will still blame MS for not offering a 100mbit fibre optics line to its users with a 100% uptime. Plus a wireless phone charger.

Does this mean, that when more and more different phones WP7 coming out, we'll have to wait longer and longer for these updates? If so, I have to admit than, I made a mistake by buying two WP7 devices... MS looks simply incompetent in comparing to Apple.

cpu said,
Does this mean, that when more and more different phones WP7 coming out, we'll have to wait longer and longer for these updates? If so, I have to admit than, I made a mistake by buying two WP7 devices... MS looks simply incompetent in comparing to Apple.

I doubt it. The first update is usually the most troublesome.

cpu said,
Does this mean, that when more and more different phones WP7 coming out, we'll have to wait longer and longer for these updates? If so, I have to admit than, I made a mistake by buying two WP7 devices... MS looks simply incompetent in comparing to Apple.

Sorry but Apple only have to update their own phones. Compare to Android, how long does it take for Android to be updated for all phones after a new release ? WP7 is a few days late for their own internal deadline that was never announced to the public anyway, that's unacceptable.

It's all because of the one issue with the updating phones, they have gotten over that problem so I doubt it will happen again.

Raa said,
Damn right.

Google updates faster than Microsoft at the moment!!


You have to compare the time the update gets to the phone.

For example, NoDo was RTM on January 24, 2011, but that doesn't mean it got to the phone.

Gingerbread RTM on December 6, 2010 and how many phones do you see with Gingerbread so far? Two.

Yeah, Google "updates" more often but then the update is held back for months by carriers + OEMs, that's if your phone is even supported in the first place.
Sure, you can root it and install a vanilla version but the average user won't have a clue about this.

DrCheese said,
the average user won't have a clue about this.

Actually, the average Android cusotmer is that tech savvy.

The reason windows phone will succeed is that we don't have to have that knowledge to get the most from our WP7 devices.

day2die said,
My friend is already running around with NoDo on his HD7: this just makes me mad.

because he went outside of the normal support/update procedures and did it himself.
This shouldn't make you mad. I know a dozen or more Galaxy S owners who updated their ROMs because they got tired of waiting for samsung. some of them bricked their devices in the process.

Just let MS get their update cycle worked out and we'll see the magic in due time.

jasonon said,
how did the update even brick phones? thats just pathetic!

Most of the 10% didn't brick - the update just failed. Big difference.

jasonon said,
how did the update even brick phones? thats just pathetic!

This type of thing happens when carriers don't do adequate testing before deploying an update. I assume it could also occur if a carrier tampers with firmware.

jasonon said,
how did the update even brick phones? thats just pathetic!

Hey, it happens countless time for Android and a couple of times for iOS.

There's always the possibility that something has gone wrong.

I'm not saying that it's excusable, but things happen.

rfirth said,

Most of the 10% didn't brick - the update just failed. Big difference.

It's not most. 5% didn't brick, 5% did (according to Microsoft)

alexalex said,

It's not most. 5% didn't brick, 5% did (according to Microsoft)


Microsoft NEVER said that.

"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."

I don't see "bricking" being mention anywhere. For the most part the fail update means just that. A reboot beings the phone back to normal.

Edited by illegaloperation, Mar 10 2011, 5:34am :

It is widely believed, but not confirmed, that Microsoft held off on the update after the issues with its pre-Nodo update that resulted in 10% of its userbase devices becoming unusable

not updating != becoming unusable

most samsung phone which failed to update are still working after a hard reset (since the update failed before beginning to flash the rom in most cases)

link8506 said,

not updating != becoming unusable

most samsung phone which failed to update are still working after a hard reset (since the update failed before beginning to flash the rom in most cases)

You said the "S" word. Enough said.

link8506 said,

not updating != becoming unusable

eh, remember tho that you are more technically minded than the average joe who may have bought a handset, only to find out that it's "dead" after an update. For them this is a big issue has they'd have to take the handset back for repair or get a friend to do it for them.

For you, it's a quick google and 5 minutes away.

The amazing thing is that it has been ready since december, and since then they haven't had the time to do an exhaustive testing of the update!

Well, better late than never, still like WP7

daniel_rh said,
The amazing thing is that it has been ready since december, and since then they haven't had the time to do an exhaustive testing of the update!

Well, better late than never, still like WP7


Actually, No. It can be determine from the leaked ROM that the update was compiled on January 24, 2011.