![]() ![]() Some further notes and screenshots I grabbed along the way. The VHD I managed to create - which is reusable, BTW, so it should be saved and copied whenever needed - rebooted once in the VM and threw up an error afterwards, saying " Something went wrong" (with code " OOBEAADV10"), but it advanced to finish without any other errors.You must have a working internet connection, then just open terminal and run ' sudo apt-get install virtualbox' around 45MB of data will be downloaded and after install finishes, just do Alt+F2 and type " virtualbox" to start it.LiveUSB preventing access to the drive they're booted from is the reason you can't do this from the internal disk.16GB will work fine and apparently you can expand VHDs later - e.g., see.Booted the VHD with Ventoy and proceed to finish WindowsToGo setup (couple of hiccups here, see d.), which might require some reboots.Īll set! Ventoy now boots WindowsToGo without any errors.Copied the VHD file to Ventoy boot location (' BOOTIMGS' folder in the main drive, in my case), alongside the already existing ' ventoy' folder with at least ' ventoy_vhdboot.img' in it.Stopped the VM without proceeding any further.Let WindowsToGo setup finish inside the VM up to the point where OOBE (" Windows Out Of Box Experience") pops its first question.Setup a discardable VirtualBox (see c.), ran it and attached the recently created VHD file to a new Windows 10 virtual machine ( VM).Booted up Linux Mint from a Ventoy liveUSB pendrive (see b.). ![]() Used Rufus and a Windows 10 ISO to setup WindowsToGo to that VHD in MBR Mode.Used ' diskmgmt.msc' to create a static size 32GB VHD (don't forget to initialize and format it to NTFS also see a., below).It took me some time - be warned this is a lenghty procedure - but I've now tested his solution in two different systems (desktop and laptop) and everything worked fairly well.įTR, let me recall here what I did, after booting Windows 10 normally (which I already run off a VHD, as detailed in my previous post): Many thanks to meilon for posting about this solution. It always fails after getting devices ready with "Windows could not update the computer's boot configuration. Now after formatting the Ventoy partition as NTFS at least the system tries to boot from vhdx, but sadly, I can't get any configuration of vhd/vhdx, mbr/gpt and dynamic/fixed to boot completely in either legacy or uefi mode. Thank you both! I read in the forum post linked in the issue the very important line (thanks to Google Translate): VHD(X) boot currently only supports dual NTFS or dual exFAT combinations, and does not support outer NTFS+in exFAT or outer exFAT+in NTFS combination. You need to manually format the first partition of your USB drive as NTFS after installing Ventoy for Windows to boot. ![]() (04-08-2021, 12:54 PM)Midas Wrote: meilon: I haven't tested any of it but you pointed at the problem yourself - Windows will not boot off an exFAT partition, which Ventoy uses by default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |