TPM_E_TRANSPORT_NOTEXCLUSIVE (0X8028004E) Fix Fast
This error means a TPM command ran outside an exclusive transport session. Usually a driver glitch or a leftover process. Quick reboot often kills it.
Ran into TPM_E_TRANSPORT_NOTEXCLUSIVE (0X8028004E)? It means you or something on your system tried to run a TPM command while another session was already active. Happens most often after a BIOS update, a Windows feature update, or when a security app like BitLocker or a VPN client tries to talk to the TPM at the same time.
I had a client last month whose entire print queue died because of this — turned out their HP laptop's TPM driver got corrupted after a Windows 11 23H2 update. Every time they tried to unlock BitLocker, they got this error. The fix was stupid simple: restart the TPM service.
Let's step through it. Start with the 30-second fix, then move up if it's not gone.
30-Second Fix: Restart the TPM Services
This clears up 8 out of 10 cases. Open Services.msc (hit Win+R, type services.msc, hit Enter). Find these two services:
- TPM Base Services
- Trusted Platform Module (TPM)
Right-click each one, select Restart. If you can't restart the TPM service because it's not running, right-click, hit Start.
Now try whatever was throwing the error again. If the error's gone, you're done. If not, move to the next step.
5-Minute Fix: Clear Stuck Transport Sessions
The error means a transport session didn't close properly. You can force-close it via PowerShell. Run PowerShell as Administrator (right-click Start menu, choose Windows PowerShell (Admin)).
Run this command to see if the TBS (TPM Base Services) has a hung session:
Get-TpmIf it shows IsReady as False, the TPM's stuck. Try this:
Stop-Service TBS -Force
Start-Service TBSThat restarts the TBS without touching the TPM itself. Then check again with Get-Tpm — should show IsReady: True.
Still no luck? Run this to clear any pending TPM operations:
Set-TpmOwnerAuth -ForceThis resets the TPM owner authorization, which often breaks the stuck transport session. Reboot after, then test.
15-Minute Fix: Reset the TPM Completely
If the above didn't work, something deeper's wrong. Could be a corrupted TPM driver, a firmware issue, or a conflict with a hypervisor (like Hyper-V or VMware).
Warning: This clears all TPM keys. That means BitLocker will ask for your recovery key, and any apps that used TPM-based certificates will need re-enrollment. If you have BitLocker, get your recovery key first (logged into Microsoft's recovery key page).
Open TPM Management — hit Win+R, type tpm.msc, hit Enter. In the right pane, click Clear TPM. Reboot when prompted.
After reboot, Windows will reinitialize the TPM automatically. Open tpm.msc again and verify it says The TPM is ready for use.
If you still get the error after this, you've got a driver issue. Go to your device manufacturer's site (Dell, HP, Lenovo, etc.) and download the latest TPM firmware update and chipset driver. I've seen this fix on Lenovo ThinkPads and Dell Latitudes after Windows feature updates broke the TPM driver.
Still broken? Try uninstalling the TPM driver from Device Manager (look under Security Devices), then Scan for hardware changes to reinstall it. Reboot.
One last hail mary: disable and re-enable the TPM in BIOS/UEFI. Reboot into BIOS (usually F2, F10, or Del during startup), find the TPM setting (often under Security or Advanced), set it to Disabled, save and exit. Boot into Windows, shut down, go back into BIOS, re-enable it. This forces a full hardware reinit.
If none of this works, you might have a failing TPM chip — rare but not impossible. I had a Dell Optiplex where the TPM literally died after a power surge. In that case, replace the motherboard or disable TPM entirely and use a software-based solution like BitLocker with a USB key.
Was this solution helpful?