FACILITY_FVE: Full volume encryption.
The source of the error code is Full volume encryption.[1][2]
0x80310000: This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel.[2]0x80310001: This drive is not encrypted.[2]0x80310002: The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions.[2]0x80310003: The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions.[2]0x80310004: A required TPM measurement is missing. If there is a bootable CD or DVD in your computer, remove it, restart the computer, and turn on BitLocker again. If the problem persists, ensure the master boot record is up to date.[2]0x80310005: The boot sector of this drive is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR).[2]0x80310006: The boot manager of this operating system is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR).[2]0x80310007: At least one secure key protector is required for this operation to be performed.[2]0x80310008: BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker.[2]0x80310009: BitLocker Drive Encryption cannot perform the requested action. This condition may occur when two requests are issued at the same time. Wait a few moments and then try the action again.[2]0x8031000A: The Active Directory Domain Services forest does not contain the required attributes and classes to host BitLocker Drive Encryption or Trusted Platform Module information. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed.[2]0x8031000B: The type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted.[2]0x8031000C: The size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted.[2]0x8031000D: The attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted.[2]0x8031000E: The attribute was not set. Verify that you are logged on with a domain account that has the ability to write information to Active Directory objects.[2]0x8031000F: The specified attribute cannot be found in Active Directory Domain Services. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed.[2]0x80310010: The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access.[2]0x80310011: The drive cannot be encrypted because it does not have enough free space. Delete any unnecessary data on the drive to create additional free space and then try again.[2]0x80310012: The drive cannot be encrypted because it contains system boot information. Create a separate partition for use as the system drive that contains the boot information and a second partition for use as the operating system drive and then encrypt the operating system drive.[2]0x80310013: The drive cannot be encrypted because the file system is not supported.[2]0x80310014: The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been tampered with. To use it with BitLocker, you must reformat the partition.[2]0x80310015: This drive cannot be encrypted.[2]0x80310016: The data is not valid.[2]0x80310017: The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically.[2]0x80310018: You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption.[2]0x80310019: The operation attempted cannot be performed on an operating system drive.[2]0x8031001A: The buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again.[2]0x8031001B: A read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker.[2]0x8031001C: A write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker.[2]0x8031001D: One or more BitLocker key protectors are required. You cannot delete the last key on this drive.[2]0x8031001E: Cluster configurations are not supported by BitLocker Drive Encryption.[2]0x8031001F: The drive specified is already configured to be automatically unlocked on the current computer.[2]0x80310020: The operating system drive is not protected by BitLocker Drive Encryption.[2]0x80310021: BitLocker Drive Encryption has been suspended on this drive. All BitLocker key protectors configured for this drive are effectively disabled, and the drive will be automatically unlocked using an unencrypted (clear) key.[2]0x80310022: The drive you are attempting to lock does not have any key protectors available for encryption because BitLocker protection is currently suspended. Re-enable BitLocker to lock this drive.[2]0x80310023: BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive.[2]0x80310024: The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again.[2]0x80310025: The authorization data for the storage root key (SRK) of the Trusted Platform Module (TPM) is not zero and is therefore incompatible with BitLocker. Please initialize the TPM before attempting to use it with BitLocker.[2]0x80310026: The drive encryption algorithm cannot be used on this sector size.[2]0x80310027: The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again.[2]0x80310028: The drive specified is not the operating system drive.[2]0x80310029: BitLocker Drive Encryption cannot be turned off on the operating system drive until the auto unlock feature has been disabled for the fixed data drives and removable data drives associated with this computer.[2]0x8031002A: The system partition boot sector does not perform Trusted Platform Module (TPM) measurements. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot sector.[2]0x8031002B: BitLocker Drive Encryption operating system drives must be formatted with the NTFS file system in order to be encrypted. Convert the drive to NTFS, and then turn on BitLocker.[2]0x8031002C: Group Policy settings require that a recovery password be specified before encrypting the drive.[2]0x8031002D: The drive encryption algorithm and key cannot be set on a previously encrypted drive. To encrypt this drive with BitLocker Drive Encryption, remove the previous encryption and then turn on BitLocker.[2]0x8031002E: BitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive.[2]0x80310030: BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker.[2]0x80310031: This key protector cannot be added. Only one key protector of this type is allowed for this drive.[2]0x80310032: The recovery password file was not found because a relative path was specified. Recovery passwords must be saved to a fully qualified path. Environment variables configured on the computer can be used in the path.[2]0x80310033: The specified key protector was not found on the drive. Try another key protector.[2]0x80310034: The recovery key provided is corrupt and cannot be used to access the drive. An alternative recovery method, such as recovery password, a data recovery agent, or a backup version of the recovery key must be used to recover access to the drive.[2]0x80310035: The format of the recovery password provided is invalid. BitLocker recovery passwords are 48 digits. Verify that the recovery password is in the correct format and then try again.[2]0x80310036: The random number generator check test failed.[2]0x80310037: The Group Policy setting requiring FIPS compliance prevents a local recovery password from being generated or used by BitLocker Drive Encryption. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent.[2]0x80310038: The Group Policy setting requiring FIPS compliance prevents the recovery password from being saved to Active Directory. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent. Check your Group Policy settings configuration.[2]0x80310039: The drive must be fully decrypted to complete this operation.[2]0x8031003A: The key protector specified cannot be used for this operation.[2]0x8031003B: No key protectors exist on the drive to perform the hardware test.[2]0x8031003C: The BitLocker startup key or recovery password cannot be found on the USB device. Verify that you have the correct USB device, that the USB device is plugged into the computer on an active USB port, restart the computer, and then try again. If the problem persists, contact the computer manufacturer for BIOS upgrade instructions.[2]0x8031003D: The BitLocker startup key or recovery password file provided is corrupt or invalid. Verify that you have the correct startup key or recovery password file and try again.[2]0x8031003E: The BitLocker encryption key cannot be obtained from the startup key or recovery password. Verify that you have the correct startup key or recovery password and try again.[2]0x8031003F: The Trusted Platform Module (TPM) is disabled. The TPM must be enabled, initialized, and have valid ownership before it can be used with BitLocker Drive Encryption.[2]0x80310040: The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode, BitLocker Drive Encryption can only be used for recovery purposes.[2]0x80310041: The Trusted Platform Module (TPM) was unable to unlock the drive. Either the system boot information changed after choosing BitLocker settings or the PIN did not match. If the problem persists after several tries, there may be a hardware or firmware problem.[2]0x80310042: The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM).[2]0x80310043: The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN.[2]0x80310044: A boot application has changed since BitLocker Drive Encryption was enabled.[2]0x80310045: The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled.[2]0x80310046: The Group Policy setting requiring FIPS compliance prohibits the use of unencrypted keys, which prevents BitLocker from being suspended on this drive. Please contact your domain administrator for more information.[2]0x80310047: This drive cannot be encrypted by BitLocker Drive Encryption because the file system does not extend to the end of the drive. Repartition this drive and then try again.[2]0x80310048: BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions.[2]0x80310049: This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system.[2]0x8031004A: BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer.[2]0x8031004B: The drive cannot be locked when the drive is in use.[2]0x8031004C: The access token associated with the current thread is not an impersonated token.[2]0x8031004D: The BitLocker encryption key cannot be obtained. Verify that the Trusted Platform Module (TPM) is enabled and ownership has been taken. If this computer does not have a TPM, verify that the USB drive is inserted and available.[2]0x8031004E: You must restart your computer before continuing with BitLocker Drive Encryption.[2]0x8031004F: Drive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging.[2]0x80310050: No action was taken as BitLocker Drive Encryption is in raw access mode.[2]0x80310051: BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use.[2]0x80310052: The path specified in the Boot Configuration Data (BCD) for a BitLocker Drive Encryption integrity-protected application is incorrect. Please verify and correct your BCD settings and try again.[2]0x80310053: BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments.[2]0x80310054: The auto-unlock master key was not available from the operating system drive.[2]0x80310055: The system firmware failed to enable clearing of system memory when the computer was restarted.[2]0x80310056: The hidden drive cannot be encrypted.[2]0x80310057: BitLocker encryption keys were ignored because the drive was in a transient state.[2]0x80310058: Public key based protectors are not allowed on this drive.[2]0x80310059: BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing.[2]0x8031005A: This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system.[2]0x8031005B: The Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information.[2]0x8031005C: Group Policy settings do not permit the creation of a recovery password.[2]0x8031005D: Group Policy settings require the creation of a recovery password.[2]0x8031005E: Group Policy settings do not permit the creation of a recovery key.[2]0x8031005F: Group Policy settings require the creation of a recovery key.[2]0x80310060: Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option.[2]0x80310061: Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option.[2]0x80310062: Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option.[2]0x80310063: Group Policy settings require the use of a startup key. Please choose this BitLocker startup option.[2]0x80310064: Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option.[2]0x80310065: Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option.[2]0x80310066: Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option.[2]0x80310067: Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option.[2]0x80310068: The PIN provided does not meet minimum or maximum length requirements.[2]0x80310069: The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector.[2]0x8031006A: Group Policy settings do not permit the creation of a password.[2]0x8031006B: Group Policy settings require the creation of a password.[2]0x8031006C: The Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information.[2]0x8031006D: A password cannot be added to the operating system drive.[2]0x8031006E: The BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive.[2]0x8031006F: The drive is too small to be protected using BitLocker Drive Encryption.[2]0x80310070: The selected discovery drive type is incompatible with the file system on the drive. BitLocker To Go discovery drives must be created on FAT formatted drives.[2]0x80310071: The selected discovery drive type is not allowed by the computer's Group Policy settings. Verify that Group Policy settings allow the creation of discovery drives for use with BitLocker To Go.[2]0x80310072: Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption.[2]0x80310073: Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption.[2]0x80310074: Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption.[2]0x80310075: Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked.[2]0x80310076: Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked.[2]0x80310077: Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives.[2]0x80310078: Group Policy settings do not permit you to turn on BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn on BitLocker.[2]0x80310079: Group Policy settings do not permit turning off BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn off BitLocker.[2]0x80310080: Your password does not meet minimum password length requirements. By default, passwords must be at least 8 characters in length. Check with your system administrator for the password length requirement in your organization.[2]0x80310081: Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols.[2]0x80310082: This drive cannot be encrypted because it is reserved for Windows System Recovery Options.[2]0x80310083: BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock fixed data drives when user recovery options are disabled. If you want BitLocker-protected fixed data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.[2]0x80310084: BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.[2]0x80310085: The Enhanced Key Usage (EKU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have an EKU attribute, but if one is configured it must be set to an object identifier (OID) that matches the OID configured for BitLocker.[2]0x80310086: BitLocker Drive Encryption cannot be applied to this drive as currently configured because of Group Policy settings. The certificate you provided for drive encryption is self-signed. Current Group Policy settings do not permit the use of self-signed certificates. Obtain a new certificate from your certification authority before attempting to enable BitLocker.[2]0x80310087: BitLocker Encryption cannot be applied to this drive because of conflicting Group Policy settings. When write access to drives not protected by BitLocker is denied, the use of a USB startup key cannot be required. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.[2]0x80310088: BitLocker Drive Encryption failed to recover from an abruptly terminated conversion. This could be due to either all conversion logs being corrupted or the media being write-protected.[2]0x80310089: The requested virtualization size is too big.[2]0x80310090: BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on operating system drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.[2]0x80310091: BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on fixed data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.[2]0x80310092: BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on removable data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.[2]0x80310093: The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have a KU attribute, but if one is configured it must be set to either Key Encipherment or Key Agreement.[2]0x80310094: The private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid.[2]0x80310095: Removal of the data recovery agent certificate must be done using the Certificates snap-in.[2]0x80310096: This drive was encrypted using the version of BitLocker Drive Encryption included with Windows Vista and Windows Server 2008 which does not support organizational identifiers. To specify organizational identifiers for this drive upgrade the drive encryption to the latest version using the "manage-bde -upgrade" command.[2]0x80310097: The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive.[2]0x80310098: The default BitLocker Key Derivation Function SP800-56A for ECC smart cards is not supported by your smart card. The Group Policy setting requiring FIPS-compliance prevents BitLocker from using any other key derivation function for encryption. You have to use a FIPS compliant smart card in FIPS restricted environments.[2]0x80310099: The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals.[2]0x8031009A: The requested TPM PIN contains invalid characters.[2]0x8031009B: The management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version.[2]0x8031009C: The feature is only supported on EFI systems.[2]0x8031009D: More than one Network Key Protector certificate has been found on the system.[2]0x8031009E: Removal of the Network Key Protector certificate must be done using the Certificates snap-in.[2]0x8031009F: An invalid certificate has been found in the Network Key Protector certificate store.[2]0x803100A0: This drive isn't protected with a PIN.[2]0x803100A1: Please enter the correct current PIN.[2]0x803100A2: You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator.[2]0x803100A3: BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator.[2]0x803100A4: Your system administrator requires that passwords contain only printable ASCII characters. This includes unaccented letters (A-Z, a-z), numbers (0-9), space, arithmetic signs, common punctuation, separators, and the following symbols: # $ & @ ^ _ ~ .[2]0x803100A5: BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage.[2]0x803100A6: BitLocker Drive Encryption does not support wiping free space on thin provisioned storage.[2]0x803100A7: The required authentication key length is not supported by the drive.[2]0x803100A8: This drive isn't protected with a password.[2]0x803100A9: Please enter the correct current password.[2]0x803100AA: The password cannot exceed 256 characters.[2]0x803100AB: A password key protector cannot be added because a TPM protector exists on the drive.[2]0x803100AC: A TPM key protector cannot be added because a password protector exists on the drive.[2]0x803100AD: This command can only be performed from the coordinator node for the specified CSV volume.[2]0x803100AE: This command cannot be performed on a volume when it is part of a cluster.[2]0x803100AF: BitLocker did not revert to using BitLocker software encryption due to group policy configuration.[2]0x803100B0: The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use.[2]0x803100B1: Group Policy settings do not allow the use of hardware-based encryption.[2]0x803100B2: The drive specified does not support hardware-based encryption.[2]0x803100B3: BitLocker cannot be upgraded during disk encryption or decryption.[2]0x803100B4: Discovery Volumes are not supported for volumes using hardware encryption.[2]0x803100B5: No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume.[2]0x803100B6: No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume.[2]0x803100B7: Group Policy settings require the creation of a startup PIN, but a pre-boot keyboard is not available on this device. The user may not be able to provide required input to unlock the volume.[2]0x803100B8: Group Policy settings require the creation of a recovery password, but neither a pre-boot keyboard nor Windows Recovery Environment is available on this device. The user may not be able to provide required input to unlock the volume.[2]0x803100B9: Wipe of free space is not currently taking place.[2]0x803100BA: BitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled.[2]0x803100BB: BitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker.[2]0x803100BC: Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates.[2]0x803100BD: BitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume.[2]0x803100BE: BitLocker Drive Encryption cannot be applied to this drive because the Group Policy setting for Enhanced Boot Configuration Data contains invalid data. Please have your system administrator resolve this invalid configuration before attempting to enable BitLocker.[2]0x803100BF: This PC's firmware is not capable of supporting hardware encryption.[2]0x803100C0: BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator.[2]0x803100C1: You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator.[2]0x803100C2: BitLocker cannot save the recovery password because the specified Microsoft account is Suspended.[2]0x803100C3: BitLocker cannot save the recovery password because the specified Microsoft account is Blocked.[2]0x803100C4: This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy.[2]0x803100C5: This PC cannot support device encryption because unencrypted fixed data volumes are present.[2]0x803100C6: This PC does not meet the hardware requirements to support device encryption.[2]0x803100C7: This PC cannot support device encryption because WinRE is not properly configured.[2]0x803100C8: Protection is enabled on the volume but has been suspended. This is likely to have happened due to an update being applied to your system. Please try again after a reboot.[2]0x803100C9: This PC is not provisioned to support device encryption.[2]0x803100CA: Device Lock has been triggered due to too many incorrect password attempts.[2]0x803100CB: Protection has not been enabled on the volume. Enabling protection requires a connected account. If you already have a connected account and are seeing this error, please refer to the event log for more information.[2]0x803100CC: Your PIN can only contain numbers from 0 to 9.[2]0x803100CD: BitLocker cannot use hardware replay protection because no counter is available on your PC.[2]0x803100CE: Device Lockout state validation failed due to counter mismatch.[2]0x803100CF: The input buffer is too large.[2]0x803100D0: The target of an invocation does not support requested capability.[2]0x803100D1: Device encryption is currently blocked by this PC's configuration.[2]0x803100D2: This drive has been opted out of device encryption.[2]0x803100D3: Device encryption isn't available for this drive.[2]0x803100D4: The encrypt on write mode for BitLocker is not supported in this version of Windows. You can turn on BitLocker without using the encrypt on write mode.[2]0x803100D5: Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator.[2]0x803100D6: Device encryption can't be turned off while this drive is being encrypted. Please try again later.[2]0x803100D7: This action isn't supported because this drive isn't automatically managed with device encryption.[2]0x803100D8: BitLocker can't be suspended on this drive until the next restart.[2]
Sources
- https://msdn.microsoft.com/en-us/library/cc231198.aspx
- winerror.h from Windows SDK 10.0.14393.0