Answered by:
Windows is not Genuine after offline updates

Question
-
We have had several complaints about the "Windows Activation" "Windows is not genuine" box displaying after deploying Offline Updates this past month. My company is using a KMS server for 98% of our machines and a slim few are using our Volume MAK but all have had the same issue. I have been reading the previous posts and have used the MGADiag.exe to generate a report. I have 2 reports, one from a KMS client and one from a MAK client and they both seem to say the same thing. Your insight on this matter will greatly be appreciated.
---------------KMS---------------
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
Windows Product ID: 00371-868-0000007-85745
Windows Product ID Type: 1
Windows License Type: KMS Client
Windows OS version: 6.1.7600.2.00010100.0.0.048
ID: {C58C152B-5ADE-4B43-BBDE-758D423D750E}(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: 7600.win7_gdr.101026-1503
TTS Error:
Validation Diagnostic:
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002Windows 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 = 0x80070002OGA 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 = 0x80070002OGA 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-3Browser Data-->
Proxy settings: 10.239.53.80:8080
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: AllowedFile 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>{C58C152B-5ADE-4B43-BBDE-758D423D750E}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-GPDD4</PKey><PID>00371-868-0000007-85745</PID><PIDType>1</PIDType><SID>S-1-5-21-1301892606-2493553669-1136250554</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude E6410</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A03</Version><SMBIOSVersion major="2" minor="6"/><Date>20100528000000.000000+000</Date></BIOS><HWID>57BB3607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL </OEMID><OEMTableID>E2 </OEMTableID></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.7600.16385Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00170-868-000000-03-1033-7600.0000-0212011
Installation ID: 007204217293462901606790178921845690502846675613953756
Partial Product Key: GPDD4
License Status: Licensed
Volume activation expiration: 257820 minute(s) (179 day(s))
Remaining Windows rearm count: 1
Trusted time: 7/6/2011 8:38:30 AMKey Management Service client information
Client Machine ID (CMID): 78a869a8-ac1e-419a-8d91-87ceb56e236c
KMS machine name from DNS: hqdc05.corp.fin:1688
KMS machine extended PID: 55041-00168-313-344893-03-1033-7600.0000-0212011
Activation interval: 120 minutes
Renewal interval: 10080 minutes
KMS host caching is enabledWindows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: OAAAAAEAAgABAAIAAAACAAAABQABAAEA6GE8mlW7iIKIyN6p8N6uKVD4BNZ7YbZhrgBe0WK5XF0=OEM Activation 1.0 Data-->
N/AOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL E2
FACP DELL E2
HPET DELL E2
BOOT DELL E2
MCFG A M I GMCH945.
TCPA
SLIC DELL E2
SSDT PmRef CpuPm---------------MAK---------------
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-*****-*****-GPFM4
Windows Product Key Hash: FNUxBtfDqVaQLxr7v4ICflP3uSA=
Windows Product ID: 55041-011-1930985-86579
Windows Product ID Type: 6
Windows License Type: Volume MAK
Windows OS version: 6.1.7600.2.00010100.0.0.048
ID: {ADE3796B-B41D-4FF7-9221-3BFB1EF77EC6}(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: 7600.win7_gdr.101026-1503
TTS Error:
Validation Diagnostic:
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002Windows 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 = 0x80070002OGA 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 = 0x80070002OGA Data-->
Office Status: 100 Genuine
Microsoft Office Professional Edition 2003 - 100 Genuine
Microsoft Office Standard Edition 2003 - 100 Genuine
Microsoft Office Visio Professional 2003 - 100 Genuine
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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005Browser Data-->
Proxy settings: 10.239.53.80:8080
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: AllowedFile 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>{ADE3796B-B41D-4FF7-9221-3BFB1EF77EC6}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-011-1930985-86579</PID><PIDType>6</PIDType><SID>S-1-5-21-1678851440-335643136-3417948307</SID><SYSTEM><Manufacturer>Dell Computer Corporation</Manufacturer><Model>PowerEdge 840</Model></SYSTEM><BIOS><Manufacturer>Dell Computer Corporation</Manufacturer><Version>A08</Version><SMBIOSVersion major="2" minor="4"/><Date>20090624000000.000000+000</Date></BIOS><HWID>E3BA3607018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL </OEMID><OEMTableID>PE_SC3 </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>79EF48D5913FD00</Val><Hash>ayhlm4yJ6uzzCUu2bQTkreYdNug=</Hash><Pid>73931-640-2174687-57909</Pid><PidType>14</PidType></Product><Product GUID="{90120409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard Edition 2003</Name><Ver>11</Ver><Val>21EBE2412F12D08</Val><Hash>MO2hJ8mUe82v24teLtEFEL6RRGI=</Hash><Pid>70141-644-9372716-57845</Pid><PidType>14</PidType></Product><Product GUID="{90510409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Visio Professional 2003</Name><Ver>11</Ver><Val>321295216616D00</Val><Hash>+1fvdVO/TbtmUhS7u9WFDt+S2Is=</Hash><Pid>72085-640-3779826-55084</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="11" Result="100"/><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="19" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><App Id="44" Version="11" Result="100"/><App Id="51" Version="11" Result="100"/></Applications></Office></Software></GenuineResults>Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7600.16385Name: 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-011-193098-03-1033-7600.0000-1102011
Installation ID: 002830046055101360174031301063231265908485420691792962
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: GPFM4
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 7/6/2011 8:34:54 AMWindows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: OgAAAAIABAABAAIAAwAAAAAAAgABAAEAJJRqlWAhcv4QsU5qqnZI5HrCFKGuKUy/xJZKsyKrKCIqhQ==OEM Activation 1.0 Data-->
N/AOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL PE_SC3
FACP DELL PE_SC3
HPET DELL PE_SC3
MCFG DELL PE_SC3
SPCR DELL PE_SC3
SLIC DELL PE_SC3Wednesday, July 6, 2011 2:04 PM
Answers
-
"Ryan Cosby" wrote in message news:5612fdcf-caa5-437f-8d5d-dfa6e083e3e6...
We have had several complaints about the "Windows Activation" "Windows is not genuine" box displaying after deploying Offline Updates this past month. My company is using a KMS server for 98% of our machines and a slim few are using our Volume MAK but all have had the same issue. I have been reading the previous posts and have used the MGADiag.exe to generate a report. I have 2 reports, one from a KMS client and one from a MAK client and they both seem to say the same thing. Your insight on this matter will greatly be appreciated.
---------------KMS---------------
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
Windows Product ID: 00371-868-0000007-85745
Windows Product ID Type: 1
Windows License Type: KMS Client
Windows OS version: 6.1.7600.2.00010100.0.0.048
Other data-->
SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude E6410</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A03</Version><SMBIOSVersion major="2" minor="6"/><Date>20100528000000.000000+000</Date></BIOSLicensing Data-->
Software licensing service version: 6.1.7600.16385Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
Partial Product Key: GPDD4
License Status: Licensed
Volume activation expiration: 257820 minute(s) (179 day(s))
Remaining Windows rearm count: 1
Trusted time: 7/6/2011 8:38:30 AMKey Management Service client information
Client Machine ID (CMID): 78a869a8-ac1e-419a-8d91-87ceb56e236c
KMS machine name from DNS: hqdc05.corp.fin:1688
KMS machine extended PID: 55041-00168-313-344893-03-1033-7600.0000-0212011
Activation interval: 120 minutes
Renewal interval: 10080 minutes
KMS host caching is enabledOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL E2
FACP DELL E2
HPET DELL E2
BOOT DELL E2
MCFG A M I GMCH945.
TCPA
SLIC DELL E2
SSDT PmRef CpuPm
(I'll deal with the MAK in a separate response)The KMS license appears to be fine - although at some point it has failed validation, it is properly activated (as of around 24 hours ago), and is currently licensed.I suggest trying to validate at www.microsoft.com/genuine/validate and see what happens. - this will install the WAT Update (KB971033), the lack of which is the source of the error messages above, but not of any activation problem.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Proposed as answer by Darin Smith MS Wednesday, July 6, 2011 9:49 PM
- Marked as answer by Ryan Cosby Friday, July 8, 2011 1:20 PM
Wednesday, July 6, 2011 2:28 PMModerator -
"Ryan Cosby" wrote in message news:5612fdcf-caa5-437f-8d5d-dfa6e083e3e6...
We have had several complaints about the "Windows Activation" "Windows is not genuine" box displaying after deploying Offline Updates this past month. My company is using a KMS server for 98% of our machines and a slim few are using our Volume MAK but all have had the same issue. I have been reading the previous posts and have used the MGADiag.exe to generate a report. I have 2 reports, one from a KMS client and one from a MAK client and they both seem to say the same thing. Your insight on this matter will greatly be appreciated.
---------------MAK---------------
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-*****-*****-GPFM4
Windows Product Key Hash: FNUxBtfDqVaQLxr7v4ICflP3uSA=
Windows Product ID: 55041-011-1930985-86579
Windows Product ID Type: 6
Windows License Type: Volume MAK
Windows OS version: 6.1.7600.2.00010100.0.0.048File 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]Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
I can see why you had to use a MAK key for this machine (the broken SLIC table would account for that)Apart from that, the system appears fine - again, validation has failed at some point, but the machine is apparently currently activated fine.Same solution is suggested as for the KMS one.Darin may have more input later, when he gets in.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Proposed as answer by Darin Smith MS Wednesday, July 6, 2011 9:49 PM
- Marked as answer by Ryan Cosby Friday, July 8, 2011 1:20 PM
Wednesday, July 6, 2011 2:32 PMModerator
All replies
-
"Ryan Cosby" wrote in message news:5612fdcf-caa5-437f-8d5d-dfa6e083e3e6...
We have had several complaints about the "Windows Activation" "Windows is not genuine" box displaying after deploying Offline Updates this past month. My company is using a KMS server for 98% of our machines and a slim few are using our Volume MAK but all have had the same issue. I have been reading the previous posts and have used the MGADiag.exe to generate a report. I have 2 reports, one from a KMS client and one from a MAK client and they both seem to say the same thing. Your insight on this matter will greatly be appreciated.
---------------KMS---------------
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
Windows Product ID: 00371-868-0000007-85745
Windows Product ID Type: 1
Windows License Type: KMS Client
Windows OS version: 6.1.7600.2.00010100.0.0.048
Other data-->
SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude E6410</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A03</Version><SMBIOSVersion major="2" minor="6"/><Date>20100528000000.000000+000</Date></BIOSLicensing Data-->
Software licensing service version: 6.1.7600.16385Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
Partial Product Key: GPDD4
License Status: Licensed
Volume activation expiration: 257820 minute(s) (179 day(s))
Remaining Windows rearm count: 1
Trusted time: 7/6/2011 8:38:30 AMKey Management Service client information
Client Machine ID (CMID): 78a869a8-ac1e-419a-8d91-87ceb56e236c
KMS machine name from DNS: hqdc05.corp.fin:1688
KMS machine extended PID: 55041-00168-313-344893-03-1033-7600.0000-0212011
Activation interval: 120 minutes
Renewal interval: 10080 minutes
KMS host caching is enabledOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL E2
FACP DELL E2
HPET DELL E2
BOOT DELL E2
MCFG A M I GMCH945.
TCPA
SLIC DELL E2
SSDT PmRef CpuPm
(I'll deal with the MAK in a separate response)The KMS license appears to be fine - although at some point it has failed validation, it is properly activated (as of around 24 hours ago), and is currently licensed.I suggest trying to validate at www.microsoft.com/genuine/validate and see what happens. - this will install the WAT Update (KB971033), the lack of which is the source of the error messages above, but not of any activation problem.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Proposed as answer by Darin Smith MS Wednesday, July 6, 2011 9:49 PM
- Marked as answer by Ryan Cosby Friday, July 8, 2011 1:20 PM
Wednesday, July 6, 2011 2:28 PMModerator -
"Ryan Cosby" wrote in message news:5612fdcf-caa5-437f-8d5d-dfa6e083e3e6...
We have had several complaints about the "Windows Activation" "Windows is not genuine" box displaying after deploying Offline Updates this past month. My company is using a KMS server for 98% of our machines and a slim few are using our Volume MAK but all have had the same issue. I have been reading the previous posts and have used the MGADiag.exe to generate a report. I have 2 reports, one from a KMS client and one from a MAK client and they both seem to say the same thing. Your insight on this matter will greatly be appreciated.
---------------MAK---------------
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-*****-*****-GPFM4
Windows Product Key Hash: FNUxBtfDqVaQLxr7v4ICflP3uSA=
Windows Product ID: 55041-011-1930985-86579
Windows Product ID Type: 6
Windows License Type: Volume MAK
Windows OS version: 6.1.7600.2.00010100.0.0.048File 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]Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
I can see why you had to use a MAK key for this machine (the broken SLIC table would account for that)Apart from that, the system appears fine - again, validation has failed at some point, but the machine is apparently currently activated fine.Same solution is suggested as for the KMS one.Darin may have more input later, when he gets in.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Proposed as answer by Darin Smith MS Wednesday, July 6, 2011 9:49 PM
- Marked as answer by Ryan Cosby Friday, July 8, 2011 1:20 PM
Wednesday, July 6, 2011 2:32 PMModerator -
I suggest trying to validate at www.microsoft.com/genuine/validate and see what happens. - this will install the WAT Update (KB971033), the lack of which is the source of the error messages above, but not of any activation problem.
When looking at KB971033 I noticed something that stood out that may not work for our environment.
"Validation is an online process that enables you to verify that the copy of Windows 7 that is running on your computer is activated correctly and is genuine."
Not all of our users have internet access, due to some company policies, having said that will this tool still work? We currently have 2 KMS servers validating our clients, as you may have seen in the report. Will this validation tool use our KMS servers or will it try to phone home?Thanks for the quick responses and all of your help on this matter.
Wednesday, July 6, 2011 3:13 PM -
"Ryan Cosby" wrote in message news:1feef3af-67a2-45e6-bf8d-46c8f78923e8...I suggest trying to validate at www.microsoft.com/genuine/validate and see what happens. - this will install the WAT Update (KB971033), the lack of which is the source of the error messages above, but not of any activation problem.
When looking at KB971033 I noticed something that stood out that may not work for our environment.
"Validation is an online process that enables you to verify that the copy of Windows 7 that is running on your computer is activated correctly and is genuine."
Not all of our users have internet access, due to some company policies, having said that will this tool still work? We currently have 2 KMS servers validating our clients, as you may have seen in the report. Will this validation tool use our KMS servers or will it try to phone home?Thanks for the quick responses and all of your help on this matter.
Validation is only required under certain circumstances - such as the install of MSE or IE9 - so if the users aren't connected to the internet they shouldn't need validation, because they are not likely to hit installations that have validation as a pre-requisite.To be honest, I'm not sure where validation (as opposed to activation) takes place - Darin may be able to give details
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed SlothWednesday, July 6, 2011 3:37 PMModerator -
I agree with Noel, I don't see anything in either report that would indicate a Non-Genuine issue.
It's possible that at boot there was a Race Condition that caused a momentary Non-Genuine state that corrected itself. Windows 7 is designed to recover from a non-genuine state on the fly (Vista needed a reboot to recover fully from a non-genuine state) but it's possible that, in these instances, Windows 7 may need to a reboot to fully recover. So in addition to Noe;'s advise, I recommend rebooting (if you haven't done so already).
As to your question about Validation, not having internet access would have no negative effect on the Genuine status of Windows.
Thank you,
Darin MS- Proposed as answer by Darin Smith MS Wednesday, July 6, 2011 9:48 PM
- Unproposed as answer by Ryan Cosby Friday, July 8, 2011 1:20 PM
Wednesday, July 6, 2011 9:48 PM -
When running the Windows Activation Update tool no reboot was necessary for the system to clean itself up, but I did notice that it accessed the internet to pull updated files. I will try and test this on one of our KMS machines tomorrow before connecting to the internet and see how it reacts.
Thanks again for your time and patience.
Wednesday, July 6, 2011 10:09 PM -
I will mark Noel's responses as the answer since the Windows Activate update will correct the issues. Although since most of our users don’t have internet access, we will try and find a different solution.
Friday, July 8, 2011 1:20 PM