Windows Update issues and how to address them
Category Windows Update
A colleague sent me the following, I thought it was blog worthy.
A couple months ago I was testing some code that I had compiled w/ the new MSDEV 8.0. During an attempt to install an ActiveX my machine hung hard. I had to cold recycle the machine. The same thing happen a day later on a different machine. I slowly began to realize over the next two days that something had hosed part of my registry. Suddenly, my windows was no longer an Authentic Copy of windows. I could not even LOGIN to the affected boxes until I “REACTIVATE” my windows. Yet, there was no way to reactivate because windows shuts down immediately after attempting to login to the machine.
Upon researching I found that there are MANY problems with this “Genuine Windows” technology from MS. I started a very long cycle of using Windows XP Recovery (booting from the Install disk) to fix my machines. I got the machines running again but continued suffering may other problems over the last two months. The first major problem was that Windows Update would not run successfully. After successfully Activating my Windows XP again, Windows Update complained that my windows was not Activated. I found a new web site at Microsoft which resolved this problem:
http://www.microsoft.com/genuine/diag
After running these tools all my configuration problems were resolved, I was able to reactivate both Windows and Office such that Windows Update would run.
Subsequent to this I was able to run Windows Update but it would fail to install after a successful download. Then I found the following article that properly describes the cause of these problems:
http://support.microsoft.com/kb/943144
I wanted to pass these along because these are both VERY common, frequent, issues that end users experience with Windows XP and the Genuine Windows Authentication mechanism.
This saved me having to completely rebuild my systems from scratch
A colleague sent me the following, I thought it was blog worthy.
A couple months ago I was testing some code that I had compiled w/ the new MSDEV 8.0. During an attempt to install an ActiveX my machine hung hard. I had to cold recycle the machine. The same thing happen a day later on a different machine. I slowly began to realize over the next two days that something had hosed part of my registry. Suddenly, my windows was no longer an Authentic Copy of windows. I could not even LOGIN to the affected boxes until I “REACTIVATE” my windows. Yet, there was no way to reactivate because windows shuts down immediately after attempting to login to the machine.
Upon researching I found that there are MANY problems with this “Genuine Windows” technology from MS. I started a very long cycle of using Windows XP Recovery (booting from the Install disk) to fix my machines. I got the machines running again but continued suffering may other problems over the last two months. The first major problem was that Windows Update would not run successfully. After successfully Activating my Windows XP again, Windows Update complained that my windows was not Activated. I found a new web site at Microsoft which resolved this problem:
http://www.microsoft.com/genuine/diag
After running these tools all my configuration problems were resolved, I was able to reactivate both Windows and Office such that Windows Update would run.
Subsequent to this I was able to run Windows Update but it would fail to install after a successful download. Then I found the following article that properly describes the cause of these problems:
http://support.microsoft.com/kb/943144
I wanted to pass these along because these are both VERY common, frequent, issues that end users experience with Windows XP and the Genuine Windows Authentication mechanism.
This saved me having to completely rebuild my systems from scratch
| Permalink | 
Comments
Posted by Pedro Quaresma At 04:37:23 AM On 05/09/2008 | - Website - |
Tripp
Posted by Tripp At 11:49:57 PM On 05/09/2008 | - Website - |