Bitlocker Windows Recovery Environment Error
Gauntlet video game. Retrieved July 8, 2015. Metacritic. ^. ^ Good, Owen S. Retrieved 2014-09-17.
- Windows Recovery Environment Xp
- Bitlocker Windows Recovery Environment Error
- Bitlocker Recovery Windows 10
Problems enabling Bitlocker on Surface Pro with Windows 8.1. Pokemon red gameshark codes move modifier. Using a brand new Surface Pro (first generation) out of the box, installed current updates, then 8.1, and any further recommended updates after 8.1 was installed. I've installed a two other things that don't seem connected to the issue: the Cisco Anywhere VPN client and Visual Studio 2013.
I have a surface pro 3 with windows 10. My bitlocker has had this weird yellow triangle on my local drive implying it wasn't working properly, so I decrypted the drive. I then proceeded to go to bitlocker to try and re-encrypt it and I get this message. I have disabled Cortana and a bunch of the privacy stuff.
- Dec 15, 2016 Otherwise, you should check your system partition and verify that you have at least 200 MB of free space on your system partition so that the Windows Recovery Environment can be retained on the system drive along with the BitLocker Recovery Environment and other files that BitLocker requires to unlock the operating system drive.
- As already stated the Windows 8.1 upgrade wipes out the WinRE environment from the recovery partition. If you look in Disk Manager the partition is now empty when under Windows 8 there was content. You can also confirm this by running.
'This PC doesn't support entering a BitLocker recovery password during startup. Ask your administrator to configure Windows Recovery Environment so that you can use BitLocker.'
Using a brand new Surface Pro (first generation) out of the box, installed current updates, then 8.1, and any further recommended updates after 8.1 was installed.
I've installed a two other things that don't seem connected to the issue: the Cisco Anywhere VPN client and Visual Studio 2013.
I'd like to enable Bitlocker, but during the verification step, the following error is displayed, with no options to continue:
This PC deosn't support entering a BitLocker recovery password during startup. Ask your administrator to configure Windows Recovery Environment so that you can use BitLocker.
The 'administrator' in this case is me, and I don't:
- .. understand why this has happened
- .. know how to fix the issue, as if it's really necessary to make this change, what would I do?
Windows Recovery Environment Xp
3 Answers
This worked well with Windows 10, with a couple of tweaks, swapping steps 5 & 6. You must use the FORMAT command before exiting DISKPART. Also, if like me you have upgraded from 8.1 to Enterprise, to Windows 10 you might have multiple recovery partitions. You can use reagent /info
beforehand to check which partition is currently being used. The reagent /enable
process failed when I tried to change to an older recovery volume.
- Start CMD as Administrator, enter
DISKPART
- Enter
LIST VOLUME
- Then select the recovery volume with
SELECT VOLUME x
where x is the corresponding number of the volume - Enter
ASSIGN LETTER=Q
(to assign the letter Q:/ to the recovery partition) - Enter
FORMAT fs=ntfs label='Recovery' quick override
where label='Recovery' is optional and works with any other name as well - Enter
EXIT
to leave diskpart - Run
Robocopy.exe C:WindowsSystem32Recovery Q:RecoveryWindowsRE /copyall /dcopy:t
- Run
reagentc /setreimage /path Q:RecoveryWindowsRE
- Run
reagentc /enable
- Run
reagentc /info
to check whether the setup worked, 'WinRe-Status' should be enabled now - Use DISKPART to remove the drive letter previously assigned to the recovery partition. To do that repeat steps 1. to 3. and then enter
REMOVE LETTER=Q
As already stated the Windows 8.1 upgrade wipes out the WinRE environment from the recovery partition. If you look in Disk Manager the partition is now empty when under Windows 8 there was content.
You can also confirm this by running
This is fixed by by copying the winre.wim file from the C:WindowsSystem32Recovery folder
which recreates the WinRE area in the recovery partition. Here are the steps to accomplish this:
- In
DISKPART
assign a drive letter to the recovery partition (I usedQ:
) - Run
Robocopy.exe C:WindowsSystem32Recovery Q:RecoveryWindowsRE Winre.wim /copyall /dcopy:t
- Run
reagentc /setreimage /path Q:RecoveryWindowsRE
- Run
reagentc /enable
- Use
DISKPART
to remove the drive letter previously assigned to the recovery partition.
Bitlocker Windows Recovery Environment Error
Confirm it works with:
Twisty ImpersonatorAs already stated the Windows 8.1 upgrade wipes out the WinRE environment from the recovery partition. If you look in Disk Manager the partition is now empty when under Windows 8 there was content.
You can also confirm this by running
reagentc /info
This is fixed by by copying the winre.wim file from the C:WindowsSystem32Recovery folder
which recreates the WinRE area in the recovery partition. Here are the steps to accomplish this:
- In
DISKPART
assign a drive letter to the recovery partition (I usedQ:
) - Run
Robocopy.exe C:WindowsSystem32Recovery Q:RecoveryWindowsREWinre.wim /copyall /dcopy:t
- Run
reagentc /setreimage /path Q:RecoveryWindowsRE
- Run
reagentc /enable
- Use
DISKPART
to remove the drive letter previously assigned to the recovery partition.
Confirm it works with:
Bitlocker Recovery Windows 10
reagentc /info
There needs to be an extra step for this method to work. After you assign the drive letter but before exiting diskpart, run:
This reformats the partition and the override allows the partition to be formatted. I had run into this same issue while deploying Windows 8.1 to Surface Pro 3 tablets. The Pro 2s that we have all worked fine but there was something funny with the new 3s.
protected by Community♦Oct 12 '15 at 19:41
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?