- Windows Non Core Edition Activation
- Windows Activation Error 0xc004d302
- 0xc004f069 On A Computer Running
- Activate Non Core Windows 10
Command line, slmgr /dli ends with 'Error: 0xc004d302 on a Computer running Microsoft Windows non-core edition, run slui.exe 0x2a 0xc004d302 to display the error text' 3. Command line slui.exe 0x2a 0xc004d302 ends with the error 'The security processor has reported that the trusted data store was rearmed. Hence we cannot activate Windows. 0xc004d302 Slui.exe 0x2a 0xc004d302 Microsoft Windows Core. Average ratng: 5,7/10 4029 reviews. Threaten the well-being of your computer. Join our community for more fix what is wrong a good deal of investigation must be made. Join & Ask a If you have run the slmgr.vbs /rearm command and try to run any other why not find out more use different codes to indicate various types of errors.
-->Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2
Registry settings
Table 3 describes the registry settings that Volume Activation supports.
Table 3. Registry settings
Registry subkey: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatform
Value | Type | Description | Scope |
|---|---|---|---|
ActivationAlternateURL | REG_SZ | Optionally contains an administrator-provided URL. If this key is populated, some activation dialog boxes will include a new link — Learn About Activation Online — that opens in the default browser. | All |
DisableDnsPublishing | REG_DWORD | Set this to a non-zero value to block auto-publishing to DNS by the KMS host. | KMS |
DnsDomainPublishList | REG_MULTI_SZ | Format:domain_name, <priority>, <weight> Optionally contains a list of fully qualified domains that KMS uses to auto-publish its DNS service (SRV) record. The KMS home domain is always used, so it is not necessary to include it here. This depends on the DisableDnsPublishing value. The priority and weight parameters are optional. If not supplied, these are set to 0 in the SRV record. | KMS |
EnableKmsLowPriority | REG_DWORD | Set this to a non-zero value to minimize contention from KMS in a co-hosted environment. Note that on a busy system, this can prevent the KMS host from maintaining a sufficient count. | KMS |
KeyManagementServiceListeningPort | REG_SZ | Set this on the KMS host to force KMS to listen on the TCP port specified. The host uses TCP port 1688 if this value is not specified. | KMS |
KeyManagementServiceName | REG_SZ | Set this value to force the use of a specific KMS host by the KMS client. No default. If you specify both App-ID and SKU-ID, this is created in a subkey under which the value is stored:..SoftwareProtectionPlatformAPPID_GUIDSKUID_GUID KeyManagementServiceName If you specify only App-ID, SKU-ID is not allowed, and the resulting key is: ..SoftwareProtectionAPPID_GUID KeyManagementServiceName If you specify neither App-ID nor SKU-ID, the resulting key is: ..SoftwareProtectionPlatform | KMS client |
KeyManagementServicePort | REG_SZ | Set this to force the use of a specific TCP port by the KMS client when it communicates with a KMS. The client uses port 1688 if this value is not specified. | KMS client |
KeyManagementServiceVersion | REG_SZ | Set this for Microsoft Operations Manager (MOM) 2005 automatic discovery of the KMS. Delete this value if the KMS is no longer functional on the computer. | KMS |
UserOperations | REG_DWORD | This value does not exist by default, and the default is 0, which requires elevation. Create this value and set it to 1 to enable standard users to install product keys and activate and rearm computers without requiring elevation. This setting can also be configured by GPOs, which are stored under the policies registry subkey. | All (not just KMS) |
VLActivationInterval | REG_DWORD | This is set initially on both KMS server and client sides. The default is 120 minutes (2 hours). The KMS client initially picks up this interval from the registry but switches to the KMS setting after it receives the first KMS response. The minimum value is 15 minutes, and the maximum is 43,200 minutes (30 days). | KMS Client and Server |
VLRenewalInterval | REG_DWORD | This is set initially on both KMS server and client sides. The default is 10,080 minutes (7 days). The KMS client initially picks up this interval from the registry but switches to the KMS setting after it receives the first KMS response. As a result, the client-side setting will never be used. The minimum value is 15 minutes, and the maximum is 43,200 minutes (30 days). | KMS Client and Server |
(APP-ID)(SKU-ID)VLActivationType | REG_DWORD | Limits the type of activation to a single type. 1 = Active Directory activation only 2 = KMS activation only 3 = Token activation only 0, blank, or values other than 1-3 = all activation types allowed (default value) | [???] |
Registry subkey: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatformActivation
Value | Type | Description | Scope |
|---|---|---|---|
Manual | REG_DWORD | 0 = Allow automatic online activation (default) 1 = Disable auto-activation | MAK and KMS host but not KMS client |
Registry subkey: HKEY_LOCAL_MACHINESOFTWAREClassesAppIDslui.exe
Value | Type | Description | Scope |
|---|---|---|---|
NoGenTicket | REG_DWORD | Turns off Online Client Activation Validation Telemetry 0 = Allow automatic activation validation telemetry (default) 1 = Disable validation telemetry | KMS |
See also
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)
Windows Non Core Edition Activation
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.
5 Answers
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
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.
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.
Windows Activation Error 0xc004d302
protected by Community♦Oct 21 '15 at 13:56
0xc004f069 On A Computer Running
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?
Activate Non Core Windows 10
Not the answer you're looking for? Browse other questions tagged windows-server-2012-r2 or ask your own question.