Group: Forum Members
KB: Yes, if you are switching platforms AND moving to dissimilar hardware, then you would do both. ReDeploy would be the final step.
Fix Boot Problems: It’s available in all types of Rescue Media. The original article was probably written before WinRE became an option (as of Reflect 7.2) and that language might never have been updated. But it’s also important to note that you have to boot the Rescue Media itself using the same mode that you want fixes applied for. So for example if you’re trying to set up Windows for UEFI boot, then you have to boot the Rescue Media in UEFI mode. You can verify this by checking the title bar along the very top of the Rescue interface. It will say “UEFI” at the very end if it was booted in UEFI mode. And this step is necessary in this specific scenario because the process described in the KB article includes making a brand new EFI partition that will be empty. Fix Boot Problems when run in UEFI mode creates a Windows Boot Manager instance on that EFI partition using bootloader files copied from the core Windows partition. A correctly configured EFI partition is necessary for UEFI booting.
Secure Boot: I don’t understand how you can be booting in UEFI mode if your disk is MBR, unless you have another physical disk in your system that contains the Windows bootloader, which is then turning around and booting from the Windows partition on your MBR disk. Perhaps a screenshot of the Local Disks tab in Reflect would be illuminating here. A picture can quite often be worth 1000 words here.
Uninstalling: Removing old devices and their associated drivers isn’t really worth the effort. They won’t load if the device is no longer present, and drivers typically won’t free up enough space to be worth the effort. Uninstalling applications of course can be useful. An uninstallation that renders your system unbootable is rather rare, but if the application/utility in question loaded a boot-time component, that can happen. Some antimalware solutions have been notorious for this. They hook deeply into the system and don’t clean themselves up properly on uninstallation, so sometimes after removing them, your system no longer starts properly because it left some dependency on a component that no longer exists.
MBR2GPT: If you’re going to attempt the KB article steps, then you can forget about this. The KB article will give you a cleaner result anyway since you’ll have the reference partition sequence, which you can’t get with MBR2GPT.