On MX's XFCE, Start>Disks didn't give the info. Start>Quick Systems Info showed: UEFI (Legacy) 8/14/2019 From that info. I *assume* my computer is UEFI & "Legacy" means... it's an old-time classic UEFI, like an abacus had, waaay back in 2019?
That's confusing. Have a look with GParted. Do you see a EFI System Partition? UEFI systems have one. MBR (Legacy, BIOS) systems don't. Also in GParted, click View, Device Information. What is the "Partition table"? It's in the left hand side. Is it msdos or gpt?
Will do so tomorrow. I'm back on Win7 now & surfing the net while (multi-tasking) watching Castle re-runs on TV.
wat0114, I checked my notes on BitLocker. Is this consistent with what you understand? Let's say you have a Win10 OS, BitLocker is on for the OS. After any restart BitLocker is on and the partition is unlocked. Because it's unlocked you can do a VSS backup. If you want to create an image offline you boot into TBWinRE. The partition is now locked and you have to unlock it before creating a backup. It's a pain to type the following so have a script. Either of the following will unlock the partition. Use your own passwords. Code: manage-bde -unlock C: -recoverypassword 098032-033550-457622-063591-281171-518969-471988-435237 Code: manage-bde -unlock C: -RecoveryKey "G:\6968786A-786B-4C69-B753-F2F5BEEE9175.BEK" Practically, the first is easier. The partition is now unlocked and you can create an IFW backup image using "Read from Volume". You can create single partition or entire drive images. But if you want BitLocker to be on after the restore, do a partition restore of the OS, not an entire drive restore. Prior to doing the restore in TBWinRE, unlock the OS partition with manage-bde. BitLocker will be on when you next boot Win10.
Hi Brian, In my case my entire Windows partition is Bitlocker encrypted. However, I don't use the methods you describe above for offline backups. What I do is: From Windows I go to Bitlocker settings then choose the "Suspend" Bitlocker option for the Windows partition. I plug in my IFW pendrive and restart computer. When booting to the Recovery environment is completed, Bitlocker is "Suspended", or unlocked, so I can backup using the "Read from Volume" option in IFW. I seem to remember some years ago you advised me to use this latter option when I had issues After creating the backup image, I remove pendrive and boot back into Windows where Bitlocker will automatically "un-suspend" itself. The Suspend option is very handy, since it does not actually remove the Bitlocker encrypted state from partition, it only unlocks it for offline image backups or restores, and basically until the next reboot into Windows. EDIT I forgot to mention my device uses TPM, so I don't need a password to unlock Bitlocker to get into Windows. I do have the Recovery key saved for it just in case.
wat0114, Thanks for that. I'd forgotten about the "Suspend" method. But if you can't get into Win10 for some reason, then you would have to unlock with manage-bde prior to doing a restore. But if you can get into Window then "Suspend" is a lot easier than manage-bde. I agree.
Exactly where your method - which I confess to not knowing about until now, thanks for that! - has an advantage if one can't get into Windows. Actually, I've been in that situation not once, but twice before, and in both cases I used a less convenient and efficient method, which works fine all the same, where I booted into Linux, used GParted to format the botched Windows drive which removes Bitlocker encryption, then I booted into the IFW live rescue environment to restore an image.
I found these tests I'd run a few years age. Tried to restore an OS image to a locked partition in TBWinRE. Failed. "A hard drive error occurred when writing 80 sectors…………" In IFL, an OS image was restored to a locked partition. The restore succeeded but BitLocker was off when Win10 booted. As expected.
Oh okay, that is probably the same or similar error that I got when I tried to restore to a locked drive years ago. I do remember you helping me out of the issue.
I just ran some BitLocker tests. In the manage-bde -unlock C: ... line, you need to edit C: to the drive letter of the OS partition as seen in TBWinRE. If you run (from a Command prompt in TBWinRE)... Code: manage-bde -status ...it will let you know the drive letter of the OS partition. It's unlikely to be C: It helps to have Explorer++ in TBWinRE as you can access the script and edit it to the correct drive letter. Put "pause" in the script so you can see what has happened. Code: manage-bde -unlock F: -recoverypassword 098032-033550-457622-063591-281171-518969-471988-435237 pause My drive letter was F:
I hate dual boot. When I install a Linux distro in a Windows PC, it means that the Windows OS has become impossible to use in a satisfactory way. With my ex Windows XP pc this critical point was never reached. With my daughter's ex-W.10 pc the tipping point was reached with 21H1.