Windows / Modules / fvevol.sys

fvevol.sys

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x60011011Encryption of volume %2 started.
0x60021011Encryption of volume %2 stopped.
0x60031011Encryption of volume %2 completed.
0x60041011Decryption of volume %2 started.
0x60051011Decryption of volume %2 stopped.
0x60061011Decryption of volume %2 completed.
0x60071011Conversion worker thread for volume %2 was started.
0x60081011Conversion worker thread for volume %2 was temporarily stopped.
0x60091011Auto-unlock enabled for volume %2.
0x600a1011An error was encountered converting volume %2.
0x600b1011Auto-unlock disabled for volume %2.
0x600c1011The conversion operation on volume %2 encountered a bad sector error. Please validate the data on this volume.
0x600d1011Failed to enable auto-unlock for volume %2.
0x600e1011Failed to disable auto-unlock for volume %2.
0x600f1011Auto-unlocking failed for volume %2.
0x60101011An attempt to automatically restart conversion on volume %2 failed.
0x60111011Metadata write: Volume %2 returning errors while trying to modify metadata. If failures continue, decrypt volume.
0x60121011Metadata rebuild: An attempt to write a copy of metadata on volume %2 failed and may appear as disk corruption. If failures continue, decrypt volume.
0x60131011Volume %2 contains bad clusters. These clusters will be skipped during conversion.
0x60141011No key file was found for Volume %2 during restart.
0x60151011A corrupt key file was encountered for Volume %2 during restart.
0x60161011No volume master key was retrieved in a key file during restart.
0x60171011The TPM was not enabled during restart.
0x60181011The SRK was found to be invalid during restart.
0x60191011The PCRs did not match during restart.
0x601a1011No volume master key was retrieved from a key file during restart.
0x601b1011A boot application hash did not match expected value during restart.
0x601c1011The boot configuration options did not match expected values during restart.
0x601d1011No volume master key was retrieved from a PIN during restart.
0x601e1011No volume master key was retrieved from a recovery password during restart.
0x601f1011A valid key was found during the last restart.
0x60201011An unexpected error was encountered attempting to retrieve the volume master key during restart.
0x60211011A key was not available from required sources during restart.
0x60221011Metadata commit: Not all copies of metadata on volume %2 could be written. If failures continue, decrypt volume.
0x60231011Metadata commit: No copies of metadata on volume %2 could be written. If failures continue, decrypt volume.
0x60241011Metadata commit: Metadata update could not be flushed.
0x60251011Metadata commit: An attempt to verify metadata update on volume %2 failed at read. If failures continue, decrypt volume.
0x60261011Metadata commit: Update verification of metadata on volume %2 failed. If failures continue, decrypt volume.
0x60271011Metadata initial read: Primary metadata record on volume %2 could not be found. Volume needs recovery.
0x60281011Metadata initial read: Failover metadata record on volume %2 could not be found. Volume needs recovery.
0x60291011Metadata initial read: Failover metadata record on volume %2 used. If failures continue, decrypt volume.
0x602a1011Metadata check: Metadata record on volume %2 could not be read and has been marked for rebuild. If failures continue, decrypt volume.
0x602b1011Metadata rebuild: An attempt build a new set of metadata on %2 failed at commit and may appear as disk corruption. If failures continue, decrypt volume.
0x602c1011Encrypted volume check: Volume information on %2 cannot be read.
0x602d1011Initial state check: Rolling volume conversion transaction on %2.
0x602e1011BIOS/TCG Memory Overwrite Control: Error finding TPM driver.
0x602f1011BIOS/TCG Memory Overwrite Control: Error registering TPM device interface.
0x60301011BIOS/TCG Memory Overwrite Control: Error changing value.
0x60311011A valid BitLocker key was found during the last restart.
0x60321011The auto-unlock master key was not available from the operating system volume. Retry the operation via the BitLocker WMI interface.
0x60331011Boot debugging is enabled on Bootmgr so TPM based keys cannot be obtained.
0x60341011The partition size specified in the partition table is smaller than the size of the file system contained by that partition. BitLocker TPM based keys cannot be used until the size of the partition calculated from the partition table is consistent with the size of the file system calculated from the bytes per sector and number of sectors fields in the boot sector.
0x60351011The system firmware failed to enable overwriting of system memory on restart. The firmware should be upgraded.
0x60361011Bootmgr failed to find a BitLocker key file for Volume %2.
0x60371011Bootmgr detected corruption in the BitLocker key file for Volume %2.
0x60381011Bootmgr failed to obtain the BitLocker volume master key from the key file contents.
0x60391011Bootmgr determined that the TPM is disabled.
0x603a1011Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker.
0x603b1011Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match.
0x603c1011Bootmgr failed to obtain the BitLocker volume master key from the TPM.
0x603d1011A boot application hash did not match the expected value during restart.
0x603e1011Bootmgr failed to obtain the BitLocker volume master key from the TPM + PIN.
0x603f1011Bootmgr failed to obtain the BitLocker volume master key from the recovery password.
0x60401011A valid BitLocker key was found during the last restart.
0x60411011An unexpected error was encountered attempting to retrieve the BitLocker volume master key during restart.
0x60421011An internal BitLocker self-test failed for drive %2. BitLocker cannot continue encrypting data. Contact your system administrator.
0x60431011Bootmgr failed to obtain the BitLocker volume master key from the TPM + enhanced PIN.
0x60441011An internal BitLocker self-test failed for drive %2 when switching from raw mode to filtering mode. BitLocker cannot continue encrypting data on this drive. Contact your system administrator.
0x60451011Bootmgr failed to obtain the BitLocker volume master key from the network key protector.
0x60461011Encryption of the used space on volume %2 started.
0x60471011Encryption of the used space on volume %2 stopped.
0x60481011Encryption of the used space on volume %2 completed.
0x60491011Wiping of free space on volume %2 started.
0x604a1011Wiping of free space on volume %2 stopped.
0x604b1011Wiping of free space on volume %2 completed.
0x604c1011A recovery password was used to start Windows. Protector ID: %5.
0x604d1011Bootmgr failed to obtain the BitLocker volume master key from the password.
0x604e1011A recovery key was used to start Windows. Protector ID: %5.
0x604f1011The BitLocker driver has started a self-healing operation on the metadata of volume %2.
0x60501011The BitLocker driver has successfully completed a self-healing operation on the metadata of volume %2.
0x60511011Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot was disabled.
0x60521011Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot configuration changed unexpectedly.
0x60531011Device Lock was triggered due to too many incorrect password attempts.
0x60541011BitLocker encryption on write started for volume %2.
0x60551011BitLocker free space sweep started for volume %2.
0x60561011BitLocker free space sweep stopped for volume %2.
0x60571011BitLocker free space sweep completed for volume %2.
0x60581011BitLocker finalization sweep started for volume %2.
0x60591011BitLocker finalization sweep paused for volume %2.
0x605a1011BitLocker finalization sweep resumed for volume %2.
0x605b1011BitLocker finalization sweep completed for volume %2.
0x605c1011BitLocker encryption on write failed for volume %2 due to disk I/O error. Check the disk for bad sectors.
0x605d1011BitLocker finalization sweep failed for volume %2 due to disk I/O error. Check the disk for bad sectors.
0x605e1011Disk containing volume %2 is employing non-volatile caching software which does not support control over its caching policies. This may temporarily impact BitLocker's ability to fully secure your data.
0x605f1011Disk containing volume %2 is employing non-volatile caching software which is experiencing problems. This may temporarily impact BitLocker's ability to fully secure your data. Contact disk manufacturer for an updated software.
0x60601011Device Lock was triggered due to Device Lockout state validation failure.
0x60611011Drive %2 is no longer automatically managed by device encryption.
0x60621011Drive %2 is now automatically managed by device encryption.
0x60631011WIM hash generation paused for volume %2.
0x60641011WIM hash generation resumed for volume %2.
0x60651011WIM hash generation completed for volume %2.
0x60661011WIM hash generation failed for volume %2.
0x60671011WIM hashes will be deleted for volume %2.
0x60681011Bootmgr failed to unseal VMK using the TPM
0x60691011Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to acquire protocol handle.
0x606a1011Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to get IP address.
0x606b1011Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to create request.
0x606c1011Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to send request.
0x606d1011Bootmgr failed to obtain the BitLocker volume master key from the network key protector: invalid response.
0x606e1011Bootmgr failed to obtain the BitLocker volume master key from the network boot protector.
0x310000001011Info
0x310000011011Start
0x310000021011Stop
0x500000021011Error
0x500000031011Warning
0x500000041011Information
0x900000011011Microsoft-Windows-BitLocker-Driver
0x900000021011System
0x910000011011Microsoft-Windows-BitLocker-Driver-Performance
0x606f11BitLocker timed out attempting to enumerate bands during volume discovery on this hardware encrypting drive.
0x607011Failed to read metadata from logical copy. Volume: %2, Start Offset: %3, Read Length: %4, Copy: %5, Number of Copies:%6
0x607111Attempted to read metadata from logical copy. Volume: %2, Start Offset: %3, Read Length: %4, Copy: %5, Number of Copies:%6
0x607211Attempted to fix metadata logical copies. Volume: %2, ManageFlags: %3
0x607311Failed to verify metadata logical copy against Primary. Volume: %2, Start Offset: %3, Read Length: %4, Copy: %5, Number of Copies:%6
0x607411Failed to verify metadata file against Primary copy. Volume: %2, Start Offset: %3, Read Length: %4, Copy: %5, Number of Copies:%6
0x607511Failed to register metadata check worker. Volume: %2
0x607611Metadata check worker started. Volume: %2
0x607711Metadata check worker completed. Volume: %2
0x607811Successfully created metadata file. Volume: %2, Offset: %3, Read Length: %4, Copy: %5, Number of Copies: %6, TpAllocationSize: %7
0x607911Failed to read a valid metadata copy. Volume: %2, Start Offset: %3, Index: %5
0x607a11Failed to fix metadata logical copy. Volume: %2, Start Offset: %3, Read Length: %4, Source Index: %5, Number of Copies: %6, TpAllocationSize: %7
0x607b11Attempted to check metadata logical copies. Volume: %2, ManageFlags: %3
0x607c11Successfully fixed metadata logical copy. Volume: %2, Start Offset: %3, Read Length: %4, Source Index: %5, Number of Copies: %6, TpAllocationSize: %7
0x607d11Volume %2 has been excluded from device encryption by BitLocker Drive Encryption policy. Excluded Hardware ID: '%3'
0x607e11Read-only BitLocker Drive Encryption policy has been applied to volume %2.
0x607f11Failed to determine whether volume %2 should be excluded from enforcement by BitLocker Drive Encryption policy.
0x608011BitLocker Drive Encryption metadata was found to use unencrypted integrity validation hash on volume %1.
0x608111TPM protector %2 binding %3 final PCR values did not match those observed in the TPM
0x608211TPM protector %2 binding %3 final PCR values did not match those observed in the TPM
0x608311TPM protector %2 binding %3 final PCR values did not match those observed in the TPM
0x608411TPM protector %2 binding %3 final PCR values did not match those observed in the TPM
0x608511This event contains the boot-time final TPM PCR values and TCG log data.
0x608611There was a problem communicating with the TPM at boot.
0x608711A V2 TPM protector was used to start Windows. Binding ID: %5.
0x608811The TPM was not available at boot.
0x608911The Inline Crypto Engine hardware did not produce the expected cryptographic output. Volume: %2
0x609011A TPM protector binding failed to unlock the volume despite matching the expected TPM unlock state.
0x609111A V2 TPM protector could not be used to start Windows. Binding ID: %5.
0x609211A hardware protected key was not provisioned for the volume.
0x609311A hardware protected key was not used for the volume.
0x609911Request for UEFI to connect networking failed. Status: %1.
0xd000000111Unspecified
0xd000000211ProtectorAdd
0xd000000311RefreshBindings
0xd000000411VmkRecycle
0xd000000511UpdatePin
0xd000000611None
0xd000000711SHA1
0xd000000811SHA256
0xd000000911SHA384
0xd000000a11SHA512
0xd000000b11SM3-256
0xd000000c11SHA3-256
0xd000000d11SHA3-384
0xd000000e11SHA3-512
0xf0000001110
0xf0000002111
0xf0000003112
0xf0000004113
0xf0000005114
0xf0000006115
0xf0000007116
0xf0000008117
0xf0000009118
0xf000000a119
0xf000000b1110
0xf000000c1111
177 entries