I asked for a solution to this problem with regard to Windows XP Mode in Windows Virtual PC at the TechNet forums, and basically I got nothing. The same problem exists with Windows XP Pro itself. So, I will ask this question once more:After installing all of the automatic updates and activating Internet Explorer 8 for the first time, and activating Windows Update, I followed the instructions for installing all of the components for Microsoft Update and ActiveX, and arrive at the following
screen:
http://screenshots.leeindy.com/WindowsUpdate/windows_update_1.gif
That's where the fun stops. I figured it would be less than 30 seconds before the process went straight to the next step. But instead, IE8 stalls for anywhere between 8 and 9 minutes before it arrives at this screen:
http://www.udel.edu/topics/windowsxp/images05/6express.jpg
My first thought is that a rogue program from the updates is interfering with Microsoft Update. It does no good to close IE8 and reopen it, and it certainly does no good to refresh IE8, because the sooner I reactivate Microsoft Update, I have to wait
another 8 to 9 minutes before the Welcome screen pops up. If I want to stop the process during this long wait, I have to activate the Task Manager and terminate it from there.
Are there any known updates that could cause Microsoft Update to stall like this? Is there a solution that will not force me to abandon IE8 (which I consider absolutely unacceptable either the OS works as it should or it is a tainted item if one of its
components is faulty)?
Please be advised, I tried the Microsoft Fix-It program and I tried a procedure that required clearing the
SoftwareDistribution folder. No good. My initial conclusion is that one of Microsoft's ActiveX components was recently upgraded (because this problem with Microsoft Update didn't exist until nearly 2 months ago), and the upgraded ActiveX component
is corrupted or faulty. How can I find out if the ActiveX component is faulty, and where do I go to roll back to the previous component, if it should turn out that an ActiveX upgrade is the problem?Please be advised yet again, that every time I activate Microsoft Update, I have to wait 8 to 9 minutes until the
Welcome screen pops up. And let me say again, nobody at the TechNet forums has a solution.
View this thread
screen:
http://screenshots.leeindy.com/WindowsUpdate/windows_update_1.gif
That's where the fun stops. I figured it would be less than 30 seconds before the process went straight to the next step. But instead, IE8 stalls for anywhere between 8 and 9 minutes before it arrives at this screen:
http://www.udel.edu/topics/windowsxp/images05/6express.jpg
My first thought is that a rogue program from the updates is interfering with Microsoft Update. It does no good to close IE8 and reopen it, and it certainly does no good to refresh IE8, because the sooner I reactivate Microsoft Update, I have to wait
another 8 to 9 minutes before the Welcome screen pops up. If I want to stop the process during this long wait, I have to activate the Task Manager and terminate it from there.
Are there any known updates that could cause Microsoft Update to stall like this? Is there a solution that will not force me to abandon IE8 (which I consider absolutely unacceptable either the OS works as it should or it is a tainted item if one of its
components is faulty)?
Please be advised, I tried the Microsoft Fix-It program and I tried a procedure that required clearing the
SoftwareDistribution folder. No good. My initial conclusion is that one of Microsoft's ActiveX components was recently upgraded (because this problem with Microsoft Update didn't exist until nearly 2 months ago), and the upgraded ActiveX component
is corrupted or faulty. How can I find out if the ActiveX component is faulty, and where do I go to roll back to the previous component, if it should turn out that an ActiveX upgrade is the problem?Please be advised yet again, that every time I activate Microsoft Update, I have to wait 8 to 9 minutes until the
Welcome screen pops up. And let me say again, nobody at the TechNet forums has a solution.
View this thread