It’s honestly wild how convenient it is. Ventoy was the only method that worked for me when I needed to install Windows alongside an existing Linux setup for dual-booting. Everything else I tried failed, but Ventoy handled it perfectly.
It’s honestly wild how convenient it is. Ventoy was the only method that worked for me when I needed to install Windows alongside an existing Linux setup for dual-booting. Everything else I tried failed, but Ventoy handled it perfectly.
Turns out you can't just dd a windows iso onto a usb drive.
You have to format it to fat32, then manually copy all the files. However there is one big installer file which is above 4gb, so you have to get some tool (also provided by Microsoft) to split the file into multiple files less than 4gb. The windows installer will recognize the split files and use those instead.
It's beyond me why the official windows iso just doesn't have this by default...
Am I doing something wrong?
Linux images have to be processed to pull the kernel and initramfs images out, rather than booting an image, and then if the image used a filesystem after boot, hope it finds it. (This is even messier for PXE, at least with USB, you have a fighting chance)
Perhaps this is obvious to many in this context, but this refers to the partitioning scheme for the disk—not the LLM service.
That said, I'm not very sure what you could be doing wrong. Make sure the drive is GPT (not MBR) and isn't starting to fail perhaps. If you've been running into this on a specific machine only it could just be that machine's UEFI is buggy.
One other small advantage is with secure boot you only need to register Ventoy once with a machine and then all the ISOs will boot, whereas with different USB sticks and images each has to be registered individually and some of them don't work with secure boot so you have to turn it off. Just another convenience.
UEFI still boots. Spec said it can boot from fat in an eltorito floppy image and sun disklabels sit in the second or so sector. Spec also said it abstracts the type of volume so all boot methods always work for all drives. ISO images don't use the first 4kB so it doesn't see there's disklabel at all
So now I can mount the ssd as iso9660 but there's also partitions on it of which the third spans the entire drive (of course, because that's the c partition)
It manifests itself as the dreaded "a media driver your computer needs is missing" error message when trying to start the install.
But instead of the process you describe (which some tools will do for you) I used Rufus to copy the install files onto a USB formatted as a NTFS partition, working around the 4GB limitation.
The progress bar that your file manager gives you is an absolute fiction. You must eject the drive through your file manager or run 'sync' in a terminal.
The other 10% is because UEFI decided it hates me today
Rufus puts such a driver in its FAT32 boot partition and loads it before starting the winpe.
It drives me nuts that the UEFI sites never included ExFAT.
What you sometimes need is a USB stick having a native "geometry" in terms of HDD emulation ability, that will be recognized properly by the particular series of chipset on the target mainboard.
Then the data bits written to a fully-zeroed drive must conform to what is expected of a bootable device on the target mainboard, for one thing the partition(s) often needs to be well-aligned with the underlying storage hardware to a more particular degree than merely when it is a "perfectly" readable & writeable drive.
Many new USB sticks fail at this fundamental point because the factory partitioning & formatting was accomplished using an image not exactly appropriate after the vendors of the silicon storage or controller chips make hardware revisions.
Analogously, also why writing an IMG or dd from a not-very-identical stick, or with dissimilar partitioning and/or formatting is quite hit or miss.
Sometimes freshly reformatting is enough for problem sticks, other times they can not be made to boot without repartitioning. Either way a fresh reformat or repartition may simply overwrite using (proven nonoptimal) disk structures still remaining in place unless the device is zeroed beforehand. Sometimes a reboot is needed for an OS to forget the structure that was recognized during most recent insertion.
I like Ventoy (and Rufus) but for best results I start with a proven bootable stick which I prepare manually from a zeroed stick and verify bootability beforehand. Similar preparation when getting ready to manually write reliable plain Windows Setup USBs from the mounted ISO.
A bit expensive, but when you rely on it for work it's worth investing a bit of money.
This is pretty advanced, and who knows if anybody else is doing it exactly like this or not, but it is exactly what the hardware is supposed to be easily capable of, just as easily as what the vast mainstream users are getting out of the hardware by "default".
This type versatile performance is built-in just like the mainstream arrangement is built-in, the thing is you have to figure it out for yourself through the complex web of capabilities that have been long bypassed in order to make the default experience seem like it is actually simpler or more reliable, when it is not.