FIXED Widowx XP update problem
I've refurbished an HP dv1000 laptop. (Short version is I installed a new screen picked ip at a very good price on Ebay.) I wiped the drive (recovery partition was gone) and installed XP pro from a disk I had using the XP pro ser number on the back of the machine which was accepted during install.
I installed SP3 and drivers from HP web site. Machine runs beautifully. However...
When I go to install updates it wants to verify that I have a legit copy of Windows. I let it do that and it goes to a blank IE page with an address that is about a mile long and just sits there. It's like I'm some kind of endless loop.
Haven't seen this before. Any help appreciated. If you need further details LMK and I'll post 'em.
Doing some searching I found and tried this:
1. Click the Start button, then click “Run”
2. Type in “iexplore http://go.microsoft.com/fwlink/?LinkID=39204” then click ‘OK’. You will be prompted to download “LegitCheckControl.cab”.
3. Choose Open. Once this completes, a window will open showing two files, LegitCheckControl.dll and LegitCheckControl.inf. Leave this window open for now.
4. Click the Start button, then click “Run”
5. Type in “system32”, then click ‘OK’. (If you are running Windows XP, you may need to click “show files” to allow access to this system directory.)
6. Drag the LegitCheckControl.dll file from the window that was open into the system32 directory. If you are prompted to overwrite a file, choose ‘Yes’ to overwrite any existing file. (If you are running Vista, you may be prompted to provide administrator permission to complete the action. If so, press “Continue” and allow it.)
7. Click the Start button, then click “Run”
8. Type “regsvr32 LegitCheckControl.dll”, and then click ‘OK’.
9. You should see a dialog saying “DllRegisterServer in LegitCheckControl.dll succeeded.”
It "succeeded" but didn't help. Then I found this MS site:
http://www.microsoft.com/genuine/diag/
This did work. Seems it was a clock issue (CMOS date had wrong month) and maybe a scripting issue. I'm really not sure of the scripting issue but followed instructions and fixed that.
All is well. The MS site seems to be a good catch to figure this one out.
Thanks to both for your input.
I've refurbished an HP dv1000 laptop. (Short version is I installed a new screen picked ip at a very good price on Ebay.) I wiped the drive (recovery partition was gone) and installed XP pro from a disk I had using the XP pro ser number on the back of the machine which was accepted during install.
I installed SP3 and drivers from HP web site. Machine runs beautifully. However...
When I go to install updates it wants to verify that I have a legit copy of Windows. I let it do that and it goes to a blank IE page with an address that is about a mile long and just sits there. It's like I'm some kind of endless loop.

Haven't seen this before. Any help appreciated. If you need further details LMK and I'll post 'em.
Doing some searching I found and tried this:
1. Click the Start button, then click “Run”
2. Type in “iexplore http://go.microsoft.com/fwlink/?LinkID=39204” then click ‘OK’. You will be prompted to download “LegitCheckControl.cab”.
3. Choose Open. Once this completes, a window will open showing two files, LegitCheckControl.dll and LegitCheckControl.inf. Leave this window open for now.
4. Click the Start button, then click “Run”
5. Type in “system32”, then click ‘OK’. (If you are running Windows XP, you may need to click “show files” to allow access to this system directory.)
6. Drag the LegitCheckControl.dll file from the window that was open into the system32 directory. If you are prompted to overwrite a file, choose ‘Yes’ to overwrite any existing file. (If you are running Vista, you may be prompted to provide administrator permission to complete the action. If so, press “Continue” and allow it.)
7. Click the Start button, then click “Run”
8. Type “regsvr32 LegitCheckControl.dll”, and then click ‘OK’.
9. You should see a dialog saying “DllRegisterServer in LegitCheckControl.dll succeeded.”
It "succeeded" but didn't help. Then I found this MS site:
http://www.microsoft.com/genuine/diag/
This did work. Seems it was a clock issue (CMOS date had wrong month) and maybe a scripting issue. I'm really not sure of the scripting issue but followed instructions and fixed that.
All is well. The MS site seems to be a good catch to figure this one out.
Thanks to both for your input.
Last edited: