Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 0x8028400F

0x8028400F and 0x80284008: Windows 11 setup cannot see a working TPM

13 min read Updated October 5, 2026 Windows Update & Setup

Fix it now

0x8028400F, 0x80284008, 0x80284001 and 0x80284010 all come from TPM Base Services, the component that brokers access to the security chip, and Windows 11 blocks the upgrade when it cannot reach a TPM 2.0 through it. The usual cause is a firmware TPM that is fitted and switched off, so find out what the machine reports before you change anything.

Run these in an elevated PowerShell window, in order

tpm.msc
Get-Tpm
Get-CimInstance -Namespace root/cimv2/security/microsofttpm -ClassName Win32_Tpm | Select-Object SpecVersion
sc.exe query tbs
  1. If Get-Tpm reports TpmPresent False and SpecVersion is empty, nothing is reaching Windows. Restart into firmware: Settings โ†’ System โ†’ Recovery โ†’ Advanced startup โ†’ Restart now, then Troubleshoot โ†’ Advanced options โ†’ UEFI Firmware Settings โ†’ Restart.
  2. In firmware, look under Advanced, Security or Trusted Computing for Security Device, Security Device Support, TPM State, Intel PTT, Intel Platform Trust Technology, AMD fTPM switch or AMD PSP fTPM. Enable it, save, then power the machine fully off and on rather than warm-restarting.
  3. If sc.exe query tbs shows anything other than RUNNING, the chip may be fine and the service path broken. Run sc.exe config tbs start= demand and then sc.exe start tbs.
  4. Confirm the version, not just the presence: SpecVersion must begin 2.0, or tpm.msc must show Specification Version 2.0. A healthy TPM 1.2 will still fail.

The space after start= is sc.exe syntax, not a typo. Use sc.exe rather than sc – in PowerShell, sc is an alias for Set-Content and will quietly do something else entirely.

If the TPM now reports present at version 2.0, start setup again – for most machines that is the whole job. If it does not, the next section works out which link in the chain is broken.

Why it happens

A TPM is never addressed directly. Firmware exposes the device, a driver binds to it, and TPM Base Services – the service Windows lists as TBS – queues commands so that setup, BitLocker, Windows Hello and the platform crypto provider can share one chip. Microsoft describes TBS as a system service that allows transparent sharing of TPM resources, so when it cannot reach a device every caller above it fails at once – which is why a TPM fault so often surfaces as a BitLocker prompt on the morning of a blocked upgrade.

The four codes split into three situations. One says no compatible TPM device can be found at all. Two are about the service rather than the chip – not running and could not be started, or disabled outright, which is a decision somebody made rather than a fault. The fourth is an internal error with no published cause. The exact wording is in the code table below.

Two platform details cause most of the wasted time. Firmware TPMs are the norm – Microsoft’s own list of settings to look for includes Intel PTT and AMD fTPM – so on most business hardware there is no separate chip to hunt for. And a TPM 1.2 device is a real TPM: Windows enumerates it, reports it, then fails the upgrade anyway. Presence and version are two checks, and the codes only cover the first.

The firmware TPM is switched off

You have this one if Get-Tpm returns TpmPresent False and tpm.msc says a compatible TPM cannot be found, on a machine modern enough to have PTT or fTPM.

  1. Reach firmware through Settings โ†’ System โ†’ Recovery โ†’ Advanced startup โ†’ Restart now, then Troubleshoot โ†’ Advanced options โ†’ UEFI Firmware Settings โ†’ Restart.
  2. Look under Advanced, Security or Trusted Computing. Microsoft lists seven names it goes by: Security Device, Security Device Support, TPM State, AMD fTPM switch, AMD PSP fTPM, Intel PTT and Intel Platform Trust Technology.
  3. Enable it, save, power the machine right down, then confirm TpmPresent is True and SpecVersion begins 2.0.

If none of those seven names appears anywhere in firmware, check the manufacturer for a firmware update before concluding the platform has no TPM.

TPM Base Services is stopped or disabled

You have this one if 0x80284008 or 0x80284010, and sc.exe query tbs reports anything other than RUNNING.

  1. Take the service off Disabled, then start it: sc.exe config tbs start= demand followed by sc.exe start tbs.
  2. If it refuses to start, open Event Viewer at Windows Logs โ†’ System and filter on the TPM source.
  3. On a managed machine, find the baseline or policy setting it to Disabled and get the exclusion made centrally. A local change will be reverted at the next refresh.

Microsoft publishes no default start type for TBS, so this sets Manual rather than Automatic: it clears the disabled state without forcing a boot-time start on no documented basis.

The chip answers, but is not in a usable state

