Using windows update in WM6.1
- hi, recently i tried using the windows update in my HTC touch diamond 2, but each time i tried to update, it will always prompt me update unsuccessful. Is there anything wrong with my phone or is there something wrong with the connection? I have tried using WiFi connection, direct connection to my computer and thru my 3G network but all the above have been unsuccessful. Can someone please tell me what is the problem??
Answers
- I believe this is a univeral problem. I read a post inquiring about the same issue dealing with Verizon phones with WM not updating. I'm also having that issue. I think it has something to do with the windows mobile update server. An update might be coming soon, although i've had this problem for a while.
- Marked As Answer bySeanwei Tuesday, July 14, 2009 2:54 PM
Thanks for your input!!
Joe, Windows update did work for quite a while on my HTC Touch Pro (Bell Canada). I have received at least one update through the phone.....but it has stopped working probably within the last month or so. It does prompt me with the same error code....check connections, check time and date etc....
Sorry, I missed that.
I bought my phone only a week or so ago, unlocked, from an independent PDA retailer.
The first thing I wanted to do (as with every other gadget I buy) was to update the OS via wi-fi and internet connection. But it did not work. HTC support told me that I have to wait untill a ROM update is available for my phone on HTC Australia website. I will then be able to download the new ROM file and install it on my phone.
So for me, Windows Update is a phantom which will never work.
Joe- Marked As Answer bySeanwei Tuesday, July 21, 2009 3:31 PM
Thanks for your question on Windows Update. Today, on retail devices updates are reserved for critical updates. Think of this as something that closes a security vulnerability. The reason for this is that Mobile Operators prefer it this way, while they figure out the right way to tackle the problems that updating a device can prevent. Three big questions around sending patches down, is who tests the patches, what does the extra volume do to the Mobile Operator's network performance, who approves the patches - Microsoft? the Mobile Operator, the OEM? And what happens if the OEM patch, or a Microsoft patch turns your device into a brick. I don't have to bet the house on it, but I'm pretty sure you'd be ahhh, upset with the Mobile Operator, the OEM, and Microsoft, and none of us want that! We are working with partners to figure out the best way to use Windows Update, and what are the best types of updaes to push down to device owners.
The Windows Update functionality does work. We have used this to update devices for internal betas in the past, and it is very cool.
Regarding using Windows Update to update from one OS to the next version...Mobile Operators and OEMs work toether to decide if they are going to updat a particular device, and if it makes sense for them to allocate the resources to accomplish the update, or if it makes more sense to allocate the resources to release a new device. To do the update, the OEM has to bring the new OS up on the device, and this means making any changes to the drivers or other special sauce that they've used. Updating any programs that need to be updated, and testing all of the pieces together. Once this is done- they figure out the best way to provide you the update. If the constraints around Windows Update are lifted, then it is possible that you will see updates to consumers take place in this fashion.
Hope this helps- Proposed As Answer by2GrokMobileMSFTFriday, July 31, 2009 12:09 PM
- Marked As Answer byMaryAliceCMSFT, OwnerMonday, August 03, 2009 3:24 PM
All Replies
- I believe this is a univeral problem. I read a post inquiring about the same issue dealing with Verizon phones with WM not updating. I'm also having that issue. I think it has something to do with the windows mobile update server. An update might be coming soon, although i've had this problem for a while.
- Marked As Answer bySeanwei Tuesday, July 14, 2009 2:54 PM
- I am having the same issue with my Verizon Wireless HTC XV6900. It just seemed to start happening this week? Any update. Please let me know.
- I am also having the same problem with my Bell HTC Touch Pro....you are not alone.
- I've asked the team to investigate and will let you know if we have any further information.
Thank you from the Microsoft Windows Mobile Team
http://www.WindowsMobile.com/TotalAccess - I think windows update in HTC phones is a phantom to fill the program menu.
I believe the only way to update WM 6.1 on HTC phones is to download a ROM update from HTC or from your provider, if and when they have it for your particular model and in your particular country.
But I am new to WM, and will gladly be corrected.
Joe - Thanks for your input!!
Joe, Windows update did work for quite a while on my HTC Touch Pro (Bell Canada). I have received at least one update through the phone.....but it has stopped working probably within the last month or so. It does prompt me with the same error code....check connections, check time and date etc.... Thanks for your input!!
Joe, Windows update did work for quite a while on my HTC Touch Pro (Bell Canada). I have received at least one update through the phone.....but it has stopped working probably within the last month or so. It does prompt me with the same error code....check connections, check time and date etc....
Sorry, I missed that.
I bought my phone only a week or so ago, unlocked, from an independent PDA retailer.
The first thing I wanted to do (as with every other gadget I buy) was to update the OS via wi-fi and internet connection. But it did not work. HTC support told me that I have to wait untill a ROM update is available for my phone on HTC Australia website. I will then be able to download the new ROM file and install it on my phone.
So for me, Windows Update is a phantom which will never work.
Joe- Marked As Answer bySeanwei Tuesday, July 21, 2009 3:31 PM
- Tha same has happened to me but with a slight difference. It was working before installing a rom update and after that Kaput. I have a Touch pro P4600 (aka at&t Fuze). I think it may have something to do with a string or proxy adress that windows mobile uses to locate the server. I'm still doing research on this matter because what's the use of having it on the unit if it doesn't work. It doesn't make sense.
Tha same has happened to me but with a slight difference. It was working before installing a rom update and after that Kaput. I have a Touch pro P4600 (aka at&t Fuze). I think it may have something to do with a string or proxy adress that windows mobile uses to locate the server. I'm still doing research on this matter because what's the use of having it on the unit if it doesn't work. It doesn't make sense.
The same happened and continues to happen to me. I have a HP Data Messenger, and I am connected to the Internet through my pc and my company LAN ADSL connection or my home ADSL connection.
The message I receive is always the same: Connection to the update server not available. Verify data connection settings and that device date and time are correct. ... Last check not completed ... result code 80072ee7. (I translated all the messages from my language Italian, so excuse for my English not so accurate).
I think that on the Mobile 6.1 version of Internet Explorer is missing the option to manage zone securities so the connection to Windows Update (Mobile) server is blocked. Or this is only my impression?
I never had the possibilities to Update Windows on my mobile device even with wireless data connection.
Is there anyone that can solve the mistery?
Thanks to everyone had the patience to read me ... and all the other...Thanks for your question on Windows Update. Today, on retail devices updates are reserved for critical updates. Think of this as something that closes a security vulnerability. The reason for this is that Mobile Operators prefer it this way, while they figure out the right way to tackle the problems that updating a device can prevent. Three big questions around sending patches down, is who tests the patches, what does the extra volume do to the Mobile Operator's network performance, who approves the patches - Microsoft? the Mobile Operator, the OEM? And what happens if the OEM patch, or a Microsoft patch turns your device into a brick. I don't have to bet the house on it, but I'm pretty sure you'd be ahhh, upset with the Mobile Operator, the OEM, and Microsoft, and none of us want that! We are working with partners to figure out the best way to use Windows Update, and what are the best types of updaes to push down to device owners.
The Windows Update functionality does work. We have used this to update devices for internal betas in the past, and it is very cool.
Regarding using Windows Update to update from one OS to the next version...Mobile Operators and OEMs work toether to decide if they are going to updat a particular device, and if it makes sense for them to allocate the resources to accomplish the update, or if it makes more sense to allocate the resources to release a new device. To do the update, the OEM has to bring the new OS up on the device, and this means making any changes to the drivers or other special sauce that they've used. Updating any programs that need to be updated, and testing all of the pieces together. Once this is done- they figure out the best way to provide you the update. If the constraints around Windows Update are lifted, then it is possible that you will see updates to consumers take place in this fashion.
Hope this helps- Proposed As Answer by2GrokMobileMSFTFriday, July 31, 2009 12:09 PM
- Marked As Answer byMaryAliceCMSFT, OwnerMonday, August 03, 2009 3:24 PM
- How will Microsft know if my smartphone has the lates critical updates on it if it is unable to connect to Windows Update. Mine has never connected since it was bought 6 months ago, and I'm sure there have been critical patches to update since then, i.e. SMS hack. This is pretty poor from Microsoft I think.
- TO the 2 MSFT folks.. the answer tagged is NOT an answer, but to tell us it works for you and is COOL, but we cannot expect any functionality or predictability as a consumer? Can we try this question again:
1) For upgrade by major version (e.g. 6 to 6.1), phones require a ROM upgrade and this is a provider to provider decision. Windows Mobile is not meant for major upgrades, correct?
2) For upgrades within a version of WM, and for upgrades of MSFT software such as explorer, office, outlook etc, this funcationality IS intended to work, correct or not?
3) If for some COOL reason the intended fucntion of Windows Mobile is NOT working for us ordinary users ( I really don;t care what happens inside your development shop), then what is the point? If we cannot use it to check the upgrade of MSFT software within major versions releases, then what are we supposed to do to even KNOW if we should?
I appreciate any pragmatic and clear answer. What should we expect, what is intended and how is it supposed to help us, and what is really possible today?
Thanks - I'm not an MSFT person, but, I'll take a stab at it.
1) Correct, although it may be capable, it is not necessarily meant for any upgrades, just hotfixes.
2) Yes, but, I don't think any updates will every show up for explorer, word, excel, etc. unless the update fixes a security hole.
3) Keep it on update automatically. If a critical updates becomes available through WU then you'll get it automatically.
Think of this as something that closes a security vulnerability, not a method to get the latest version of software that isn't even updated that often.
If your device is working as intended without any security holes, there is no real benefit for a cell provider to constantly be pushing or ever push out new program or program updates that may infact break your device's functionality.
So, basically, there is an update fuction that is disabled due to the fact that there doesn't seem to be any security holes in WM 6.1, atm. This may change and if so lets hope all the parties involved can get together and release a critical update to us before its too late. - At a minimum, if the functionality has been blocked or disabled, we should not get the message stating "connection to the update server is not available." I then think something is wrong with my phone of 3G connection. Then I go through all types of hoops, trying to get this to work, such as changing the GPRS settings, proxy settings, or other actions.
At least tell us that this service has been discontinued, temporarily or otherwise. then
In the world of XP/Vista, we are told to run the Windows Update process months, if not more frequently than than. I have tried doing that with the OS on my phone, because I know how important this is.
I spent two months trying to get this to work, and now I find out that it was all for nothing. What a waste. I'm using Blackjack with WM6. I just noticed that the auto-update was getting errors last week, (mid-August). I've seen the update function complete successfully even with now update availible. It just says "No update availible", not "unable to connect". What's up? Is microsoft rejecting devices for update?
TO the 2 MSFT folks.. the answer tagged is NOT an answer, but to tell us it works for you and is COOL, but we cannot expect any functionality or predictability as a consumer? Can we try this question again:
Weel said ! The answers given by the MSFT folks are very diplomatic but not consumer centric and thats what the MS is famous or rather infamous about !! right ?
1) For upgrade by major version (e.g. 6 to 6.1), phones require a ROM upgrade and this is a provider to provider decision. Windows Mobile is not meant for major upgrades, correct?
2) For upgrades within a version of WM, and for upgrades of MSFT software such as explorer, office, outlook etc, this funcationality IS intended to work, correct or not?
3) If for some COOL reason the intended fucntion of Windows Mobile is NOT working for us ordinary users ( I really don;t care what happens inside your development shop), then what is the point? If we cannot use it to check the upgrade of MSFT software within major versions releases, then what are we supposed to do to even KNOW if we should?
I appreciate any pragmatic and clear answer. What should we expect, what is intended and how is it supposed to help us, and what is really possible today?
Thanks- Hi Mary, Are there any news? I have a E-ten Glofiish X900. Same problem when trying to update and same error msg. OS is 6.1 WWE. Tried to phone Irish HQ first; that was a big mistake. They where not helpful at all. I already regret the purchase. Guar ** This was written on an openSuSE 11.0 Linux in a Firefox 3.5 ;-) **
- Have to agree with Bryan, the "Answers" are anything but.
- If "Windows Update" on mobile devices only works for Redmond internal betas, it's beta software and DOESN'T belong on my device.
- If "Windows Update" is reserved for critical updates, then the software should say "No critical updates available.", not "Connection to update server not available"
- The message "Check your data connections and ensure the device date and time are correct" implies that there is something I, as a consumer who has a choice whether to ever purchase another mobile device with an MS O/S, can do to establish a connection. Misleading if the intent is only to drop critial updates when the Big Three players agree something bad enough is going to happen that they can't avoid the issue.
It will be interesting to see if Motorola/Verizon/Google have similar update issues with Droid ... - Yep - I'm another sucker that's just wasted a few hours trying to get Windows Update working on my WM6.1 phone.
Silly me - I thought "Check your data connections and ensure the device date and time are correct" meant that I should check my data connections and ensure the date & time were correct on my device - I should have realised that it meant there were no critical updates available.
I've no problem with the strategy/approach with Windows update for emergency/security patches but c'mon you collective bunch o' jokers - fix the "error" message and stop more "currently WM6" people wasting their time chasing red herrings all because of a bogus error message.
