You can create vhd drive. Add necessary values using boot ice* And extract wim files to vhd loaded drive It should be working *You can achieve same thing with bcdboot tool Just point it to loaded vhd drive letter
Does anybody else have this kind of problems, too? At least the last three releases had issues on my Lenovo P14s - Device and Disk Manager correctly see and identify the Bitlocker partitions, but there is no way by GUI or commands to unlock them - all end in error messages. Does anybody know which was the last release that worked correctly with Bitlocker?
Don't believe any version works with bitlocker. I remove and disable bitlocker everywhere as I like my data. Prevent it from coming back with : reg add "HKLM\System\CurrentControlSet\Control\BitLocker" /v "PreventDeviceEncryption" /t REG_DWORD /d "1" /f fsutil behavior set disableencryption 1 manage-bde -off C: manage-bde -off D: (add any other drives) cipher /d /s:C:\ sc config EFS start= disabled sc config BDESVC start= disabled
The 2023.03.21 or 2023.06.25 release worked for me before I upgraded to the most recent 3 versions - the most recent ones don't work with BitLocker.
Not my decision who's bitlockered PC I have to try to rescue data from. Too bad strelec ran into this problem - is he even aware of it? Until then, I'll resort to other emergency boot media like Ankh.
I had a failed laptop to recover a while back with full bitlocker encryption, luckily the user had the key wrote down. I booted from a Strelec drive and putting the key in did nothing to allow access to the laptop drive. I ran the bat file to change Strelec to boot with Microsoft efi (secure boot) and think that was the secret to getting the decrypt to work with AOMEI Partition Assistant or Acronis. The version of Strelec was WinPE11_10_8_Sergei_Strelec_x86_x64_2023.02.15_English using win 10 boot. It took a few attempts to get it to open the drive. Because of the problems with recovery I avoid bitlocker and block it from encrypting drives everywhere I can. I will include Ankh's iso on my tools drive as well as this is only going to get worse.
Its a nice PE, little longer boot. Used it a couple times last winter. I use macrium, and nothing stood out as better or have to have. As long as macrium works it is a contender. With Strelec, delete wim files you dont use its very small and fast. Boots on everything, Dell tower server to old PC's. In the boot folder is the bat files to switch between grub or ms efi loader. I switch to ms then secure boot isn't a problem. Macrium makes it easy to switch drive layout, old mbr to uef just coy first two partitions to new drive then the recovery part and float right. Write that to the drive. Select image of mbr drive and drag data partition between 3rd and 4th partitions and write that. Macrium has the "fix boot problems" and re-write uef files, disk ID. Easy convert of say a server with 2016 mbr to be a uef drive. I use it all the time. Tried a couple of the others but always go back to Strelec;s. spam_abuse made a decent pe but they haven't updated it in a long time.
BitLocker is not bad, even for data recovery, if you know the recovery key or the password I don't think you have issue recovering them. I'm currently using NHV Boot which I paid for life time license. It has been working for me with BitLocker encrypted drives. All other similar WinPE all have issues. Been a long time strelec user but this BitLocker bug is really a deal breaker for me as I use BitLocker extensively on all my computers.
Thanks for the hint. There still seems to be a dependeny on the actual hardware. For me, on a Lenovo P14s, Paragon HD Manager worked (Acronis and AOMEI didn't) with the latest 24.09.20. Still awkward, password didn't do the trick, but with the BEK file it worked. My best guess is that strelec messed up the Windows-internal bde setup, and some of these partitioning tools bring their own internal routines.
Everytime I try to run Active File Recovery 24.0.2 or Active Partition Recovery 24.0.2 they just output an exception error and close. Also EaseUS Data Recovery 19.1.0 Build 20240821 was able to find deleted files, but when starting to recover, it does not start, stays at 0% forever and no disk activity (I guess the program was not properly patched).