Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Product Key Puzzlement with WGA Diagnostic report RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm a retired programmer & I fix PCs in my neighborhood for people of little means - it's really just a hobby.

    But I have a PC that a woman purchased from a very reputable company in our area.  This company purchases computers from businesses when that company decides to upgrade all the employees PCs to a new OS.  She bought this XP Pro SP3 tower manufactured by IBM about 4 years ago and it has served her without a hitch.

    Several days ago she brought it to me - it wouldn't get past the IBM logo screen.  I opened it up, rehooked all the connections, and it booted beautifully.  Then I figured that as long as I had it overnight, I might as well check it for malware.  I installed, updated, and ran a full MalwareBytes scan, finding 2 Trojan trackers, and 2 pieces of adware.  After I removed the infections I was prompted to reboot when I was greeted with:

    'A problem is preventing Windows from accurately checking the license for this computer. Error code: 0x80004005'.  It won't get past this error except for safe mode without networking.  I have tried re-registering a number of the DLL files without success.  Now this PC's screens all indicate that it is running XP Pro SP3, and the Microsoft sticker on the chassis reads XP Professional, yet when I run the Magic Jelly Bean key finder, the product key that displays is not the 25 digit key on the sticker.

    Being curious, I ran both Belarc Advisor and the Magic JB on a Dell Vista laptop I'm fixing.  I know that this laptop was purchased new at a BestBuy store, yet the identical product keys found by BA and MJB did not match the key on the bottom of the laptop.

    I then ran both of them on my Compaq Vista laptop.  Of the 3 PCs tested, only this one returned keys that matched the sticker, although in the case of my own laptop, I wiped the hard drive and reinstalled the OS a couple years ago, using the key from the sticker to complete the installation.  So it would have been totally bizarre if that didn't match.

    But I'm confused about the other PCs, and I don't know exactly what to do about the woman's XP Pro.  Should I be changing the registry so that I have to revalidate the OS.  And if so, what product key do I use?  The one that Belarc and MJB spit out, or the one on the sticker?  And she never received a CD for her PC, and though I've got several XP disks - Dell, Gateway, and Microsoft - they're all either XP Home or XP Media Center.  I do have an XP Pro iso image that I downloaded and burned, but it's never seemed to work just right on a repair install - it always seems to want to do an actual install instead of a repair install.

    And I really don't know what to attempt, assuming I can get it to boot from a CD, if I go to the recovery console.

    Any ideas?  Thoughts?   Could the XP Pro's sticker have something to do with an original corporate license?  And after they wiped the drive and reinstalled the OS they used a different key?  I dunno.  And what about the Dell Vista laptop?  I was with these folks a few years ago when they bought the laptop.  How can that key not match?      

    I'm very puzzled.

    Here is my WGA Diagnostic Tool report.  The partial product key listed here matches the product key displayed by Magic Jelly Bean, not the key on my MS sticker.   The COA has IBM in black lettering below the line that reads Windows XP Professional.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-4W3BK-PK4BJ-YKCTY
    Windows Product Key Hash: YUQ0E+tcRyAX3cYHdVBwlEvlmGw=
    Windows Product ID: 76487-640-0078643-23292
    Windows Product ID Type: 1
    Windows License Type: Volume
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {491BFA81-DB0A-4A29-B46C-DDE54B2A41D5}(3)
    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-449-80004005_025D1FF3-229-80004005_025D1FF3-230-1_025D1FF3-528-80004005_025D1FF3-237-80004005_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: 0
    File Exists: Yes
    Version: 1.9.40.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    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: 025D1FF3-449-80004005_025D1FF3-229-80004005_025D1FF3-230-1_025D1FF3-528-80004005_025D1FF3-237-80004005_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:\Program Files\Mozilla Firefox\firefox.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>{491BFA81-DB0A-4A29-B46C-DDE54B2A41D5}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-YKCTY</PKey><PID>76487-640-0078643-23292</PID><PIDType>1</PIDType><SID>S-1-5-21-746137067-179605362-839522115</SID><SYSTEM><Manufacturer>IBM</Manufacturer><Model>830644U</Model></SYSTEM><BIOS><Manufacturer>IBM</Manufacturer><Version>24KT54AUS</Version><SMBIOSVersion major="2" minor="31"/><Date>20040604000000.000000+000</Date></BIOS><HWID>F501304F01842052</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.9.40.0"/><File Name="WgaLogon.dll" Version="1.9.40.0"/></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: yes
    Marker string from BIOS: 101EB:GENUINE C&C INC|12E9F:IBM
    Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005

    OEM Activation 2.0 Data-->
    N/A

     



    • Changed type Darin Smith MS Tuesday, January 3, 2012 8:46 PM
    • Edited by scotto Thursday, January 5, 2012 7:23 AM
    Monday, January 2, 2012 9:52 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello scotto,

      I understand that you are frustrated but that is in no way an excuse for swearing and criticizing the help given freely to you by unpaid (non-Microsoft) volunteers who have been trying to assist you in resolving this issue out of the kindness of their hearts.

      They may not have a complete understanding of Windows XP because it's 10 years old and people that volunteer in these forums tend to be technology enthuses that likely don't spend allot of time staying up on obsolete/retired technology.  This is also why Microsoft charges for XP support because XP has been retired. It is no longer produced and is no longer covered by standard Microsoft support. (in addition, I am not aware of any company that provides any support, paid or not, for retired 10 year old software)

      The Windows XP Product Key Update Tool is intended to be used in a full functional copy of Windows XP to change the Product key.  Your Windows XP is not fully functional.  There are deeper unknown issues at play. I know this because your Windows will not boot into normal mode and a Windows XP suffering from a Non-Genuine issue (which is what we specialize in, in this forum) is not designed to only boot in Safe Mode. So there has to be something more wrong than just a non-genuine product key.

      I have been working in this forum for over 5 years and I am not even sure what is causing your particular issue.  What I do know (and what has already been communicated to you by Noel and Carey) is:

    A) the Product Key and software, currently installed, is a Volume License that does not belong to the current owner of the PC.

    and

    B) The issue would be resolved be reinstalling Windows using the proper Product key listed on the Certificate of Authenticity (CoA) sticker that is affixed to the PC.

     

      It is unfortunate that you do not like this resolution but that is the resolution that will resolve your issue.

     

    <Thread Locked>

     

    Thank you,

     

    Darin MS



    Friday, January 6, 2012 11:30 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    "scotto" wrote in message news:ddc26ee8-ac42-425f-b4ee-3cd635e9e65d...

     

    Any ideas?  Thoughts?   Could the XP Pro's sticker have something to do with an original corporate license?  And after they wiped the drive and reinstalled the OS they used a different key?  I dunno.  And what about the Dell Vista laptop?  I was with these folks a few years ago when they bought the laptop.  How can that key not match?     

    I'm very puzzled.

    ALWAYS use the one on the sticker – assuming it’s for the same edition of Windows (Home/Pro).
     
    Most recent computers come with Windows installed using OEM_SLP licensing – with a Key from the Manufacturer which cannot be activated in the normal way, but which self-activates using a SLIC Table from the BIOS, and certificates within the OS. The COA sticker activates in the normal way, and is there for situations where the OEM_SLP process breaks down for some reason. So your situation is totally normal, except that the self-activation appears to have broken down.
     
    If the machine won’t boot to Normal Mode, boot to Safe Mode, and try this -

    1. If the computer can be started to a safe mode command prompt, do so.

    2. At the command prompt, type this command exactly (space, caps, and comma are essential):

    rundll32.exe syssetup,SetupOobeBnk

    3. Restart.

    If you were successful, your activation grace period will have been reset, giving you more time to work on the problem.

    You should then post an MGADiag report, so that we can see what the problem is – but you may simply need to change the Product Key to the one on the COA sticker using the Product Key Update Tool - http://windows.microsoft.com/en-US/windows/help/genuine/product-key

    HTH

     
     
    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, January 2, 2012 10:10 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    The first time I did it, I got to the spalsh screen, and it froze.  The litle blus dots were not moving.  I turned it off after 20 minutes without moving, booted normally and got the same msg. 

    I then used this PC, copied your text to a word document on a flash drive, and used your exact command on the DOS screen (accessed afer starting in safe mode) in the XP Pro machine. 

    No change.  Same message - A problem is preventing Windows from accurately checking the license fro this computer.  Error Cocde: 0x80004005.

    Monday, January 2, 2012 7:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    "scotto" wrote in message news:2548ecc1-0ac0-4ba7-89cb-270799ad3bcb...

    The first time I did it, I got to the spalsh screen, and it froze.  The litle blus dots were not moving.  I turned it off after 20 minutes without moving, booted normally and got the same msg.

    I then used this PC, copied your text to a word document on a flash drive, and used your exact command on the DOS screen (accessed afer starting in safe mode) in the XP Pro machine.

    No change.  Same message - A problem is preventing Windows from accurately checking the license fro this computer.  Error Cocde: 0x80004005.

    may apply
     
    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Proposed as answer by Darin Smith MS Tuesday, January 3, 2012 8:46 PM
    Monday, January 2, 2012 7:59 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    The article itself is puzzling. 

    First it wants me to rename files:

    Rename the following files by using the REN command. To do this, type REN <var>File_Name.extension</var><var>File_Name.old</var> at the command prompt.

    • Wpa.dbl
    • Pidgen.dll
    • Actshell.htm

      Note This file is located in the following subfolder:
      oobe

    Then later it wants to expand files from the CD:

    Type the following commands individually. Press ENTER after each command:

    • Expand licwmi.dl_ <var>C:\WINDOWS</var>\System32
    • Expand regwizc.dl_ <var>C:\WINDOWS</var>\System32
    • Expand licdll.dl_ <var>C:\WINDOWS</var>\System32
    • Expand wpabaln.ex_ <var>C:\WINDOWS</var>\System32
    • Expand wpa.db_ <var>C:\WINDOWS</var>\System32
    • Expand actshell.ht_ <var>C:\WINDOWS</var>\System32
    • Copy pidgen.dll <var>C:\WINDOWS</var>\System32

    Shouldn't it really be asking me to expand actshell.ht_ into c:\windows\system32\oobe?

    At any rate that's what I did and it didn't do squat.

    Any other suggestions?

    Thursday, January 5, 2012 2:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    "scotto" wrote in message news:d7d2df30-ef56-4dac-aff5-e2034ce191da...

    The article itself is puzzling.

     

    Shouldn't it really be asking me to expand actshell.ht_ into c:\windows\system32\oobe?

    At any rate that's what I did and it didn't do squat.

    Any other suggestions?

    I agree – that does seem to be an error in the article. Just in case, please copy the file to the System32 folder, and reboot.
     
    At a command prompt, type the following commands.
     
    REGSVR32  LICDLL.DLL
    REGSVR32  REGWIZC.DLL
    REGSVR32  LICWMI.DLL
     
    you should get success messages after each.
    reboot – see if that helps.
     
    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, January 5, 2012 9:52 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    As I mentioned in the orig. post, 'I have tried re-registering a number of the DLL files without success'.  Those 3 were among the 10 or so, but I did just those again.

    No change.

    Does the Diagnostic report I added to the first post shed any additional light?

    Thursday, January 5, 2012 3:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    "scotto" wrote in message news:f622d8d8-37f3-4d2e-a39f-522abfc2e18c...

    As I mentioned in the orig. post, 'I have tried re-registering a number of the DLL files without success'.  Those 3 were among the 10 or so, but I did just those again.

    No change.

    Does the Diagnostic report I added to the first post shed any additional light?

     
    Not really, unfortunately – the diagnostic capabilities in XP are minimal :(
     
    I think it’s probably best to hand you off to WGA support at this point – it looks as if the problem needs more work than can reasonably be done in a forum context (and my knowledge of XP activation processes is limited!).
     
    WGA Support can be found here-
    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4

    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0

    Please let us know if (and how) MS manage to repair the problem without a repair install of the OS - it would be useful for future reference!
    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, January 5, 2012 4:04 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Please let us know if (and how) MS manage to repair the problem without a repair install of the OS - it would be useful for future reference!

    I just hope you managed to keep a straight face as you typed that sentence...

    I visited the link, called MS, went through the mind-numbing and eternal automated process, got a live person, was told I'd gotten the wrong department - that there was a seperate area for XP activation problems, was xferred again and (eventually) got another live person who xferred me one last time before I got someone who informed me that support for XP had ended but that she'd be glad to connect me to another fee-based group who'd be thrilled to help me for $59.95.

    Money grubbing <deleted>!!!!  How exactly do these people sleep?

    Noel, I'd thank you..... but.... I've basically done nothing but waste a whole day on this.  The 'thanks' would ring hollow.  You mentioned that your knowledge of XP activation processes was limited.  I'm sorry to be so <deleted>, but I'm wondering why then we've been carrying on this dialog.  Shouldn't there someone on a Microsoft Genuine Advantage forum who does have something beyond 'limited knowledge' of the Microsoft Genuine Advantage process?

    If a Windows XP Activation problems forum can't help me, and MS won't .....

    Well, there really is no justice, is there?


    • Edited by Darin Smith MS Friday, January 6, 2012 10:15 PM Profanity deleted
    Friday, January 6, 2012 2:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You need to contact IBM Support and see if they have a Windows XP recovery disk for that IBM computer.  If not, its time for the lady to recycle that PC relic and purchase a new computer that comes with Windows 7 preinstalled (and is far more secure than Windows XP will ever be).
    Carey Frisch
    Friday, January 6, 2012 3:03 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    You need to contact IBM Support and see if they have a Windows XP recovery disk for that IBM computer.  If not, its time for the lady to recycle that PC relic and purchase a new computer that comes with Windows 7 preinstalled (and is far more secure than Windows XP will ever be).
    Carey Frisch
    You DO realize that when it comes to actually solving an immediate problem, your answer contains very little of relevance, don't you?
    Friday, January 6, 2012 4:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As you stated earlier, you have no Windows XP Professional OEM installation CD.  How can anyone help you if you do not have the physical resources (i.e. Windows XP Professional OEM CD)?  The current installation was performed with a Windows XP Professional Volume License CD and a Windows XP Professional Volume License product key that belonged to the company that original owned the computer.  That Volume License is non-transferrable to another owner and the company should not have let anyone have that computer without removing that Volume License.

    Your only possible alternative is to try and use the Windows XP Product Key Update Tool to change the product key to the one that is affixed to the computer (the Windows XP Professional OEM product key printed on the Product Key Label).

    Carey Frisch
    Friday, January 6, 2012 7:14 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    As you stated earlier, you have no Windows XP Professional OEM installation CD.  How can anyone help you if you do not have the physical resources (i.e. Windows XP Professional OEM CD)?  The current installation was performed with a Windows XP Professional Volume License CD and a Windows XP Professional Volume License product key that belonged to the company that original owned the computer.  That Volume License is non-transferrable to another owner and the company should not have let anyone have that computer without removing that Volume License.

    Your only possible alternative is to try and use the Windows XP Product Key Update Tool to change the product key to the one that is affixed to the computer (the Windows XP Professional OEM product key printed on the Product Key Label).

     

     

    Carey Frisch


    Windows XP Product Key Update Tool will not run in safe mode which is all I have.  I would have expected you to know that.

    I rather assumed with having 2 legitimate product keys for Windows XP Professional on an XP Pro machine... that someone at this forum would be able to guide me through a 5 step process whereby I could get one of these keys validated - bring up the screen where you type in the product key, call an automated number, read a series of other numbers to the automated voice and hit a couple of keys.

    It seems obvious that there's some sort of registry problem that's probably been caused by the 2 different keys, and the fact that a corporate license has been replaced by an OEM license. 

    I just didn't think it would be necessary to do a repair install to correct a validation problem.  And dollars to donuts, you can bet that a MS tech engineer wouldn't think so either.  



    • Edited by scotto Friday, January 6, 2012 6:07 PM
    Friday, January 6, 2012 9:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello scotto,

      I understand that you are frustrated but that is in no way an excuse for swearing and criticizing the help given freely to you by unpaid (non-Microsoft) volunteers who have been trying to assist you in resolving this issue out of the kindness of their hearts.

      They may not have a complete understanding of Windows XP because it's 10 years old and people that volunteer in these forums tend to be technology enthuses that likely don't spend allot of time staying up on obsolete/retired technology.  This is also why Microsoft charges for XP support because XP has been retired. It is no longer produced and is no longer covered by standard Microsoft support. (in addition, I am not aware of any company that provides any support, paid or not, for retired 10 year old software)

      The Windows XP Product Key Update Tool is intended to be used in a full functional copy of Windows XP to change the Product key.  Your Windows XP is not fully functional.  There are deeper unknown issues at play. I know this because your Windows will not boot into normal mode and a Windows XP suffering from a Non-Genuine issue (which is what we specialize in, in this forum) is not designed to only boot in Safe Mode. So there has to be something more wrong than just a non-genuine product key.

      I have been working in this forum for over 5 years and I am not even sure what is causing your particular issue.  What I do know (and what has already been communicated to you by Noel and Carey) is:

    A) the Product Key and software, currently installed, is a Volume License that does not belong to the current owner of the PC.

    and

    B) The issue would be resolved be reinstalling Windows using the proper Product key listed on the Certificate of Authenticity (CoA) sticker that is affixed to the PC.

     

      It is unfortunate that you do not like this resolution but that is the resolution that will resolve your issue.

     

    <Thread Locked>

     

    Thank you,

     

    Darin MS



    Friday, January 6, 2012 11:30 PM