How to fix Windows activation error 0xC004D302?

Error 0xC004D302 means the Windows licence store was just rearmed, usually by slmgr /rearm, slmgr /rilc or Sysprep, and Windows refuses further licence commands until it restarts. In most cases a full restart followed by slmgr /ato clears it. If it comes back after a restart, something keeps rearming or the licence files are damaged.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What error 0xC004D302 means and why it says "non-core edition"

Most people first see the code in a small Windows Script Host box after running an slmgr command. The box reads: "Error: 0xC004D302 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004D302' to display the error text." The box does not explain the code. It tells you how to ask Windows for the explanation.

When you run slui.exe 0x2a 0xC004D302, Windows shows the real text: "The security processor reported that the trusted data store was rearmed." The trusted data store is where Windows keeps its licence state. Rearming resets the activation timers, and Microsoft's slmgr reference says /rearm does exactly that. Until Windows restarts, the licence service treats the store as in the middle of a change and refuses further commands.

Why error 0xC004D302 appears, from most to least common

Every case starts with something that reset the licence store. The question is whether a restart is all that is missing, or whether something else is wrong as well. Find your row, then go to its fix.

Some older pages blame the MachineKeys folder or broken crypto permissions. One answer on Microsoft Q&A repeats that idea, but we could not confirm it from a Microsoft page, so this guide does not ask you to change folder permissions.

Run slui.exe 0x2a 0xC004D302 and check the licence state (2 minutes)

These checks read the licence state and change nothing. Microsoft notes that slmgr /dli and slmgr /dlv do not need administrator rights. Do them once before the fixes, and again after each fix.

1. Press Win + R, type the command below and press Enter. A window shows the full error text.

   slui.exe 0x2a 0xC004D302

2. If the window says the trusted data store was rearmed, the cause is a rearm. Go to Fix 1.
3. Open Command Prompt and run the command below. Note the Description line (OEM, RETAIL or VOLUME), the Partial Product Key and the License Status.

   slmgr /dli

4. For more detail, such as the edition name and the activation ID, run:

   slmgr /dlv

5. If slmgr shows another code instead, run slui.exe 0x2a followed by that code to read its text.

How to fix Windows activation error 0xC004D302

Fix 1 solves most cases in five minutes. Fixes 2 to 4 are for a Windows that still does not activate after the restart. Fix 5 stops a rearm that keeps coming back, Fix 6 repairs system files, and Fix 7 is for the cases only Microsoft can solve. Do not run slmgr /rearm again to clear this error.

Fix 1. Restart Windows fully, then activate with slmgr /ato

5 minutesNo riskEveryone who sees 0xC004D302 right after an slmgr command, a licence repair or a Sysprep run.

The error text itself says the store was rearmed. Microsoft's slmgr reference says licence changes need a restart, or a restart of the Software Protection service, to keep the licence service stable. After the restart the store accepts commands again.

1. Save your work and close open apps.
2. Select Start > Power > Restart. Do not use Shut down: with Fast Startup on, a shutdown does not start Windows fresh.
3. After Windows starts, type cmd in the search box on the taskbar and select Run as administrator next to Command Prompt, then Yes.
4. Start online activation:

   slmgr /ato

5. Check the result:

   slmgr /dli

Fix 2. Run the Activation troubleshooter after the restart

5 minutesNo riskThe rearm error is gone after the restart, but the Activation page still says Windows is not activated.

A rearm only resets timers. It does not activate anything. If the PC has a digital licence linked to its hardware or your Microsoft account, the troubleshooter can apply it once the store accepts commands again.

Activation needs a working connection. If the PC is offline, fix that first: How to check your internet connection in Windows

1. Sign in with an administrator account.
2. Open Settings > System > Activation. On Windows 10 it is Settings > Update & Security > Activation.
3. Select Troubleshoot. The option is shown only while Windows is not activated.
4. If it offers Activate Windows, select it and then Activate.
5. Read any new code it shows and run slui.exe 0x2a with that code to see its text.

