locked
Windows XP Home won't activate with messages 24579 and 28673 RRS feed

  • Question

  • Hello,

    I work in a computer workshop and I've been having this problem in 3 or 4 PCs by now.

    I can't activate Windows XP Homes, and gives messages 24579 and 28673.
    In c:\windows\setuplog.txt I can find this:

    12/21/2011 11:17:59.890,d:\xpsp\base\ntsetup\oobe\msobmain\msobmain.cpp,6739,,m_pLicenseAgent->AsyncProcessHandshakeRequest() failed.  Error = 24579

    It does activate through phone, but I would like to know, why can't I activate them through internet? :\

    [Edit] I said about HTTP 403 but it seems it happens even when it activates (saw that on another computer, this still fails to activate)

    Wednesday, December 21, 2011 10:33 AM

Answers

  • As of today it's working alright... Without any changes.

    Last week I couldn't activate any XP Home, deployed via image cloning or clean install with an original OEM disc, and now I've activated 3 of them flawlessly.

    One more for the x-files :!

    Monday, December 26, 2011 1:06 PM

All replies

  • "Pablo Navarro" wrote in message news:1255cad8-bd59-49f4-a53a-a2a172437b20...

    Hello,

    I work in a computer workshop and I've been having this problem in 3 or 4 PCs by now.

    I can't activate Windows XP Homes, and gives messages 24579 and 28673.
    In c:\windows\setuplog.txt I can find this:

     

    12/21/2011 11:17:52.046,d:\xpsp\base\ntsetup\oobe\msobcomm\connmgr.cpp,1480,,HTTP status code from WPA HTTP server 403
    12/21/2011 11:17:59.890,d:\xpsp\base\ntsetup\oobe\msobmain\msobmain.cpp,6739,,m_pLicenseAgent->AsyncProcessHandshakeRequest() failed.  Error = 24579

    It does activate through phone, but I would like to know, why can't I activate them through internet? :\

    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
      - **in your own thread**, please
     
    Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine, but do NOT quote the Key on the sticker!
    http://www.microsoft.com/howtotell/content.aspx?pg=coa

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, December 21, 2011 11:43 AM
    Moderator
  • There it goes:

     

    Diagnostic Report (1.9.0027.0):
    
    -----------------------------------------
    
    Windows Validation Data-->
    
    Validation Status: Not Activated
    
    Validation Code: 1
    
    Cached Validation Code: N/A
    
    Windows Product Key: *****-*****-BDDBQ-69Y49-HJMGQ
    
    Windows Product Key Hash: V9FfLF2agFuKLI7NWvoErsnRI9M=
    
    Windows Product ID: 76459-OEM-2167471-96341
    
    Windows Product ID Type: 3
    
    Windows License Type: OEM System Builder
    
    Windows OS version: 5.1.2600.2.00010300.3.0.hom
    
    ID: {C23634D0-5FC7-4E07-943F-387AE2C5C63D}(1)
    
    Is Admin: Yes
    
    TestCab: 0x0
    
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    
    Signed By: Microsoft
    
    Product Name: N/A
    
    Architecture: N/A
    
    Build lab: N/A
    
    TTS Error: N/A
    
    Validation Diagnostic: 025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3
    
    Resolution Status: N/A
    
    
    
    Vista WgaER Data-->
    
    ThreatID(s): N/A
    
    Version: N/A
    
    
    
    Windows XP Notifications Data-->
    
    Cached Result: N/A, hr = 0x80070002
    
    File Exists: No
    
    Version: N/A, hr = 0x80070002
    
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    
    
    
    OGA Notifications Data-->
    
    Cached Result: N/A, hr = 0x80070002
    
    Version: N/A, hr = 0x80070002
    
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    
    
    OGA Data-->
    
    Office Status: 109 N/A
    
    OGA Version: N/A, 0x80070002
    
    Signed By: N/A, hr = 0x80070002
    
    Office Diagnostics: B4D0AA8B-543-80070002_025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3
    
    
    
    Browser Data-->
    
    Proxy settings: N/A
    
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    
    Default Browser: C:\Archivos de programa\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>{C23634D0-5FC7-4E07-943F-387AE2C5C63D}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010300.3.0.hom</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-HJMGQ</PKey><PID>76459-OEM-2167471-96341</PID><PIDType>3</PIDType><SID>S-1-5-21-3869434499-1740671700-1788819588</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>ASUS M2A-VM ACPI BIOS Revision 2302</Version><SMBIOSVersion major="2" minor="4"/><Date>20090205000000.000000+000</Date></BIOS><HWID>BB41371701842078</HWID><UserLCID>0C0A</UserLCID><SystemLCID>0C0A</SystemLCID><TimeZone>Hora estándar romance(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    
    
    
    Licensing Data-->
    
    N/A
    
    
    
    Windows Activation Technologies-->
    
    N/A
    
    
    
    HWID Data-->
    
    N/A
    
    
    
    OEM Activation 1.0 Data-->
    
    BIOS string matches: no
    
    Marker string from BIOS: N/A
    
    Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005
    
    
    
    OEM Activation 2.0 Data-->
    
    N/A
    
    

    The PK in the COA sticker is the same that the one that mgdiag reports, and it is also Windows XP Home

    Wednesday, December 21, 2011 11:51 AM
  • "Pablo Navarro" wrote in message news:f5d6b4aa-8834-4bbb-aa81-0072dc94e68f...

    There it goes:

     

    Diagnostic Report (1.9.0027.0):
    
    -----------------------------------------
    
    Windows Validation Data-->
    
    Validation Status: Not Activated
    
    Validation Code: 1
    
    Cached Validation Code: N/A
    
    Windows Product Key: *****-*****-BDDBQ-69Y49-HJMGQ
    
    Windows Product Key Hash: V9FfLF2agFuKLI7NWvoErsnRI9M=
    
    Windows Product ID: 76459-OEM-2167471-96341
    
    Windows Product ID Type: 3
    
    Windows License Type: OEM System Builder
    
    Windows OS version: 5.1.2600.2.00010300.3.0.hom
    
    
    
    File Scan Data-->
    
    
    
    Other data-->
    
    SYSTEM><Manufacturer>System manufacturer</Manufacturer>
    <Model>System Product Name</Model></SYSTEM>
    <BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer>
    <Version>ASUS M2A-VM ACPI BIOS Revision 2302</Version>
    <SMBIOSVersion major="2" minor="4"/>
    <Date>20090205000000.000000+000</Date></BIOS>
     
    I suspect that the issue is with your installation disk  - is it a slipstreamed disk? If so, was it generated from an XP system, or from Vista/WIn7?
     
    There are reports that slipstreamed disks generated from a WIn6.x system will cause problems.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, December 21, 2011 2:57 PM
    Moderator
  • It was cloned and it's HAL was changed after, but it's a NT 5.x, not 6.x, and it's been working and activating for a month at least, until now.

    Wednesday, December 21, 2011 3:27 PM
  • "Pablo Navarro" wrote in message news:05dc547f-4c3e-4026-a6fc-df9ce459b3aa...

    It was cloned and it's HAL was changed after, but it's a NT 5.x, not 6.x, and it's been working and activating for a month at least, until now.

    Then I suspect that’s the problem – the Activation/Validation servers are seeing it as a new PC with the same Key – which will eventually be blocked if too many attempts are made to activate it, unless you use the proper procedure for the installation, by using the OPK, so that the Key is removed before the install, and then inserted on first use.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, December 21, 2011 3:32 PM
    Moderator
  • Same thing started happening for me yesterday, and still today. :-/ It activated no problem like 3 times during the 2 days before that (I've been experimenting with customizing my install disc further). And then when I was ready to format/install for the final time (for now :^)), it fails. :-(  I guess there was no reason for me to activate during those temp installs, but it's just a habit. But as far as I know, activating on the same hardware many times is OK (it's a laptop and config has never changed).

    I activated it probably almost 20 times during the summer when I was messing with stuff last, including several times over a few days... One time it was not working (online) for a few hours back then, but other than that, fine.

    I didn't attempt the phone method yet, and really don't want to...  Is it automated, Pablo, Noel?

    I guess soon I'll have to save an image of my desktop and reinstall here with its key and see what happens. :-/

    This activation stuff really sucks at times like this!

    Wednesday, December 21, 2011 4:02 PM
  • If you have activated Windows numerous times during a short period of timje, you'll now need to "activate by phone" and speak with a product activation representative which takes less than 10 minutes.
    Carey Frisch
    Wednesday, December 21, 2011 4:50 PM
    Moderator
  • I have to activate many copies of Windows XP, vista and 7, almost on each computer I get full of viruses to be fixed... And each one with its own product key. It's just too much time lost if I need to call everytime for this thing.

    Is there any way to know what does those "detail codes" mean?? :(

    Wednesday, December 21, 2011 5:07 PM
  • Also I've tried from an original CD and it happens the same :\
    Wednesday, December 21, 2011 6:45 PM
  • As of today it's working alright... Without any changes.

    Last week I couldn't activate any XP Home, deployed via image cloning or clean install with an original OEM disc, and now I've activated 3 of them flawlessly.

    One more for the x-files :!

    Monday, December 26, 2011 1:06 PM
  • You may consider this "Answered" but I don't.

    I've been a few days wasting time by activating Windows by phone and I can't get an answer about what are the meaning of those detail codes, and I won't know how to solve it the next time it happens .

    Monday, December 26, 2011 5:35 PM
  • What happens if you attempt to validate a system that fails to activate?

    Next time you get such a system, please try that, and then post a new MGADiag report.


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, December 26, 2011 8:28 PM
    Moderator