Blog

What to test after enabling full-disk encryption

Check encryption status, recovery access, reboot behavior, and storage speed after turning on full-disk encryption, without mistaking a benchmark for proof.

Jason TurnerHardware tests 5 min read

You turned on full-disk encryption and want to know whether your files are protected and your computer still works normally. A few checks can catch an unfinished setup, a missing recovery key, or a performance change before you rely on the encrypted device.

Start with the operating system's encryption status, then check everyday access and storage speed. A browser test can show how the drive performs, but it cannot confirm that encryption is enabled.

Check the computer after enabling encryption

  1. Once the operating system reports that encryption is complete, open the Storage Test. If the system shows encryption progress, wait for it to finish before measuring drive speed.
  2. Run the test and note the results for large-file speed and small writes. Keep the computer on a stable power source, close file transfers and other heavy tasks, and use the same browser for any repeat test.
  3. Confirm encryption in the operating system. On Windows 11, check Settings › Privacy & security › Device encryption, if that setting is available. For BitLocker, check Control Panel › System and Security › BitLocker Drive Encryption. On a Mac, check System Settings › Privacy & Security › FileVault.
  4. Make sure you can access the recovery key from somewhere other than the encrypted computer. Keep it in a secure place, and do not leave your only copy on the drive it unlocks.
  5. Restart the computer, sign in as usual, and open a few files you use regularly. If you use an external encrypted drive too, disconnect and reconnect it, then confirm that it unlocks with the expected password or key.

If you did not measure storage speed before enabling encryption, the first test is still useful as a reference for later. For a fair comparison, run it again under similar conditions rather than comparing a busy computer with an idle one.

What the results mean

The operating system says encryption is on

This is the useful confirmation that the system's encryption feature is enabled. If a progress indicator is still moving, leave the computer powered on and let the process finish. The Storage Test cannot verify encryption, even if its results look normal.

Files open and the computer restarts normally

Your basic access check passed. Confirm that you know where the recovery key is and that you can reach it from another device. A restart test does not prove that every file or every drive is encrypted, so check each drive you intended to protect in the operating system's settings.

Storage speed is lower than expected

Encryption can add some work when the computer reads and writes data. The effect varies with the processor, drive, and encryption support, and a browser benchmark can also vary with background activity, power settings, and caching. A single lower result does not show that encryption is faulty.

The test results vary between runs

Small writes and large-file transfers can respond differently to other computer activity. Close downloads, cloud sync, and other disk-heavy programs, then repeat the test. If the computer freezes, reports drive errors, or struggles to open files as well, treat that as a separate problem rather than an encryption result.

How to fix problems you find

  1. Let encryption finish. Keep the computer connected to power and avoid shutting it down while the operating system reports that encryption is in progress. If progress appears stuck for hours, restart only if the system asks you to, and check the encryption status again afterward.
  2. Save or locate the recovery key. Use the recovery-key option provided by your operating system and store the key somewhere secure that you can access without this computer. If you cannot find it, do not assume your password can replace it in every recovery situation.
  3. Check which drive is protected. On Windows 11, review Settings › Privacy & security › Device encryption or Control Panel › System and Security › BitLocker Drive Encryption. On macOS, review System Settings › Privacy & Security › FileVault. If an external drive was meant to be encrypted, check that drive's own encryption setting too.
  4. Repeat the speed test under steady conditions. Close apps that use the drive, pause large downloads or backups, and connect a laptop to power. Run the Storage Test again. A browser test is a comparison tool, not a full drive-health check.
  5. Check available storage and system updates. Low free space or a pending update can make the computer feel slow regardless of encryption. On Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage.
  6. Get help before changing encryption settings. If the system asks for a recovery key you do not have, or reports an encryption error, stop and check the computer maker's or operating system's official support instructions. Do not turn encryption off as a quick speed fix until you have a safe backup and understand the recovery steps.

When it may be a drive problem

Encryption is less likely to be the cause if the computer was already freezing, showing file errors, or losing access to the drive before encryption began. Back up important files while the drive is still readable. If errors continue across restarts or the drive disconnects, check its health with the computer's built-in diagnostics or ask a repair professional to inspect it. A browser speed test cannot diagnose failing storage hardware.

What a browser storage test can tell you

The Storage Test measures drive performance for large files and small writes through the browser. It can help you compare results on the same computer, but the operating system and browser affect what the test can access. It cannot inspect the drive's encryption state, check every part of the disk, or certify that your recovery key works.

For encryption status, trust the operating system's settings. For drive speed, compare repeat tests taken under similar conditions, and keep your recovery key separate from the encrypted device.