Fix 3. Reinstall the licence files with slmgr /rilc

10 minutesLow riskThe error or another licence code comes back after a real restart, and no script is running slmgr.

Microsoft's slmgr reference says /rilc reinstalls the known-good licence copies stored in %SystemRoot%\system32\oem and %SystemRoot%\System32\spp\tokens, replacing the matching licences in the trusted store. That repairs a store damaged by malware, a disk error or a migration.

1. Open Command Prompt as administrator, as in Fix 1.
2. Reinstall the licence files:

   slmgr /rilc

3. Wait for the Windows Script Host box to confirm, then select OK.
4. Restart with Start > Power > Restart before any other licence command. Skipping this restart brings 0xC004D302 back.
5. Open Command Prompt as administrator again and activate:

   slmgr /ato

A user on Microsoft's forum ran slmgr -rilc and slmgr -rearm one after the other and got exactly this error. The restart between the commands, and after them, is the part that matters.

Fix 4. Install the product key that matches your edition

10 minutesLow riskYou typed a new key, the server was migrated to new hardware or a new hypervisor, or slmgr /dli shows another edition than you bought.

On Microsoft Q&A, 0xC004D302 was reported together with 0x80041014 on a Windows Server 2016 virtual machine after a move from Xen to Hyper-V. The advisor's first check was whether the key matched the edition, Standard or Datacenter, and the channel.

1. Run slmgr /dlv and note the edition name and the channel (OEM, RETAIL or VOLUME).
2. Compare them with the key you own: the box, the email from the shop, or your volume licence portal.
3. Open Command Prompt as administrator and install the matching key, replacing the X characters:

   slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

4. Restart the PC. Microsoft says to restart after installing a key so the licence service stays stable.
5. Activate:

   slmgr /ato

On a home PC with the key in the firmware, the edition must match the one the PC was sold with. Our guide to error 0xC004F215 shows how to read that key and compare editions.

Fix 5. Stop the script or tool that keeps rearming Windows

15 minutesLow risk0xC004D302 is back after every restart and you did not run slmgr yourself.

One rearm and one restart clear the error. If it returns at every start, something runs slmgr /rearm again. Microsoft's reference says Sysprep calls the rearm too, so deployment scripts and activator tools both fit this pattern.

1. Press Win + R, type taskschd.msc and press Enter to open Task Scheduler.
2. Select Task Scheduler Library and look for tasks you do not know whose Actions tab runs slmgr, cscript or a .cmd file.
3. Right-click such a task and select Disable. Do not delete Microsoft's own tasks under Microsoft > Windows.
4. Check the apps that start with Windows and turn off unknown ones: Stop apps from opening at startup
5. If you ran an activator tool or a script from a forum, remove it and scan the PC: How to scan for malware with Microsoft Defender
6. Restart, then run slmgr /ato as in Fix 1.

Fix 6. Repair Windows system files with DISM and SFC

20 to 30 minutesNo riskslmgr or /rilc fails with errors, or the licence problem started after malware, a crash or a disk error.

The licence service and the known-good licence copies are system files. If they are damaged, /rilc has nothing good to copy from. The advisor on Microsoft Q&A suggested the same repair before rebuilding the licence store.

DISM repairs the Windows component store, then SFC replaces damaged system files from it. Step by step: Run DISM and SFC to repair Windows system files

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Fix 7. Activate by phone or contact Microsoft support

15 to 30 minutesNo riskYou have a valid key or proof of purchase and Fixes 1 to 6 did not help.

Phone activation and support work outside the local licence commands that keep failing. The advisor on Microsoft Q&A named slui 4 and an escalation to Microsoft as the last step for this code.

1. Restart the PC first, so no rearm is pending.
2. Type SLUI 04 in the search box on the taskbar and press Enter.
3. Choose your country and follow the steps: call the number, read out the installation ID and type the confirmation ID you are given.
4. If phone activation is not offered, save screenshots of slmgr /dlv and of the error.
5. Contact Microsoft support from support.microsoft.com/contactus with the code 0xC004D302, the edition, the channel and what ran before the error.

