Use BitLocker Repair Tool to Recover Encrypted Drive in Windows  

Page 5 of 5 FirstFirst ... 345
  1. Brink's Avatar
    Posts : 59,940
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #40

    Darkane said:
    it didnt work and other apps that work need like 150 $ i can't afford that
    i was trying to make the chkdsk work you think it is possible?
    It doesn't seem like it will if corrupted.
      My Computers


  2. Posts : 9
    windows 10 pro 64 bit
       #41

    it is ok thanks anyway for trying to help i appreciate it
      My Computer


  3. Posts : 6
    Windows 10
       #42

    I had performed option 2 on OS drive, but User files are not on the target drive.

    My Bitlocker encrypted computer shut down a few times by itself when I was away from the keyboard. Every time when I came back to it from another room, the power was off, but there were no power surges in my house, so I don't know the cause for it shutting down by itself. The next time I tried booting up, the computer attempted to boot into Automatic Repair, but asked never succeeded, it just asking my for Bitlocker password and going into a loop. Couldn't go into safe mode either.

    I connected OS NVMe SSD via external enclosure to a laptop and recovered the data to another drive via option 2. After performing chkdsk D: /f, everything seems to be on that new drive except my User folder. There are only 2 folders under X:\Users\ that are called Default and Public. I had copied all the output I could grab from CMD (6 thousands lines) and this did grab my attention:

    Code:
    ...
    2 thousands lines of "Failed to read sector X at offset Y" Lines
    ...
    
    
    Failed to read sector at offset 1783707142656. (0x00000017)
    LOG ERROR: 0xc0000037
    Failed to read sector at offset 1783707143168. (0x00000017)
    LOG ERROR: 0xc0000037
    Failed to read sector at offset 1783707143680. (0x00000017)
    Decrypting: 100% Complete.
    Finished decryption.
    
    
    ACTION REQUIRED: Run 'chkdsk D: /f' before viewing decrypted data.
    
    
    C:\Users\Laptop>chkdsk D: /f
    The type of the file system is NTFS.
    
    
    Stage 1: Examining basic file system structure ...
    Deleted corrupt attribute list entry
    with type code 30 in file 6A7F.
    Deleted corrupt attribute list entry
    
    
    ...
    3 thousands lines later
    ...
    
    
    CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 5C8.
    Sorting index $I30 in file 5C8.
    Deleting index entry mpcache-7DC74330A002CFBA30F88A5F1241607B94D5DC12.bin.7C in index $I30 of file 5C8.
    Deleting index entry mpcache-7DC74330A002CFBA30F88A5F1241607B94D5DC12.bin.7E in index $I30 of file 5C8.
    Deleting index entry MPCACH~1.7C in index $I30 of file 5C8.
    Deleting index entry MPCACH~1.7E in index $I30 of file 5C8.
    Deleting index entry MP2CF5~1.BIN in index $I30 of file 5C9.
    Deleting index entry MPDeviceControl-20210804-133053.log in index $I30 of file 5C9.
    Deleting index entry MPDEVI~1.LOG in index $I30 of file 5C9.
    Deleting index entry MPLog-20211118-080721.log in index $I30 of file 5C9.
    Deleting index entry MPLOG-~1.LOG in index $I30 of file 5C9.
    Deleting index entry MpWppTracing-20211123-151417-00000003-ffffffff.bin in index $I30 of file 5C9.
    Deleting index entry SH3A3E~1.ETL in index $I30 of file 5DF.
    Deleting index entry SHS-11232021-151440-7-7f-19041.1.amd64fre.vb_release.191206-1406.etl in index $I30 of file 5DF.
    Deleting index entry UP8384~1.ETL in index $I30 of file 5EB.
    Deleting index entry UpdateSessionOrchestration.82448e79-70da-4606-a58d-c32ebbd2f579.1.etl in index $I30 of file 5EB.
    Deleting index entry UpdateSessionOrchestration.af0e84b4-56ef-4ae9-b69b-75eb25b73f25.1.etl in index $I30 of file 5EB.
    Deleting index entry UPE46B~1.ETL in index $I30 of file 5EB.
    Deleting index entry WU95E6~1.ETL in index $I30 of file 5EB.
    Deleting index entry WUAD56~1.ETL in index $I30 of file 5EB.
    Deleting index entry WuProvider.54c17b44-665f-4c59-8edc-1cc4ff5e2538.1.etl in index $I30 of file 5EB.
    Deleting index entry WuProvider.a7dc25f8-325d-4570-991c-12b91aacc49f.1.etl in index $I30 of file 5EB.
    Deleting index entry NO64F8~1.ETL in index $I30 of file 5EC.
    Deleting index entry NO8272~1.ETL in index $I30 of file 5EC.
    Deleting index entry NODD86~1.ETL in index $I30 of file 5EC.
    Deleting index entry NotificationUx.159cf477-7bf8-4017-8386-ec0dbcce5da6.1.etl in index $I30 of file 5EC.
    Deleting index entry NotificationUx.6e6a3b0d-ab51-4e3f-93dd-16c3de9e12f4.1.etl in index $I30 of file 5EC.
    Deleting index entry NotificationUx.fa963793-0f95-4409-ae7e-0ce9c3186daf.1.etl in index $I30 of file 5EC.
    Deleting index entry Boss in index $I30 of file 5EF.
    Correcting error in index $I30 for file 628.
    CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 628.
    Sorting index $I30 in file 628.
    Deleting index entry gdrv3.sys in index $I30 of file 628.
    Deleting index entry Amcache.hve in index $I30 of file 62D.
    Deleting index entry Amcache.hve.tmp.LOG1 in index $I30 of file 62D.
    Deleting index entry Amcache.hve.tmp.LOG2 in index $I30 of file 62D.
    Deleting index entry AMCACH~3.LOG in index $I30 of file 62D.
    Deleting index entry AMCACH~4.LOG in index $I30 of file 62D.
    Deleting index entry NativeImages_v2.0.50727_32 in index $I30 of file 635.
    Deleting index entry NATIVE~2.507 in index $I30 of file 635.
    Deleting index entry DE4EB0~1 in index $I30 of file 671.
    Deleting index entry Devolutionse2b1e0ad# in index $I30 of file 671.
    Correcting error in index $I30 for file 6E1.
    CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 6E1.
    Sorting index $I30 in file 6E1.
    Deleting index entry Microsoft.V0f908656# in index $I30 of file 6E1.
    Deleting index entry Microsoft.Vdf92321b# in index $I30 of file 6E1.
    Deleting index entry Boss in index $I30 of file 5EF
    Boss is actual username and the folder name. Could that folder been by chkdsk or rather not recovered by recover-bde?

    Another strange thing is I did perform all the actions on a laptop in safe mode as CMD was either giving me a generic error or telling me that one of the drives were in use, so this is what I see from the laptop from safe mode:
    Use BitLocker Repair Tool to Recover Encrypted Drive in Windows-untitled3.png

    Yet, it doesn't work from normal mode:
    Use BitLocker Repair Tool to Recover Encrypted Drive in Windows-2021-11-27_11-20-52.png

    @Brink, could you give me an advice how to recover User files or/and how to keep using the original drive, please?
    Last edited by TenBoss; 3 Days Ago at 04:08.
      My Computer

  4. Brink's Avatar
    Posts : 59,940
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #43

    Hello @TenBoss,

    Check the permissions of the "D" drive to make sure you have access rights.

    Change Permissions of Objects for Users and Groups in Windows 10

    It looks like either there was drive corruption or the BitLocker recovery process may have been interrupted since the "E" drive still shows as encrypted by BitLocker in normal mode and "in use" in safe mode, and no access to the "D" drive you recovered to.
      My Computers


 
Page 5 of 5 FirstFirst ... 345

Tutorial Categories

Use BitLocker Repair Tool to Recover Encrypted Drive in Windows Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 06:51.
Find Us




Windows 10 Forums