0xc004d302 Slui.exe 0x2a 0xc004d302 Microsoft Windows Core.

agencypowerup.netlify.com › ★ 0xc004d302 Slui.exe 0x2a 0xc004d302 Microsoft Windows Core. ★

0xc004d302 Slui.exe 0x2a 0xc004d302 Microsoft Windows Core. Posted on 6/6/2019 by admin agencypowerup.netlify.com › ★ 0xc004d302 Slui.exe 0x2a 0xc004d302 Microsoft Windows Core. Apr 22, 2015 Windows 2012 is based on the same core as Windows 8 - and doesn't use the same licensing protection system as Windows 7 I don't have a Win 8/Server 2012 system handy, but if you run the licensingdiag tool, it will produce a report similar to the MGADiag one.

0xc004d302 Slui.exe 0x2a 0xc004d302 Microsoft Windows Core.

Symptoms :

On already activated KMS client a Windows Activation window comes up with the error

An error has occurred:

Code: 0xC004D302

Description: The Security processor reported that the trusted data store was rearmed.

Cause :

1. Changes in the default permissions of the 'C:ProgramDataMicrosoftCryptoRSAMachineKeys' .

2. Corruption in the Licensing Files. (tokens.dat)

3. If you have run the slmgr.vbs /rearm command and try to run any other activation command(/dlv or /dli for example) prior to rebooting you will experience this error. You must reboot after using the slmgr.vbs /rearm command prior to attempting activation.

Resolution:

1. Change the directory on the command prompt by typing in

(For Vista and Windows 2008)

cd '%windir%ServiceProfilesNetworkServiceAppDataRoamingMicrosoftSoftwareLicensing'

(For Win 7 and Windows 2008 R2)

cd '%windir%ServiceProfilesNetworkServiceAppDataRoamingMicrosoftSoftwareProtectionPlatform'

2. Backupy tokens.dat to tokens.old by typing the command and copy the token.dat from activated machine.

ren tokens.dat tokens.old

3. Activated using slmgr command by typing in

- slmgr –ato (using Internet)

- slui.exe -4 (using telephone)

I am trying to activate MS Server 2012 R2 Standard and I'm having issues.

I have installed the software from the ISO file I downloaded from the volume licensing site. I have learned that this file installs a KMS client version of the software by default. I have both KMS and MAK keys for this software but since I'm only installing 2 instances of the software, MAK makes the most sense to me. I don't have a KMS host running on my network so I need to use MAK client. However, I cannot get my MAK keys to work when I run a powershell command such as slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx. I always get the same result which is an error message 0xc004e016 - on a computer running ms windows non-core edition, run slui.exe to display the error text.

Basically, its telling me that it doesn't like the license code. So, is there a separate ISO file for MAK client installations or is there a way to convert this KMS client to a MAK client. There is some documentation on this on google but they did not work. Just received the same error message. Can anyone offer some assistance for this issue? Calls to MS support have so far provided no help.

DecaDeca

5 Answers

Slui.exe 0x2a 0xc004d302

The reason you can't activate it is because you are not connected to the internet. I learn it the hard way. 2012 R2's error is very generic. When you put the license key, it try active the license right way. Because you dont have internet, it cant verify it.

Here is for anyone who try activate over phone on machine that has no internect connection.

Here is the trick I finally figured out.

You can't activate windows by phone because you have not put in the correct product key number. Here are the steps and I was able to activate over the phone. I have not see any one post these steps yet. I spent 4 days with Microsoft trying to get some helps. With other user's input and I was able to put together the complete steps.

1.To Change Product Key Number in a Command Prompt Open an elevated command prompt. In the elevated command prompt, type in the command below and press enter.

NOTE: Substitute XXXXX-XXXXX-XXXXX-XXXXX-XXXXX in this command below with your actual product key number with dashes instead. slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

2.type slui.exe 4 to access the phone activation screen and follow the steps to activate over the phone.

Ok, I went back to MS Volume Licensing and downloaded the ISO file again for MS Server 2012r2 and I noticed that it was different that the one that I had previously installed. I reinstalled this OS on the server and my MAK key worked this time. So all is good again. Thank you for your input.

Darrell

DecaDeca