If error 0xC004D302 is still there

When none of the fixes worked, collect the facts below before you contact anyone. They show whether the store keeps being rearmed, or whether the licence itself is the problem.

• A home PC that came with Windows: the PC maker can restore a missing or wrong OEM key.
• A PC or server from work: the IT department, which owns the image and the volume licence.
• Windows bought from Microsoft: Microsoft support with your order (Fix 7).

How to avoid error 0xC004D302 next time

Nearly every case starts with a licence command that was not followed by a restart. A short rule for scripts and manual work prevents it.

Frequently asked questions

What does error 0xC004D302 mean?

It means the security processor of the Windows licence service reports that the trusted data store was rearmed. In plain words, the activation timers were reset, usually by slmgr /rearm, slmgr /rilc or Sysprep, and Windows has not restarted since. Until the restart, the licence service refuses new commands. A full restart followed by slmgr /ato clears it in most cases. Your files are not affected.

How do I read the error text with slui.exe 0x2a 0xC004D302?

Press Win + R, type slui.exe 0x2a 0xC004D302 and press Enter. Windows opens a window with the full text of the code. The same trick works for any licence code that slmgr prints without an explanation: replace the last part with that code. This is the step the Windows Script Host box asks for when it says to run slui to display the error text.

What is a "Windows non-core edition" activation error?

It is not a separate error. The sentence "On a computer running Microsoft Windows non-core edition, run slui.exe" is what slmgr prints for many codes when it does not show their text itself. A non-core edition is a normal Windows with a desktop, where the slui window can open, unlike Windows Server Core. The code at the end of the sentence is the one that matters, here 0xC004D302.

Why do I get a slui.exe error when I try to activate?

slui.exe is the Windows activation window. When it or slmgr shows an error, the hex code tells you the reason. With 0xC004D302 the reason is a rearm that still needs a restart. Restart with Start > Power > Restart, then try again. If slui itself does not open, repair system files with DISM and SFC (Fix 6) and try again after a restart.

Do I get 0xC004D302 on Windows 11 and Windows 10 in the same way?

Yes. The licence service, slmgr and slui work the same on Windows 11 and Windows 10, so the fixes are the same. Only the path to the Activation page differs: Settings > System > Activation on Windows 11, Settings > Update & Security > Activation on Windows 10. Windows 10 left support on 14 October 2025, but activation still works. Windows Server shows the same code after a rearm or a migration.

Will running slmgr /rearm again fix 0xC004D302?

No. A rearm is what causes the code. Running it again resets the timers once more and needs another restart, and the number of rearms is limited. Restart instead, then run slmgr /ato. If you need to extend a grace period on a test machine, run one rearm, restart at once, and only then run other licence commands. Never use a rearm as a replacement for a valid licence.

What does slui.exe 0x2a 0xC004D307 mean?

It is a different code from the same family. Run slui.exe 0x2a 0xC004D307 to read its text on your PC. In user reports it appears when the allowed number of rearms is used up, after repeated slmgr /rearm runs. We could not confirm that from a Microsoft page. In either case another rearm will not help: activate with a valid key (Fix 4) or by phone (Fix 7).

Did an activator tool cause my 0xC004D302 error?

It can. Free activation scripts often call slmgr /rearm or reinstall licence files, and some run at every start. If the error came right after such a tool, remove it, scan the PC with Microsoft Defender and check Task Scheduler (Fix 5). Then reinstall the licence files (Fix 3) and activate with a genuine key. This page does not help with activators, which work around Microsoft's licence terms.

I ran the fixes and still get the same error. What now?

Check that you really restarted between commands, with Restart and not Shut down. Then look for a script or task that runs slmgr (Fix 5). If none exists, the licence files or the key are the problem: run Fix 6, then Fix 3, then Fix 4. Collect slmgr /dlv and the Security-SPP events and contact the PC maker, your IT team or Microsoft. This page is in English; the steps are the same in every language.