2.) You can then unpack the 4,6gb *.Msix file using winrar. There you will also find the vhdx flash image.
3. ) You will then receive the 8,4gb file "Flash.vhdx", after unpacking the Msix file. Mount it, then select "Storage Spaces" and you should get this : (thx to @rcstar6696)
I got confused by the "You dont have permission to mount the file." But you are right, a 128 GB Virtual Disks shows up...unrecognized
I'm wondering if the execution of it isn't needed until MEM boots it, and it just places a pre-loaded one, if not one from the host OS. I only say this because when you open a copy of the Flash VHDX converted with QEMU to VHD, it gives a bootx64.efi that specifies a build of Windows that's older (19526) than the build we currently have (19563). It might just be a coincidence but I am curious. It makes me wonder why 1. the file size increases from the Flash VHDX to the Snapshot VHDX, and 2. why neither of the VHDX' are bootable with VBox, and give such weird errors when trying to mount and/or extract. Thoughts?
I converted the VHDX to VHD, using "StarWind V2V" now and VirtualBox on booting says : "FATAL : No bootable medium found! System halted."