This topic covers how to manually create a Windows installation flash drive from Windows installation ISO disc image file or DVD, and is intended for manufacturers looking into creating media that they can use to manufacture Windows devices.
The steps described on this page assume you have Windows installation media and access to a Windows technician PC. If you're looking for an easy, automated way to create a bootable Windows installation flash drive, see:
You can create a bootable USB flash drive to use to deploy Windows Server Essentials. The first step is to prepare the USB flash drive by using DiskPart, which is a command-line utility. For information about DiskPart, see DiskPart Command-Line Options.
In the new command line window that opens, to determine the USB flash drive number or drive letter, at the command prompt, type list disk, and then click ENTER. The list disk command displays all the disks on the computer. Note the drive number or drive letter of the USB flash drive.
If your server platform supports Unified Extensible Firmware Interface (UEFI), you should format the USB flash drive as FAT32 rather than as NTFS. To format the partition as FAT32, type format fs=fat32 quick, and then click ENTER.
My goal is so simple, the title says it all, but every way I've tried, I've failed. I've read instructions on various sites (besides here) and they all seem to be missing something... this is what I have:
Though I can easily create a bootable Windows 10 USB with Rufus, my goal is more educational: I want to understand what is going on, and what is the source of my failure, and if possible, to make it work.
This is confusing the heck out of me. I know that I'd save myself the trouble if I just stayed with Rufus, but this is not about going simple, but about understanding what is going on. I know a few GUI tools on Linux might solve the problem, but, again, my hope is to do it using the old Unix terminal if possible. if it's not possible, then I'd like to know why.
What way too many people fail to understand, because Linux ISOs are applying this method, but this is essentially a MAJOR HACK CALLED 'ISOHYBRID', is that, in most cases, you cannot simply take an ISO image and copy it byte for byte to a USB drive, and expect that to boot.
That is because the ISO format and the underlying file systems it uses (ISO9660 or UDF) are designed for optical boot, which is a completely different beast from regular HDD or USB boot. For one thing optical media, and therefore (regular) ISO images, don't have a partition table, which is (usually) essential for HDD or USB boot, and they also (usually) don't have a Master Boot record, a.k.a. MBR, which is essential for BIOS boot.
Now, the above only works when the secondary bootloaders (i.e. the ones that comes from Windows and which Rufus doesn't modify) are designed to support both optical and regular boot, which typically mean they need to handle both UDF or ISO9660 and FAT32 or NTFS file systems, as well as the other differences that present themselves when booting from disk vs from optical. But Microsoft did design its bootloader precisely for that, which is the smart thing to do, because, if your target system is UEFI, it means you (usually, as long as the 4 GB max filesize issue of FAT32 doesn't rear its ugly head) don't need a utility to convert an ISO to a bootable USB, but you can just format that USB to FAT32 and copy the ISO files onto it (file copy, not byte copy), and you have a bootable media.
And now that we have gone through all of the above, I can get into a rant and explain why I believe that the Linux distro maintainers, who usually are smarter than that, are actually doing some disservice to their users, even as they are trying to help them:
Almost all recent Linux distros use a MAJOR HACK called "IsoHybrid", where someone managed to figure out a way to make an ISO9660 optical image masquerade as a regular disk image, with a partition table, an MBR and everything... In other words, most Linux ISOs you find these days are abusing the ISO9660 file system to make it look like something it was never designed to look like: a dual disk and optical image.
Obviously, the goal is to create an ISO that can also be used with the dd command, even as an ISO should never be able to work that way. And I agree that, in theory, this sounds awesome, because being able to use a single image for completely different uses should be great for users, but in practice, this leads to issues that are often overlooked:
As far as I know, Microsoft have no plans to switch to the "hack" that is ISOHybrid for their Windows ISOs, which means that you're unlikely to ever be able to use dd to create a bootable USB media from it, and therefore, if you want to create Windows bootable media from an ISO you either:
Used the insights here as motivation to find a way to build a Windows Server 2019 bootable USB drive from Mac OS. The catch is that you need a GPT formatted disk as FAT32 and there are limitations around 4GB max filesize that you need to work around using wimlib-imagex extension. I originally tried using dd utility - but quickly realized that the disk format could not be used for WinOS boot.
I'm running into a frustrating issue where I need to create a Windows 10 bootable USB for my Macbook Pro 2023, but every attempt to use Boot Camp Assistant has ended in errors. This has left me in a bit of a bind, as I'm keen to find an alternative method that bypasses Boot Camp altogether. The goal is to successfully prepare a USB drive with Windows 10 installation files, which I plan to use on a PC. If anyone knows how to do this directly on macOS, avoiding Boot Camp issues, I'd really appreciate a simplified guide or tool suggestions to get this done.
There are many ways and tools can be used to make Windows 10 bootable USB installer on Mac, like rufus, WonderISO or Unetbootin. But for me, I used to installed windows 10 in a VM (vmware i think is what I used) on Mac and then created the USB drive from there. I wish that you had known about this method.
Bootcamp assistant app is removed from Apple Silicon on Mac so you can't create Windows 10 bootable USB on Mac with Bootcamp app. I am using WonderISO on my Apple Silicon Mac running the latest macOS Sonoma and it only takes 3 clicks to create a Windows 10 bootable USB on my Mac.
Parallels Desktop, a popular virtualization software for Mac, allows you to run Windows and other operating systems within macOS without needing to reboot. So you can create Windows 10 bootable USB on Mac in a Windows virtual machine.
Firstly, you need to have a copy of the Windows 10 ISO file. Microsoft provides this file for free on their website, intended for users who need to install or reinstall Windows. Download this file to your Mac before proceeding to the next steps.
With the Windows 10 ISO file downloaded, the next crucial step is to obtain a USB drive with sufficient storage space. Typically, a drive with at least 8GB of space is recommended. This ensures that there is enough room for the Windows installation files and any additional updates or drivers you might need to include in the bootable media.
Once Parallels Desktop is installed, you can use it to create a new virtual machine using the Windows 10 ISO file. During the setup process, Parallels will ask where you want to install Windows. At this stage, instead of installing it on a virtual disk, you'll choose your USB drive as the installation destination. This process effectively turns your USB drive into bootable Windows 10 installation media.
However, it's important to note that directly creating Windows 10 bootable USB on Mac through Parallels Desktop might not be as straightforward as using dedicated software for making bootable drives. It takes more time and storage space on your Mac.
If you want to create windows 10 bootable USB on Mac without bootcamp, you can try using a different tool called Etcher. Etcher is a free and open-source tool that allows you to create bootable USB drives from ISO files. Here are the steps to create a Windows 10 bootable USB on Mac using Etcher:
It becomes much challenging to create Windows 10 bootable USB on Mac as Bootcamp is not available on Apple Silicon Mac. Instead, you can borrow another Intel Mac and use Bootcamp to make a bootable Windows 10 USB on Mac.
Step 1: Open the Boot Camp Assistant in the Utilities folder within your Applications folder. Alternatively, use Spotlight search (Cmd + Space) and type "Boot Camp Assistant" to find and open it.
I found a way to install Windows on system without Mac OS system. You will need a USB with a Mac OS system on it. Reason why you will need to format the HD of the mac. With the system off. Turn on the mac. Access the boot up Options menu. Select the USB with the mac os. You will not be loading the Mac Os system. Don't worry. It will load to install the Mac OS system. You click the desktop and select Disk Utility. Choose the hard drive. Select Partition. Select one Partition. Under the Partition window Select Master Boot Record. This will allow you to format the hard drive that is not GUID partition that is for Mac. Once that is done. You are golden. Make sure you have a bootable USB with Windows on it. I used a bootable CD with Windows 7. When selecting the bootable media, it will load windows. You may receive error that unable to use the hard drive. No worries. Select the hard drive, delete and format. and Try again. This should allow you use the hard drive and install windows. No boot camp and no Mac OS on the system. If you need to get drivers. Try using IOBIT Driver Booster. It is free. Or you can view the devices in Device manager to locate the kind of devices that maybe needed to be updated.
@Delaney_Justin Tried this today. My commands seemed to have worked. Files were created on my USB Flash Drive, but still doesn't seem to be recognized by my new PC. Do you have ideas on how to verify that the correct files were created? Maybe I messed up the path part?
d3342ee215