Use BitLocker Repair Tool to Recover Encrypted Drive in Windows  

THANKS FOR YOUR PATIENCE

Hello, I have used option 2 successfully to recover the SSD that came out of my daughter's Surface Pro 4. She experienced, like many, a black-screen freeze problem. After many trials of trying to reset it with power-button-hold cycles (and power-button-+volume holds). I harvested the SSD out and have gotten all the files out like the option 2 tutorial showed [Tremendous THANK YOU, BTW]. I notice in Disk Manager now [picture below], that it shows up now as Disk-1. It has a MB partition, then a healthy F-drive (BitLocked), and a Windows RE tools drive. It looks like this may be her old operating system and data. Somewhere I read this might usable to boot from and in fact, may come back to life just like it looked on her Surface, but now in a different tower-form.
When I change the boot order in BIOS to have 1) USB Hard Disk SABRENT [the name of the adapter I used] and 2) UEFI USB SABRENT, and I disconnect the other hard drive in the tower-computer, restart, It comes back with "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key"

OK, thank you. I am intrigued now. I solved the booting issue. I needed to make "UEFI Hard Disk:SABRENT" the first choice. It then started to load and asked me for the BitLocker key. So, I inputted. Started to wake up. Got a message about updating configuration, then it crashed. BSOD with "stop code: driver unloaded without cancelling pending operations". It eventually shut down. I have reconnected the main drive. I can go in and unlock the SSD drive with the key. So, no harm to the recovered drive.
Just starting to research that stop error.
Also, while I am in the control panel page where I unlock the drive. It gives me an option to turn BitLocker off for that drive. Also an option for "Turn on Auto-Unlock". I was going to fiddle around with those too. Thank you!

Hello, I get the SSD to boot up, but I get:<br>"stop code: driver unloaded without cancelling pending operations. What failed dump_WppRecorder.sys". As it tries to update. I have gone through advance recovery and done a "repair". I eventually was able to get all the way back in. I had read that drivers may be the culprit. I updated them all, some were old, and new ones were found. I did get all the latest updates downloaded, it shows "up to date". But then when I go to restart, I get the error again. I have been able to get in using the recovery method twice now. I have read that some have gone in through the command prompt in safe-mode and disabled the WppRecoder.sys. But I have also read that it is pretty important. Have you seen something like this before? Thank you

No, I am trying to avoid that (but may give up soon).

Hi @Brink Any specific reason why not to use the destination\recover.img in the commands?