Answered by:
Windows 7 - Build 7601 - This copy of Windows is not genuine

Question
-
Hi there - I'm hoping one of you good techie experts can help with my problem. I've had a Compaq laptop for just over 3 years now (more or less problem free) and when logging into windows today I was presented with a black desktop and a message that my copy of windows is not genuine. I've tried re-activating windows using my original product key but got error 0xC004E003. I've read a few posts which appear to have a similar problem to mine but I thought it safer to provide a copy of my MGADiag report to see if anyone can help with the best way forward for my specific issue?
Thanks for any assistance anyone can provide.
I'm running Windows 7 Home Premium 64-bit SP1. Here's the MGADiag report.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 50
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-73CQT-WMF7J-3Q6C9
Windows Product Key Hash: KaFG+RmurcM3ZxzWyfEP9WtPUJw=
Windows Product ID: 00359-OEM-8992687-00010
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {737A953F-5869-4F8C-9FE4-B80BEF68F948}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120503-2030
TTS Error:
Validation Diagnostic:
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002Windows 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 = 0x80070002OGA 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 = 0x80070002OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\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: AllowedFile Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{737A953F-5869-4F8C-9FE4-B80BEF68F948}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3Q6C9</PKey><PID>00359-OEM-8992687-00010</PID><PIDType>2</PIDType><SID>S-1-5-21-4095349620-154717430-1631491393</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>SLIC-MPC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.11</Version><SMBIOSVersion major="2" minor="4"/><Date>20090821000000.000000+000</Date></BIOS><HWID>305E3507018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7601.17514Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800010-02-2057-7601.0000-0072013
Installation ID: 010440329735822573903833341603283952950224059720322152
Processor Certificate URL:
Machine Certificate URL:
Use License URL:
Product Key Certificate URL:
Partial Product Key: 3Q6C9
License Status: Notification
Notification Reason: 0xC004F059.
Remaining Windows rearm count: 2
Trusted time: 07/01/2013 18:50:36Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 11:4:2012 19:31
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: MgAAAAEAAgABAAIAAAABAAAAAwABAAEAeqjuyV4RvOx6fwrp9mXWFfh+sPYWKbxgVrg=OEM Activation 1.0 Data-->
N/AOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC HPQOEM SLIC-MPC
FACP HPQOEM SLIC-MPC
HPET HPQOEM SLIC-MPC
BOOT HPQOEM SLIC-MPC
MCFG HPQOEM SLIC-MPC
ASF! HPQOEM SLIC-MPC
SLIC HPQOEM SLIC-MPC
SSDT PmRef Cpu0Cst
SSDT PmRef Cpu0CstMonday, January 7, 2013 7:15 PM
Answers
-
Your problem is that for some reason, the system is unable to properly read the SLIC table in the BIOS, which is required to be able to self-activate the OEM_SLP Key with which the computer came installed.
The normal solution is to change the Key to the one on your COA sticker - but you say that you are unable to read the Key there.
In such circumstances, the only things you can do are
1) recreate the Licensing Store - in case it's a minor software problem causing the misread
2) try updating the BIOS to the latest available Vista-compliant one, from the manufacturer's website
3) Contact the manufacturer direct, and see if they can provide assistance to correct the SLIC table
4) a reformat and reinstall using the manufacturer's recovery media
5) purchase a new license for Windows (or a new computer)
There *may* be an alternative solution though, if you are patient and persistent.
Attempt Telephone Activation, and speak to an operator - they will tell you that your current Key
is blocked (they should then ask for confirmation of your Product Key). Explain
to them your problem, that you need to change the Key to the one on your sticker,
but that the sticker is unreadable (could they please supply a replacement
Key?). Hopefully they will ask for documentary proof of the sticker, in the
form of an email with a picture of the affected sticker - and you can proceed
from there.Sometimes it takes two or three calls before you get an operator who actually knows and uses
this procedure - but I know that it can and does happen.
Please first try recreating Licensing Store.
Recreate the Licensing Store
Go to Start > All Programs > Accessories
Right-Click on Command Prompt and select Run as Administrator - accept the UAC prompt
Run the following commands in the Command Prompt window, using the Enter key at the end of each
net stop sppsvc
(wait until the service has stopped before entering the following lines)
CD %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
REN tokens.dat tokens.bar
net start sppsvc
slui.exe
After a couple of seconds the Windows Activation dialog will appear.
You may be asked to re-activate and/or re-enter your product key, or Activation may occur automatically.
If you are asked for your Key, use the one on the COA sticker on the machine's case (in your instance you will have to cancel out at this point)
Reboot and Post back with a new MGADiag report
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
- Proposed as answer by Noel D PatonModerator Wednesday, January 9, 2013 11:06 AM
- Marked as answer by Noel D PatonModerator Wednesday, January 16, 2013 4:26 PM
Monday, January 7, 2013 10:29 PMModerator
All replies
-
The problem is that your system is unable to properly read the BIOS SLIC table that should be present in the system to be able to self-activate the OS.
You need to change the Product Key to the one on the COA sticker on the machine's case (or inside the battery compartment), using the Change Product Key link at the bottom of the System properties page.
You may need to activate by phone.
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
Monday, January 7, 2013 9:12 PMModerator -
Hi Noel - thanks for the quick response - much appreciated. I think I may have a problem - as the laptop is a few years old, the product key label has worn to the point that the key is no longer legible. Is there any way I can retrieve this elsewhere?Monday, January 7, 2013 10:17 PM
-
Your problem is that for some reason, the system is unable to properly read the SLIC table in the BIOS, which is required to be able to self-activate the OEM_SLP Key with which the computer came installed.
The normal solution is to change the Key to the one on your COA sticker - but you say that you are unable to read the Key there.
In such circumstances, the only things you can do are
1) recreate the Licensing Store - in case it's a minor software problem causing the misread
2) try updating the BIOS to the latest available Vista-compliant one, from the manufacturer's website
3) Contact the manufacturer direct, and see if they can provide assistance to correct the SLIC table
4) a reformat and reinstall using the manufacturer's recovery media
5) purchase a new license for Windows (or a new computer)
There *may* be an alternative solution though, if you are patient and persistent.
Attempt Telephone Activation, and speak to an operator - they will tell you that your current Key
is blocked (they should then ask for confirmation of your Product Key). Explain
to them your problem, that you need to change the Key to the one on your sticker,
but that the sticker is unreadable (could they please supply a replacement
Key?). Hopefully they will ask for documentary proof of the sticker, in the
form of an email with a picture of the affected sticker - and you can proceed
from there.Sometimes it takes two or three calls before you get an operator who actually knows and uses
this procedure - but I know that it can and does happen.
Please first try recreating Licensing Store.
Recreate the Licensing Store
Go to Start > All Programs > Accessories
Right-Click on Command Prompt and select Run as Administrator - accept the UAC prompt
Run the following commands in the Command Prompt window, using the Enter key at the end of each
net stop sppsvc
(wait until the service has stopped before entering the following lines)
CD %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
REN tokens.dat tokens.bar
net start sppsvc
slui.exe
After a couple of seconds the Windows Activation dialog will appear.
You may be asked to re-activate and/or re-enter your product key, or Activation may occur automatically.
If you are asked for your Key, use the one on the COA sticker on the machine's case (in your instance you will have to cancel out at this point)
Reboot and Post back with a new MGADiag report
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
- Proposed as answer by Noel D PatonModerator Wednesday, January 9, 2013 11:06 AM
- Marked as answer by Noel D PatonModerator Wednesday, January 16, 2013 4:26 PM
Monday, January 7, 2013 10:29 PMModerator -
Thanks again Noel.
I came across a utility called speccy, ran it and it retrieved a product key from my system which looks valid - it ends in the same 15 characters as those in the MGADiag report I provided earlier. Do you think this could be reliable enough for me to use when attempting to re-recreate the licensing store?
Sorry for all the questions - I don't want to jump in and make matters worse!
Monday, January 7, 2013 10:41 PM -
No problem - I'd much rather people asked first, than complained later :)
The Key in the report is about as much use currently as a chocolate teapot - it's the OEM_SLP Key.....
Computers that come pre-installed with Windows from large manufacturers usually come with two Product Keys.
OEM SLP: This is the key that came in Windows (from the factory). It works by connecting to a BIOS flag (the SLIC table) found only on computers from that Manufacturer. It also checks for the existence of proper matching licenses in the OS itself. Once it sees both, it self-activates every time the machine is rebooted.
COA SLP: This is the key seen on the sticker located on the side, bottom or in the battery compartment of your machine. This key is for use if the OEM SLP self-activation stops working for whatever reason.
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
Monday, January 7, 2013 10:46 PMModerator -
OK, I tried re-creating the licensing store following the instructions provided. I had to cancel out at the point I was asked for a product key as you suspected. I've re-booted and the updated MGADiag report is below...
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 50
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-73CQT-WMF7J-3Q6C9
Windows Product Key Hash: KaFG+RmurcM3ZxzWyfEP9WtPUJw=
Windows Product ID: 00359-OEM-8992687-00010
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {737A953F-5869-4F8C-9FE4-B80BEF68F948}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120503-2030
TTS Error:
Validation Diagnostic:
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002Windows 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 = 0x80070002OGA 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 = 0x80070002OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\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: AllowedFile Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{737A953F-5869-4F8C-9FE4-B80BEF68F948}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3Q6C9</PKey><PID>00359-OEM-8992687-00010</PID><PIDType>2</PIDType><SID>S-1-5-21-4095349620-154717430-1631491393</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>SLIC-MPC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.11</Version><SMBIOSVersion major="2" minor="4"/><Date>20090821000000.000000+000</Date></BIOS><HWID>305E3507018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7601.17514Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800010-02-2057-7601.0000-0072013
Installation ID: 010440329735822573903833341603283952950224059720322152
Processor Certificate URL:
Machine Certificate URL:
Use License URL:
Product Key Certificate URL:
Partial Product Key: 3Q6C9
License Status: Notification
Notification Reason: 0xC004F063.
Remaining Windows rearm count: 2
Trusted time: 07/01/2013 23:00:49Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 11:4:2012 19:31
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: MgAAAAEAAgABAAIAAAABAAAAAwABAAEAeqjuyV4RvOx6fwrp9mXWFfh+sPYWKbxgVrg=OEM Activation 1.0 Data-->
N/AOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC HPQOEM SLIC-MPC
FACP HPQOEM SLIC-MPC
HPET HPQOEM SLIC-MPC
BOOT HPQOEM SLIC-MPC
MCFG HPQOEM SLIC-MPC
ASF! HPQOEM SLIC-MPC
SLIC HPQOEM SLIC-MPC
SSDT PmRef Cpu0Cst
SSDT PmRef Cpu0CstMonday, January 7, 2013 11:09 PM -
I'm afraid you'll have to work through the other options :( - we can be of no more real assistance here.
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
Monday, January 7, 2013 11:25 PMModerator -
No problem Noel - thanks for your assistance anyway.
Just one final question - do you have any thoughts on how this may have happened all of a sudden? My kids generally use this laptop and I try to be careful about gaming sites etc which they are visiting. Could this be the result of a virus or is there something else which could have caused it? I'd like to avoid the same scenario again once I eventually get this resolved.
Cheers.
Tuesday, January 8, 2013 1:27 AM -
No-one knows the cause of these things, unfortunately - it could simply be the BIOS chip aging, and so a physical thing, or it could be the result of malware (but I personally think it's unlikely).
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
Tuesday, January 8, 2013 9:44 AMModerator