Fix Office activation error 0x80070005 — permissions block activation

You try to activate Microsoft Office — maybe Office 365, maybe Office 2021 — and you get error 0x80070005. The message just says Access Denied. You're logged in as admin. You're connected to the internet. And still nothing. It's frustrating because the error tells you nothing useful.

The fix: reset registry permissions for SoftwareProtectionPlatform

What's actually happening here is that the Office activation service — sppsvc.exe, the Software Protection Platform service — can't read its own registry key because the ACL (access control list) got corrupted or locked down by a security tool or a previous failed activation attempt. The quickest fix is to take ownership of that key and restore full control to SYSTEM and Administrators.

1. Close all Office apps. Open Command Prompt as Administrator. (Right-click Start, pick Command Prompt (Admin) or Windows Terminal (Admin).)
2. Run this command to take ownership of the SoftwareProtectionPlatform key:

   takeown /f "C:\ProgramData\Microsoft\Windows\SoftwareProtectionPlatform" /r /d y

3. Now grant full control to SYSTEM and Administrators:

   icacls "C:\ProgramData\Microsoft\Windows\SoftwareProtectionPlatform" /grant SYSTEM:F /grant Administrators:F /t

4. Next, reset the registry key permissions. Open Regedit as Administrator. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform

5. Right-click that key → Permissions. Click Advanced. Change owner to Administrators. Check "Replace owner on subcontainers and objects". Apply.
6. Back in Permissions, add SYSTEM with Full Control, and Administrators with Full Control. Check "Replace all child object permission entries". Apply, OK.
7. Restart the Software Protection service. In an admin command prompt:

   net stop sppsvc
   net start sppsvc

8. Try activating Office again. Open Word or Excel, go to File → Account → Activate.

The reason step 5-6 works is that sppsvc runs as SYSTEM. If SYSTEM doesn't have write permission on its own registry hive, it can't generate or store the activation token. The error 0x80070005 is literally the Windows API returning "Access Denied" when sppsvc tries to write the activation blob.

Why the fix works

Office activation uses the Software Protection Platform (SPP) — same system that handles Windows activation. SPP stores activation status in a mix of registry keys and files under ProgramData\Microsoft\Windows\SoftwareProtectionPlatform. When a third-party antivirus, a group policy, or a previous manual permission change locks down that path, SPP can't write the confirmation that says "this Office copy is legit." By resetting ownership and permissions, you give SPP back the keys to its own house.

I've seen this happen most often after a Windows feature update (22H2 to 23H2, for example) that resets some permissions but not others, leaving the SPP folder partially locked. Also common after uninstalling a third-party security suite that locked down system folders.

Less common variations of the same problem

The 0x80070005 error can also appear in these scenarios, all rooted in the same permission denial:

• Windows Firewall blocking sppsvc. Check services.msc for Software Protection. Verify its logon account is LocalSystem, not a custom account. Run sc qc sppsvc in cmd to confirm.
• Corrupt activation tokens. Delete the contents of C:\ProgramData\Microsoft\Windows\SoftwareProtectionPlatform (after backing up). Then run cscript ospp.vbs /act from Office's program folder. Yes, this is safe — Windows and Office regenerate the tokens on next activation.
• Volume licensing key conflicts. If you see 0x80070005 alongside "product key blocked," run slmgr /rearm in admin cmd, then retry Office activation.
• Windows built-in Administrator account. Office doesn't activate under the hidden Administrator account due to UAC token restrictions. Create a standard admin account and activate from there.

How to prevent this from coming back

Two things cause this error to recur: aggressive security software and manual registry permission changes.

If you run a third-party antivirus, add %ProgramData%\Microsoft\Windows\SoftwareProtectionPlatform and sppsvc.exe to its exclusions. Bitdefender, Norton, and even Windows Defender's tamper protection have been known to lock this folder after updates.

Never manually change permissions on HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform unless you absolutely know what you're doing. One wrong ACL entry and activation dies.

If you're in a corporate environment where Group Policy locks the SPP path, talk to your domain admin. They need to ensure the SPP service account (SYSTEM) has write access. A GPO that restricts all user write access to C:\ProgramData will break Office activation.

Also, keep Windows and Office fully patched. Microsoft fixed a bug in November 2023 (KB5032194) where a Windows update reset the SPP folder permissions incorrectly. Staying current avoids that class of problem.

That's it. No reinstall of Office needed. No product key re-entry. Just give the activation system back its write permission.