Select a language to translate this page!
Powered by Microsoft® Translator
UPDATE—Fri. Mar. 4
This week we began sending the February update to more customers around the world, adding 10 additional carriers to the distribution list. Since then we’ve been listening and watching the rollout closely. Despite the increased scale of the distribution, we continue to improve on the 90% percent success rate I’ve mentioned.
We also received reports this week that a small number of customers—about 100 total worldwide—are encountering a new issue when trying to install the February update. The problem only appears to prevent the update from installing.
We’ve spent the last 24 hours aggressively investigating the issue, and have identified a work around for error code 800705b4. You can find it here. We appreciate the patience of customers affected by the error and will continue to carefully monitor the update rollout and troubleshoot any issues that arise.
UPDATE—Wed. Mar. 2
Starting today, we plan to resume rolling out the February update to Samsung phones. Meanwhile, we’re continuing to dispatch the update to other Windows Phone models. As has been the case, the software patch is being sent out on a rolling schedule. You’ll see a message on your phone when it’s available.
During the past week the engineering team has pinpointed and fixed problems that were preventing a small percentage of Windows Phones from installing the February software patch. We apologize again for the delay and continue looking for ways to improve the update process.
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 paint a very different picture about update progress:
Has the update process 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.
This post is the best thing you guys have ever done when it comes to communication with the public. Seriously, this is just awesome!
I agree with TDA.
I, like many others, understand that things don't always go as smoothly as we'd like . But when there's an open communication then we feel that you value us as customers.
Thank you for the post. It is very useful and us end uers love this kind of interaction and information.
Thanks so much for the transparancy. If you hit a snag it sucks, but thats life. As long as you are open, honest, and timely with updates (both written and software), I think that things will go well. I really love this platform and want to see it succeed. With this kind of interaction with clients, I think that that should be an easier reality.
Keep up the good work.
Quick question if you have a second... I bought 3 devices to use for development and do not have service w/ a carrier. Will I ever get an update? If so is the process different for my situation? (LG Quantum 7 "AT&T" and 2x HTC HD7 "T-Mobile")
Please try to be more open. Exactly what "technical issue" did you find--and why did you not find it before? How many phones are being BRICKED? How long exactly have the "partners" been testing this update? It sounds like you are talking with PR in mind, instead of being honest.
Very glad to see an update. So refreshing that it is so clean and open (as far as I know!). Thanks
Appreciate the clarification and quick response! http://tinyurl.com/5sn4mnr
Thank you, I truly appreciate this type of communication! Opening up a little like this makes us all feel a little more confident that something structured (aka good engineering) is going on behind the scenes with the WP Team. I hope this is the start of turning this, or the Development Blog into something similar to IEBlog or the Engineering Windows 7 Blog.
i have an unlocked non telco HD7 and still have no notifiaction and i cant see any update on the zune when i connect to it...
and when i force update on zune it says my phone is upto date..
Thanks for posting this followup! We do appreciate been kept in the loop so to speak.
But your post raises some questions, specially for future updates; lets say for argument sake that the 'NoDo' update is announced to be available on March 8th (based on rumors at this point), and say that none of the carriers are going to stop it:
If I'm reading your post correctly - it could take weeks for us to get this update based on the carriers testing schedule.
I think it is misleading to say the update will be released on Day 1 when the user community with locked phones may actually get the update on day 45 or 90 (on a 6 to 8 week testing schedule).
I believe librarianscott makes a good point, how long have the carriers been testing, and better yet, have they already begun their testing so when the official word comes out from MS they release it to their customer base? We all want them to test with the phones the are supporting but we also want to get our updates when they are announced to the world.
Otherwise - MS is going to have a lot of upset customers, claiming they were lied to when the news come that 'there's a new update available" but your not getting it until the carrier is good and ready to give it to you - if they let you have it.
Yes, I do understand that updates are cumulative... but that's even worst should the carrier decides to exercise their right to 'block' a particular update...
I agree with everyone thus far asking for more community involvement. WP7 has such visibility from a consumer perspective, that Micrsoft should provide more information on when updates will be released. While I am happy carriers have no control over the development of WP7, I do have a problem with them being able to hold up a release. OEM's should be the only participant that should be allowed to delay a release, not the carriers.
I would also suggest a deeper involvement with the community. Allow selected participants to join a Beta program. Those that have bought a WP7 device are ealy adopters, but the entire community shouldn't be Beta testers for new updates. Microsoft has programs in place for corporate and consumer markets to test early products (MSDN, CTP, RC, etc. are all great examples.) I know for one that I would love to help be involved with that process. I beta test software for many other companies, including MS and my own employer.
Can this be pushed to the Insider app so the regular joe gets this info? I'm emailing my less techy WP7 owner friends to keep them up to date.
Okay, so why ALL Samsung phones? I've not seen indication that the problems are affecting any devices except the Omnia 7. The reports from across the more popular Windows mobile device sites can't seem to agree on the terminology or the parameters of the failure, but it seems clear that the Omnia has the issue. Again, why penalize Focus owners--unless you have information indicating there are failures there, too? I loathe generic answers.
@ScubaDog2008, for what is worth, I read on the WP7 forum that the Omnia 7 is the European version of the Focus. MS may be just being overly careful not to break any more Samsung devices until they know the combination(s) of model/firmware is the problem. Also, if they have a fix for it, that the fix doesn't break the other Samsung devices....
you have to expand the beta testing of the product, to selected consmer in all country
I have the problem!!! Update Bricked My Phone ! I am very raging!
(1) Samsung Focus Model SGH-i917R, Rogers Canada
(2) Step 6 of 10
(3) Error code C101002E (whenever I now plug in the phone) (I have a screenshot)
(4) It recognizes it with a Restoration Error.
(5) Windows 7 Ultimate 32bit (fully updated and patched)
How to fix this problem?
MS must fix as fast as possible.
what is the version number after the update, I just bought my WP7 phone and I've tired to update and I got up to date message with version 7.0 (7004) which number should I expect after the update ?
Another Question. for Arabic support. I see that it works fine in applications but the shaping isn't working in IE. will that be fixed soon ?! or in The major update that annouced to be later this year ?
Unupdated, my Focus has Firmware revision=2188.8.131.52, Hardware revision=184.108.40.206 and bootloader version=220.127.116.11. My device only shows a model of SGH-i917.....without the "R". Also, according to reports, there is now a way to rescue the bricked phones by connecting them to the PC while doing a special power-up mode. It boots the device in "download mode", which I assume would be the initial way any device would have to accept it's initial system.
Also, apparently the 10% of users who have experienced this issue the top contenders for the cause are not enough storage space left on their hard drives (or at least the one the update uses to backup the device) and inconsistent internet connection. Since I normally sync my Focus to my notebook (my desktop unit is my music studio/gaming workhorse), you can bet that when I do finally get to update I'm going to be connecting my notebook using the ethernet port instead of relying on wifi. And I have over 150GB free space, so even though my Focus has the 32GB microSDHC card, that should be plenty of space.
If a Microsoft update bricks my Omnia 7 by corrupting the firmware (which is what seems to have happened), but the firmware is the responsibility of Samsung, who is liable to fix it?
I fixed my Omnia 7 by flashing the latest Samsung firmware. Will this method be made public for other users? If not, why not?
Returning the handset to your carrier, as recommended by Microsoft, seems like a poor option, as the carrier is neither to blame or responsible for a solution.
@ausejxi I agree.. how do we know when these update will actually be available to us? How is this different from the BS of the Android.. Nobody knows if you will get the update or when it will show up until the day your phone tells you there is one.. even though everybody else around could be using their updated phones with new features for MONTHS
I love my Windows Phone... I just typed a 24-word long text in 15 seconds without a single error. Incredible auto-correction is just one of the things that makes it a joy to use.
That said, this update scenario is a joke. This tiny update, which changes no features, is being blocked by mobile operators AND has bricked 10% of the phones it has gone out to? And the big update (which has allegedly been finished since December) is being sent out in the first two weeks of March - is that when we'll all get it, or will the mobile operators block it again? If that happens, when will we actually get it? April? May? Unbelievable.
Microsoft, you make so many good products. Why do you make it so hard for me to love them?
Calum, why are you laying allt he blame on Microsoft? I see people doing this all the time, and while I'm not a fanboy, I'm honest and THOROUGH about assigning responsibility to situations. It seems like you, and others, just want to launch at M$ as if they had total control of this. If this were Apple, you'd be almost 100% correct since they own the entire process, minus what the carriers (which until now was only AT&T) did. If some carriers are blocking the update (and we have no explicit statement from any carrier that they are blocking it) then the fault for that lies squarely on the carriers, not Microsoft. Period. If the update is bricking phones, the jury is still out on why. If it is only affecting certain Samsung phones, then the fault is likely SHARED between Samsung (since indications are that certain firmware versions are in common) and M$ for not working with Samsung to test enough machines to see if a problem popped up. Early indicators also show that contributors to update failure involve not enough hard drive space and poor internet connection---both of which are the fault of the user. Some of us out here are WELL AWARE that you never do ANY kind of update--whether on a desktop, notebook or mobile device--without a completely stable hardware layer. Okay, so maybe the average user--who by now should be a bit more saavy than most of my generation is--can't be expected to anticipate such "conventional wisdom" and that Microsoft should have found a way to include a precautionary disclaimer with the update. So, we could debate fault there. But don't couple your frustration regarding the speed of updates and weak communication from Microsoft with the issues with this update. That's a completely dishonest approach, and some of us out here get tired of seeing it.
............not all of a person's behavior problems are due to a bad relationship with mommie.
Agreed. Hopefully all the parties involved, from MS to the Carriers will do a much better job of communicating with the comunity when the updates are available. MS is doing its part by comunicating (regarless of how much more details we may want) Where are the communications from carriers and OEM's?
@ScubaDog2008 I think you lost quite a bit of credibility by typing "M$", but anyway... at the end of the day, whose fault it is is irrelevant to the user. I blame Microsoft because they are supposed to be taking a vertical approach to Windows Phone 7. We were all sold on the notion that the OEMs would from now on be reduced to box assemblers and the mobile operators reduced to dumb pipes, with neither of these groups being able to do anything to ruin the experience. This has turned out to be a lie. As I said, I love WP7; I just wish Microsoft would take the responsibility they said they would, and not say we are getting things "very very soon" if we actually aren't.
1st off: it's awesome to have a post explaining and detailing how things are going. I don't have an WP7 but looking very, very forward to buy one.
There's just one question in mind which applies as to the Samsung device itself as to the 10% listed above: couldn't you have tested those defects before submitting the update? How are you hoping to have updates tested on OEMs hardwares' without having theses issues repeated? It's really important to not screw up here because the market isn't patient to issues like these continuously, specially coming from MS.
Now that there's a phone backup procedure in Zune, will that backup and restore be useful when installing an 'approved' SD card? I know the approved list has not appeared yet, but from what I've read, adding an SD card will reset the phone. It would be great if this backup and restore would work for those upgrades in the future.
I feel a little misled, I have not had an update notification (I am with o2 in the UK with an HD7) from what I understand, I may have to wait up to 2 months while O2 test this update which means I would not get it until late April, I may then have to wait another two months until NoDo is available to me (assuming O2 do not skip it) meaning late June. If O2 do skip NoDo, I will have to wait until early 2012 to get it rolled in with Mango. I was prepared to tolerate missing copy and paste functions until March based on the "early 2011" guidance from Microsoft but not until mid 2011 or even 2012. My question is, why did Microsoft not factor in carrier testing times when they give a schedule of update availability, what MS appear to have done is provide the availablity date to the carrier, not the consumer. Being successful in this industry is partly about managing consumer expectation then delivering a litlle better than expectation, something Apple do very well.
We do need clarification not only from MS but from the Carriers as well - I can only speak for my own carrier (TMob) when I mention the 6-8 week timeframe as that was what they told me.. Your carrier may have a shorter/longer testing time. It would also depend on when MS delivered the updates to them.... So, if we were to believe the rumor that NoDo was release to the Carriers back in the Dec/Jan timeframe, they should be able to release it by March... So as you can see, there are a lot of assumptions being made (and you know what they say about those...)
Again, maybe the carriers have tested this update to the updater and are going to release it shortly OR are currently testing NoDo and will release it in tandem with the MS notification. BUT we, the community, need to know what to expect.
Glad to finally get at least a little information from Microsoft. Don't know why that's always such a challenge.
But while you're all congratulating yourselves on your 90% success rate, let me just remind you that out here in the real world Windows Phone has been stagnant since launch. Not a single bug fix has been deployed. Not a single new feature has been deployed. Nothing. This is FAR from the "rapid innovation" we were promised. You've got to move faster!
And regarding this specific [non-]update: you seem to stop just shy of saying that the 5% of failures (those due to low space/internet connectivity) are USER errors. What an insult. A patch mechanism that can't determine and/or doesn't check for it's own resource requirements before beginning is just plain broken. And how you and your esteemed partners could've missed that in all the testing you've supposedly been doing since December is beyond me. And what about the remaining 5%? What's the story there?
Now that the machine is feeling communicative, how about answering the real questions:
1. How much is this going to delay the "first 2 weeks of march" update? We know it's coming, so just give us the bad news now.
2. Which carriers are blocking this update, and which will block the March update?
I keep hoping Microsoft is just under-promising and will over-deliver. But I'm losing the faith...
Calum said:"I think you lost quite a bit of credibility by typing "M$""
Really? Why? They are one of the most "well healed" corporations in the world and, being a business, they are (and SHOULD be) about making $. Also, regardless false starts and failures like Kin, they seem to have a knack for continuing to be profitable. Not really a bad thing
Calum said:"at the end of the day, whose fault it is is irrelevant to the user. I blame Microsoft because they are supposed to be taking a vertical approach to Windows Phone 7. We were all sold on the notion that the OEMs would from now on be reduced to box assemblers and the mobile operators reduced to dumb pipes, with neither of these groups being able to do anything to ruin the experience. This has turned out to be a lie."
Okay, please show me anywhere that there was an official statement or direct marketing scheme that this WAS a completely vertical approach and that OEMs would be box assemblers and carriers "dumb pipes", because that is NOT what I observed way back last April when I started following the development. I believe you heard what you wanted to hear, as did many others. I'm not saying that Microsoft didn't play a little bit of a game using vagueness and our own tendency toward assumptions to their advantage---all companies do this. But how can anyone with any sort of awareness of the reality of carries and OEMs begin to assume that they would be "eunuchs" in the WP7 world? That's just ridiculous. What Microsoft DID make explicit was that they established MINIMUM REQUIREMENTS that OEMs had to abide by. That means OEMs can play above the line as much as they want to. Now, Microsoft has initially controlled that horizontal playing field to a great degree by not releasing all the APIs, which means OEMs may have a bigger sandbox but not a lot of toys to play in the sandbox with. For pity's sake, folks, none of this is a really big mystery. We've had decades of previous Microsoft behavior and many years of behavior from the phone companies, carriers, and OEMs to bump all this against. I'm not trying to diminish the validity of our frustration (believe me, I'm nearly as frustrated), but people are behaving like spoiled little brats, quite frankly.
I think Paul Thurrott has actually articulated the whole WP7 arena quite accurately and honestly. He nailed the poor choices and failures as well as the smart things they've done. Microsoft has ALWAYS been horrible about communication--marketing is NOT communicating. Microsoft's stock in trade is not so much innovation as it is renovation--taking a good idea and making it a much better one. But with few exceptions, hardware has not been their forte'. They have been and will continue to be reliant upon partnerships with OEMs---yes, even to a great extent with the Nokia marriage. Apple avoids this by being a TRULY vertical approach---talk about a collective. But you are stuck with what they give you. Android, in contrast, is (as is typical for Google, the least innovative of the bunch) is ALL OVER THE FLIPPIN' MAP. Yes, there's plenty to like there, too. But even more to dislike. Microsoft, agree or disagree, chose a path somewhere between, maintaining a somewhat vertical while allowing some horizontal play (and apparently even more with Nokia, but that remains to seen).
By the way, I don't think ANYONE knew this pre-update was coming--most of us were anticipating the NoDo update as being The First. So, for anyone to say they were "misled" is again being a bit dishonest. I'm convinced that this "pre-update" was most likely a result of what Microsoft discovered as they were helping some of the new CDMA devices prep for deployment (e.g., Sprint's "Arrive" device that has the NoDo update already on it). They probably discovered some issues with the original updater and tried to fix it and push it out.....probably bad judgement in not testing that on a larger number of devices and carriers.
This situation has been a feeding frenzy for those that have been saying from the beginning that WP7 would fail. I love WP7 and am a user but I am seriously upset at what has gone down.
1. This update bricked users phones and they have been sent back to carriers and Samsung to deal with it. They are being told they are being told that is not their problem. When they are helped they are told 4-6 weeks for repair and can not secure a loaner. This is unacceptable at a minimum. How can die hard fans not have a better option than this?
2. I really wish MS would have been honest about the update process. Carriers having control over the update process is going to do Windows Phone a lot of good (note sarcasm). So basically at the current rate, if they skip an update we could be waiting 4 - 10 months per update.
I have not received this update. I can not wait for the same thing to happen when "Mango" comes out. Because you are telling us that they can skip it if they feel like.
Here is a question that I need answered. I have an lg e900h from telus now this phone has been unlocked so I could use it on sasktel's network. But here is my problem, both sasktel's and telus have released this new update on their networks and I have confirmed this by phone conversation with both parties but yet I have not received the update notification on my phone. Could this be because my phone is unlocked and technically not supported by sasktel's network? And not registered on the telus network? Zune software on my computer says I am up to date but I am not because it shows the 7.0.4 not the 7.0.8 that is the new update. These are Canadian carriers guys
I'm dissapointed at the amount of time it is taking for us to recieve the update on Telstra in Australia. Surely if Apple can push out updates all at once WP7's could be pushed out like that aswell.
@TwiceBitten - I agree that a bad internet connection, or lack of disk space in no way should be causing issue. Zune software should be smart enough to see how much data it needs to back up, which could be up to 40GB theoretically, and act responsibly on that information.
Also not sure how a bad internet connection would have any effect on updating software, you download it, then you update it. Unless there is some sort of cloud backup going on here, in which case this should also be tested beforehand.
As far as firmwares causing the problem on certain devices, I think the WP7 team should have been testing that, not the manufacturers! And the update should confirm that the device has a set list of valid tested firmware. If the update has not been tested on a firmware revision, it should follow a procedure to update the firmware first.
That being said, I still appreciate this openness, and hope you are learning from these mistakes. Because you only have 10 or so phone types out there, once that number gets into the 20's, 50's, etc... the process and firmware validation are going to have to be locked down extremely tight!
As long as you are refining and continue refining and reporting those refinements I will be happy. Say next time you solve the internet connectivity, storage space, and some of the firmware problems and you hit 96%. With still 1% storage problems (people downloading something else while phone is backing up, etc...), 1% loss of connection to cloud causes hang, and 2% firmware problems. Report it and chart the progress to show it's being reduced, refined, and improved....this will certainly give people a lot to cheer about.
Microsoft is stating that devices will or should get updates even if they are not in the country, i am from singapore and currently living in malaysia next door.... and no i cant get an update for my HD7. i called HTC in malaysia and they told me as my device is from singapore i cant get update in malaysia???? i will call sinagpore HTC or the retailer who sold me the unit... but it seems so rediculeus that the update is through zune and i have every thing but cant update my unit out of singapore (if its true i think its bullshit...and i will like to have refund for my phone)..
When I said I felt misled, it was because MS announced a 21st February update - this was a nice surprise, but they misled me because it has not been delivered
Hmmmmm, it's like waiting for my ISP to allow me to update my Windows - I really don't like this... If anything, I could imagine that mobile phone vendors would need to validate the functionality (which in this case would mean that we would blame probably Samsung and not Microsoft), but providers??
Anyway, I wanted to say THANK YOU for sharing this information with us, I really do appreciate the way how you keep us in loop!
Might I suggest you put the backup Zune makes of the phone, to either a user definable path, or to %temp%?
Personally, I never have many GB's free space on my OS/App drive, and when Zune started making my backup to my App drive I was first wondering why suddenly all my free space was gone... And with people having the possibility of having 32GB or more of a phone, which means a backup of 32GB or more, well, it might need a lot of space, so having the option to put it on your data drive (where I do have a lot of free space) makes a lot of sense to me.
So is MS going to tell us how much of free space we need to have on our computers for the update to go without issues? Sufficient does not mean a lot.
Ok Michael, it's now over 48 hours, and a number of user questions, since your original post and we haven't heard a peep out of you. Any chance of a further post answering some of those questions?
I don't have a WP7 phone yet and, to be honest, I came very close to hitting the "Buy Now" button on an Android HTC Desire HD yesterday (but just couldn't make myself do it!) If this fiasco goes on much longer I'm going to run out of patience and simply go elsewhere.
Hey!! I'm From Mexico City and I have my Windows Phone LG Optimus when i get the Update? my Mobile Operator is Telcel and I have a lit problems whit the clock and the Music
So AT&T is probably the worst of the carriers when it comes to rolling out updates. They never rolled out the 2.1 update for my Sony Ericsson Experia for example though it was available for nearly 6 months and other carriers around the world were pushing the updates out. I ended up having to jail break the thing in order to update it to 2.1.
I would hope that AT&T doesn't futz around with this one. I went back to my Sony while waiting for this update on my HTC Surround which I love. But the absence of cut and paste etc was annoying enough to make me put my HTC back in the box until the update was distributed. This is not good yes? If I were Microsoft I would be beating the carrier's about the head to ensure they don't delay their testing / distribution of these updates. It nearly killed the Sony brand though Sony should never have shipped with 1.6 Android anyway but that's a different discussion.
So I am putting the HTC back in the box after waking it up briefly this morning in an attempt to load the update. Sigh.
No update here yet.......Just seams like WP7 went so backwards from where WM left off. Sure it kinda works better, but its missing the stuff that made WM worth using. Like Remote Desktop, copy past, a drive letter..... Also would be nice to have a complete media player with all the functions built in like audiobooks. Just thought if your going to replace an OS make it better or at the least have keep the good stuff from the previous version. Hope some of it is coming in future updates.
While it's nice to see some communication from you on the issues, there are still many unanswered questions here which, quite frankly, you really need to respond to in a more timely fashion..
Keep the communication open and honest, and you will keep loyal customers. Ignore us, and you will start to see more and more defections to Android and iPhone.
Its been a week since Windows Phone 7 update is released. i am in singapore and using HTC HD7.
Hope to see it coming soon on my phone.
I will object on your remark that WP7 is backward to WM... it’s a great OS, however with this OS MS is very tight lipped, and at this moment they can’t even tell us that they pushed out the update to who??? it’s not device specific, it’s not by carriers it’s not for Open market devices.... then who the hell got the update and why... if they picked the live ID's and send them update I am fine but MS is not telling their customers anything, OEM partners have no clue as well... not committing a date was the right thing but after pushing out the pre update to some is very bad as the rest of the ppl will be wondering what the hell is going on....
I like the OS but the way the update is handled is not good at all..
i really think that Microsoft should make these updates available without carrier's involved and just push them out to us because some carriers are not very responsive to clients and updates. in the end this will hurt sales of phone 7!! i have told most of my friends who have been looking at my phone and are interested in buying one to wait until this mess is resolved about update issues like some carriers holding back the update for no reason at all. i am having this problem right now with not getting this update and frankly debating if i should sell the phone and move to different platform Microsoft cant seem make a decision about whether the end user is important for the platform or if the carrier is. at the same time they are slow to respond to these problems and are very vague about the whole situation.
don't get me wrong i love phone 7 and i thinks it is one of the best phone os's i have used and it links everything that matters to me in one package. but if i cant get these updates in a timely manner or worst case scenario not at all i just don't see any point in supporting a platform that cant support its clients.
now i know you guys are reading this and maybe getting back to us on these problems would be great.
or even just acknowledging that you are looking into it would be a start.
Great discussion. Don't worry: I haven't slipped out the back door on you.
Been a hectic couple of days, but I wanted you to know I'm reading your responses and looking into some of your update-releated questions--so please hang tight.
As soon as I have more to share, I'll post it here.
Still haven't receive the update, checked everyday, but nothing...
When you connect the phone and Zune shows the update shortinfo it has a link saying "more info". However pressing that you just go to homepage of microsoft.com or something like that. People will want to know what the update is about so you should fix the "more info" link
Why is it so hard for Microsoft to cooperate with the homebrew guys and use their virtual keyboard layouts for other languages? Esp. with Greek it's a pain writing in Greeklish (with english chars) and having the current kbd change your words to other English ones - see forum.xda-developers.com/showthread.php
For FrancisAmar Singh - unfortunately WP7 doesn't allow switching between multiple Windows Live accounts, but has a main one and others serve for aggregation of contacts etc. info. Combining that with the fact that they use separate marketplaces for separate countries (e.g. for Greece the phone is totally locked down since there's no marketplace although carriers do sell it here), you have to use a fake US/UK or similar (from country with Windows Phone marketplace available). Windows Live account by giving fake Postal Code and Address info at http://www.passport.net and then using that to sign up for Xbox Live too and on you WP7 phone. A total failure on Microsoft's part. Similar situation is on XBOX, but there you can have multiple Xbox live accounts on XBOX and you can switch to the US/UK one to download something that is missing from e.g. the Greek marketplace (for example a fail is that they were selling on XBOX Family Game Night extras [games] on greek marketplace, but then you realized you couldn't download the family game night free client to play what you just bought, because someone forgot to add it to the marketplace - signing in with UK account saves the day then). Come'on MS, wake up and don't torture users
Hi. tnx for letting us to commence here and say our problems !
I live in iran- tehran. It's about 7 days i am waiting to get update ! i was one of the first one who bought wp7 device ( Mozart 7 ) . But what i see now ?!! still no update for me ! my friends get their own update last week in my country but...
i check everyday my phone by GPRS , Wi-Fi and zune for update ! but i see no update !
Is this MS support for it's customers ?!!!
it makes us angry and so disappointed .
Michael Jackson : " ... They( MS) don't really care about us ... "
My wife and I both have Windows Phones. I have the Samsung Focus and she has the LG Quantum - both AT&T. I know that the Samsungs have had the update put on hold, but it seems odd that she hasn't received the "pre-updated" yet either. Just speculating here, but could AT&T be putting the breaks on these pre-updates? I realy hope that doesn't happen, I hate being an early adopter only to get the shaft.
Don't forget it really doesn't matter if you get this initial update or not, the functionality it brings (nothing you'll notice in day-to-day phone usage) will also be present in the cut-and-paste update due in the next few weeks.
Think of it this way, this first release was a trial run for the update process and not everyone needed to participate. Yes, there was a problem with a certain sub-set of firmware on a certain phone, but Microsoft are learning from that lesson.
if we can not get this update then we can not get thenext update !
it is simple ! some of us are still waiting to see notification of update on our phones !
MS should learnfrom NOKIA how to update simultanously thier phones in countries !
I thought I chime and notify people that I have a Samsung Omnia and plugged my phone in to pc via Zune today and have received notification of update. Updated OS successfully. It looks like Microsoft have released the update with the fix for Samsung handsets. Kudos to Microsoft and my carrier Optus.
It would seem that the update has truly been released for Samsung WP7 devices - Unfortunately, it would also seem there are still people experiencing the problem Already starting to see post/complaints over at the MS Answer site :-(
Unfortunately I just tried the update tonight on my Focus and it's errored out again! :< Please see my blog for the blow by blow details.
As I mentioned, this is either one of two problems IMHO, either Rogers errored in re-releasing without your permission, OR this next re-release is still buggy and not working. I hope you can address this asap!
I just updated my blog. After uninstalling some apps and games, I WAS indeed able to get the update onto the phone! Very cool! An opportunity for some learning still exists though IMHO.
I just updated my Samsun Omnia 7... all works fine!
I am looking forward to the update as well. I wished that we would have direct synchronization with the Windows desktop rather than cloud only options. I would love to synchronization with tasks on the phone. I miss that from my older phone!
Still nothing for HTC Mozart on Orange UK.
To Mahdihaj, that's not a correct statement. Microsoft has already stated, MANY times, that even if a carrier blocks one update they cannot block the one that follows it. So, IF a carrier blocks this pre-update they will NOT be able to block the next one, and THAT one will be cumulative---meaning it WILL have the pre-update code as well. I wouldn't be surprised if that turns out to be a two-stage affair, but Microsoft was quite clear. So, quit being fearful.
It WOULD be nice to know, however, if anyone on AT&T has received this pre-update yet (on ANY phone, not just the Samsung). That way we'd know if they are indeed block the update (or that AT&T hasn't been rolled out as part of the staged schedule).
I have tried 5 times with my Omnia 7 using Zune for the update, the error message is always 800705B4, in fact I have uninstalled a lot of unused apps and make the free space to be about 4.23G and my Windows 7(x64) does have plenty of harddisk space. I am from Singapore and my telco provider is SingTel.
It always seems to timeout at the STEP 7 OF 9: INSTALLING UPDATES. PLEASE WAIT... It waits at the step for about 3min 30 second , then timeout I presume, it will then proceed to reboot the phone and subsequently shows the failed message.
I trusted MS will do a proper testing after last week update failure but failed again the second time, this is not acceptable. I think Microsoft should look at your competency of doing this update seriously and ask why it failed again. Dissapointing!!!
Update just came down on an o2 UK HTC HD7. Install took about 5 minutes, maybe a bit less.
Can not update either (800705B4). Samsung Omnia 7.
I STILL HAVE NOT RECEIVED THE UPDATE AND I LIVE IN THE VIRGIN ISLAND WILL I GET THIS UPDATE.
I have an AT&T Surround in the USA, I have not gotten the pre update so I stopped at the local AT&T corprate store (not an authorized reseller) and they said they have no data on the pre update or on NO-DO. MS needs to start kicking around some carrier butt. At this rate new buyers of the Sprint Arrive will have the update before we do.
Well, I'm an owner of an HD7 through T-Mobile. The only update I have ever seen was one made to my zune software about 3-4 days ago. I hooked up my phone in hopes of receiving one to my HD7, but no luck. Oh well, I still love my phone and the Windows Phone 7 OS, to me, is bad *ss and I cannot wait to see what lies in its future.
With that being said, when should I expect the NoDos or Mango updates? I guess what I'm asking is this.....What update is being rolled out now? The pre-Update Update that is prepariing our phones for future updates? The confusion comes in when MS says that there is an update to be rolled out in the first 2 weeks of March. Is this the NoDos update that is expected?
Just a little confused at the timing of everything. Anyone else have an HD7 through T-Mobile that has received any updates?
This is not the NoDo update, it's just a re-start of the pre-NoDo update that was previously suspended for Samsung Owners. From reading the Windows Answers thread, this "fixed" update hasn't fully resolved Samsugn owners problems with the upgrade - answers.microsoft.com/.../2ae42929-2645-e011-90b6-1cc1de79d2e2
Hey Pete, thanks for the info. I wish MS and the carriers could agree on some dates and let us know when to expect NoDo and Mango.
SO THE UPDATE FOR SAMSUNG PHONES ARE OK NOW WE CAN UPDATE THE PHONES NOW.
Yes, Gunnah - you may retry the update. Just make sure that you have plenty of disk space on your desktop computer before updating. Personally, I wouldn't attempt it with less than 7Gb free space to be on the safe side.
Good luck and please report back (good or bad). Us Samsung owners need all the reassurance we can get!! :D
just 4 days later the MARCH UPDATE is going to be released but me and someone like me do not get the pre-update yet !
i changed my carrier but i doesn't make sense ! i tryed zune on some other computer with different ISP but still no update !
MS should solve it soon !
when we sould wait to see our pre-update ?!!!
mahdihaj. Don't worry. If you don't get the pre-NoDo update before NoDo is released, you can simply update to NoDo (it's a culmulative update). Installing the pre-NoDo won't make any difference at this time to your phone, so you can quite safely not install it. Don't worry, you're not missing anything.
So when is NoDo's supposed to available? Sometime in the first two weeks of March, correct?
I don't know Odd. I remember seeing something about the first 2 weeks of March, and then I see that I read that from your post earlier in the thread. I've not seen anything officialy from Microsoft that indicates a timescale of anything except "early March". I guess that it'll be released when Microsoft feel that it (and they) are fully ready.
staged rollout is a complete disaster. Whoever came up with this idea.. should be FIRED!. Why in the world can't we just hook up the phone to the Zune software and get the update.. it's been 2 weeks I have yet to receive any notification of any update.. and neither have the 8 phones of my friends or family.
That 's what I figured, just wanted to see if you had heard anything official as of yet. Have my fingers crossed that is is soon!
The 2nd update for Samsung Omnia 7 did not work for me! It says that the timer ran out on what it was doing and the error code is 800705b4!
This blog post is much appreciated for keeping us "in the loop". Thanks for that.
I haven't been too worried about the update because I'm not sure what it consists of. The main (only) thing I've heard is the presence of a backup mechanism to be used for the larger update that should be imminent. I saw someone else in this thread ask if the backup could be used for other purposes. I can see the following:
1. A phone gets a warranty replacement. Instead of manually reinstalling the applications, you chould restore from the backup that Zune now will have.
2. Would be a great use for when/if the "approved" SD card list finds its way to approval.
3. If a hard reset is ever needed for anything
4. If you do a remote wipe because you lost your phone and then realize that you just left it somewhere.
to Pete !
tnx . but it is concluded that if the pre update can not be accessable for some of us ! so the main update wont be accessable too ! :(
it is the main reason for being woirried for nex updates !
i hope MS change its proccedure of updating for all of customers !
Yeah, thanks for the transparency guys! Keep us as much posted as you can, best for both sides.
mahdihaj, if you want to beleive that you're excluded from the update, despite being told differently, then that is up to you. I don't yet have an update for my Samsung, but I'm not worried about it.
I'll get the update when it comes through.
Any news on the dates for the NoDo update?
The updated update for my Samsung Focus on Rogers in Canada didn't work. Got the 800705b4 error at step 2 of 2 in the second stage after the first stage's 9 step process finished. The phone is fine but not updated.
@dalydose: Not sure if I totally understand your question, but once a backup has been created by the update process, you can use it to restore your phone any time you like. In the Zune software (with phone connected) go to Settings>Phone>Update.
One thing to note: You can't manually create backups (restore point). Backups are only created during the update process.
@dalydose & Michael Stroh : dalydose is offering quite useful feature suggestion to build upon the first update - good ideas i think. Being a Samsung owning Win Phone 7 enthusiast i'm totally relieved you fixd the update so quickly and looking forward to the extra feature goodness.
Wish you guys would update little and often though instead of huge updates sparsley, i thought when i purchased a Win Phone 7 this was the plan, and you wouldn't be held back by carriers - it damn well should have stayed that way!
BTW - why i must i sign up for another account for these blogs when i've already got a windows live account. MS joined up services - FAIL
My friend and I both have the HD7 (T-Mobile), and have yet to see any notification of any update. I wonder if T-mobile is blocking this patch.
I just saw something over on the Microsoft Answers side from an MVP that worried me slightly. This is in answer to a query from someone who had a carrier branded phone that was unlocked:-
The update is controlled by your Mobile Operator, so I encourage you to speak with Vodafone. Depending on what information they want or can release, hopefully you will speak with someone that can give you some kind of answer as to when it will be coming.</quote>
I was under the impression that carriers could only block the OTA notification of an available update and that Microsoft/Zune actually controlled the update (so people should be able to connect their phone to Zune and check/apply an update regardless of the carrier).
Hi pete !
don't worry . my friends in iran updated their wp7 phones without any notofication of updating from their carrier . Some of the just plug in their phone to computer and check for updat with zune !
But i still waiting to see my update with zune or carrier ! :(
Okay, this pre-update is so sad now that it's almost comical. Some of the message traffic on Microsoft Answers indicates that at about Step 6 there's a driver issue and a timing problem. Apparently, the phone is not recognized by Zune at that point as being "Zune", but rather as another mode. For my Samsung Focus brothers & sisters you probably know there's a way to go into diagnostic mode and reboot the device in other modems (e.g., MODEM to allow tethering). It looks like the update routine is looking for the phone to respond quicker and be in the correct mode. In some cases to a reboot of the phone lets the update pass, but in others it doesn't. I'm always one to give Microsoft the benefit of the doubt, but this is simply too many significant issues. Of course, separately, I'm quit angry with AT&T for what appears to be their intentional holding back of the update. Since this latest error is still on a minority of devices I believe I should be the one deciding if I want to load the update or not. Anyway, at this point I will surprised if we don't see yet another suspension of the update while M$ figures out what they overlooked this time. <sigh>
Guys, there's some interesting discussion regarding Microsoft's update strategy here. Mike, I hope you don't mind me posting the link here from Microsoft Answers, but the answers from the MS MVPs are informative and explain the situation more clearly than I've manage to understand in the past.
@ Pete--Not at all!
@jhu et. al.: Take a look at the link I just posted up top about 800705B4.
Is Microsoft still going to fix the problem or expecting us to follow the workaround to bypass the error 800705b4 reported?
Microsoft, you should really read this post and think about it: wmpoweruser.com/the-pace-of-microsoft
Why MS don't change it's update way?!!
just release update in internet !
carrier should not make decision about give release to customers !
it is us who make decision about get update or not .
MS please attention to our comments !
we are disappointed .