KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY
Server : Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12
System : Windows NT SERVER-PC 10.0 build 26200 (Windows 11) AMD64
User : ServerPC ( 0)
PHP Version : 8.2.12
Disable Function : NONE
Directory :  C:/Windows/System32/drivers/en-US/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : C:/Windows/System32/drivers/en-US/fvevol.sys.mui
MZ����@���	�!�L�!This program cannot be run in DOS mode.

$�X=��9S��9S��9S������9S���Q��9S�Rich�9S�PEL�VLc�!&t

��@ �p8.rdata�@@.rsrc�p r@@�VLc
lPP�VLc$����8.rdata8.rdata$voltmdP�.rdata$zzzdbg .rsrc$01"�n.rsrc$02 �XOmR�
h��xV�p�*�Åy(�VLc��0�H���������9��6��7�8(�@�X�	p	�	�	�	�	�	�	��!���"p� #h��#��|&��)��h*�b����MUI����1L%��������P���Ӣ=Ih���K骝���MUIen-US(BitLocker Drive Encryption Filter Driver$BitLocker conversion is in progress.	BitLocker	BitLocker/BitLocker Drive Encryption performance countersMin Read Split SizeMin Read Split Size<Minimum read buffer split size in bytes during last intervalMax Read Split SizeMax Read Split Size<Maximum read buffer split size in bytes during last intervalMin Write Split SizeMin Write Split Size=Minimum write buffer split size in bytes during last intervalMax Write Split SizeMax Write Split Size=Maximum write buffer split size in bytes during last intervalRead Requests/secRead Requests/sec5Number of read requests received over the last secondRead Subrequests/secRead Subrequests/sec6Number of read subrequests issued over the last secondWrite Requests/secWrite Requests/sec6Number of write requests received over the last secondWrite Subrequests/secWrite Subrequests/sec7Number of write subrequests issued over the last secondPA`�`d�`�`�\11_PPH_���_���_��d`���aLEncryption of volume %2 started.

LEncryption of volume %2 stopped.

PEncryption of volume %2 completed.

LDecryption of volume %2 started.

LDecryption of volume %2 stopped.

PDecryption of volume %2 completed.

pConversion worker thread for volume %2 was started.

�Conversion worker thread for volume %2 was temporarily stopped.

PAuto-unlock enabled for volume %2.

hAn error was encountered converting volume %2.

PAuto-unlock disabled for volume %2.

�The conversion operation on volume %2 encountered a bad sector error. Please validate the data on this volume.

`Failed to enable auto-unlock for volume %2.

dFailed to disable auto-unlock for volume %2.

TAuto-unlocking failed for volume %2.

�An attempt to automatically restart conversion on volume %2 failed.

�Metadata write: Volume %2 returning errors while trying to modify metadata. If failures continue, decrypt volume.

4Metadata rebuild: An attempt to write a copy of metadata on volume %2 failed and may appear as disk corruption. If failures continue, decrypt volume.

�Volume %2 contains bad clusters. These clusters will be skipped during conversion.

pNo key file was found for Volume %2 during restart.

�A corrupt key file was encountered for Volume %2 during restart.

�No volume master key was retrieved in a key file during restart.

XThe TPM was not enabled during restart.

hThe SRK was found to be invalid during restart.

XThe PCRs did not match during restart.

�No volume master key was retrieved from a key file during restart.

�A boot application hash did not match expected value during restart.

�The boot configuration options did not match expected values during restart.

�No volume master key was retrieved from a PIN during restart.

�No volume master key was retrieved from a recovery password during restart.

hA valid key was found during the last restart.

�An unexpected error was encountered attempting to retrieve the volume master key during restart.

�A key was not available from required sources during restart.

�Metadata commit: Not all copies of metadata on volume %2 could be written. If failures continue, decrypt volume.

�Metadata commit: No copies of metadata on volume %2 could be written. If failures continue, decrypt volume.

xMetadata commit: Metadata update could not be flushed.

�Metadata commit: An attempt to verify metadata update on volume %2 failed at read. If failures continue, decrypt volume.

�Metadata commit: Update verification of metadata on volume %2 failed. If failures continue, decrypt volume.

�Metadata initial read: Primary metadata record on volume %2 could not be found. Volume needs recovery.

�Metadata initial read: Failover metadata record on volume %2 could not be found. Volume needs recovery.

�Metadata initial read: Failover metadata record on volume %2 used. If failures continue, decrypt volume.

Metadata check: Metadata record on volume %2 could not be read and has been marked for rebuild. If failures continue, decrypt volume.

<Metadata 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.

�Encrypted volume check: Volume information on %2 cannot be read.

�Initial state check: Rolling volume conversion transaction on %2.

�BIOS/TCG Memory Overwrite Control: Error finding TPM driver.

�BIOS/TCG Memory Overwrite Control: Error registering TPM device interface.

|BIOS/TCG Memory Overwrite Control: Error changing value.

|A valid BitLocker key was found during the last restart.

The auto-unlock master key was not available from the operating system volume.  Retry the operation via the BitLocker WMI interface.

�Boot debugging is enabled on Bootmgr so TPM based keys cannot be obtained.

�The 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.

�The system firmware failed to enable overwriting of system memory on restart. The firmware should be upgraded.

�Bootmgr failed to find a BitLocker key file for Volume %2.

�Bootmgr detected corruption in the BitLocker key file for Volume %2.

�Bootmgr failed to obtain the BitLocker volume master key from the key file contents.

dBootmgr determined that the TPM is disabled.

�Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker.

�Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match.

�Bootmgr failed to obtain the BitLocker volume master key from the TPM.

�A boot application hash did not match the expected value during restart.

�Bootmgr failed to obtain the BitLocker volume master key from the TPM + PIN.

�Bootmgr failed to obtain the BitLocker volume master key from the recovery password.

|A valid BitLocker key was found during the last restart.

�An unexpected error was encountered attempting to retrieve the BitLocker volume master key during restart.

An internal BitLocker self-test failed for drive %2. BitLocker cannot continue encrypting data. Contact your system administrator.

�Bootmgr failed to obtain the BitLocker volume master key from the TPM + enhanced PIN.

�An 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.

�Bootmgr failed to obtain the BitLocker volume master key from the network key protector.

pEncryption of the used space on volume %2 started.

pEncryption of the used space on volume %2 stopped.

tEncryption of the used space on volume %2 completed.

`Wiping of free space on volume %2 started.

`Wiping of free space on volume %2 stopped.

dWiping of free space on volume %2 completed.

�A recovery password was used to start Windows.%nProtector ID: %5.

�Bootmgr failed to obtain the BitLocker volume master key from the password.

�A recovery key was used to start Windows.%nProtector ID: %5.

�The BitLocker driver has started a self-healing operation on the metadata of volume %2.

�The BitLocker driver has successfully completed a self-healing operation on the metadata of volume %2.

�Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot was disabled.

Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot configuration changed unexpectedly.

�Device Lock was triggered due to too many incorrect password attempts.

tBitLocker encryption on write started for volume %2.

lBitLocker free space sweep started for volume %2.

lBitLocker free space sweep stopped for volume %2.

pBitLocker free space sweep completed for volume %2.

pBitLocker finalization sweep started for volume %2.

pBitLocker finalization sweep paused for volume %2.

pBitLocker finalization sweep resumed for volume %2.

tBitLocker finalization sweep completed for volume %2.

�BitLocker encryption on write failed for volume %2 due to disk I/O error. Check the disk for bad sectors.

�BitLocker finalization sweep failed for volume %2 due to disk I/O error. Check the disk for bad sectors.

�Disk 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.

�Disk 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.

�Device Lock was triggered due to Device Lockout state validation failure.

�Drive %2 is no longer automatically managed by device encryption.

�Drive %2 is now automatically managed by device encryption.

\WIM hash generation paused for volume %2.

`WIM hash generation resumed for volume %2.

dWIM hash generation completed for volume %2.

\WIM hash generation failed for volume %2.

\WIM hashes will be deleted for volume %2.

`Bootmgr failed to unseal VMK using the TPM

Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to acquire protocol handle.

�Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to get IP address.

�Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to create request.

�Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to send request.

�Bootmgr failed to obtain the BitLocker volume master key from the network key protector: invalid response.

�Bootmgr failed to obtain the BitLocker volume master key from the network boot protector.

�BitLocker timed out attempting to enumerate bands during volume discovery on this hardware encrypting drive.

�Failed to read metadata from logical copy. Volume: %2, Start Offset: %3, Read Length: %4, Copy: %5, Number of Copies:%6

Attempted to read metadata from logical copy. Volume: %2, Start Offset: %3, Read Length: %4, Copy: %5, Number of Copies:%6

�Attempted to fix metadata logical copies. Volume: %2, ManageFlags: %3

Failed to verify metadata logical copy against Primary. Volume: %2, Start Offset: %3, Read Length: %4, Copy: %5, Number of Copies:%6

Failed to verify metadata file against Primary copy. Volume: %2, Start Offset: %3, Read Length: %4, Copy: %5, Number of Copies:%6

tFailed to register metadata check worker. Volume: %2

\Metadata check worker started. Volume: %2

`Metadata check worker completed. Volume: %2

Successfully created metadata file. Volume: %2, Offset: %3, Read Length: %4, Copy: %5, Number of Copies: %6, TpAllocationSize: %7

�Failed to read a valid metadata copy. Volume: %2, Start Offset: %3, Index: %5

,Failed to fix metadata logical copy. Volume: %2, Start Offset: %3,  Read Length: %4, Source Index: %5, Number of Copies: %6, TpAllocationSize: %7

�Attempted to check metadata logical copies. Volume: %2, ManageFlags: %3

8Successfully fixed metadata logical copy. Volume: %2, Start Offset: %3,  Read Length: %4, Source Index: %5, Number of Copies: %6, TpAllocationSize: %7

�Volume %2 has been excluded from device encryption by BitLocker Drive Encryption policy. Excluded Hardware ID: '%3'

�Read-only BitLocker Drive Encryption policy has been applied to volume %2.

�Failed to determine whether volume %2 should be excluded from enforcement by BitLocker Drive Encryption policy.

�BitLocker Drive Encryption metadata was found to use unencrypted integrity validation hash on volume %1.

�TPM protector %2 binding %3 final PCR values did not match those observed in the TPM

�TPM protector %2 binding %3 final PCR values did not match those observed in the TPM

�TPM protector %2 binding %3 final PCR values did not match those observed in the TPM

�TPM protector %2 binding %3 final PCR values did not match those observed in the TPM

�This event contains the boot-time final TPM PCR values and TCG log data.

xThere was a problem communicating with the TPM at boot.

�A V2 TPM protector was used to start Windows.%nBinding ID: %5.

PThe TPM was not available at boot.

�The Inline Crypto Engine hardware did not produce the expected cryptographic output. Volume: %2

�A TPM protector binding failed to unlock the volume despite matching the expected TPM unlock state.

�A V2 TPM protector could not be used to start Windows.%nBinding ID: %5.

�A hardware protected key was not provisioned for the volume.

tA hardware protected key was not used for the volume.

Info

Start

Stop

Error

Warning

 Information

PMicrosoft-Windows-BitLocker-Driver

System

hMicrosoft-Windows-BitLocker-Driver-Performance

 Unspecified

$ProtectorAdd

(RefreshBindings

 VmkRecycle

UpdatePin

None

SHA1

SHA256

SHA384

SHA512

SM3-256

SHA3-256

SHA3-384

SHA3-512

0

1

2

3

4

5

6

7

8

9

10

11

�4VS_VERSION_INFO��
��e
��e?StringFileInfo�000004B0LCompanyNameMicrosoft Corporationl"FileDescriptionBitLocker Drive Encryption Drivern'FileVersion10.0.26100.4768 (WinBuild.160101.0800)6InternalNameFVEVOL.SYS�.LegalCopyright� Microsoft Corporation. All rights reserved.FOriginalFilenameFVEVOL.SYS.MUIj%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.26100.4768DVarFileInfo$Translation�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING

Anon7 - 2021