I'm running version 4.0.3848 of Parallels under MacOS 10.6.1 (Snow Leopard) with Windows XP as my VM. I am unable to get Windows Update to work under XP. This is the same problem that has been reported elsewhere, but all of the suggestions that I have been able to find here and elsewhere do not work for me. This problem also existed under at least one earlier 4.0.x version of Parallels under MacOS 10.6.1. Whenever I try to access Windows Update, I get sent to http://windowsupdate.microsoft.com in IE7, and then after 30-60 seconds of waiting, I get a page that states "Internet Explorer cannot display the webpage". This is under Bridged Networking. I haven't been able to get any internet accesses to work under Shared Networking. Everything else works fine under XP: I can get to all other web pages that I have tried, and I can do it under IE7, Firefox, Chrome, Opera, and Safari. I can ssh to various sites, and my email client works. Also, Windows Update used to work fine in 4.0.x Parallels under MacOS 10.5.x. It therefore seems like it might be related to Snow Leopard. I've seen a number of discussions about this problem on the net, but some are contradictory of others, and some are unclear. Therefore, I don't know what to do in order to get Windows Update to work for my setup. Can anyone point me to the definitive docs that explain how to get Windows Update working for my version of Parallels and Windows XP? Thank you very much, in advance.
Resolved? Did you ever resolve this problem. I'm currently having the same issue, only major difference is I'm using Parallels 6.
Solution http://answers.microsoft.com/en-us/...cessible/08dce679-496d-43f4-a4b5-bb467800bb90 The second solution solved my issues: Re-register the windows installer Click Start, open the run box (windows key +R) Type msiexec.exe /unreg and click ok. If you receive a confirmation message, click OK again. Click Start, open the run box (windows key +R) Type msiexec /regserver and click ok. If you receive a confirmation message, click OK again. Try to install the application and see if the issue persists. If you still get the error then try next method.
