Another issue - It seems that if a disk/volume is protected by FDE with Pre-Boot-Authentication turned on (which is one of the main reasons people install FDE), the startup bootloader of the Disk Imaging software would not work, because that bootloader conflicts with the bootloader of the FDE app. I wonder if the use of SpinRite would affect the effective working of the bootloader of either the Disk Imaging app or the FDE app?
Correct me if I'm wrong, it seems that only 1 bootloader can be installed. Wonder if it's possible to create a "SpinRite meta-bootloader" where SpinRite users can at startup choose between the SpinRite 8.0 bootloader, the Disk Imaging app's bootloader, or the FDE's bootloader? But then it may defeat the purpose of activating FDE's Pre-Boot-Authentication in the first place... just thinking aloud.
Or is it possible to have SpinRite 8.0 bootloader automatically loaded after FDE Pre-Boot-Authentication?
i.e. Power up PC => FDE Pre-Boot-Authentication bootloader => enter FDE pre-boot credentials => SpinRite 8.0 bootloader loads up and provides options to 1) start SpinRite to check/repair disk, or 2) Windows 10 startup bootloader, with options for entering UEFI, boot using external devices or proceed to normal Windows startup