Thanks for the replies, and Happy Monday! That is a relatively fair assumption. Although, I could also be classified as an overly ambitious tweaker as well... Back when Win 7 was originally released, I jumped straight into running from VHD, before I even tried the OS in a "standard" setup. I have sunk many hours into tweaking Windows to Go, managing to get it up and running off of a VHDx as well, and made quite a snazzy USB drive. (I could boot to-go x86 as well as x64; and had a single Install.WIM for multiple versions of 7 and 8, both x86 and x64.) And then I wiped everything and started over. Sounds like I'm in for an adventure, in that case! I'll have to do some experimenting, and document the procedure for posterity. I'm personally a little paranoid about my backups, compared to the average computer user. I manually copy & keep backups of my boot VHDs, and my data lives on a separate data drive, RAID 1 with ReFS, that is backed up continually to the cloud and my wife's PC, as well as to a weekly rotating pair of external drives that I keep offsite... In a nutshell, my PC is setup thusly: Boot SSDData HDD (RAID 1, ReFS)Data HDD (RAID 1, ReFS) On my boot SSD is arranged like this: A small UEFI system partition with the boot entriesPrimary partition to house my VHDx filesMy VHDx files are laid out as indicated in the first post. Essentially, each is treated as a completely separate install of Windows, as far as the boot loader is concerned. Each VHDx has its own BCD entry, and switching between them is as simple as a reboot. Each boot, I can choose what VHDx to load in the standard BCD boot menu. To be perfectly honest, I primarily use two different ones, my "Daily Use" and my Gaming. It was a complete pain to have to configure my screens for multi-monitor gaming, and then reconfigure them for normal use. So I simply made a new VHDx that has the appropriate settings, and can switch quickly.