Answered by:
Windows 7 suddenly not genuine anymore

Question
-
This morning everything was working fine. Later on the day my mouse wasn't being recognized anymore (not sure if this is related).
After i got the mouse issue fixed, by unplugging my computer from the power supply, I got the message of windows 7 not being genuine anymore.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 50
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-2QWT6-HCQXJ-9YQTR
Windows Product Key Hash: PVjSC5x6njvqunmbCY3lOD7rYDo=
Windows Product ID: 00359-OEM-8992687-00007
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {2482D2E7-4B3E-4389-9A30-271C5FC5F4FC}(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/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
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: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
Browser 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: Allowed
File Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{2482D2E7-4B3E-4389-9A30-271C5FC5F4FC}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-9YQTR</PKey><PID>00359-OEM-8992687-00007</PID><PIDType>2</PIDType><SID>S-1-5-21-3432822270-2317398591-329092291</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0504 </Version><SMBIOSVersion major="2" minor="5"/><Date>20090714000000.000000+000</Date></BIOS><HWID>76F43307018400FE</HWID><UserLCID>0413</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(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>
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7601.17514
Name: 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-800007-02-1043-7601.0000-3022011
Installation ID: 009804696943521255606603575805202260911684269885540893
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: 9YQTR
License Status: Notification
Notification Reason: 0xC004F057.
Remaining Windows rearm count: 3
Trusted time: 21-9-2012 1:45:31
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Not Registered - 0x80070005
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: OgAAAAMABAABAAEAAQADAAAAAQABAAEAonZE2VOji3foD0a8jCaENGhluHgqZo3vmoh+utzhKFnqgg==
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC 071409 APIC1603
FACP 071409 FACP1603
HPET 071409 OEMHPET
MCFG 071409 OEMMCFG
OEMB 071409 OEMB1603
OSFR 071409 OEMOSFR
SSDT DpgPmm CpuPm
Friday, September 21, 2012 12:11 AM
Answers
-
you are using an Asus OEM SLP key on a retail motherboard. that simply won't work.
you will have to purchase a genuine windows.
OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows 7 looks at the motherboard and sees the special instructions and Self-Activates.
- Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Tuesday, October 2, 2012 10:20 PM
- Marked as answer by Noel D PatonModerator Tuesday, October 9, 2012 3:28 PM
Friday, September 21, 2012 12:38 AMAnswerer -
An OEM SLP key must interact with that manufacturers slic table in order to self activate. A retail motherboard does not have a slic table. I doubt that it has worked for several years.
- Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Tuesday, October 2, 2012 10:20 PM
- Marked as answer by Noel D PatonModerator Tuesday, October 9, 2012 3:29 PM
Friday, September 21, 2012 2:23 AMAnswerer -
George is correct. Your motherboard was manufactured on July , 2009 but Windows 7 was not even available to manufacturer's until July 24, 2009. It cannot have a factory preinstalled copy of Windows 7 even if the mobo were not a retail one. OEM SLP copies of Windows cannot be used to upgrade a computer or on a custom built computer. Your copy is taken from a later computer from a major manufacturer. When and how this happened is irrelevant. You need a retail copy of Windows to fix this. It is likely that a recent update required genuine Windows validation and that would be when the system failed to validate.
Colin Barnhorst Windows 7 Ultimate x64 on DIY with 8GB ram.
- Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Tuesday, October 2, 2012 10:20 PM
- Marked as answer by Noel D PatonModerator Tuesday, October 9, 2012 3:29 PM
Friday, September 21, 2012 12:06 PMAnswerer -
There has almost certainly been a loader installed, which may have been broken by an update - look at the WAT data.
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Not Registered - 0x80070005
HealthStatus Bitmask Output:Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
- Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Tuesday, October 2, 2012 10:20 PM
- Marked as answer by Noel D PatonModerator Tuesday, October 9, 2012 3:29 PM
Friday, September 21, 2012 3:10 PMModerator
All replies
-
you are using an Asus OEM SLP key on a retail motherboard. that simply won't work.
you will have to purchase a genuine windows.
OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows 7 looks at the motherboard and sees the special instructions and Self-Activates.
- Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Tuesday, October 2, 2012 10:20 PM
- Marked as answer by Noel D PatonModerator Tuesday, October 9, 2012 3:28 PM
Friday, September 21, 2012 12:38 AMAnswerer -
I don't understand how that simply won't work, as it has been working for several years, up until now that is.Friday, September 21, 2012 1:47 AM
-
An OEM SLP key must interact with that manufacturers slic table in order to self activate. A retail motherboard does not have a slic table. I doubt that it has worked for several years.
- Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Tuesday, October 2, 2012 10:20 PM
- Marked as answer by Noel D PatonModerator Tuesday, October 9, 2012 3:29 PM
Friday, September 21, 2012 2:23 AMAnswerer -
George is correct. Your motherboard was manufactured on July , 2009 but Windows 7 was not even available to manufacturer's until July 24, 2009. It cannot have a factory preinstalled copy of Windows 7 even if the mobo were not a retail one. OEM SLP copies of Windows cannot be used to upgrade a computer or on a custom built computer. Your copy is taken from a later computer from a major manufacturer. When and how this happened is irrelevant. You need a retail copy of Windows to fix this. It is likely that a recent update required genuine Windows validation and that would be when the system failed to validate.
Colin Barnhorst Windows 7 Ultimate x64 on DIY with 8GB ram.
- Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Tuesday, October 2, 2012 10:20 PM
- Marked as answer by Noel D PatonModerator Tuesday, October 9, 2012 3:29 PM
Friday, September 21, 2012 12:06 PMAnswerer -
There has almost certainly been a loader installed, which may have been broken by an update - look at the WAT data.
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Not Registered - 0x80070005
HealthStatus Bitmask Output:Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
- Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Tuesday, October 2, 2012 10:20 PM
- Marked as answer by Noel D PatonModerator Tuesday, October 9, 2012 3:29 PM
Friday, September 21, 2012 3:10 PMModerator