Answered by:
Windows 7 is no longer genuine

Question
-
Hello everyone,
I recently have built 5 computers for a customer and after about 2-3 months one of the computers is reporting as not genuine.
All 5 of the of the Windows discs were bought from the same place, MaLabs.com (which is where I get most of my parts and all of my Windows through) so I don't see there being an issue with a pirated copy, but what do I know, that's why I'm here. Below is the report from the Windows Genuine Diagnostics Tool. Any help would be appreciated.
If any further information is needed I will gladly provide. Thanks.
Diagnostic Report (1.9.0027.0):
----------------------------------------- Windows Validation Data--> Validation Code: 0 Cached Online Validation Code: N/A, hr = 0xc004f012 Windows Product Key: *****-*****-*****-*****-63JBW Windows Product Key Hash: wSPDoIfEPBqlu5v2QmzwPkSxBng= Windows Product ID: 55041-007-1623655-86834 Windows Product ID Type: 6 Windows License Type: Volume MAK Windows OS version: 6.1.7601.2.00010100.1.0.048 ID: {76C14B2B-984C-41D8-A2F5-1E2EED2DD634}(1) Is Admin: Yes TestCab: 0x0 LegitcheckControl ActiveX: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows 7 Professional Architecture: 0x00000009 Build lab: 7601.win7sp1_ldr.160408-2045 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)\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--> File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003] Other data--> Office Details: <GenuineResults><MachineData><UGUID>{76C14B2B-984C-41D8-A2F5-1E2EED2DD634}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-007-1623655-86834</PID><PIDType>6</PIDType><SID>S-1-5-21-2590811111-1567108508-4293653768</SID><SYSTEM><Manufacturer>Supermicro</Manufacturer><Model>X10DAx</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>2.0</Version><SMBIOSVersion major="3" minor="0"/><Date>20160309000000.000000+000</Date></BIOS><HWID>63103507018400FA</HWID><UserLCID>340A</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific SA Standard Time(GMT-04: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, Professional edition Description: Windows Operating System - Windows(R) 7, VOLUME_MAK channel Activation ID: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 55041-00172-007-162365-03-1033-7601.0000-2392016 Installation ID: 020096048910993210945195624813905306807242975846991204 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: 63JBW License Status: Initial grace period Time remaining: 28920 minute(s) (20 day(s)) Remaining Windows rearm count: 2 Trusted time: 05-09-2016 15:17:45 Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: 0xC004C4A2 HealthStatus: 0x0000000000000000 Event Time Stamp: 8:18:2016 08:02 ActiveX: Not Registered - 0x80040154 Admin Service: Not Registered - 0x80040154 HealthStatus Bitmask Output: HWID Data--> HWID Hash Current: NgAAAAEAAgABAAEAAgACAAAAAwABAAEA2MgSNbTFsE/kJ05Q7Diyx1YW9oakVcNh5tbiq6zs 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 SRAT ALASKA A M I MSCT ALASKA A M I HPET ALASKA A M I MCFG ALASKA A M I FPDT ALASKA A M I FIDT ALASKA A M I UEFI ALASKA A M I MCEJ INTEL SLIT ALASKA A M I WDDT ALASKA A M I SSDT ALASKA PmMgt SSDT ALASKA PmMgt SSDT ALASKA PmMgt PRAD ALASKA A M I DMAR ALASKA A M I HEST ALASKA A M I BERT ALASKA A M I ERST ALASKA A M I EINJ ALASKA A M I
Tuesday, September 6, 2016 2:42 PM
Answers
-
there are only two reasons for such a change
1) a reinstall using Volume media
2) an attempt to gain some extra functions - which wouldn't happen in this case.
I'll post morr instructions when I can get to my PC!
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 Ed Price - MSFTMicrosoft employee, Owner Thursday, September 15, 2016 7:14 AM
- Marked as answer by Noel D PatonModerator Tuesday, September 27, 2016 8:05 AM
Wednesday, September 7, 2016 6:21 AMModerator
All replies
-
The installed Product Key is a Volume License Key.
As such it should not be sold to the general public, or to resellers or OEM System Builders.
It looks to me as ifthe Key has been blocked by Microsoft - probably for abuse.
Is this the Key that is on the COA sticker on the case (ending -63JBW)?
When you purchased the Windows for these machines, did it even come with COA sticker for each machine??
If the answer to the first question is 'No' then you need to find out why it was changed - and change it back again.
If the answer to the second question is 'No' then the installations are definitely counterfeit, and you will need to seek redress from the supplier.
Noel Paton | Nil Carborundum Illegitemi CrashFixPC | The Three-toed Sloth No - I do not work for Microsoft, or any of its contractors. Tuesday, September 6, 2016 4:29 PMModerator -
The COA does not end in 63JBW, and I have been sent an image by the customer showing that they have entered the correct code from their COA sticker to attempt to activate.
Not sure why the diagnostic report would show a different COA code.
But yes, all our Windows come with a COA sticker that gets placed on the side of the computer. Each COA is a different code.
Tuesday, September 6, 2016 5:20 PM -
there are only two reasons for such a change
1) a reinstall using Volume media
2) an attempt to gain some extra functions - which wouldn't happen in this case.
I'll post morr instructions when I can get to my PC!
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 Ed Price - MSFTMicrosoft employee, Owner Thursday, September 15, 2016 7:14 AM
- Marked as answer by Noel D PatonModerator Tuesday, September 27, 2016 8:05 AM
Wednesday, September 7, 2016 6:21 AMModerator