I created an account just to answer this question. I just ran into this issue, and when I figured out the fix, I realized that I had run into this before.

SET YOUR CLOCK.

That's it. For some reason Server 2012 R2 doesn't seem to sync up with an outside source at all, so until you set it manually, you're going to be off and activation and checking for updates won't work. For my install today the system thought it was November 2014 - 11 months ago!

The ISO is the same - it will accept the MAK key, or let you use KMS.

Make sure you aren't accidentally using the KMS key - that needs to be installed on a KMS server and won't work directly. Also make sure you installed the correct version of Server 2012R2 - some ISOs give you the option to install Standard or Datacenter, but the license key from one will not work on the other.

Also double check that you typed (or preferably copy/pasted) the key correctly - didn't mix up an 8 for a B, etc.

If that still fails, the easiest thing to do would be to install the GUI and activate it through the GUI, since you'll be able to see the full error messages easily. One of the nice things about Server 2012 is you can add and remove the GUI at any time.

If it still fails, you'll have to call Microsoft support for them to verify the license key is correct or issue you a new one. Contacting wherever you bought the volume license may be easier than calling Microsoft directly - they may know who best to call to handle licensing issues.

GrantGrant

This can happen if you have no internet through the client firewall.

Even though the server looked like it had internet, because it could reach the DNS servers. Internet traffic was being blocked by the firewall the client had in place. Once the policy allowed the IP out, activation completed successfully.

John FlintJohn Flint

protected by CommunityOct 21 '15 at 13:56

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged windows-server-2012-r2 or ask your own question.

-->

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 codeError messageActivation type
0x8004FE21This computer is not running genuine Windows.MAK
KMS client
0x80070005Access denied. The requested action requires elevated privileges.MAK
KMS client
KMS host
0x8007007b0x8007007b DNS name does not exist.KMS client
0x80070490The product key you entered didn't work. Check the product key and try again, or enter a different one.MAK
0x800706BAThe RPC server is unavailable.KMS client
0x8007232ADNS server failure.KMS host
0x8007232BDNS name does not exist.KMS client
0x8007251DNo records found for DNS query.KMS client
0x80092328DNS name does not exist.KMS client
0xC004B100The activation server determined that the computer could not be activated.MAK
0xC004C001The activation server determined the specified product key is invalidMAK
0xC004C003The activation server determined the specified product key is blockedMAK
0xC004C008The activation server determined that the specified product key could not be used.KMS
0xC004C020The activation server reported that the Multiple Activation Key has exceeded its limit.MAK
0xC004C021The activation server reported that the Multiple Activation Key extension limit has been exceeded.MAK
0xC004F009The Software Protection Service reported that the grace period expired.MAK
0xC004F00FThe Software Licensing Server reported that the hardware ID binding is beyond level of tolerance.MAK
KMS client
KMS host
0xC004F014The Software Protection Service reported that the product key is not availableMAK
KMS client
0xC004F02CThe Software Protection Service reported that the format for the offline activation data is incorrect.MAK
KMS client
0xC004F035The Software Protection Service reported that the computer could not be activated with a Volume license product key.KMS client
KMS host
0xC004F038The 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
0xC004F039The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) is not enabled.KMS client
0xC004F041The Software Protection Service determined that the Key Management Server (KMS) is not activated. KMS needs to be activated.KMS client
0xC004F042The Software Protection Service determined that the specified Key Management Service (KMS) cannot be used.KMS client
0xC004F050The Software Protection Service reported that the product key is invalid.MAK
KMS
KMS client
0xC004F051The Software Protection Service reported that the product key is blocked.MAK
KMS
0xC004F064The Software Protection Service reported that the non-genuine grace period expired.MAK
0xC004F065The Software Protection Service reported that the application is running within the valid non-genuine period.MAK
KMS client
0xC004F06CThe 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
0xC004F074The 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 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

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

0xc004d302 Activation

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:
    1. Run slmgr /dti and then record the value of the Installation ID.
    2. Contact the Microsoft Licensing Activation Centers and provide the Installation ID in order to receive a Confirmation ID.
    3. 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:

Error Code 0xc004d302

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

Slui.exe 0x2a 0xc004d302

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.