Having problems enabling BitLocker on a new hard drive? There might be a simple solution.
Setting up BitLocker is typically straightforward, especially if you are using an MDM solution like DriveStrike. But sometimes an unforeseen error can get in the way of a quick setup.
Normally, running the following command enables BitLocker:
manage-bde -on c: -rp
However, you might get this error:
ERROR: An error occurred (code 0x80070002): The system cannot find the file specified. NOTE: If the -on switch has failed to add key protectors or start encryption, you may need to call “manage-bde -off” before attempting -on again.
Thankfully, this error has a simple fix. The cause is likely a corrupt or unreadable ReAgent.xml file, located in C:\Windows\System32\Recovery\ReAgent.xml. This file is automatically created when initializing BitLocker, so the existing one might interfere with the encryption process on your new hard drive. You can rename or delete this file to troubleshoot the error, and a new one will be created when you enable BitLocker or restart your computer.
More BitLocker troubleshooting:
If you have questions about troubleshooting BitLocker or you are dealing with a different error, see the Microsoft documentation.
Visit our Encryption page to learn more about BitLocker integration with DriveStrike.
If you manage Windows machines for your business, DriveStrike can help you have peace of mind about the security of your data. In addition to BitLocker encryption, DriveStrike provides Remote Wipe, Lock, and Locate features, which are essential to any robust cybersecurity program. Start your free 30-day trial to start protecting your Windows devices today, and contact us if you have any questions about DriveStrike, BitLocker, or cybersecurity in general.