Should You Enable Device Encryption If Your PC Has a TPM Chip
- 14 steps
- Needs administrator rights
- Group Policy needs Windows 11 Pro, Enterprise or Education
Device Encryption in Windows 11 needs a working TPM 2.0 chip, so a device TPM problem usually shows up as a missing Device encryption entry under Settings Privacy & security. Device Encryption is a built-in Windows feature that locks your files so no one can read them without your password or recovery key. It uses BitLocker technology, which is built into Windows 11 (Windows 10 reached end of support on October 14, 2025).
Windows can set it up automatically during installation or at first sign-in if your PC has a compatible TPM (Trusted Platform Module) chip and modern hardware. If the entry is missing, the PC does not meet the requirements, and later sections show how to find out why. The steps below are written for current Windows 11.
Yes, you should turn on Device Encryption if your PC has a TPM chip, provided it is TPM 2.0 with UEFI and Secure Boot enabled. Open Settings, go to Privacy & security, and look for Device encryption. If the entry is there, your hardware supports it. Back up your recovery key first, because a hardware change can lock the drive.
The Role of the TPM Chip in Data Security
A Trusted Platform Module is a dedicated security chip on your motherboard. It acts as a secure vault for your encryption keys. Windows does not store the key on your hard drive, where a thief could find it. It keeps the key inside the chip, so unauthorized software cannot read it.
When you boot, the TPM releases the key only if it verifies that the system boot files have not been tampered with. Suppose someone steals your computer and puts the drive into a different machine. The TPM on the new motherboard will not release the key, so the data stays locked.
System Requirements for Device Encryption
Windows will not let you turn on Device Encryption until your computer has certain hardware and firmware features. Your PC needs a compatible TPM (2.0 on Windows 11), Unified Extensible Firmware Interface (UEFI) enabled, and Secure Boot active. UEFI is the modern replacement for traditional BIOS firmware, and it initializes your hardware at startup.
- A compatible Trusted Platform Module (version 2.0 or later).
- Unified Extensible Firmware Interface (the modern replacement for traditional BIOS firmware that initializes hardware) enabled on your motherboard.
- Secure Boot (a security standard that ensures your device boots using only software trusted by the manufacturer) enabled in your firmware settings.
- Modern Standby or HSTI-compliant hardware capabilities.
Your sign-in method also matters. On Windows 11 24H2 and later, device encryption turns on automatically on a clean install or at first sign-in with a Microsoft account (or a work or school account) on supported hardware. If you set the PC up with a local account, it does not turn on by itself, so you must enable it manually. Backing up the recovery key to your account also depends on being signed in with that account.
The TPM and Secure Boot options are switched on or off in your firmware setup screen. Many PCs ship with the TPM disabled, and Windows treats a disabled TPM as a missing one. Firmware menus differ by manufacturer, so check your PC’s manual or support page for the exact location. Older PCs that run in legacy BIOS mode usually cannot use Device Encryption at all.
Pros of Enabling Device Encryption
Device Encryption protects your personal files if your laptop is lost or stolen. A thief cannot bypass your login screen by pulling the drive and plugging it into another computer. Without the key, every file on the drive stays scrambled and unreadable.
On modern processors the performance impact is virtually nonexistent. They include dedicated hardware instruction sets, such as AES-NI, built to handle encryption and decryption in the background. You should not notice a difference in your apps or games.
Cons and Potential Risks
The main risk is permanent data lockout. It can happen after a major hardware failure, or if you lose your recovery key. If the TPM detects an unexpected change to your hardware or boot configuration, it locks the drive as a safety precaution. You then have to type a long recovery key (a 48-digit number) to get back in.
Motherboard replacements, firmware updates and BIOS/UEFI changes are common triggers. Before you apply any of them, suspend BitLocker protection if your edition offers that option, and make sure you have the recovery key on hand. On Pro, Manage BitLocker in Control Panel is where you can suspend protection. Resume it once the update is finished.
Performance overhead is negligible on modern hardware. Older systems without hardware-accelerated encryption might see a minor dip in file transfer speeds. For most users the security benefits outweigh the performance concerns.
So, should you turn it on if your PC has a TPM? In most cases, yes. Back up your recovery key first and store it somewhere other than the encrypted PC. The later sections cover how.
How to Check if Your PC Supports Device Encryption
You can check whether your computer supports Device Encryption with the built-in System Information tool. The check takes under a minute and shows whether your hardware meets the requirements before you try to turn protection on. It changes nothing on your PC.
- Open the Start menu, type
msinfo32, and press Enter. The System Information window opens.