You have this one if Get-Tpm reports TpmPresent True with TpmReady False, and BitLocker or Windows Hello began failing at about the same time.

  1. Retrieve the BitLocker recovery key and store it off this machine. Nothing below is safe until you have.
  2. Suspend BitLocker so it cannot resume mid-procedure: manage-bde -protectors -disable C: -rc 0.
  3. Clear it from Windows Security โ†’ Device security โ†’ Security processor details โ†’ Security processor troubleshooting โ†’ Clear TPM, restart, accept the firmware prompt, then re-enable protection.

Clearing destroys every key sealed in the TPM and Microsoft states plainly that it can result in data loss. Microsoft is also explicit that you clear through the operating system, never from UEFI.

Full reference

Reading the four codes against each other

Taken together the codes triangulate the fault. 0x8028400F means the service is running and telling you there is nothing to talk to, so look at firmware. 0x80284008 and 0x80284010 mean the chip may be healthy and the software path is broken, so look at the service. 0x80284001 tells you neither and is a signal to go to the event log rather than re-run the same check.

Code What the stack is reporting Where to look first
0x8028400F No compatible TPM security device can be found Firmware – the device is not being exposed to Windows
0x80284008 The service is not running and could not be started Service state, then the System log for the start failure
0x80284001 An internal software error inside the TPM stack System log, source TPM; then firmware level and driver
0x80284010 The service has been disabled Start type, and whatever policy or baseline set it

Commands that tell you which situation you are in

Command What it answers
Get-Tpm Presence, readiness, enabled and activated state, ownership and lockout counters
Get-CimInstance -Namespace root/cimv2/security/microsofttpm -ClassName Win32_Tpm SpecVersion – the TCG specification version, which is the field the Windows 11 check cares about
tpm.msc Specification Version under TPM Manufacturer Information, and the status text in plain English
sc.exe query tbs Whether TPM Base Services is running, stopped or disabled
manage-bde -status C: Whether the volume is protected, and therefore whether a TPM change is about to cost you

Get-Tpm does not report the specification version. Its documented output covers TpmPresent, TpmReady, TpmEnabled, TpmActivated, TpmOwned, ManufacturerId, ManufacturerVersion and the lockout fields – and ManufacturerVersion is the TPM’s own firmware revision, not 1.2 against 2.0. Use Win32_Tpm.SpecVersion or the Specification Version field in tpm.msc for that question.

Where Windows records TPM failures

The TPM device driver logs to the standard System log rather than to an application-specific channel, under the source TPM. Two events are worth filtering for. Event ID 14 records that the driver hit a non-recoverable error in the TPM hardware, which prevents TPM services such as data encryption from being used – that one points at the device, not the configuration. Event ID 17 records that the TPM hardware failed to execute a TPM command, which is the one you tend to see alongside 0x80284001.

Log Source Event ID What it means
System TPM 14 Non-recoverable error in the TPM hardware; TPM-backed services cannot be used
System TPM 17 The TPM hardware failed to execute a TPM command

Clearing the chip without losing the volume

Clearing a TPM destroys every key sealed in it – BitLocker protectors, Windows Hello credentials, virtual smart cards and any certificate held by the platform crypto provider. Microsoft states plainly that clearing the TPM can result in data loss. Do not start without the recovery key in your hand.

Clearing is the last resort here, not the first move, and the order matters more than the commands. Get the recovery key off the machine, then suspend protection so it cannot come back on its own: a bare manage-bde -protectors -disable C: resumes automatically after the next restart, and a TPM clear needs a restart with a firmware confirmation in the middle of it. Use -rc 0 and resume deliberately when you are finished.

Check, capture the recovery key, then suspend indefinitely

manage-bde -status C:
manage-bde -protectors -get C:
manage-bde -protectors -disable C: -rc 0

Then clear from Windows Security, restart, accept the firmware prompt, and re-enable protection with manage-bde -protectors -enable C:. Anything else that was using the chip – Windows Hello, virtual smart cards, certificates in the platform crypto provider – has to be re-enrolled afterwards, because the keys those relied on no longer exist.

Guests, hosts and virtual TPMs

A guest that fails while its host is healthy is a fifth situation, and the fix has nothing to do with the host’s hardware. The virtual TPM is a generation 2 feature: a generation 1 guest cannot be given one and has to be rebuilt if it needs to run Windows 11. Add the device with the guest shut down, either from the Security page of the virtual machine’s settings or with Enable-VMTPM. Microsoft is clear that the emulated TPM 2.0 in the guest does not depend on the host having a TPM, so a bare-metal host with no chip of its own can still present compliant guests.

When the answer is different hardware

