Diagnostic Report (1.9.0027.0):
Causes and resolutions 0x8004FE21 This computer is not running genuine Windows Possible cause. This issue can occur for several reasons. The most likely reason is that language packs (MUI) have been installed on computers that are running Windows editions that are not licensed for additional language packs. Not genuine windows popup - posted in Windows 7: yesterday i started getting a popup coming up telling me im not running a genuine windows operating system, but its the same one the laptop came. Windows 7 hit by rash of bogus 'not genuine' reports, validation code 0x8004FE21 Windows 7 is suddenly telling users it isn't genuine - and it has nothing to do with Windows being stolen. Outlook 2010 Check for New Mail Frequency Find the Options menu by launching Outlook 2010, clicking the File tab at the top-left corner. Feb 09, 2015 Install this update to resolve issues in Windows. Download Update for Windows 7 for x64-based Systems (KB3004394) from Official Microsoft Download Center.
-----------------------------------------
Windows Validation Data-->
Validation Code: 0x8004FE21
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-MGV6H-XCF6R-F76B4
Windows Product Key Hash: kW/nY6iVDksk/0m8t6X1dh337Lc=
Windows Product ID: 00426-293-2665036-85616
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {557F9A92-1D5B-41B2-B147-450A8B8AF27C}(1)
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.140303-2144
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: 114 Blocked VLK 2
Microsoft Office Professional Edition 2003 - 114 Blocked VLK 2
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_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 Firefoxfirefox.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:Windowssystem32sppobjs.dll[6.1.7601.17514], Hr = 0x80092003
File Mismatch: C:Windowssystem32sppc.dll[6.1.7601.17514], Hr = 0x800b0100
File Mismatch: C:Windowssystem32sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:Windowssystem32sppwinob.dll[6.1.7601.17514], Hr = 0x80092003
File Mismatch: C:Windowssystem32en-USslc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:Windowssystem32slcext.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:Windowssystem32sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003
File Mismatch: C:Windowssystem32slui.exe[6.1.7601.17514], Hr = 0x80092003
File Mismatch: C:Windowssystem32sppcomapi.dll[6.1.7601.17514], Hr = 0x800b0100
File Mismatch: C:Windowssystem32sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:Windowssystem32sppsvc.exe[6.1.7601.17514], Hr = 0x80092003
File Mismatch: C:Windowssystem32driversspsys.sys[6.1.7127.0], Hr = 0x80092003
File Mismatch: C:Windowssystem32driversspldr.sys[6.1.7127.0], Hr = 0x80092003
File Mismatch: C:Windowssystem32systemcpl.dll[6.1.7601.17514], Hr = 0x800b0100
File Mismatch: C:Windowssystem32user32.dll[6.1.7601.17514], Hr = 0x800b0100
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{557F9A92-1D5B-41B2-B147-450A8B8AF27C}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-F76B4</PKey><PID>00426-293-2665036-85616</PID><PIDType>5</PIDType><SID>S-1-5-21-674461134-2442528559-3055296478</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv6 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.04</Version><SMBIOSVersion major='2' minor='6'/><Date>20090910000000.000000+000</Date></BIOS><HWID>5DD63907018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>114</Result><Products><Product GUID='{90110409-6000-11D3-8CFE-0150048383C9}'><LegitResult>114</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>59D1605114E3500</Val><Hash>vfZmaSmFPIYrLWTcZSZErUQg+Fo=</Hash><Pid>73931-640-0000106-57418</Pid><PidType>14</PidType></Product></Products><Applications><App Version='11' Result='114'/><App Version='11' Result='114'/><App Version='11' Result='114'/><App Version='11' Result='114'/><App Version='11' Result='114'/><App Version='11' Result='114'/><App Version='11' Result='114'/></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: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00170-293-266503-00-1033-7601.0000-0012015
Installation ID: 018992525332651036319471699250017943969276087130702473
Processor Certificate URL: http://go.microsoft.com/fwlink/?Lin...
Machine Certificate URL: http://go.microsoft.com/fwlink/?Lin...
Use License URL: http://go.microsoft.com/fwlink/?Lin...
Product Key Certificate URL: http://go.microsoft.com/fwlink/?Lin...
Partial Product Key: F76B4
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 1/20/2015 10:16:25 AM
Windows Activation Technologies-->
HrOffline: 0x8004FE21
HrOnline: N/A
HealthStatus: 0x000000000001EFF0
Event Time Stamp: 1:15:2015 11:08
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
Tampered File: %systemroot%system32sppobjs.dll
Tampered File: %systemroot%system32sppc.dll|sppc.dll.mui
Tampered File: %systemroot%system32sppcext.dll|sppcext.dll.mui
Tampered File: %systemroot%system32sppwinob.dll
Tampered File: %systemroot%system32slc.dll|slc.dll.mui
Tampered File: %systemroot%system32slcext.dll|slcext.dll.mui
Tampered File: %systemroot%system32sppuinotify.dll|sppuinotify.dll.mui
Tampered File: %systemroot%system32slui.exe|slui.exe.mui|COM Registration
Tampered File: %systemroot%system32sppcomapi.dll|sppcomapi.dll.mui
Tampered File: %systemroot%system32sppcommdlg.dll|sppcommdlg.dll.mui
Tampered File: %systemroot%system32sppsvc.exe|sppsvc.exe.mui
Tampered File: %systemroot%system32driversspsys.sys
HWID Data-->
HWID Hash Current: MAAAAAEAAQABAAEAAAACAAAAAwABAAEAln02PV4R0FoousKPyiw6FZTIuO5UF3ZW
OEM Activation 1.0 Data-->
N/A
OEM 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 HPQOEM SLIC-MPC
FACP HPQOEM SLIC-MPC
HPET HPQOEM SLIC-MPC
BOOT HPQOEM SLIC-MPC
MCFG HPQOEM SLIC-MPC
ASF! HPQOEM SLIC-MPC
SLIC HPQOEM SLIC-MPC
ASPT HPQOEM SLIC-MPC
SSDT PmRef CpuPm
Note
This article is intended for technical support agents and IT professionals. If you're looking for more information about Windows activation error messages, see Get help with Windows activation errors.
This article provides troubleshooting information to help you respond to error messages that you may receive when you try to use a Multiple Activation Key (MAK) or the Key Management Service (KMS) to perform Volume Activation on one or more Windows-based computers. Look for the error code in the following table, and then select the link to see more information about that error code and how to resolve it.
For more information about volume activation, see Plan for volume activation.
For more information about volume activation for current and recent versions of Windows, see Volume Activation [client].
For more information about volume activation for older versions of Windows, see KB 929712, Volume Activation information for Windows Vista, Windows Server 2008, Windows Server 2008 R2 and Windows 7.
Diagnostic tool
Note
This tool is intended to help fix Windows activation problems on computers that run Enterprise, Professional, or Server edition of Windows.
Microsoft Support and Recovery Assistant (SaRA) simplifies Windows KMS Activation troubleshooting. Download the diagnostic tool from here.
This tool will try to activate Windows. If it returns an activation error code, the tool will display targeted solutions for known error codes.
The following error codes are supported: 0xC004F038, 0xC004F039, 0xC004F041, 0xC004F074, 0xC004C008, 0x8007007b, 0xC004C003, 0x8007232B.
Summary of error codes
| Error code | Error message | Activation type |
|---|---|---|
| 0x8004FE21 | This computer is not running genuine Windows. | MAK KMS client |
| 0x80070005 | Access denied. The requested action requires elevated privileges. | MAK KMS client KMS host |
| 0x8007007b | 0x8007007b DNS name does not exist. | KMS client |
| 0x80070490 | The product key you entered didn't work. Check the product key and try again, or enter a different one. | MAK |
| 0x800706BA | The RPC server is unavailable. | KMS client |
| 0x8007232A | DNS server failure. | KMS host |
| 0x8007232B | DNS name does not exist. | KMS client |
| 0x8007251D | No records found for DNS query. | KMS client |
| 0x80092328 | DNS name does not exist. | KMS client |
| 0xC004B100 | The activation server determined that the computer could not be activated. | MAK |
| 0xC004C001 | The activation server determined the specified product key is invalid | MAK |
| 0xC004C003 | The activation server determined the specified product key is blocked | MAK |
| 0xC004C008 | The activation server determined that the specified product key could not be used. | KMS |
| 0xC004C020 | The activation server reported that the Multiple Activation Key has exceeded its limit. | MAK |
| 0xC004C021 | The activation server reported that the Multiple Activation Key extension limit has been exceeded. | MAK |
| 0xC004F009 | The Software Protection Service reported that the grace period expired. | MAK |
| 0xC004F00F | The Software Licensing Server reported that the hardware ID binding is beyond level of tolerance. | MAK KMS client KMS host |
| 0xC004F014 | The Software Protection Service reported that the product key is not available | MAK KMS client |
| 0xC004F02C | The Software Protection Service reported that the format for the offline activation data is incorrect. | MAK KMS client |
| 0xC004F035 | The Software Protection Service reported that the computer could not be activated with a Volume license product key. | KMS client KMS host |
| 0xC004F038 | The Software Protection Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator. | KMS client |
| 0xC004F039 | The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) is not enabled. | KMS client |
| 0xC004F041 | The Software Protection Service determined that the Key Management Server (KMS) is not activated. KMS needs to be activated. | KMS client |
| 0xC004F042 | The Software Protection Service determined that the specified Key Management Service (KMS) cannot be used. | KMS client |
| 0xC004F050 | The Software Protection Service reported that the product key is invalid. | MAK KMS KMS client |
| 0xC004F051 | The Software Protection Service reported that the product key is blocked. | MAK KMS |
| 0xC004F064 | The Software Protection Service reported that the non-genuine grace period expired. | MAK |
| 0xC004F065 | The Software Protection Service reported that the application is running within the valid non-genuine period. | MAK KMS client |
| 0xC004F06C | The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) determined that the request timestamp is invalid. | KMS client |
| 0xC004F074 | The Software Protection Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information. | KMS client |
Causes and resolutions
0x8004fe21 Fix
0x8004FE21 This computer is not running genuine Windows
Possible cause
This issue can occur for several reasons. The most likely reason is that language packs (MUI) have been installed on computers that are running Windows editions that are not licensed for additional language packs.
Note
This issue is not necessarily an indication of tampering. Some applications can install multi-lingual support even when that edition of Windows is not licensed for those language packs.)
This issue may also occur if Windows has been modified by malware to allow additional features to be installed. This issue may also occur if certain system files are corrupted.
Resolution
To resolve this issue, you must reinstall the operating system.
0x80070005 Access denied
Windows Genuine Validation Error 0x8004fe21
The full text of this error message resembles the following:
Access denied. The requested action requires elevated privileges.
Possible cause
User Account Control (UAC) prohibits activation processes from running in a non-elevated Command Prompt window.
Resolution
Run slmgr.vbs from an elevated command prompt. To do this, on the Start menu, right-click cmd.exe, and then select Run as administrator.
0x8007007b DNS name does not exist
Possible cause
This issue may occur if the KMS client cannot find the KMS SRV resource records in DNS.
Resolution
For more information about troubleshooting such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.
0x80070490 The product key you entered didn't work
The full text of this error resembles the following:
The product key that you entered didn't work. Check the product key and try again, or enter a different one.
Possible cause
This issue occurs because the MAK that was entered was not valid, or because of a known issue in Windows Server 2019.
Resolution
To work around this issue and activate the computer, run slmgr -ipk <5x5 key> at an elevated command prompt.
0x800706BA The RPC server is unavailable
Possible cause
Firewall settings are not configured on the KMS host, or DNS SRV records are stale.
Resolution
On the KMS host, make sure that a firewall exception is enabled for the Key Management Service (TCP port 1688).
Make sure that the DNS SRV records point to a valid KMS host.
Troubleshoot network connections.
For more information about troubleshooting such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.
0x8007232A DNS server failure
Possible cause
The system has network or DNS issues.
Resolution
Troubleshoot network and DNS.
0x8007232B DNS name does not exist
Possible cause
The KMS client cannot find KMS server resource records (SRV RRs) in DNS.
Resolution
Verify that a KMS host has been installed and DNS publishing is enabled (default). If DNS is unavailable, point the KMS client to the KMS host by using slmgr.vbs /skms <kms_host_name>.
If you do not have a KMS host, obtain and install an MAK. Then, activate the system.
For more information about troubleshooting such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.
0x8007251D No records found for DNS query
Possible cause
The KMS client cannot find KMS SRV records in DNS.
Resolution
Troubleshoot network connections and DNS. For more information about how to troubleshoot such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.
0x80092328 DNS name does not exist
Possible cause
This issue may occur if the KMS client cannot find the KMS SRV resource records in DNS.
Resolution
For more information about troubleshooting such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.
0xC004B100 The activation server determined that the computer could not be activated
Possible cause
The MAK is not supported.
Resolution
To troubleshoot this issue, verify that the MAK that you are using is the MAK that was provided by Microsoft. To verify that the MAK is valid, contact the Microsoft Licensing Activation Centers.
0xC004C001 The activation server determined the specified product key is invalid
Possible cause
The MAK that you entered is not valid.
Resolution
Verify that the key is the MAK that was provided by Microsoft. For additional assistance, contact the Microsoft Licensing Activation Centers.
0xC004C003 The activation server determined the specified product key is blocked
Possible cause
The MAK is blocked on the activation server.
Resolution
To obtain a new MAK, contact the Microsoft Licensing Activation Centers. After you obtain the new MAK, try installing and activating Windows again.
0xC004C008 The activation server determined that the specified product key could not be used
Possible cause
The KMS key has exceeded its activation limit. A KMS host key can be activated up to 10 times on up to six different computers.
Resolution
If you require additional activations, contact the Microsoft Licensing Activation Centers.
0xC004C020 The activation server reported that the Multiple Activation Key has exceeded its limit
Possible cause
The MAK has exceeded its activation limit. By design, MAKs can be activated a limited number of times.
Resolution
If you require additional activations, contact the Microsoft Licensing Activation Centers.
0xC004C021 The activation server reported that the Multiple Activation Key extension limit has been exceeded
Possible cause
The MAK has exceeded its activation limit. By design, MAKs activate a limited number of times.
Resolution
If you need additional activations, contact the Microsoft Licensing Activation Centers.
0xC004F009 The Software Protection Service reported that the grace period expired
Possible cause
The grace period expired before the system was activated. Now, the system is in the Notifications state.
Resolution
For assistance, contact the Microsoft Licensing Activation Centers.
0xC004F00F The Software Licensing Server reported that the hardware ID binding is beyond level of tolerance
Possible cause
The hardware has changed or the drivers were updated on the system.
Resolution
If you are using MAK activation, use either online or phone activation to reactivate the system during the OOT grace period.
If you are using KMS activation, restart Windows or run slmgr.vbs /ato.
0xC004F014 The Software Protection Service reported that the product key is not available
Possible cause
No product keys are installed on the system.
Resolution
If you are using MAK activation, install a MAK product key.
If you are using KMS activation, check the Pid.txt file (located on the installation media in the sources folder) for a KMS Setup key. Install the key.
0xC004F02C The Software Protection Service reported that the format for the offline activation data is incorrect
Possible cause
The system has detected that the data entered during phone activation is not valid.
Resolution
Verify that the CID is entered correctly.
0xC004F035 Invalid Volume License Key
The full text of this error message resembles the following:
Error: Invalid Volume License Key. In order to activate, you need to change your product key to a valid Multiple Activation Key (MAK) or Retail key. You must have a qualifying operating system license AND a Volume license Windows 7 upgrade license, or a full license for Windows 7 from a retail source. ANY OTHER INSTALLATION OF THIS SOFTWARE IS IN VIOLATION OF YOUR AGREEMENT AND APPLICABLE COPYRIGHT LAW.
The error text is correct, but is ambiguous. This error indicates that the computer is missing a Windows marker in its BIOS that identifies it as an OEM system that is running a qualifying edition of Windows. This information is required for KMS client activation. The more specific meaning of this code is 'Error: Invalid Volume License Key'
Possible cause
Windows 7 Volume editions are licensed only for upgrade. Microsoft does not support installing a Volume operating system on a computer that does not have a qualifying operating system installed.
Resolution
In order to activate, you need to do one of the following:
- Change your product key to a valid Multiple Activation Key (MAK) or Retail key. You must have a qualifying operating system license AND a Volume license Windows 7 upgrade license, or a full license for Windows 7 from a retail source.
Note
If you receive error 0x80072ee2 when you attempt to activate, use the phone activation method that follows instead.
- Activate by phone by following these steps:
- Run slmgr /dti and then record the value of the Installation ID.
- Contact the Microsoft Licensing Activation Centers and provide the Installation ID in order to receive a Confirmation ID.
- To activate by using the Confirmation ID, run slmgr /atp <Confirmation ID>.
0xC004F038 The count reported by your Key Management Service (KMS) is insufficient
The full text of this error message resembles the following:
The Software Protection Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.
Possible cause
The count on the KMS host is not high enough. For Windows Server, the KMS count must be greater than or equal to 5. For Windows (client), the KMS count must be greater than or equal to 25.
Resolution
Before you can use KMS to activate Windows, you must have more computers in the KMS pool. To obtain the current count on the KMS host, run Slmgr.vbs /dli.
0xC004F039 The Key Management Service (KMS) is not enabled
The full text of this error message resembles the following:
The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) is not enabled.
Possible cause
KMS did not respond to the KMS request.
Resolution
Troubleshoot the network connection between the KMS host and the client. Make sure that TCP port 1688 (default) is not blocked by a firewall or is otherwise filtered.
0xC004F041 The Software Protection Service determined that the Key Management Server (KMS) is not activated
The full text of this error message resembles the following:
The Software Protection Service determined that the Key Management Server (KMS) is not activated. KMS needs to be activated.
Possible cause
The KMS host is not activated.
Resolution
Activate the KMS host by using either online or telephone activation.
0xC004F042 The Software Protection Service determined that the specified Key Management Service (KMS) cannot be used
Possible cause
This error occurs if the KMS client contacted a KMS host that could not activate the client software. This can be common in mixed environments that contain application-specific and operating system-specific KMS hosts, for example.
Resolution
Make sure that if you use specific KMS hosts to activate specific applications or operating systems, the KMS clients connect to the correct hosts.
0xC004F050 The Software Protection Service reported that the product key is invalid
Possible cause
This can be caused by a typo in the KMS key or by typing in a Beta key on a Released version of the operating system.
Resolution
Install the appropriate KMS key on the corresponding version of Windows. Check the spelling. If the key is being copied and pasted, make sure that em-dashes were not substituted for the hyphens in the key.
0xC004F051 The Software Protection Service reported that the product key is blocked
Possible cause
The activation server determined that Microsoft has blocked the product key.
Resolution
Obtain a new MAK or KMS key, install it on the system, and activate.
0xC004F064 The Software Protection Service reported that the non-genuine grace period expired
Possible cause
Windows Activation Tools (WAT) has determined that the system is not genuine.
Resolution
For assistance, contact the Microsoft Licensing Activation Centers.
0xC004F065 The Software Protection Service reported that the application is running within the valid non-genuine period
Possible cause
Windows Activation Tools has determined that the system is not genuine. The system will continue to run during the Non-Genuine grace period.
Resolution
Obtain and install a genuine product key, and activate the system during the grace period. Otherwise, the system will go into the Notifications state at the end of the grace period.
0xC004F06C The request timestamp is invalid
The full text of this error message resembles the following:
The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) determined that the request timestamp is invalid.
Possible cause
The system time on the client computer is too different from the time on the KMS host. Time sync is important to system and network security for a variety of reasons.
Resolution
Fix this issue by changing the system time on the client to sync with the KMS host. We recommend that you use a Network Time Protocol (NTP) time source or Active Directory Domain Services for time synchronization. This issue uses UTP time and does not depend on Time Zone selection.
0xC004F074 No Key Management Service (KMS) could be contacted
The full text of this error message resembles the following:
The Software Protection Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.
Possible cause
All of the KMS host systems returned an error.
Resolution
In the Application Event Log, identify each event that has Event ID 12288 and is associated with the activation attempt. Troubleshoot the errors from these events.
For more information about troubleshooting DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.