- Make usb a windows 10 loader how to#
- Make usb a windows 10 loader install#
- Make usb a windows 10 loader full#
- Make usb a windows 10 loader iso#
Some EFI firmware does support NTFS, as I read. Given EFI spec doesn’t say that EFI partition must be FAT32, but that it’s the least that needs to be supported, I tried exFAT and NTFS partition, but the ProBook wouldn’t take them. I presume it didn’t find install.wim, even though it was available on the NTFS partition. After that, it failed with an error message. On the machine I was installing HP ProBook 4340s, it booted and it allowed me to do the partitioning.
Make usb a windows 10 loader install#
Because Windows Setup is run from NTFS partition, you can use this method for your custom install media with larger than 4 GB install.wim files.Īlas, I was a bit too enthusiast: I was in a hurry, saw it booted, considered it a success, and left this comment. This USB flash drive can be used to boot any BIOS / MBR and UEFI / GPT computer.
The difference between these two partitions is that on FAT32 partition, the Sources folder only contains one single file, the boot.wim file that’s required for the USB to be bootable. Now I had a USB flash drive to install Windows 10 which boots from a small FAT32 partition, then runs Windows Setup from the bigger NTFS partition: Then I simply copied all of the ISO’s content, including the complete Sources folder to the bigger NTFS partition on the USB drive.
Make usb a windows 10 loader iso#
Now I created an empty folder on this FAT32 partition, labelling it Sources, and copied Sources\boot.wim file from mounted ISO to this folder: I mounted the ISO, selected everything except the Sources folder, and copied these files and folders to the small FAT32 partition: Next, I created a 1 GB FAT32 partition and used the rest of USB’s capacity for an NTFS partition.
Make usb a windows 10 loader full#
The first step was to remove the existing single FAT32 partition that used the full 8 GB capacity of the USB. Here is how I created Windows 10 USB install media which boots from a small FAT32 partition, then gives control to a larger NTFS partition which contains the 4GB+ install.wim file. So, I had to create FAT32 media to do the job instead. Knowing his hardware, I suspected that at least on two computers he wants to reinstall he would not be able to boot from NTFS. Then, he could run Windows Setup from an NTFS partition. However, knowing my friend for whom I was making this installer USB is not familiar with manually deploying from a split WIM, it would be easier for me to make the ISO bootable from a FAT32 partition. OK, no problems, I thought, thinking that I would just split the WIM using DISM. For this multi edition ISO, the install.wim file is annoyingly 0.03 GB too big to fit in FAT32 formatted USB flash drive: I had the Consumer Editions ISO, downloaded from my Visual Studio subscription, and I wanted to use this specific ISO.
Make usb a windows 10 loader how to#
For those interested in how to do this very thing, I’ve written a tutorial on .Įarly this morning I had to make Windows 10 version 1803 multi edition USB install media. Deploying my custom Windows image on that laptop from USB, I have been forced to split the 12 to 20 GB custom install.wim files that I create, so I can deploy them using DISM instead of running Windows Setup. I have an Asus laptop: it’s only a few years old, and it simply refuses to boot from NTFS. That’s the real reason why they can only boot from FAT32. But, unfortunately, there are still a number of computers where BIOS / UEFI lacks proper drivers.
0 kommentar(er)
