You’re trying to activate Windows, and instead of that satisfying ‘Windows is activated’ message, you get slapped with error code 0x80070005. The description says ‘Access is denied,’ which is about as helpful as a locked door with no key in sight.
I’ve seen this error hundreds of times over the years, and the good news is that it’s almost always fixable. Let’s walk through what’s actually happening and how to sort it out.
Error 0x80070005 is a generic Windows permissions error. When it shows up during activation, it means something on your system is blocking the activation process from accessing the resources it needs — usually registry keys or system services.
The most common culprits are:

Error 0x80070005 during Windows activation means something is blocking access to licensing files or services. Open Command Prompt as administrator, run net stop sppsvc, then net start sppsvc, and try activating again. If that fails, navigate to C:\Windows\System32\spp\store, right-click the folder, and take ownership for SYSTEM and Administrators with Full Control. Resetting the Software Protection service fixes this error in the majority of cases.
This might sound obvious, but I can’t tell you how many times this single step solves the problem. Right-click on Command Prompt or PowerShell and select ‘Run as administrator.’ Every command in this guide should be run from an elevated prompt.
The Software Protection service (sppsvc) handles Windows licensing. If it’s stuck or corrupted, activation fails. Here’s how to reset it:
“`
net stop sppsvc
“`
“`
cd %windir%\System32\spp\store\2.0
“`
“`
ren tokens.dat tokens.old
“`
“`
net start sppsvc
“`
“`
cscript.exe %windir%\system32\slmgr.vbs /rilc
“`
This works in probably 60% of cases I’ve dealt with.
Sometimes the permissions on the licensing folder get mangled — especially after major Windows updates or if you’ve migrated from another machine. Here’s how to fix that:
“`
C:\Windows\System32\spp
“`
Third-party antivirus and firewall software can block activation. I’ve seen this with Kaspersky, Bitdefender, and even some corporate endpoint protection tools.
Temporarily disable your security software, try activating, and then re-enable it. If that works, you’ll need to add an exception for the Software Protection service.
Corrupted system files can cause all sorts of weird issues, including activation failures:
sfc /scannow
Let it complete (it takes a while), restart, and try activating again.
If SFC finds problems it can’t fix, follow up with:
DISM /Online /Cleanup-Image /RestoreHealth
Then run SFC again.
Windows has a built-in troubleshooter that occasionally works:
It won’t solve permission issues on its own, but it can help identify the problem.
If nothing else works, you can completely reset the licensing status:
slmgr.vbs /rearm
Restart your computer, then re-enter your product key:
slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Then activate:
slmgr.vbs /ato
Note: You can only use /rearm a limited number of times (usually three), so don’t overuse it.
If you’ve tried everything and you’re still seeing 0x80070005, there might be a deeper issue — possibly with your product key itself or your organization’s activation infrastructure.
If you’re running Windows in a business environment with volume licensing, the issue could be with your KMS server or MAK key limits. That’s a different conversation entirely.
For straightforward retail or OEM activation issues, reaching out to Microsoft support with your error details is the next step. Or if you need a legitimate Windows license, we can help with that — we’re an authorized Microsoft reseller and can sort you out with proper licensing.
Error 0x80070005 looks scary, but it’s usually just Windows being overly protective of its own licensing files. In most cases, resetting the Software Protection service or fixing folder permissions does the trick.
The key is running everything as administrator and being methodical. Work through these fixes in order, and you’ll likely have Windows activated before you finish your coffee.
If you’re still running into Windows Activation Error 0x80070005 after trying the steps above, work through them once more in order — most cases resolve without needing anything more advanced.
Windows Activation Error 0x80070005 is frustrating, but it’s rarely a sign of serious hardware failure — in most cases it’s a driver or configuration issue like the ones covered here.
Keep this guide handy if Windows Activation Error 0x80070005 comes back after a Windows update, since driver-related regressions are the most common repeat cause.
A fresh driver install resolves Windows Activation Error 0x80070005 in the majority of cases we see, so start there before assuming it’s a hardware fault.
Windows Activation Error 0x80070005 that returns right after a Windows update almost always points back to a driver conflict, not new hardware failure.
Most people fixing Windows Activation Error 0x80070005 for the first time are done within ten minutes once they know which driver to update.
If none of the steps above resolve Windows Activation Error 0x80070005, check whether it only happens on battery power or only when plugged in — that narrows it down fast.
Windows Activation Error 0x80070005 caused by a driver issue is one of the most common support requests we see, and also one of the easiest to fix for good.
For more detail, see Microsoft’s own troubleshooting documentation.
For more Windows and Microsoft software activation guides, visit our Help Center.
The 0x80070005 error appears when Windows can’t access its own licensing files due to corrupted permissions, a stuck Software Protection service, or security software blocking the activation process. Running commands as administrator and resetting the sppsvc service usually resolves it.
Yes, third-party antivirus programs like Kaspersky, Bitdefender, and corporate endpoint protection tools can block the activation process. Temporarily disable your security software, attempt activation, and if it works, add an exception for the Software Protection service.
No, the /rearm command resets your licensing status but doesn’t invalidate your product key. You’ll need to re-enter your key afterward with slmgr.vbs /ipk followed by slmgr.vbs /ato to activate. Note that you can only use /rearm about three times before it stops working.
Not usually. This error is specifically about permissions and access, not key validity. If your key were invalid, you’d see a different error like 0xC004F050 or a message stating the key didn’t work. Fix the permissions issues first before suspecting a problem with your key.
Save on your order — use code FIXIT10
Limited-time, limited-use offer. Redeem it before it's gone.