Activated fine for one year, now suddenly not genuine

[ChuckBradley]

I built a computer and activated Windows 7 Pro on it. I used it occasionally for about one year, with no difficulties. Then I made some hardware changes. I added a solid state disk and moved the OS to it. I removed several small HDs that I had used only to verify that all the ports on the MB worked. I added a 2TB disk. A few hours or days later I got the black screen and the not genuine messages.

I have tried several means to make the system appear appear legal to MS, including some from here. They all seem to be doing something, but all end with error code C004E003, licensing service reported that license evaluation failed.

I suspect that the source of the W7pro software is related to this problem, perhaps as a cause, but at least as a complication. I bought it on eBay from someone that claimed he put Linus on his new Dell
computer without ever booting the W7pro that was installed at Dell. Before buying, I checked on the web and that seemed to be a fairly common and legal approach. The DVD arrived in a sealed envelope with a Dell bar code and part number. A smaller sealed envelope attached to it had the license key inside.

After trying all the claimed fixes I could find, I called Microsoft Activation center at 888-352-7140. They admit it is MS software that set the bit in a DB that causes C004E003. They either can not, or will not tell me what is wrong that caused the bit to be set. They also say that only Dell can unset the bit.

So I called Dell. I talked to people at four different support groups. It was difficult to get them to understand that I did not buy anything from Dell. Even after they accepted I was not a customer, they were still polite and seemed to be trying to help. Apparently, nobody at Dell can take a 25 character product license key and find out if it is actually from Dell, known to be fake, used more than once, or anything.

Can you tell if the OS is fake, or offer any other help.

Thanks very much.

Diagnostic Report (1.9.0019.0):
-----------------------------------------
WGA Data-->
Validation Status: Genuine
Validation Code: 0

Cached Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-BYTP3-JWB98-9J64J
Windows Product Key Hash: w7ErUSvGp2X5cHY89l2sma7bo6w=
Windows Product ID: 00371-OEM-8992671-00211
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {D4EA2ECC-5DF9-438B-B887-71A73A79E426}(3)
Is Admin: Yes
TestCab: 0x0
WGA Version: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.151019-1254
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

WGA 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)\Mozilla Firefox\firefox.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 = 0x80070002]
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[hr = 0x80070002]
File Mismatch: C:\Windows\system32\wat\watux.exe[hr = 0x80070002]
File Mismatch: C:\Windows\system32\wat\watweb.dll[hr = 0x80070002]

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{D4EA2ECC-5DF9-438B-B887-71A73A79E426}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-9J64J</PKey><PID>00371-OEM-8992671-00211</PID><PIDType>2</PIDType><SID>S-1-5-21-4094212397-924725953-2029785017</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1801</Version><SMBIOSVersion major="2" minor="7"/><Date>20130228000000.000000+000</Date></BIOS><HWID>E7533207018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05: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, OEM_SLP channel
Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00178-926-700211-02-1033-7601.0000-2062016
Installation ID: 001275723781846873950111644325211111535830675351787451
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: 9J64J
License Status: Initial grace period
Time remaining: 40140 minute(s) (27 day(s))
Remaining Windows rearm count: 2
Trusted time: 7/26/2016 3:57:07 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0xC004C533
HealthStatus: PASS
Event Time Stamp: 7:8:2016 17:48
WAT Activex: Not Registered - 0x80040154
WAT Admin Service: Not Registered - 0x80040154

HWID Data-->
HWID Hash Current: LgAAAAIAAQABAAEAAQABAAAAAQABAAEAHKL6v0AuTjQKUzyi7kLeiLKCogiWYw==

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            SataRe        SataTabl
  BGRT            ALASKA        A M I
  SSDT            SataRe        SataTabl
  SSDT            SataRe        SataTabl

 

[torchwood]

Hi Chuck,

Sorry to be the bearer of bad news but its a non-genuine install, you were sold a pup

Your very first words "i built a computer"
Means that the only types of product key you can use legitamately are
OEM System Builder
Retail

You have a OEM only key, for use solely on Factory built models.
The product ID data, i believe, was for use on demo machines.

MS picked it up as non genuine when you started swapping your HDD's/SSD's
There is no way you can check to see if a 25 character key is genuine or not UNTIL its been on a comp for roughly 90 days, when MS performs a major genuine check.
The slmgr/rearm you used will only work another 2 times.

Roy

 

[ChuckBradley]

Thanks for the info, even if it is bad news. So I went looking to buy a valid license, or kit with license. I did not find any retail kits, but there are lots of system builder kits available. Does it make any difference where I get one from. One seller claims a system builder kit can go through many system builder's hands before it goes into a system, but I can not find any confirmation of that at Microsoft.com. I don't want to make the same kind of mistake again.

 

[Layback Bear]

One System Builder OEM COA key will only work legal on the first system it is installed and activated on.
It is tied to the motherboard in that system.

You can not buy a legal Windows 7 COA key by itself. It must come with a media; example DVD.

If you can try and buy Windows 7 from a reputable local dealer. That way if you have a problem it can be taken care of.