locked
Windows XP Pro - product activation stalls RRS feed

  • Question

  • Hello,

    Please can you help, me I'm trying to activate a valid OEM copy of Windows XP Pro. I purchased & installed this about 2 years ago, but  recently I replaced a failing optical drive. As a result I have been prompted to activate my copy of windows, but when I press the activate icon all I get is a blank pop-up screen. Here is what the WGA diagnostic tool report says:

    Diagnostic Report (1.5.0540.0):
    -----------------------------------------
    WGA Data-->
    Genuine Validation Status: Not Activated
    Windows Product Key: *****-*****- ( sorry, thats private)
    Windows Product Key Hash: P0kt0lCD/1RchfC/peKMzHOSHHc=
    Windows Product ID: ( sorry, thats private)
    Windows Product ID Type: 3
    Windows License Type: COA/Sysem Builder
    Windows OS version: 5.1.2600.2.00010100.2.0.pro
    Download Center code: HMMMHC7
    ID: 3e5a9ffd-70f9-4eab-a377-70bdf2505774
    Is Admin: Yes
    AutoDial: No
    Registry: 0x0
    WGA Version: Registered, 1.5.540.0
    Signature Type: Microsoft
    Validation Diagnostic:

    System Scan Data-->
    Scan: Complete
    Cryptography: Complete

    Notifications Data-->
    Cached Result: 1
    Cache refresh Interval: 546 seconds
    Extended notification delay(non-genuine): 14
    Extended notification delay(un-activated): 31
    All disabled: 0
    Reminder reduced: 0
    File Exists: Yes
    Version: 1.5.540.0
    Signatue Type: Microsoft

    OGA Data-->
    Office Status: 109
    Office Diagnostics:

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>3e5a9ffd-70f9-4eab-a377-70bdf2505774</UGUID><Version>1.5.0540.0</Version><OS>5.1.2600.2.00010100.2.0.pro</OS><PKey>*****-*****-*****-*****-MWKGY</PKey><PID>( sorry, thats private)
    </PID><PIDType>3</PIDType><SID>S-1-5-21-1935655697-1202660629-1343024091</SID><SYSTEM><Manufacturer>System Manufacturer</Manufacturer><Model>System Name</Model></SYSTEM><BIOS><Manufacturer>Award Software, Inc.</Manufacturer><Version>ASUS A7V600-X ACPI BIOS Revision 1009</Version><SMBIOSVersion major="2" minor="3"/><Date>20050628000000.000000+000</Date></BIOS><HWID>7D353B8F01842259</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone></MachineData>   <Software><Office><Result>109</Result><Products/></Office></Software></GenuineResults> 

     

    Sunday, July 2, 2006 10:37 PM

Answers

  • Try the following:

    1. Reboot your computer into "Safe Mode".

    2. Go to Start > Run and type: %systemroot%\system32 then press the Enter key.

    3. Locate these two files: wpa.dbl and wpa.bak

    4. Rename the wpa.dbl file to wpaold.dbl and wpa.bak to wpaold.bak

    5. Reboot your computer into Normal mode.

    This will force activation on the following boot, but should remove the message that you are already activated message.

    Sometimes if these files get corrupted, they can cause this type of problem.

    Sunday, July 2, 2006 10:54 PM
    Moderator

All replies

  • Try the following:

    1. Reboot your computer into "Safe Mode".

    2. Go to Start > Run and type: %systemroot%\system32 then press the Enter key.

    3. Locate these two files: wpa.dbl and wpa.bak

    4. Rename the wpa.dbl file to wpaold.dbl and wpa.bak to wpaold.bak

    5. Reboot your computer into Normal mode.

    This will force activation on the following boot, but should remove the message that you are already activated message.

    Sometimes if these files get corrupted, they can cause this type of problem.

    Sunday, July 2, 2006 10:54 PM
    Moderator
  • What would the process be for same symptoms on Windows Server 2003 for Small Business?
    Saturday, December 9, 2006 3:15 PM