Why does Eazy Fix modify the MBR on both the internal NVMe SSD and the Samsung T7 Shield portable USB 3.2 Gen 2 SSD during installation of the subconsole? This causes Ventoy on the portable SSD to no longer work because it fails the MBR check when I try to boot Ventoy from the portable SSD from the one-time boot menu until I reinstall Ventoy.
It shouldn't be doing that if that external disk is not selected for protection when Easy Fix is installed... CUSTOM install should insure that that disk is not selected, DEFAULT install may select them all.
The MBR on all drives including USB gets written each time I turn on protection and then the subsystem is reinstalled. While Eazy Fix protection is enabled if I try to install Ventoy to a USB drive it fails when it tries to write the MBR.
