The Real Way to Make a Bootable Windows 10 USB on Mac Without Losing Your Mind

You're probably here because Boot Camp Assistant failed you. It’s the classic Mac experience: you try to do something cross-platform, and Apple’s built-in software gives you a vague error message about "not enough space" or "disk could not be partitioned," even though you have a 2TB SSD. Honestly, making a bootable Windows 10 USB on Mac has become a legitimate nightmare lately. It used to be easy when Windows ISO files were smaller, but now that the install.wim file has ballooned past 4GB, the old FAT32 formatting tricks just don't work anymore.

Windows doesn't naturally want to live on a Mac. Apple doesn't really want it there either.

If you're using an Intel Mac, you have a fighting chance with the old-school methods. If you're on Apple Silicon (M1, M2, or M3 chips), you're likely trying to create this drive for a different PC, because you can't natively boot Windows 10 on an ARM-based Mac anyway. Whatever your reason, the process is finicky. You’ve got to deal with Terminal commands, file splitting, and the occasional prayer to the silicon gods.

Why the Standard Methods Fail Every Single Time

Most people think they can just drag and drop the ISO contents onto a USB drive. That's a mistake. Specifically, it's a file system limitation mistake.

Macs and PCs talk to each other through a translator called FAT32 when it comes to bootable media. The problem? FAT32 cannot handle any single file larger than 4GB. The modern Windows 10 ISO contains a file named install.wim that is almost always 4.5GB to 6GB. When you try to copy it, the process just dies.

Then there's the "Burn to Disk" myth. Nobody has optical drives anymore, and even if you did, the modern Windows 10 image is too large for a standard DVD. You’re stuck with USB. But not all USB drives are created equal. You need at least 16GB, and if you're using a cheap promotional thumb drive you found in a drawer, expect it to fail midway through the write process. Use a USB 3.0 or 3.1 drive. Your sanity is worth the ten dollars.

The Terminal Method: For People Who Aren't Afraid of Code

If you want to make a bootable Windows 10 USB on Mac without downloading sketchy third-party "helpers" that are actually just wrappers for adware, Terminal is your best friend. It’s built-in. It’s powerful. It’s also very good at erasing your entire hard drive if you type the wrong letter.

First, get your ISO. Download it directly from Microsoft. Don't get it from a mirror or a torrent; those are often modified with "optimizations" that include keyloggers. Once you have that Win10_English_x64v1.iso sitting in your Downloads folder, plug in your USB.

Open Terminal. Type diskutil list.

You’ll see a list of drives. Look for your USB stick. It’ll probably be /dev/disk4 or something similar. Double-check the size. If you see a 500GB drive, that’s your internal SSD. Do not touch it. If you see a 16GB or 32GB drive, that’s your target.

Format the drive using this command, replacing diskX with your actual disk number:
diskutil eraseDisk MS-DOS "WINDOWS10" GPT /dev/diskX

This sets the stage. But now we hit the 4GB wall I mentioned earlier. To get around this, we use a tool called Homebrew to install wimlib. If you don't have Homebrew, you should. It’s the package manager for macOS that makes the OS actually useful for power users.

Splitting the Giant File

Once wimlib is installed via brew install wimlib, you can perform the magic trick. You’ll copy everything except the giant file first, then use wimlib to slice the install.wim into two smaller chunks that FAT32 can handle. Windows installer is smart enough to join them back together during the installation process.

The command looks like this:
wimlib-imagex split /Volumes/RESOURCENAME/sources/install.wim /Volumes/WINDOWS10/sources/install.swm 4000

It takes forever. Seriously. It might look like Terminal has frozen. It hasn't. It's just moving gigabytes of data through a narrow pipe. Go get a coffee. Maybe two.

The Third-Party Shortcut: When Terminal Feels Too Risky

I get it. Not everyone wants to play "Hackerman" just to install an OS. If the command line makes you sweat, there are GUI tools, but the landscape is a minefield.

UUByte ISO Editor is a popular choice, and it actually works quite well for this specific task because it handles the WIM splitting automatically. However, it’s not free. You’re paying for the convenience of not having to learn Bash commands.

Then there’s BalenaEtcher. People love Etcher. It’s beautiful. It’s simple. It also frequently fails to make bootable Windows drives on Mac. Etcher is fantastic for Linux distros or Raspberry Pi images, but Windows uses a different boot structure that Etcher doesn't always "map" correctly for a Mac-to-PC transition.

If you're on an older Intel Mac (pre-2015), you might actually be able to use the built-in Boot Camp Assistant. Open it, check the box that says "Create a Windows 10 or later install disk," and follow the prompts. But if you're on a 2018 MacBook Pro or anything newer, Apple removed this feature because they expect you to just run Windows in a virtual machine or use their specific "Install Windows" partition logic.

Common Roadblocks You'll Definitely Encounter

Errors are part of the process. One of the most annoying is the "No bootable device found" error when you finally plug the USB into your PC. This usually happens because the Mac formatted the USB with a MBR (Master Boot Record) partition scheme instead of GPT (GUID Partition Table). Modern PCs using UEFI—which is basically every computer made in the last decade—require GPT.

Another snag: the ISO version. Microsoft occasionally releases "multi-edition" ISOs that are even larger than the standard ones. If your ISO is over 7GB, even some splitting tools might struggle. Try to find the "Media Creation Tool" ISO if possible, though that's easier to download on a Windows machine.

If you are trying to do this on a Mac to fix that same Mac (installing Windows via Boot Camp), remember that T2 Security Chip Macs (2018-2020 Intel models) have a setting in "Startup Security Utility" that blocks booting from external media. You have to reboot into Recovery Mode (Command + R), go to Utilities, and explicitly allow booting from external drives. If you don't, that USB you spent an hour making will be ignored by the system.

Practical Steps to Success

Success isn't about following a tutorial perfectly; it's about pivoting when the software acts up.

💡 You might also like: Surface to Volume Ratio Calculator: Why Size Actually Matters in Design and Science

1. Verify your ISO hash. Use the shasum -a 256 command in Terminal to make sure your download wasn't corrupted. A single missing bit will cause a blue screen of death during the Windows installation.
2. Use a USB-A drive if possible. If you’re using a MacBook with only USB-C ports, use a high-quality adapter. Cheap hubs often drop the connection during large file transfers, which ruins the boot sector of the USB.
3. The "Manual Copy" method. If you're on an older version of Windows 10, you might still fit the install.wim on a drive formatted as ExFAT. While some modern UEFI BIOS can boot from ExFAT, many cannot. Stick to the FAT32 + wimlib splitting method for the highest compatibility.
4. Check the "Sources" folder. After you've made the drive, open it in Finder. Look in the sources folder. If you see install.swm and install2.swm instead of install.wim, you did it right.

The reality is that Apple and Microsoft are like two neighbors who haven't spoken in twenty years. They share a fence, but they won't help each other fix it. Making a bootable Windows 10 USB on Mac requires you to be the middleman who knows how to navigate both worlds. It's tedious, but once that Windows logo pops up on the screen, it feels like a genuine victory over the machines.

Final Checklist Before You Start

• Download the official ISO from Microsoft's website.
• Ensure your USB drive is at least 16GB and formatted to GPT.
• Install wimlib if you're using the Terminal method to avoid the 4GB file limit.
• Disable Secure Boot on the target PC (or the Mac itself) if the drive isn't recognized.
• Keep the Mac plugged into power; the file splitting process is CPU-intensive and drains the battery fast.

Once the process finishes, always "Eject" the drive properly in macOS. Pulling it out early is the fastest way to corrupt the partition table you just spent twenty minutes building.