I've been trying to make a rescue disk, as a way of having a total, bootable restore of Windows 10, on a new DELL computer with uEFI Booting.
If I understand, Windows requires a Master Boot Record (MBR) to recognize and use a Rescue Disk. MBR is also the old partitioning scheme that has given way to a new partitioning scheme called GPT. GPT and the new Booting scheme, uEFI, go together like peas and carrots. They are litterally made to work with each other.
The newer drive formatting scheme is NTFS, which has advantages over the older FAT32. FAT32 is limited in File size to 4GB, while NTFS has a limit that is beyond anything a home user would ever need.
If I'm going to make a rescue disk of a new computer with GPT disks and uEFI booting, FAT32 drive formatting is required, because uEFI will not recognize NTFS. (from Macrium user guide) Why wouldn't the new booting recognize the new drive format scheme?
I find this very unintuitive and confusing. I'm hoping there is simply something that I am not understanding. I want to make a single file on an external SSD (a really big thumb drive) but the size is much bigger than the 4GB limitation of FAT32.
To be clear:
I want to create a single, large file (about 80GB) on an external, non-disk SSD formatted NTSF (just like the internal HD is) that will boot GPT/uEFI and install an identical copy of Windows 10, with all it's updated stuff. Isn't that what everybody wants?!?
I'm not sure about which way to go. Is it unfeasible to use an external HD for my purposes? And why would Windows require MBR on a newer system with GPT/uEFI? Shouldn't it be NTFS/GPT/uEFI all the way? Isn't the HD set up like that for the OS? The OS is certainly not broken up into 4GB pieces, is it? This makes no sense to me.
Is this a problem with Rescue Disk, such that I'd be better off to use Disk Image with an added Boot file, or some other option???
What am I missing? (Please imply scattered turret-like outbursts)