Device encryption not showing or not available in Windows 11: what each reason means and how to fix it
Device encryption is the simple form of BitLocker that Windows turns on by itself, Windows 11 Home included, when a PC meets its requirements. When the PC doesn't, device encryption is not available and the Device encryption page is simply missing from Settings, with no message. Windows does record the reason, in one line of the System Information app that most people never open. This guide shows where to find that line, what each message means, how to fix it, and which messages stopped mattering in Windows 11 version 24H2.
Step 1: check your Windows version, because 24H2 changed the rules
- Right-click Start and choose Settings.
- Go to System → About.
- Under Windows specifications, note the Edition and Version.
The edition matters less than people think. Microsoft says device encryption is available on all Windows versions, Home included; it's full BitLocker, with all its settings, that needs Pro, Enterprise or Education (see device encryption vs BitLocker on Windows 11 Home). The version matters a lot. Starting with Windows 11 version 24H2, Microsoft removed two requirements: the PC no longer has to support Modern Standby or pass the Hardware Security Test Interface (HSTI) checks, and external DMA ports no longer block it. On Windows 10, and on Windows 11 before 24H2, both requirements still apply. (Microsoft ended Windows 10 support on October 14, 2025.)
Step 2: read the Device Encryption Support line
- Select Start and type System Information.
- Right-click System Information in the results and select Run as administrator. Select Yes if Windows asks whether to allow changes.
- With System Summary selected on the left, scroll the list on the right to Device Encryption Support. On some PCs it's called Automatic Device Encryption Support.
- Read the value. Meets prerequisites means the PC qualifies. Otherwise, System Information shows a message such as Reasons for failed automatic device encryption: followed by one or more reasons, separated by commas, as in the examples users have posted on Microsoft Q&A (see Sources).
Fix the reasons one at a time, TPM first, and open System Information again after each change to see what's left. Microsoft says that if a change later makes the PC qualify, for example turning on Secure Boot, device encryption turns BitLocker on automatically as soon as it detects it. When it does, sign in as an administrator with a Microsoft account if you haven't, then check that a key for this PC is listed at aka.ms/myrecoverykey (see how to find your BitLocker recovery key). With only local accounts, the drive isn't protected. The exception: once device encryption has been turned off, it won't turn itself back on, so you switch it on in Settings. The same list also has Secure Boot State and PCR7 Configuration lines, which show the Secure Boot state and whether PCR7 binding is possible; Microsoft's guide for PC makers checks these two lines when PCR7 binding fails.
What each message means and how to fix it
These are the messages you're most likely to see. Microsoft's pages explain what most of them mean but don't print all of them word for word; for the others, the wording below comes from System Information results that users have posted on Microsoft Q&A, and it varies slightly between PCs (for example "DMA-capable" with a hyphen, or "the device is not Modern Standby").
| What it says | What it means | How to fix it | Still applies on Windows 11 24H2 and later? |
|---|---|---|---|
| Meets prerequisites | The PC qualifies for device encryption. | If Settings has no Device encryption page, sign in with an administrator account. If the page shows Off, turn it on (see below). | Not a problem |
| Elevation required to view | System Information wasn't opened as administrator, so it won't show the result. Microsoft notes some devices need elevated permissions to view these settings. | Close it and open it again with Run as administrator. | Not a problem |
| TPM is not usable | The PC has no Trusted Platform Module (TPM), or the TPM isn't enabled in the BIOS or UEFI. | Turn on the TPM in the UEFI firmware settings (Intel PTT, AMD fTPM, Security Device Support). | Yes |
| PCR7 binding is not supported | Secure Boot is off, or devices such as a docking station, external graphics card or special network adapter are connected during startup. | Unplug those devices at startup; turn on Secure Boot and boot in UEFI mode, not Legacy/CSM. | Yes |
| WinRE is not configured | Windows Recovery Environment isn't set up. | Run reagentc /enable in Terminal (Admin). | Yes |
| Hardware Security Test Interface failed and device is not Modern Standby | The PC neither supports Modern Standby nor passes Microsoft's HSTI security tests. | Update to Windows 11 version 24H2 or later. On Windows 10, that means upgrading to Windows 11, which needs a PC that meets its requirements, including TPM 2.0. Microsoft documents no fix for older versions. | No: requirement removed in 24H2 |
| Un-allowed DMA capable bus/device(s) detected | Windows found at least one possible external port or device that can read memory directly (DMA) and may be a risk. | Update to Windows 11 version 24H2 or later (on Windows 10, only possible if the PC meets Windows 11's requirements). Don't edit the AllowedBuses registry key. | No: requirement removed in 24H2 |
| Disabled by policy | Microsoft doesn't document this message. It likely means a policy or setting (such as PreventDeviceEncryption, which Microsoft documents for PC makers and organizations) blocks automatic device encryption. | Work or school PC: ask IT. Your own PC: whoever installed Windows may have set it on purpose (see below); otherwise ask the PC maker. Don't edit the registry. | Not part of the 24H2 change |
TPM is not usable
Microsoft's explanation: the PC doesn't have a TPM, or the TPM isn't enabled in the BIOS or UEFI. First check what Windows sees:
- Open Windows Security (select Start and type it) and choose Device security. If there's no Security processor section, Microsoft says the PC probably has no TPM or it isn't enabled in UEFI.
- Or press Windows + R, type
tpm.mscand select OK. "Compatible TPM cannot be found" means the TPM may be disabled.
To turn it on:
- Save your work. In Windows 11, open Settings → System → Recovery and select Restart now next to Advanced startup. In Windows 10, it's Settings → Update & Security → Recovery → Restart now.
- On the blue screen, choose Troubleshoot → Advanced options → UEFI Firmware Settings → Restart.
- Look for the TPM option, often under Advanced, Security or Trusted Computing. Names vary: Intel PTT or Intel Platform Trust Technology, AMD fTPM switch or AMD PSP fTPM, Security Device, Security Device Support or TPM State. Enable it, then save and exit.
- Back in Windows, open System Information as administrator and check again.
Every firmware is laid out differently. If you can't find the option, follow your PC or motherboard maker's guide, which is where Microsoft's TPM article points too. Microsoft's page for PC makers lists a TPM 1.2 or TPM 2.0 for automatic device encryption, though Windows 11 itself requires TPM 2.0.
PCR7 binding is not supported
PCR7 is a register in the TPM where the firmware records the Secure Boot settings at startup. Device encryption needs to tie its key to it. Microsoft gives two causes for this message: Secure Boot is disabled in the BIOS/UEFI, or peripherals are connected during startup, such as specialized network interfaces, docking stations or an external graphics card.
- Unplug docks, external graphics and other add-on devices, restart, and check System Information again.
- If the message is still there, turn on Secure Boot. Open UEFI Firmware Settings as in the TPM steps above. If the boot mode is Legacy (also called CSM), switch it to UEFI, or make UEFI the first or only option. Then enable Secure Boot. Microsoft's Secure Boot page links to guides from the main PC makers for the exact menu names.
Warning for Legacy installs: if Windows was installed in Legacy mode, Microsoft says it won't start after you switch the firmware to UEFI. The disk has to be converted from MBR to GPT first, with Microsoft's MBR2GPT tool. To check your disk, right-click Start, choose Disk Management, right-click your system disk (usually Disk 0), choose Properties and open the Volumes tab: Partition style says MBR or GPT. If it says MBR, take these steps in order:
- Confirm that the PC supports UEFI boot, in its firmware settings or the PC maker's documentation. Microsoft says to make sure of this before converting: after the conversion the firmware has to boot in UEFI mode, so a PC that only supports Legacy boot won't start from the converted disk.
- Back up your files.
- If BitLocker or device encryption is on, suspend it first, so that it stays suspended until you resume it yourself. In Terminal (Admin), run
Suspend-BitLocker -MountPoint "C:" -RebootCount 0ormanage-bde -protectors -disable C: -rc 0. This is the one case where a count of 0 is right, not the count of 2 used for firmware updates. Microsoft says an encrypted disk converts only while protection is suspended, and that the existing protectors must be deleted and recreated before BitLocker resumes (step 6). With a count of 2, protection can come back on by itself after the restarts, still using the old protectors. If that's unfamiliar, get help from your PC maker or Microsoft support before you start. - Follow Microsoft's MBR2GPT guide, which starts with a check that changes nothing. The conversion itself can't be undone.
- Switch the firmware to boot in UEFI mode, then turn on Secure Boot.
- If BitLocker was on, recreate its protectors and save the new key. Microsoft says the existing protectors have to be deleted and recreated before BitLocker can resume. Recreating the recovery password makes a new 48-digit recovery key, and your old copy (at aka.ms/myrecoverykey, on paper or in a file) no longer unlocks the drive. Back up the new key straight away: on Pro, use Manage BitLocker → Back up your recovery key; otherwise write down the key that
manage-bde -protectors -get C:shows (Microsoft doesn't say whethermanage-bdeworks on Home). Then check that its Key ID is listed at aka.ms/myrecoverykey. If it isn't, keep your own copy somewhere safe, away from the PC. Finally, turn protection back on withResume-BitLocker -MountPoint "C:"ormanage-bde -protectors -enable C:, and check thatmanage-bde -status C:says Protection On. Don't leave the drive suspended: while it is, the key is stored unprotected on the drive.
On some desktops, an add-in card that loads its own firmware driver at startup stops Windows from using PCR7, and Microsoft documents no simple fix for that. BitLocker itself still works without PCR7, and Microsoft says it's still secure with its regular profile.
WinRE is not configured
Windows Recovery Environment (WinRE) is Windows' built-in repair system. Microsoft says this message means it isn't configured on your PC. To check and turn it on:
- Right-click Start (or press Windows key + X) and choose Terminal (Admin). On some PCs it's called Windows Terminal (Admin) or Windows PowerShell (Admin). Select Yes when Windows asks whether to allow changes.
- Type
reagentc /infoand press Enter. It shows the status of Windows RE and, if it's installed, a Windows RE location. - If it's disabled, type
reagentc /enableand press Enter. - Run
reagentc /infoagain to confirm, then check System Information.
By default, reagentc /enable uses the recovery image Winre.wim in C:\Windows\System32\Recovery. If the command reports an error, don't start deleting or resizing partitions from forum posts. Get help from Microsoft support or your PC maker.
Hardware Security Test Interface failed / not Modern Standby, and un-allowed DMA
These two messages describe requirements that applied before Windows 11 version 24H2:
- Hardware Security Test Interface failed and device is not Modern Standby: the PC neither supports Modern Standby nor passes Microsoft's HSTI security self-tests. Both depend on how the PC maker built the hardware and firmware.
- Un-allowed DMA capable bus/device(s) detected: in Microsoft's words, Windows "detected at least one potential external DMA capable bus or device that may expose a DMA threat".
Microsoft removed both requirements in Windows 11 version 24H2, and says more devices are now eligible for automatic and manual device encryption. So the way past these messages is a newer version of Windows:
- Windows 11: select Start → Settings → Windows Update, select Check for Windows updates and install the latest version. If it isn't offered, Microsoft says you can get it manually through the Windows Update Assistant.
- Windows 10: this means upgrading to Windows 11, which needs a PC that meets Windows 11's requirements, including TPM 2.0. Windows 10's updates are under Settings → Update & Security → Windows Update.
Microsoft documents no fix for home users who stay on Windows 10 or older Windows 11 versions.
Don't take ownership of the AllowedBuses registry key. Many forum answers copy Microsoft's steps for adding DMA buses to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DmaSecurity\AllowedBuses. Those steps are written for PC makers, to use only after the hardware vendor confirms a bus has no external DMA ports. Marking a real external port as safe defeats the point of the check. And Microsoft says Windows 11 24H2 ignores that key anyway.
Disabled by policy
Microsoft doesn't document this exact message. It likely means a policy or setting is blocking automatic device encryption. Microsoft does document one such setting, PreventDeviceEncryption: PC makers can use it when they ship their own encryption instead, and Microsoft's IT documentation gives the same setting for organizations that want to stop automatic device encryption.
- Work or school PC: ask IT before changing anything. The organization may protect the drive in another way.
- Windows installed by you or a PC builder: whoever installed it may have set
PreventDeviceEncryptionon purpose, as described in stopping device encryption during a fresh install. If you set it yourself, the message is expected. - Otherwise, on your own PC: ask the PC maker's support why it's set. Don't edit the registry to undo it.
It says "Meets prerequisites" but Settings has no Device encryption page
Then the PC qualifies, and the likely cause is your account. Microsoft says that if Device encryption doesn't appear, it's either unavailable on your device or you might be signed in with a standard user account. Sign in with an administrator account and look again under Settings → Privacy & security → Device encryption. On Windows 10, where Settings is laid out differently, press Windows key + R, type ms-settings:deviceencryption and select OK: Microsoft's Device Encryption page gives that shortcut, and Microsoft Learn lists it as the Encryption settings page.
If the page is there but switched Off, turn it on yourself with the toggle. Microsoft notes that once device encryption has been turned off, it won't turn itself back on; you have to switch it on in Settings. Before you do, make sure the recovery key will be backed up (see the next section). While the drive is being encrypted, Settings may not show it as on yet: Microsoft says it doesn't show device encryption enabled until encryption is complete.
Using a local account?
With only a local account, device encryption isn't turned on automatically. Microsoft's IT documentation goes further: on a PC that uses only local accounts, the drive "remains unprotected even though the data is encrypted", because the key isn't locked away and no recovery key is backed up until an administrator signs in with a Microsoft account. Before you change any firmware settings on a PC that might already be encrypted, make sure you can reach the recovery key: see how to find your BitLocker recovery key. For why Windows encrypts some PCs without asking, and how to turn it off safely, see turning off device encryption in Windows 11.
If your PC still can't use device encryption
- Fix the firmware settings. If the cause is a TPM or Secure Boot switched off in UEFI, fixing it costs nothing.
- BitLocker on Windows 11 Pro. BitLocker is part of Pro, Enterprise and Education. On a PC without a TPM, it can still encrypt the Windows drive using a startup key on a USB drive that you insert to start the PC. This first has to be allowed in Group Policy: Microsoft's Configure BitLocker page says to enable Require additional authentication at startup and select Allow BitLocker without a compatible TPM. If that policy isn't configured, Microsoft says users can configure only basic options, on computers with a TPM. If you lose the USB key, Microsoft says you must use one of the BitLocker recovery options, such as the recovery key, to get into the drive. Microsoft also notes this skips the startup integrity check a TPM provides. Moving from Home to Pro is a paid upgrade: Microsoft's upgrade page has you buy it in Microsoft Store or enter a Windows Pro product key.
- Encrypt your most sensitive files one by one. This doesn't protect the whole drive, but it does protect the files that matter most, and it keeps protecting them once they leave the PC.
For that last option: Clavis Encrypt does not encrypt drives and is not a replacement for device encryption or BitLocker. Its free version encrypts individual files, one or several at a time, on Windows 11 (Home included) and Windows 10. Those files stay encrypted while you're signed in and when you copy them to a USB stick, an email or a cloud folder. Clavis is closed source and hasn't been independently audited; its file format is public, with an open-source decryptor. For Windows' built-in options as well, see how to encrypt files in Windows 11 Home.
Questions
Why is device encryption not showing in Windows 11 Home?
Either you're signed in with a standard account, or the PC fails a requirement. Open System Information as administrator and read the Device Encryption Support line. If it says Meets prerequisites, sign in with an administrator account and look under Settings, Privacy & security. If it lists reasons, common ones are a TPM or Secure Boot switched off in the UEFI firmware settings. Windows 11 Home does have device encryption; it's full BitLocker that it lacks.
What does "Reasons for failed automatic device encryption" mean?
It's how System Information introduces the list of reasons your PC can't use device encryption, such as TPM is not usable, PCR7 binding is not supported or WinRE is not configured. Fix each reason in turn, starting with the TPM, and check again. On Windows 11 version 24H2 and later, the Modern Standby (HSTI) and DMA reasons no longer block device encryption.
What does "Elevation required to view" mean in System Information?
It means System Information wasn't opened with administrator rights, so it won't show whether device encryption is supported. Close it, right-click System Information in the Start menu results, choose Run as administrator, and read the Device Encryption Support line again.
Does device encryption still need Modern Standby in Windows 11 24H2?
No. Starting with Windows 11 version 24H2, Microsoft removed the Modern Standby or HSTI requirement and the DMA requirement for automatic device encryption, so more PCs qualify. On Windows 10 and on Windows 11 versions before 24H2, those requirements still apply. The way past them is Windows 11 version 24H2 or later; on Windows 10, that means upgrading to Windows 11, which needs a PC that meets Windows 11's requirements, including TPM 2.0.
How do I fix "PCR7 binding is not supported"?
Microsoft gives two causes: Secure Boot is turned off, or devices such as a docking station, external graphics card or special network adapter are connected at startup. Unplug those devices and restart. If the message remains, turn on Secure Boot in the UEFI firmware settings and use UEFI boot mode, not Legacy or CSM. If Windows was installed in Legacy mode, it won't start in UEFI mode until the disk is converted with Microsoft's MBR2GPT tool. Before converting, confirm the PC supports UEFI boot, back up your files, and suspend BitLocker if it's on, with a reboot count of 0 so it stays suspended until you resume it. The conversion can't be undone; after it, switch the firmware to UEFI. Microsoft says BitLocker's protectors must then be recreated, which makes a new recovery key: back it up straight away and check its Key ID at aka.ms/myrecoverykey, because the old key no longer works. Then resume protection and check that manage-bde -status C: says Protection On.
What does "TPM is not usable" mean?
The PC either has no Trusted Platform Module or it's switched off in the BIOS or UEFI. Check Windows Security, Device security, Security processor, or run tpm.msc. To turn it on, restart into UEFI Firmware Settings and enable the TPM option, often called Intel PTT, AMD fTPM or Security Device Support. Microsoft's page for PC makers lists TPM 1.2 or 2.0 for automatic device encryption, though Windows 11 itself requires TPM 2.0.
Can I use device encryption with a local account?
Not properly. With only a local account, Windows doesn't turn device encryption on automatically, and Microsoft says a PC that uses only local accounts remains unprotected even though the data is encrypted. An administrator needs to sign in with a Microsoft account so the recovery key is backed up and the drive is fully protected.
How do I turn on device encryption in Windows 11 Home?
Sign in with an administrator account, and use a Microsoft account so Windows backs up the recovery key to it automatically. Open Settings, then Privacy & security, then Device encryption, and switch it on. Then check that the recovery key is listed at aka.ms/myrecoverykey. If the page isn't there, open System Information as administrator and read Device Encryption Support to see which requirement your PC fails.
Sources
- Microsoft Support: Device Encryption in Windows (System Information values, standard accounts, local accounts, turning it on, the ms-settings:deviceencryption shortcut)
- Microsoft Learn: BitLocker drive encryption in Windows 11 for OEMs (requirements, TPM 1.2 or 2.0, 24H2 changes, un-allowed DMA, AllowedBuses ignored in 24H2, PreventDeviceEncryption, PCR7 and add-in cards)
- Microsoft Learn: BitLocker overview (device encryption, turning on automatically once a PC qualifies, local accounts, re-enabling, editions, startup key without a TPM, Legacy/CSM and MBR2GPT)
- Microsoft Learn: Windows 11 security book, Encryption and data protection (DMA and HSTI/Modern Standby prerequisites removed)
- Microsoft Support: Find information about your Windows device (edition and version under Windows specifications)
- Microsoft Support: Install Windows Updates (Windows 11 and Windows 10 paths, Windows Update Assistant)
- Microsoft Support: Enable TPM 2.0 on your PC (TPM 2.0 required for Windows 11, tpm.msc, firmware option names, Windows 10 end of support)
- Microsoft Support: Device Security in the Windows Security app (Security processor)
- Microsoft Support: Windows 11 and Secure Boot (UEFI Firmware Settings, Legacy/CSM)
- Microsoft Learn: MBR2GPT (checking UEFI support first, BitLocker suspended during conversion, switching the firmware to UEFI, checking the partition style)
- Microsoft Learn: REAgentC command-line options
- Microsoft Support: KB5028997 (checking WinRE with reagentc /info as administrator)
- Microsoft Learn: BitLocker recovery overview (events that trigger recovery, suspending BitLocker for planned changes)
- Microsoft Learn: BitLocker operations guide (suspending and resuming BitLocker; removing and adding a recovery password protector gives a new recovery password)
- Microsoft Learn: Suspend-BitLocker (a RebootCount of 0 keeps BitLocker suspended until you resume it; the key is in the clear while suspended)
- Microsoft Learn: manage-bde protectors (-disable with -rc 0 suspends protection indefinitely; -enable turns it back on)
- Microsoft Learn: Configure BitLocker (Require additional authentication at startup, Allow BitLocker without a compatible TPM, lost USB key)
- Microsoft Support: Upgrade Windows Home to Windows Pro (purchase in Microsoft Store or a Pro product key)
- Microsoft Support: Find your BitLocker recovery key
- Microsoft Learn: Launch Windows Settings (ms-settings:deviceencryption, the Encryption page)
- Microsoft Learn: Windows Terminal FAQ (Windows key + X, Windows Terminal (Admin))
- Microsoft Q&A, user post: System Information - Device Encryption Question (example wording: Elevation required to view, the HSTI and DMA-capable messages)
- Microsoft Q&A, user post: Setting up Device Encryption (example wording: Reasons for failed automatic device encryption, PCR7, HSTI and DMA messages)
Related: how to check if a drive is encrypted in Windows 11, how to turn off device encryption in Windows 11 and how to find your BitLocker recovery key.