Bitlocker encryption hangs windows 10

Question

Some time ago I started the Bitlocker encryption, but it not succeed, but stucks at 76,2% on the C: drive. As I wanted to reset the Computer it does not work because of that. Reseting the TPM havn`t helped either. What can I do to either reset the PC adequatly or to stop the encryption? Thanks for your suggestions

Answer 1

Hi there,

Better late than never, I hope. I had exactly the same problem, which occurred because I resized the partition during Bitlocker decryption. I was also unable to resume decryption after successfully pausing using manage-bde.

The solution I found was to resize the partition back to what it was before I made the change using disk manager, and then to resume decryption using manage-bde -resume. It worked! Hopefully it will work for you too.

Answer 2

Hi There!

To stop or pause the bitlocker encryption, from an elevated (Run as administrator) powershell or command prompt window, you can use the manage-bde tool.

To get the current status of the drive and the encryption, the command would be manage-bde -status <drive letter>.

Example: manage-bde -status c:

To pause the encryption you can use the command of manage-bde -pause <drive letter>.
To resume the encryption you can use the command of manage-bde -resume <drive letter>.
To turn off bitlocker encryption you can use the command of manage-bde -off <drive letter>.

Hope this helps you!

Answer 3

Hey, few days back i experienced something similar and mine was stuck on 75.6% and I've successfully recovered all my data and also made a video for reference.
Here's the link - https://www.youtube.com/watch?v=CW6VKck7JXA&t=25s

Answer 4

I could identify that for me the issue was that I have bad blocks on my Samsung 870 EVO 2TB SSD drive, as specified by eventvwr.msc.

I was able to bring the computer back to a working state by hard-rebooting and then very quickly at reboot, before it hangs again, getting an admin prompt and typing manage-bde -off e: (where e: is my drive that I'm trying to encrypt.)

This successfully went on the path to decryption, which succeeded.

Then I ran chkdsk e: /f /r /x to try and disable those "damaged clusters", but that eventually failed with An unspecified error occurred (766f6c756d652e63 470). (Seemingly after the bad block fix because it said it fixed a bunch of files and subsequent runs don't show fixes for specifically those files at the cluster check step, although they show some others, but I can't be sure because it's in french and I'm not sure how to set terminal language to english, so it's talking about "clusters" and I'm not completely sure if that is the same thing as "blocks".)

Unfortunately, after all this, when I try encrypting again, it fails at the exact same percentage with the exact same errors of "Le périphérique \Device\Harddisk1\DR1 comporte un bloc défectueux." in eventvwr.msc. Seemingly, chkdsk does not take an action that prevents bitlocker from dying upon encountering the bad block. I'd be very interested to get further help on why that doesn't work, because my understanding is that chkdsk should flag blocks as un-usable so that the system does not attempt using them.

Thanks for any further help...