From 0e15e921dcb55aa52ec7d6e1fff80608ba849243 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Tue, 6 Feb 2018 14:27:46 -0800 Subject: [PATCH] added note about -forcerecovery --- .../bitlocker/bitlocker-recovery-guide-plan.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/windows/device-security/bitlocker/bitlocker-recovery-guide-plan.md b/windows/device-security/bitlocker/bitlocker-recovery-guide-plan.md index add5645218..9e780394d7 100644 --- a/windows/device-security/bitlocker/bitlocker-recovery-guide-plan.md +++ b/windows/device-security/bitlocker/bitlocker-recovery-guide-plan.md @@ -100,15 +100,14 @@ Before you create a thorough BitLocker recovery process, we recommend that you t 1. Click the **Start** button, type **cmd** in the **Start Search** box, right-click **cmd.exe**, and then click **Run as administrator**. 2. At the command prompt, type the following command and then press ENTER: - ```powershell - `manage-bde -forcerecovery` _BitLockerVolume_ - ``` + `manage-bde -forcerecovery ` + **To force recovery for a remote computer** 1. On the Start screen, type **cmd.exe**, and then click **Run as administrator**. 2. At the command prompt, type the following command and then press ENTER: - `manage-bde. -ComputerName` _RemoteComputerName_ `-forcerecovery` _BitLockerVolume_ + `manage-bde. -ComputerName -forcerecovery ` > **Note:**  Recovery triggered by `-forcerecovery` persists for multiple restarts until a TPM protector is added or protection is suspended by the user.