- In the left pane, make sure System Summary is selected. Then scroll the main list to the Device Encryption Support item.
- Read the value. If it says “Reasons for failed automatic device encryption: …” followed by technical warnings, your system does not meet the requirements out of the box. Each warning names a missing item, such as the TPM or Secure Boot, so you know what to fix.
- If the value reports that prerequisites are met (typically “Meets prerequisites”), your system supports the feature.
That’s it. You now know whether your PC can use Device Encryption, and if it cannot, you have the specific reasons Windows lists.
Next, check the status of your TPM chip. This is the quickest way to pin down a device TPM problem.
- Open the Start menu, type
tpm.msc, and press Enter. The Trusted Platform Module Management window opens. If it reports that no compatible TPM can be found, the chip is either missing or disabled in your firmware settings. - Look at the Status section. It should state that the TPM is ready for use.
- Look at the Specification Version in the lower right and confirm it reads 2.0.

That’s it. You now know whether your TPM is present, ready and at version 2.0. If it is missing or disabled, enable it in your firmware setup screen. Suspend BitLocker first if the drive is already encrypted, as the warning above explains.
How to Enable Device Encryption in Windows
You can turn on Device Encryption from the Settings app if your hardware supports it and it is not already running. You need administrator rights on the PC. On Windows 11 24H2 and later, a Microsoft account sign-in on supported hardware may have already turned it on, so check the switch before you change anything.
- Open Settings by pressing Win+I.
- Click Privacy & security in the left sidebar. The privacy and security options appear on the right.

- Click Device encryption. If you do not see this entry, the hardware does not support it (see the System Information check above). Pro editions may show BitLocker options instead.

- Set the Device encryption switch to On. If the switch is greyed out, sign in with an administrator account. Windows then encrypts the drive in the background, and you can keep working while it runs.
That’s it. Device Encryption is now on, and Windows keeps encrypting the drive while you work. Restarting is not required, though encryption may take longer on a large disk.
To undo this, return to the same page and set the switch to Off. Windows will decrypt the drive, which can take a while on a large disk.
How to Backup Your Recovery Key
- Open Settings and go to Privacy & security Device encryption.

- Click the option to back up your recovery key.
- Choose a backup method. You can save it to your Microsoft account, save it as a file on a USB drive, or print a physical copy.
That’s it. Your recovery key now has a copy outside the Windows installation, which is what you need if the TPM ever refuses to unlock the drive.
If you sign in with a Microsoft account, Windows normally saves a copy of the key to that account automatically. Check that it is really there rather than assuming. From any other device, sign in and open aka.ms/myrecoverykey to see the keys saved to your account. With a local account, nothing is saved online, so use a USB drive or a printout.
Whichever method you use, keep the copy away from the encrypted PC. A key file saved on the same drive is no help when you cannot get into that drive. On Pro, you can also open Manage BitLocker in Control Panel, or use the manage-bde command-line tool from an administrator prompt, to view and manage protection.
Enterprise vs Home Editions: BitLocker Differences
Windows Home editions use a simplified version called Device Encryption for everyday users. Windows Pro and Enterprise editions include full BitLocker Drive Encryption. BitLocker adds advanced security controls such as startup PINs, pre-boot authentication, and centralized management tools for IT administrators.
Device Encryption is essentially an automated subset of BitLocker. On Pro, you can fine-tune cipher strengths and policy enforcement through the Local Group Policy Editor. Home users get a simpler, set-it-and-forget-it experience, with no extra options to tune.
The recovery key works the same way on both. Whichever edition you run, store it safely before you touch firmware or replace hardware.
Have a question about this guide?
Answered by AI from this guide. Good questions may be added to this page — please don't include personal details.
Did this guide fix your problem?
About the Author
Richard
Tech Writer, IT Professional
Richard is a writer at Geek Rewind who turns complex IT tasks into clear, step-by-step guides. He draws on years of hands-on experience in system administration and enterprise IT operations, focusing on Windows, Linux and WordPress: the problems people actually run into, and the fixes that work. His server and WordPress guides come from systems he runs himself. Richard builds and maintains the platform behind Geek Rewind, from its Ubuntu servers and Nginx configuration to its custom WordPress plugins. Many new tutorials start with readers' questions, and he's always glad to answer them in the comments.
No comments yet — be the first to share your thoughts!