Switching to MBR and therefore Legacy BIOS booting means you can't use UEFI Secure Boot, which is a nice anti-rootkit protection mechanism. And MBR disks only allow 4 primary partitions; having more partitions requires creating an "extended partition" and then having logical volumes in it. And MBR can't be used for disks larger than 4TB, at least not if you want to be able to use the full capacity of the disk. (I'm ignoring an ugly hack implemented on some old USB enclosures that allowed >4TB disks in MBR specifically to allow such disks to be used with Windows XP.) Additionally, it seems that as of recent Windows 10 feature releases, if Windows 10 is set up for Legacy BIOS booting but detects that your system is capable of booting in UEFI mode, it will force you to convert to GPT and therefore UEFI booting. The only way around this is to have a system that allows you to enable ONLY Legacy BIOS mode, i.e. disable UEFI completely. But some systems only allow you to enable Legacy support alongside UEFI by enabling Legacy Option ROMs (aka UEFI CSM). If that's your system, you might find yourself forced to convert back to GPT/UEFI boot on the next Win10 feature release before Windows will allow you to install it. Giving up on a security feature like UEFI Secure Boot just to look at a different logo for the 1-3 seconds that your system displays it seems foolish -- particularly as you're asking on a security forum -- but if you really want to do it, Macrium has this guide for how to perform a custom restore of a GPT disk onto an MBR disk, including making the necessary changes to allow it to boot in BIOS mode. But honestly, just set your desktop background to the Microsoft logo if you really like looking at it. Then you can see it even more and still get to keep UEFI Secure Boot. But in terms of your later question about restoring, if you do that custom restore and then later on run a regular restore of a backup that was captured while your disk was GPT, then your restored disk will be GPT. If you restore a disk from a backup that was made while it was MBR, then it will be MBR after the restore. The only exception would be if you performed a custom restore by dragging and dropping specific source partitions onto specific destination partitions (or pockets of free space) in which case Reflect will restore only those partitions without changing the entire disk layout scheme.