0X80280041

Fix TPM_E_WRITE_LOCKED (0X80280041) in 3 Steps

TPM NV area locked after a failed update or BIOS tamper. Quick reset or clear fixes it. Here's the real deal.

30-Second Fix: Reboot and Check BitLocker

Had a client last week whose laptop threw this error right after a Windows update reboot. The NV area lock is often a one-time glitch from a failed TPM command. First, do a full shutdown — not a restart. Hold Shift while clicking Shut Down in Windows to force a full power-off. Boot back up and see if the error clears.

If you're using BitLocker, grab your recovery key first. Windows might ask for it after the TPM resets. You'll find the key in your Microsoft account under Devices > Recovery keys. I've had three calls this year where people ignored that and locked themselves out. Don't be that person.

Still seeing 0X80280041? Move to the next step.

5-Minute Fix: Clear the TPM via Windows

This is the most common fix. The NV area gets locked when a previous TPM write operation didn't complete — like a failed BIOS update or a Secure Boot setting change mid-boot. Clearing the TPM resets that lock.

Open the TPM Management Console: press Win+R, type tpm.msc, hit Enter. If the console says "Compatible TPM cannot be found," the TPM might be disabled in BIOS — skip to the advanced fix. Otherwise, click "Clear TPM" in the Actions panel. You'll need to restart and press a key to confirm at the prompt. Do that.

After reboot, check the error. If it's gone, done. If not, one more thing: run tpmtool in an admin Command Prompt. Type:

tpmtool /forcedclear

This forces a clear even if the TPM is in a weird state. I've used this twice on Dell OptiPlex 7080s that wouldn't clear via the GUI. It works.

15+ Minute Fix: BIOS Reset and Firmware Update

If clearing the TPM in Windows didn't work, the lock is deeper — likely in UEFI firmware. This happens after a failed Secure Boot toggle or a BIOS update that left the TPM in a written state. Here's the process:

Step 1: Reset BIOS to Defaults
Reboot into BIOS (usually F2, Del, or F10 on startup). Look for "Load Optimized Defaults" or "Reset to Factory Settings." Save and exit. This clears any half-finished TPM commands stuck in firmware. On a Lenovo ThinkPad last month, this alone fixed the error after a Secure Boot change left the NV area locked.

Step 2: Disable and Re-enable TPM
In BIOS, find the TPM or Security Chip setting. Switch it to "Disabled," save, and reboot. Then go back into BIOS and enable it again. This forces the TPM to reinitialize from scratch. Note: you might need to press F12 or something to confirm the TPM clear again when Windows boots.

Step 3: Update TPM Firmware
Some systems — looking at you, HP ProDesk 400 G7 — ship with buggy TPM firmware that locks after certain writes. Check your motherboard manufacturer's site for a TPM firmware update. On a Dell, use the Dell Command | Update tool. On an HP, the HP Support Assistant. Apply the update, reboot, and retry.

Step 4: BitLocker Recovery Fallback
If all else fails and you're locked out, boot from a Windows installation USB, go to Troubleshoot > Advanced Options > Command Prompt, and run manage-bde -unlock C: -RecoveryPassword [your-key]. Then manage-bde -protectors -disable C: to temporarily disable BitLocker. This gets you back in without the TPM. I had a server once where the TPM was physically dead — this was the only way.

Why This Happens
The error 0X80280041 specifically means the TPM's Non-Volatile (NV) storage area is write-locked. That storage holds keys, hashes, and Secure Boot policies. A failed write — like a power loss during a BIOS update, or a misconfigured UEFI setting — leaves it in a locked state. Clearing the TPM or resetting firmware releases it. Don't bother with driver updates or Windows reinstall. The lock is hardware-level.

One final tip: if you're on a Surface Pro 7 or newer, Microsoft locks the TPM in firmware. You can't clear it via the usual methods. Use the Surface UEFI settings (Volume Up + Power) and select "Clear TPM" there. Everything else is a waste of time.

Related Errors in Windows Errors
0X800D0004 NS_W_FILE_BANDWIDTH_LIMIT (0X800D0004) Fix for Windows Media 0XC0000043 STATUS_SHARING_VIOLATION 0XC0000043: File locked by another process 0XC00002AB STATUS_DS_OBJ_CLASS_VIOLATION (0XC00002AB) Fix 0X8034001E Ndis Resource Conflict 0x8034001E: Fix in 10 Minutes

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.