Answered by:
Windows 7 suddnely not Genuine

Question
-
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 50
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-WJ2H8-R6B6D-7QJB7
Windows Product Key Hash: ckKNc+BBPDWmo1LUlOkraNjlQ34=
Windows Product ID: 00359-OEM-8992687-00006
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {D50F186A-9590-4513-87EB-ABF9CACE374B}(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: 0x00000000
Build lab: 7601.win7sp1_gdr.130828-1532
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\Google\Chrome\Application\chrome.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>{D50F186A-9590-4513-87EB-ABF9CACE374B}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-7QJB7</PKey><PID>00359-OEM-8992687-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-2072860903-3764228434-1560630091</SID><SYSTEM><Manufacturer>ASUS</Manufacturer><Model>All Series</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1007</Version><SMBIOSVersion major="2" minor="7"/><Date>20130517000000.000000+000</Date></BIOS><HWID>EF923207018400F4</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06: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-800006-02-1033-7601.0000-3362013
Installation ID: 019956834154163254217806466311202672702991677903865854
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: 7QJB7
License Status: Notification
Notification Reason: 0xC004F063.
Remaining Windows rearm count: 3
Trusted time: 1/7/2014 6:42:53 PM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0xC004C533
HealthStatus: 0x0000000000000000
Event Time Stamp: 1:6:2014 15:16
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: LgAAAAEAAQABAAEAAAADAAAAAQABAAEA6GFECUY6rBDkCpI5cCBoGP118mXI9g==
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 ALASKA A M I
FACP ALASKA A M I
HPET ALASKA A M I
MCFG ALASKA A M I
FPDT ALASKA A M I
SSDT PmRef Cpu0Ist
SSDT PmRef Cpu0Ist
SSDT PmRef Cpu0Ist
SSDT PmRef Cpu0Ist
BGRT ALASKA A M II have recently upgraded my computer parts the last being the motherboard. I had trouble at first getting Microsoft windwos back on it but got it to work eventually. NOW after 2 months of working fine it suddenly isn't genuine.
I did the live chat thing and 'Bianca' person who I asked for help in figuring this out dismissed my issues as not having anything to do with Microsoft but the computer companies themselves then logged out of chat without solving the problem. Her last reply to me was "feel free to ask us for help again if you continue to have issues' which mine weren't even solved.
Can anyone please be more helpful?
Edit: Supposedly my key is not valid anymore and that the computer company I originally got it from is blocking the key but when I asked what that meant and who would be blocking it. Bianca gave a "I do not have that information".- Edited by Waterinu Wednesday, January 8, 2014 12:56 AM add details
Wednesday, January 8, 2014 12:53 AM
Answers
-
The problem here is that the OEM_SLP Key cannot be correlated with the BIOS SLIC table for whatever reason - but it looks to me like this is a Retail motherboard, which doesn't have a SLIC table.
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.
OEM licenses are ONLY valid on the computer with which they were supplied - and Microsoft's definition of 'a computer' for licensing purposes is the motherboard.
Your having changed the motherboard therefore invalidated the original license.
Noel Paton | Nil Carborundum Illegitemi CrashFixPC | The Three-toed Sloth No - I do not work for Microsoft, or any of its contractors. - Proposed as answer by Noel D PatonModerator Tuesday, January 14, 2014 9:38 PM
- Marked as answer by Noel D PatonModerator Saturday, January 25, 2014 11:43 AM
Saturday, January 11, 2014 12:26 AMModerator
All replies
-
I gave up and bought a retail version of windows 8.1 hope this will be a good thing. Already encountered one problem but was easily solved by prompt command.Friday, January 10, 2014 10:27 PM
-
The problem here is that the OEM_SLP Key cannot be correlated with the BIOS SLIC table for whatever reason - but it looks to me like this is a Retail motherboard, which doesn't have a SLIC table.
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.
OEM licenses are ONLY valid on the computer with which they were supplied - and Microsoft's definition of 'a computer' for licensing purposes is the motherboard.
Your having changed the motherboard therefore invalidated the original license.
Noel Paton | Nil Carborundum Illegitemi CrashFixPC | The Three-toed Sloth No - I do not work for Microsoft, or any of its contractors. - Proposed as answer by Noel D PatonModerator Tuesday, January 14, 2014 9:38 PM
- Marked as answer by Noel D PatonModerator Saturday, January 25, 2014 11:43 AM
Saturday, January 11, 2014 12:26 AMModerator