If tpm.msc shows Specification Version 1.2, or SpecVersion returns a string beginning 1.2, the machine has a real TPM of the wrong generation. Two things are worth checking before you write it off. Some business platforms of that era shipped a manufacturer firmware update that moves the device from 1.2 to 2.0, so look at the vendor’s support pages for the exact model. And if the board carries a TPM header, the manufacturer may sell a compatible 2.0 module – check its own part list rather than guessing, because headers and pinouts are not interchangeable between vendors.

If neither exists, there is a real boundary here and it is worth naming rather than working around. Windows 11’s published requirements list TPM 2.0 and UEFI with Secure Boot capability. A platform with no firmware path to 2.0, or with no TPM and no PTT or fTPM option, has failed a hardware test rather than a configuration test. It can stay on a supported release for as long as one is available to it, and then it is a replacement decision. Nothing in a licence, a key or a registry edit changes the outcome of the check.

Things that look like this and are not

Two neighbours are worth ruling out before you spend an evening in firmware. If the TPM is present at 2.0 and the block persists, the failing requirement is something else on the list – Secure Boot capability, the processor model or the boot mode – and the codes are a red herring. And if TPM-backed sign-in broke on a machine that worked yesterday, check the change history for a firmware update: those can return security settings to their defaults, switching PTT or fTPM back off and taking BitLocker’s measurements with them.

When a licence is the actual fix

If the platform has no TPM 2.0 and no firmware route to one, no licence changes that – the hardware check runs long before any product key is considered, and anyone selling a key as the fix for a TPM error is selling you something that cannot work. Where replacement is the honest answer, Arco supplies Windows 11 Pro OEM licences for the new hardware and can tell you which SKU applies to a rebuilt machine as against a genuinely new one, which is the distinction that most often gets ordered wrongly.

Every code this article covers

Code What it points at Source
0x8028400F TBS_E_TPM_NOT_FOUND – a compatible Trusted Platform Module security device cannot be found on this computer Microsoft Learn
0x80284008 TBS_E_SERVICE_NOT_RUNNING – the TBS service is not running and could not be started Microsoft Learn
0x80284001 TBS_E_INTERNAL_ERROR – an internal software error occurred; Microsoft publishes no cause Microsoft Learn
0x80284010 TBS_E_SERVICE_DISABLED – the TBS service has been disabled, as distinct from stopped Microsoft Learn

Confirm the fix worked

  1. Run Get-Tpm and confirm TpmPresent, TpmEnabled and TpmReady all report True.
  2. Run Get-CimInstance -Namespace root/cimv2/security/microsofttpm -ClassName Win32_Tpm | Select-Object SpecVersion and confirm the value begins 2.0.
  3. Run sc.exe query tbs and confirm STATE reads RUNNING.
  4. Filter the System log on the TPM source and confirm no new Event ID 14 or 17 has been written since the change.
  5. If BitLocker was suspended, run manage-bde -status C: and confirm protection is back on before you walk away.
  6. Start the upgrade and confirm the hardware check no longer stops it.

Questions people ask about this

Is a firmware TPM good enough, or do I need a real chip?

For this check, a firmware TPM is enough. Microsoft’s own instructions for enabling TPM 2.0 name Intel PTT and AMD fTPM among the settings to look for, alongside discrete Security Device entries, and setup does not distinguish between them. Discrete modules have advantages in some threat models, but that is a separate argument from whether the upgrade will run.

Does Get-Tpm tell me whether the TPM is 1.2 or 2.0?

No, and this catches people out. Get-Tpm’s documented output has no specification version field, and ManufacturerVersion is the TPM’s own firmware revision rather than the TCG specification level. Read SpecVersion from the Win32_Tpm class, or the Specification Version field under TPM Manufacturer Information in tpm.msc.

Should I set TPM Base Services to start automatically?

Not on this evidence. Microsoft publishes no default start type for TBS, so the safe change for a disabled service is Manual – sc.exe config tbs start= demand – which clears exactly what 0x80284010 is reporting. If the machine is managed, the durable fix is to stop the baseline disabling the service, not to keep resetting it locally.

Why did my TPM stop being detected after a firmware update?

Firmware updates can return security settings to their defaults, and on many platforms the default for PTT or fTPM is off. Go back into firmware and re-enable it. If BitLocker was on, have the recovery key to hand before you restart, because the change alters the measurements the volume was sealed against.

Can I add a TPM module to any desktop?

Only where the board has the right header and the manufacturer sells a matching module. Pinouts are not standard between vendors, so a module for one board will not necessarily work in another. Check the board’s own documentation and parts list before ordering anything.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0xC1900130 and 0x80190001: the feature update download never finishes License Error 0x80070070 – 0x50011: the upgrade runs out of disk space and rolls back License Error 0xC004F050 and 0xC004F025: the ESU product key is rejected on install License Error 0x80073712 and 0x800F081F: component store corruption blocking updates
โ† Back to Knowledge Base