Windows 7 Build 7601 this copy of Windows is not genuine.

Hujahmahflip · 12 Dec 2012

A gaming rig I built up last year just popped up with this little error a couple days ago. After a little googling about it I was brought here, and it seems I'm far from the only one with this issue. Going to the microsoft website to validate states that the key for my product is in use or has been locked.

Here is my WGADiag.exe info :

Code:

 
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 50
Cached Online Validation Code: 0xc004c4a2
Windows Product Key: *****-*****-6B7VY-HCP6P-JPCDT
Windows Product Key Hash: /jNj5IBqhpqckmafkXRxyxwN/1w=
Windows Product ID: 00426-068-4500804-86048
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {F0D1C17C-2BE0-4183-BCB2-795011BCFCED}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120830-0333
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>{F0D1C17C-2BE0-4183-BCB2-795011BCFCED}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-JPCDT</PKey><PID>00426-068-4500804-86048</PID><PIDType>5</PIDType><SID>S-1-5-21-3330503127-3747116357-4256512668</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>X58A-UD3R</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>FB</Version><SMBIOSVersion major="2" minor="4"/><Date>20100824000000.000000+000</Date></BIOS><HWID>B2073B07018400FE</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/><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, Ultimate edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: a0cde89c-3304-4157-b61c-c8ad785d1fad
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00172-068-450080-00-2057-7600.0000-1572012
Installation ID: 016242001530053112215243675234527094783684327161516353
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: JPCDT
License Status: Notification
Notification Reason: 0xC004F200 (non-genuine).
Remaining Windows rearm count: 4
Trusted time: 12/12/2012 11:16:21
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0xC004C4A2
HealthStatus: 0x0000000000000000
Event Time Stamp: 12:4:2012 10:05
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:

HWID Data-->
HWID Hash Current: PgAAAAIABgABAAEAAgADAAAAAQABAAEAonZEj2RdQE+Uigw15L9GvIQ0agNev5zWfIfCj1gpv/lRWwrN6oI=
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   GBT     GBTUACPI
  FACP   GBT     GBTUACPI
  HPET   GBT     GBTUACPI
  MCFG   GBT     GBTUACPI
  EUDS   GBT     
  MATS   GBT     
  TAMG   GBT     GBT   B0
  SSDT   INTEL  PPM RCM

I can't think of anything else noteworthy to add at the moment, but if any additional info is needd I'll get it asap. Thanks in advance for the help.

NoelDP · 12 Dec 2012

The Key in use is an MSDN Key from a not-for-resale MSDN account.
Unless you are an MSDN subscriber, you are not entitled to use the Key – and whoever sold it to you was not entitled to do so.
You need to claim an immediate refund from the vendor - do NOT accept the offer of a new key (all they are trying to do is to get past the 45-day claims window or avoid you sending the evidence of their crimes to the authorities)

Please read the following posts.... .................................

http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/a2444f34-0aff-4f29-a8ac-67e28b0c0285

and

http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/309bb621-92d5-43d6-98c1-2bb51b35607f

The pirates have got VERY good at this over the past few years, as the price of equipment for manufacturing the packages drops, and as factories open in less well-policed countries.

see also this post....

http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/46a58748-5a64-41ff-b7f4-f6d3b47beca9

Also - have a look at this video....

http://www.youtube.com/watch?v=hzqNNiOM0cs

Hujahmahflip · 12 Dec 2012

Thanks for the blazingly quick response, even if it isnt particulary good news.

This is very worrying considering I bought this way back in the middle of last year...I think...and what makes it more concerning is that I've been able to use it for this long without a hitch.

I will read over all of the info you have linked and report back here when I can. Is there anything else you would recommend I can do?

NoelDP · 12 Dec 2012

You may be able to get a complementary replacement - report the piracy at How to Tell - Home and see what they say.

Here's my standard spiel on the time-delays involved in tagging abused keys....

For MSDN Keys:- MS can only act once a key hits a threshold (and they won't tell an outsider what that threshold is, understandably). They then have to put it through internal systems to ensure that all relevant parties are informed, just in case it's an oversight - then it enters the queue for the next update to the system.
I have no idea how often the WAT checking system is updated, but I would suspect that it's no more than weekly because of admin and timing issues. The internal MS processes could therefore take easily a couple of months. It therefore depends on how close to the end of a vendors sales list you are, and how quickly he's selling them.
The cannier ones will sell just enough to stay under the threshold for each product (MSDN subs include a huge number of products), until they've maximised the profits, then try and flood the market before disappearing into the sunset, laden with your cash.
This could take anything up to a year or more.

For products sold using a loader:- The loader gets around online activation by fooling the computer into thinking that the OS is installed onto the correct machine, by modifying certain files.
Because of a number of factors, it's impossible to stop this, so MS came up with the WAT update - which has the ability to scan the relevant files, and detect the use of a loader tool. If the user fully updates the machine, including recommended updates and optional updates, then the WAT update is installed and starts work, and within 3 days, a loader-installed machine will get a notification.
However, the WAT update is a voluntary one, at least at the first update run, and can be uninstalled or refused. The other time the WAT update is installed is when you validate Windows for some reason - it is part of the validation process, rather than the activation process. This time, it does the scan immediately, and again this will show as non-genuine if a Loader is present. If a user never needs/wants to validate, then they need never install the WAT update, and may never see a non-genuine notification.