mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Merge branch 'main' into v-smandalika-BL-nonenyp-4491111
This commit is contained in:
@ -2,12 +2,12 @@
|
||||
title: BitLocker cannot encrypt a drive known issues
|
||||
description: Provides guidance for troubleshooting known issues that may prevent BitLocker Drive Encryption from encrypting a drive
|
||||
ms.reviewer: kaushika
|
||||
ms.technology: windows
|
||||
ms.prod: w10
|
||||
ms.technology: windows-sec
|
||||
ms.prod: m365-security
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
author: Teresa-Motiv
|
||||
ms.author: v-tea
|
||||
ms.author: v-tappelgate
|
||||
manager: kaushika
|
||||
audience: ITPro
|
||||
ms.collection: Windows Security Technologies\BitLocker
|
||||
@ -25,7 +25,7 @@ This article describes common issues that prevent BitLocker from encrypting a dr
|
||||
|
||||
## Error 0x80310059: BitLocker drive encryption is already performing an operation on this drive
|
||||
|
||||
When you turn on BitLocker drive encryption on a computer that is running Windows 10 Professional, you receive a message that resembles the following:
|
||||
When you turn on BitLocker Drive Encryption on a computer that is running Windows 10 Professional or Windows 11, you receive a message that resembles the following:
|
||||
|
||||
> **ERROR:** An error occurred (code 0x80310059):BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing.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.
|
||||
|
||||
@ -40,7 +40,8 @@ This issue may be caused by settings that are controlled by group policy objects
|
||||
|
||||
To resolve this issue, follow these steps:
|
||||
|
||||
1. Start registry editor, and navigate to the following subkey:
|
||||
1. Start Registry Editor, and navigate to the following subkey:
|
||||
|
||||
**HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies\\Microsoft\\FVE**
|
||||
|
||||
1. Delete the following entries:
|
||||
@ -52,15 +53,19 @@ To resolve this issue, follow these steps:
|
||||
|
||||
## "Access is denied" message when you try to encrypt removable drives
|
||||
|
||||
You have a computer that is running Windows 10, version 1709 or version 1607. You try to encrypt a USB drive by following these steps:
|
||||
You have a computer that is running Windows 10, version 1709 or version 1607, or Windows 11. You try to encrypt a USB drive by following these steps:
|
||||
|
||||
1. In Windows Explorer, right-click the USB drive and select **Turn on BitLocker**.
|
||||
|
||||
1. On the **Choose how you want to unlock this drive** page, select **Use a password to unlock the drive**.
|
||||
|
||||
1. Follow the instructions on the page to enter your password.
|
||||
|
||||
1. On the **Are you ready to encrypt this drive?** page, select **Start encrypting**.
|
||||
|
||||
1. The **Starting encryption** page displays the message "Access is denied."
|
||||
|
||||
You receive this message on any computer that runs Windows 10 version 1709 or version 1607, when you use any USB drive.
|
||||
You receive this message on any computer that runs Windows 10 version 1709 or version 1607, or Windows 11, when you use any USB drive.
|
||||
|
||||
### Cause
|
||||
|
||||
@ -72,21 +77,21 @@ To verify that this issue has occurred, follow these steps:
|
||||
|
||||
1. At the command prompt, enter the following command:
|
||||
|
||||
```cmd
|
||||
```console
|
||||
C:\>sc sdshow bdesvc
|
||||
```
|
||||
|
||||
The output of this command resembles the following:
|
||||
|
||||
> D:(A;;CCDCLCSWRPWPDTLORCWDWO;;;SY)(A;;CCDCLCSWRPWPDTLORCWDWO;;;BA)(A;;CCLCSWRPLORC;;;BU)(A;;CCLCSWRPLORC;;;AU)S:(AU;FA;CCDCLCSWRPWPDTLOSDRCWDWO;;;WD)
|
||||
> `D:(A;;CCDCLCSWRPWPDTLORCWDWO;;;SY)(A;;CCDCLCSWRPWPDTLORCWDWO;;;BA)(A;;CCLCSWRPLORC;;;BU)(A;;CCLCSWRPLORC;;;AU)S:(AU;FA;CCDCLCSWRPWPDTLOSDRCWDWO;;;WD)`
|
||||
|
||||
1. Copy this output, and use it as part of the [**ConvertFrom-SddlString**](https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/convertfrom-sddlstring?view=powershell-6&preserve-view=true) command in the PowerShell window, as follows.
|
||||
1. Copy this output, and use it as part of the [**ConvertFrom-SddlString**](/powershell/module/microsoft.powershell.utility/convertfrom-sddlstring) command in the PowerShell window, as follows.
|
||||
|
||||

|
||||

|
||||
|
||||
If you see NT AUTHORITY\INTERACTIVE (as highlighted) in the output of this command, this is the cause of the issue. Under typical conditions, the output should resemble the following:
|
||||
|
||||

|
||||

|
||||
|
||||
> [!NOTE]
|
||||
> GPOs that change the security descriptors of services have been known to cause this issue.
|
||||
@ -95,10 +100,10 @@ To verify that this issue has occurred, follow these steps:
|
||||
|
||||
1. To repair the security descriptor of BDESvc, open an elevated PowerShell window and enter the following command:
|
||||
|
||||
```ps
|
||||
```powershell
|
||||
sc sdset bdesvc D:(A;;CCDCLCSWRPWPDTLORCWDWO;;;SY)(A;;CCDCLCSWRPWPDTLORCWDWO;;;BA)(A;;CCLCSWRPLORC;;;BU)(A;;CCLCSWRPLORC;;;AU)S:(AU;FA;CCDCLCSWRPWPDTLOSDRCWDWO;;;WD)
|
||||
```
|
||||
|
||||
1. Restart the computer.
|
||||
|
||||
The issue should now be resolved.
|
||||
The issue should now be resolved.
|
Reference in New Issue
Block a user