Received invalid notification/won't accept key on COA on machine

All replies

• 

  

  0

  Sign in to vote

  Hello rebell1952,

  In order to receive the best support, we request all users initially download and run the Genuine Diagnostics tool at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Run" several times to download and start the Utility.  When asked, click the "Continue" button.  When the utility completes its run, click the "Copy" button, then come back here and paste the report into your post.

  Also, please tell us if the computer in question has a Certificate of Authenticity affixed to it and if so, what version and edition of Windows is listed on it, and does it have the computer manufacturer's name on the CoA?  (Don't post the product key.)

  ---

  Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97

  Tuesday, June 29, 2010 1:34 AM
• 

  

  0

  Sign in to vote

  Here is the MGADiag report.
   
  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  Validation Status: Invalid Product Key
  Validation Code: 8
  Cached Validation Code: N/A
  Windows Product Key: *****-*****-JRJRY-JX74Y-9W2BQ
  Windows Product Key Hash: ooZQoJC4yJKV1Bh289tCHFE6PvE=
  Windows Product ID: 55274-640-5337971-23865
  Windows Product ID Type: 1
  Windows License Type: Volume
  Windows OS version: 5.1.2600.2.00010100.3.0.pro
  ID: {E0365FCC-246B-4458-A283-4091F77D398C}(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-230-1
  Resolution Status: N/A
  Vista WgaER Data-->
  ThreatID(s): N/A
  Version: N/A
  Windows XP Notifications Data-->
  Cached Result: 8
  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: B4D0AA8B-543-80070002_025D1FF3-230-1
  Browser Data-->
  Proxy settings: :0
  User Agent: Mozilla/4.0 (compatible; MSIE 8.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>{E0365FCC-246B-4458-A283-4091F77D398C}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-9W2BQ</PKey><PID>55274-640-5337971-23865</PID><PIDType>1</PIDType><SID>S-1-5-21-448539723-1482476501-725345543</SID><SYSTEM><Manufacturer>Gateway                         </Manufacturer><Model>E4300                           </Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>SE91510J.15A.2525.2005.0414.1610</Version><SMBIOSVersion major="2" minor="3"/><Date>20050414000000.000000+000</Date></BIOS><HWID>345332470184406D</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: 1E848:emachines inc|1E848:Gateway, Inc|1E840:Gateway, Inc
  Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005
  OEM Activation 2.0 Data-->
  N/A
   
  The above product key is not the one on the CoA sticker on the machine. However, I have been unable to change the product ket to the one on the sticker. The CoA says XP Professional, which is what is installed on the machine according to System Information. The manufacturer is Gateway (though that in not actually printed on the CoA sticker), but the machine is far too old to get any tech or other support from them. The machine was bought used from the original owner, but there is a probability that the OS was reinstalled from an XP disc that was not an OEM disc. I don't know if that would make any difference, but that's probably why the product key listed in the MGADiag report is different to the one on the OEM CoA sticker. Unless the person I bought the machine from was not the original owner and the machine actually came from a school or corporation and has a volume license, I don't see why the original key won't validate.

  Tuesday, June 29, 2010 2:36 AM
• 

  

  0

  Sign in to vote

  "rebell1952" wrote in message news:f474a44b-9a0e-45b6-975d-c945bf1c2439...

  Here is the MGADiag report.
   
  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  Validation Status: Invalid Product Key
  Validation Code: 8
  Cached Validation Code: N/A
  Windows Product Key: *****-*****-JRJRY-JX74Y-9W2BQ
  Windows Product Key Hash: ooZQoJC4yJKV1Bh289tCHFE6PvE=
  Windows Product ID: 55274-640-5337971-23865
  Windows Product ID Type: 1
  Windows License Type: Volume
  Windows OS version: 5.1.2600.2.00010100.3.0.pro
  ID: {E0365FCC-246B-4458-A283-4091F77D398C}(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-230-1
  Resolution Status: N/A
  Vista WgaER Data-->
  ThreatID(s): N/A
  Version: N/A
  Windows XP Notifications Data-->
  Cached Result: 8
  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: B4D0AA8B-543-80070002_025D1FF3-230-1
  Browser Data-->
  Proxy settings: :0
  User Agent: Mozilla/4.0 (compatible; MSIE 8.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>{E0365FCC-246B-4458-A283-4091F77D398C}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-9W2BQ</PKey><PID>55274-640-5337971-23865</PID><PIDType>1</PIDType><SID>S-1-5-21-448539723-1482476501-725345543</SID><SYSTEM><Manufacturer>Gateway                         </Manufacturer><Model>E4300                           </Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>SE91510J.15A.2525.2005.0414.1610</Version><SMBIOSVersion major="2" minor="3"/><Date>20050414000000.000000+000</Date></BIOS><HWID>345332470184406D</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: 1E848:emachines inc|1E848:Gateway, Inc|1E840:Gateway, Inc
  Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005
  OEM Activation 2.0 Data-->
  N/A
   
  The above product key is not the one on the CoA sticker on the machine. However, I have been unable to change the product ket to the one on the sticker. The CoA says XP Professional, which is what is installed on the machine according to System Information. The manufacturer is Gateway (though that in not actually printed on the CoA sticker), but the machine is far too old to get any tech or other support from them. The machine was bought used from the original owner, but there is a probability that the OS was reinstalled from an XP disc that was not an OEM disc. I don't know if that would make any difference, but that's probably why the product key listed in the MGADiag report is different to the one on the OEM CoA sticker. Unless the person I bought the machine from was not the original owner and the machine actually came from a school or corporation and has a volume license, I don't see why the original key won't validate.

   

   

  I'm sure Dan or someone else will be back here later but one part of the information I see is:

   

  Windows Product ID Type: 1
  Windows License Type: Volume

   

  which indicates to me that someone has installed a volume license version of Windows XP Pro.  The key on the COA will not validate a Volume license.  You will need to find a OEM version disk of XP Pro, either from Gateway or you may be able to purchase disks for your model from www.restoredisks.com (and a quick check shows that they have XP Pro available for your E4300 Gateway for $26.99.) If you do the restoredisks route use the COA key to clean reinstall XP using the new disk.

  Tuesday, June 29, 2010 3:01 AM
• 

  

  0

  Sign in to vote

  Hello rebell1952,

  Windows Validation Data-->
  Validation Status: Invalid Product Key
  Validation Code: 8
  Cached Validation Code: N/A
  Windows Product Key: *****-*****-JRJRY-JX74Y-9W2BQ
  Windows Product Key Hash: ooZQoJC4yJKV1Bh289tCHFE6PvE=
  Windows Product ID: 55274-640-5337971-23865
  Windows Product ID Type: 1
  Windows License Type: Volume
  Windows OS version: 5.1.2600.2.00010100.3.0.pro
  ID: {E0365FCC-246B-4458-A283-4091F77D398C}(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-230-1
  Resolution Status: N/A
  Vista WgaER Data-->
  ThreatID(s): N/A
  

  As noted by LVTravel and yourself, this Gateway E4300 computer has a nongenuine Volume Licensing installation of XP Pro on it.  The Volume Licensing product Key is Invalid, meaning it was made up by a pirating program known as a Key Generator, or KeyGen for short.  The product key was never issued by Microsoft, making it invalid.

  You noted that you have not been able to change the product key to the one one the CoA because the product key on the CoA is also rejected as Invalid.  When you write this, I am assuming that you have attempted to use the Microsoft Product Key Updater Utility available here http://go.microsoft.com/fwlink/?linkid=45668  and the utility is telling you that the key on the computer's CoA is Invalid.

  If the PK updater is telling you the product key on the CoA in Invalid, then it's very likely that the CoA is counterfeit.  Like you, I find it odd that a Gateway computer with a CoA does not have Gateway printed on the CoA.  Does the CoA have "OEM Product" or "OEM Software" printed on it?

   

  ---

  Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97

  • Marked as answer by Darin Smith MS Wednesday, June 30, 2010 9:02 PM

  Tuesday, June 29, 2010 12:07 PM
• 

  

  0

  Sign in to vote

  "Dan at IT Associates" wrote in message news:552754ed-0c27-4f8d-8f96-ac50ccba80ae...

  Hello rebell1952,

  Windows Validation Data-->
  Validation Status: Invalid Product Key
  Validation Code: 8
  Cached Validation Code: N/A
  Windows Product Key: *****-*****-JRJRY-JX74Y-9W2BQ
  Windows Product Key Hash: ooZQoJC4yJKV1Bh289tCHFE6PvE=
  Windows Product ID: 55274-640-5337971-23865
  Windows Product ID Type: 1
  Windows License Type: Volume
  Windows OS version: 5.1.2600.2.00010100.3.0.pro
  ID: {E0365FCC-246B-4458-A283-4091F77D398C}(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-230-1
  Resolution Status: N/A
  Vista WgaER Data-->
  ThreatID(s): N/A
  

  As noted by LVTravel and yourself, this Gateway E4300 computer has a nongenuine Volume Licensing installation of XP Pro on it.  The Volume Licensing product Key is Invalid, meaning it was made up by a pirating program known as a Key Generator, or KeyGen for short.  The product key was never issued by Microsoft, making it invalid.

  You noted that you have not been able to change the product key to the one one the CoA because the product key on the CoA is also rejected as Invalid.  When you write this, I am assuming that you have attempted to use the Microsoft Product Key Updater Utility available here http://go.microsoft.com/fwlink/?linkid=45668  and the utility is telling you that the key on the computer's CoA is Invalid.

  If the PK updater is telling you the product key on the CoA in Invalid, then it's very likely that the CoA is counterfeit.  Like you, I find it odd that a Gateway computer with a CoA does not have Gateway printed on the CoA.  Does the CoA have "OEM Product" or "OEM Software" printed on it?

   

  ---

  Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97

  
  

  Dan, please correct me if I am wrong in my assumptions - An XP volume license can only be made "genuine" by a genuine volume license key (which the OP does not, and can not have as an individual) and a retail key will not activate a VL version of XP.  If my assumption is correct the OP will not be able to use the Key Updater to change the key and will have to do a full reinstall of the same version of XP Pro (OEM) that the COA is created for on the COA sticker.

  Tuesday, June 29, 2010 3:16 PM
• 

  

  0

  Sign in to vote

  Hello LVTravel,

  The Product Key Updater was specifically written to accomplish the "genuine-ization" of nongenuine Volume Licensing installations of XP Pro that were put on computers that had did not have a genuine CoA for XP Pro----it facilitated the sale of the WGA Kit because in many cases it eliminated the drudgery of backing up and then using genuine media to put a genuine installation of Windows XP back onto the computer.  The people could buy their WGA Kit, get the new genuine key in email, run the Updater, and be genuine in less than an hour.

  It was also programmed to do the same when there is a genuine XP CoA on the computer with a genuine product key---it will indeed genuine-ize a nongenuine Volume Licensing installation into a genuine OEM installation as long as the product key on the OEM CoA is genuine.

  In both scenarios the PK Updater is limited by how hacked and cracked any given installation of XP is---if there are too many damaged or hacked files, it won't be able to cope and will exit out saying that the update was unsuccessful.  In such case the person would have to backup their data and then do a clean installation from genuine Microsoft or manufacturer recovery media.

  You are right when you state that an XP volume license can only be made genuine by a genuine VLK.  There is a KB article that tells us how to do that:  http://support.microsoft.com/kb/328874

  And you are right that a retail key will not activate a volume license for XP.

  What the updater does is change both the product key and the sales channel (most often volume to retail or volume to OEM, to match the sales channel of the genuine product key being used) of the license.

  ---

  Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97

  • Edited by Dan at IT Associates Tuesday, June 29, 2010 11:17 PM typo

  Tuesday, June 29, 2010 4:01 PM
• 

  

  0

  Sign in to vote

   If CoA key is for XP Home (and the VL software is XP Pro) the Product Key Updater tool will give an error. 

   I'm not sure if I remember correctly (it's been a while since I messed with changing a product key in XP), but I believe the error could be interpreted, by the customer, as meaning the key is "Invalid" when, in fact, it's just the wrong key for that version of XP.

    to be on the safe side, I recommend contacting the OEM for the proper Windows Recovery Software for that PC, install it and then see if the CoA works or not.

   

  Thank you,

  ---

  Darin MS

  • Proposed as answer by Darin Smith MS Tuesday, June 29, 2010 7:44 PM

  Tuesday, June 29, 2010 7:39 PM
• 

  

  0

  Sign in to vote

  In addition, I notice that the Diag does show a Bios Marker for emachines/Gateway which suggests that the OEM Windows Recovery software should resolve the issue.

  ---

  Darin MS

  • Proposed as answer by Darin Smith MS Tuesday, June 29, 2010 7:44 PM

  Tuesday, June 29, 2010 7:43 PM
• 

  

  0

  Sign in to vote

  I have tried the Product Key Updater Utility and it gives me the error message, "The product key could not be updated on your computer. This may be due to technical difficulties or netwok connectivity issues." I don't know to what technical difficulties this refers, but there are no connectivity issues.

  The CoA sticker does have Gateway on it, but it was so small I had to use a powerful magnifying glass to find it. There are some other numbers on the sticker as well; one is the bar code number, another is above the product key (9003698) to which I don't know the reference and one on the side of the sticker that is X10-60256.

  Apparently the XP Pro that was installed was a VLP install and so I suppose I will have to reinstall the OEM version of XP Pro in order for the CoA sticker key to work. I read KB-328874 and it appears to only apply to replacing a VLP key with a different VLP key, as it directly says this and says something about this not working with other key replacements. I'm not sure I understand how to use the VB scripting method and the KB article is not very clearly explained as to how to save a .vsb file without Visual Basic, nor how to use that file in conjunction with the command line command.

  I contacted Gateway and they will not provide restore dics for this machine because it is out of warranty and because I am not the original owner. I have not tried restorediscs.com. If there is no other way to restore the OS to an OEM version, I will try restorediscs.com, but the cost is somewhat restrictive as I am on a very small fixed income.

  Thank you for all of your help in this matter. I build a few computers a year and do some computer repair to supplement my income, but lately I have been encountering some very unusual problems in regard to Microsoft software keys and the prevelance of MSDN keys and counterfeit software.

  Tuesday, June 29, 2010 9:55 PM
• 

  

  0

  Sign in to vote

  Hello rebell1952,

  If the PK Updater is telling you, "The product key could not be updated on your computer. This may be due to technical difficulties or netwok connectivity issues," then what I wrote to LVTravel applies:

  "In both scenarios the PK Updater is limited by how hacked and cracked any given installation of XP is---if there are too many damaged or hacked files, it won't be able to cope and will exit out saying that the update was unsuccessful.  In such case the person would have to backup their data and then do a clean installation from genuine Microsoft or manufacturer recovery media."

  LVTravel posted that you can purchase recovery media from www.restoredisks.com for $26.99.  Assuming they send you genuine recovery media and the discs work on your computer, then running the recovery from these discs will get your computer back to having a genuine installation of XP Pro.

  Since you posted that you occasionally build some computers, you may have a genuine hologrammed Microsoft XP Pro systembuilder/OEM installation CD hanging about.  If so, you can use that disc to cleanly install XP Pro using the product key on the CoA.  When it comes time to activate you will have to use the phone activation method because its likely the automatic online method will not approve the PK on the Gateway CoA.

  ---

  Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97

  • Marked as answer by Darin Smith MS Wednesday, June 30, 2010 9:04 PM

  Tuesday, June 29, 2010 11:24 PM
• 

  

  0

  Sign in to vote

  "Dan at IT Associates" wrote in message news:fcf0cca7-df3a-42b4-9db9-4acec25e7a2d...

  Hello LVTravel,

  The Product Key Updater was specifically written to accomplish the "genuine-ization" of nongenuine Volume Licensing installations of XP Pro that were put on computers that had did not have a genuine CoA for XP Pro----it facilitated the sale of the WGA Kit because in many cases it eliminated the drudgery of backing up and then using genuine media to put a genuine installation of Windows XP back onto the computer.  The people could buy their WGA Kit, get the new genuine key in email, run the Updater, and be genuine in less than an hour.

  It was also programmed to do the same when there is a genuine XP CoA on the computer with a genuine product key---it will indeed genuine-ize a nongenuine Volume Licensing installation into a genuine OEM installation as long as the product key on the OEM CoA is genuine.

  In both scenarios the PK Updater is limited by how hacked and cracked any given installation of XP is---if there are too many damaged or hacked files, it won't be able to cope and will exit out saying that the update was unsuccessful.  In such case the person would have to backup their data and then do a clean installation from genuine Microsoft or manufacturer recovery media.

  You are right when you state that an XP volume license can only be made genuine by a genuine VLK.  There is a KB article that tells us how to do that:  http://support.microsoft.com/kb/328874

  And you are right that a retail key will not activate a volume license for XP.

  What the updater does is change both the product key and the sales channel (most often volume to retail or volume to OEM, to match the sales channel of the genuine product key being used) of the license.

  ---

  Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97

  
  

  Thanks for the complete and clear explanation.  I didn't know about the Key Updater actually changing the "sales channel," basically changing the VL version to a retail or OEM.  Thanks again.

  Wednesday, June 30, 2010 3:04 AM