Answered by:
5 year old System built with OEM system builder disk now asking for validation

Question
-
Office PC left on over the weekend had a bunch of memory errors when I returned. Strange as this machine has 32GB. So I restart and a get the, "this copy of Windows is not genuine" error message. I was thinking maybe I some how got hacked until I saw this thread about validation with recent responses. Here are the results from the diagnostic tool. Please help!
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 50
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-CYB9G-B6T77-QDMK3
Windows Product Key Hash: MqA7uE3VRImvtpUIPZK0r37IGLY=
Windows Product ID: 00371-OEM-9045476-42522
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {838CAA99-AECA-4CC9-9D39-ED2FCBFD8BAE}(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.170913-0600
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: B4D0AA8B-604-645_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-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{838CAA99-AECA-4CC9-9D39-ED2FCBFD8BAE}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-QDMK3</PKey><PID>00371-OEM-9045476-42522</PID><PIDType>3</PIDType><SID>S-1-5-21-1193544348-2381054293-932372072</SID><SYSTEM><Manufacturer>BIOSTAR Group</Manufacturer><Model>TZ77XE3</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>4.6.5</Version><SMBIOSVersion major="2" minor="7"/><Date>20120823000000.000000+000</Date></BIOS><HWID>C0633307018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08: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-->
C:\Windows\system32\slmgr.vbs(1333, 5) (null): 0xC004F012
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 8:30:2017 18:11
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: MgAAAAEABAABAAEAAAACAAAAAQABAAEAhFFiqfo8/KYai2AadLi6hsgVjCb8Rd6RlmM=
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
SSDT IdeRef IdeTable
SSDT IdeRef IdeTable
SSDT IdeRef IdeTable
BGRT ALASKA A M I
- Changed type Carey FrischMVP, Moderator Tuesday, November 28, 2017 4:07 AM Question
Monday, November 27, 2017 5:47 PM
Answers
-
OK. So no replys oddly enough. So I thought I would come back with an update that worked for me.
After getting the validation nag dialog a few more times, I decided to follow the directions.
I entered the product code and voilà it worked. Every thing has been fine since. I can only speculate what went wrong.Here is my theory (I'm certain someone will correct me):
Since windows validation is tied to system hardware, I think during one of the many Windows updates I've recently run may be a hardware ID changed some how?
Making Windows think it was invalid or better stated, requiring re-validation? Not sure but everything thing is fine now.
- Marked as answer by OADesign Monday, December 11, 2017 9:43 PM
Monday, December 11, 2017 9:43 PM
All replies
-
OK. So no replys oddly enough. So I thought I would come back with an update that worked for me.
After getting the validation nag dialog a few more times, I decided to follow the directions.
I entered the product code and voilà it worked. Every thing has been fine since. I can only speculate what went wrong.Here is my theory (I'm certain someone will correct me):
Since windows validation is tied to system hardware, I think during one of the many Windows updates I've recently run may be a hardware ID changed some how?
Making Windows think it was invalid or better stated, requiring re-validation? Not sure but everything thing is fine now.
- Marked as answer by OADesign Monday, December 11, 2017 9:43 PM
Monday, December 11, 2017 9:43 PM -
A little late, but...
Here is the significant error code from the report...
C:\Windows\system32\slmgr.vbs(1333, 5) (null): 0xC004F012
This is a fairly uninformative error, but in combination with the HWID data would tend to imply file corruption.
I would suggest running a SFC /SCANNOW to check out your OS files - and possibly a SCANDISK as well.
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 Carey FrischMVP, Moderator Tuesday, December 26, 2017 7:49 PM
Sunday, December 17, 2017 1:01 PMModerator