As Boot Camp Dies, Here’s How to Create a Windows 11 USB Installer on macOS (Intel and Apple Silicon)

Microsoft has officially authorized Parallels Desktop as the way to run Windows 11 on M1 and M2 Macs, hammering the final nail into Boot Camp’s coffin. But that move hasn’t erased the need to create Windows 11 installation media on a Mac. Whether you’re provisioning a PC, resurrecting an Intel Mac’s secondary OS, or just keeping a repair tool handy, building a bootable Windows 11 USB from macOS remains a practical necessity—and it works across both Intel and Apple Silicon machines.

Apple’s transition to its own Arm-based silicon excised Boot Camp from all M-series Macs. The feature still exists on Intel Macs, but Apple hasn’t shown any interest in reviving it for newer hardware. Microsoft’s endorsement of Parallels Desktop 18 as the authorized way to run Arm versions of Windows 11 Pro and Enterprise effectively closes the door on native Boot Camp support forever. Yet the installation media problem is separate from the “running Windows on a Mac” problem. For system builders, IT admins, and tinkerers, the question is “How do I make a USB stick that can install Windows 11 on any PC?” It turns out macOS handles that job quite well once you understand the filesystem nuances, the split-WIM trick, and the right tool for the target machine.

The Boot Camp Era Ends, but USB Creation Lives On

Apple introduced Boot Camp in 2006 alongside the Intel transition, giving Mac users a dual-boot pathway into Windows. With Apple Silicon, the architecture changed—Windows on Arm exists, but Microsoft’s licensing never officially sanctioned running it natively on Mac hardware. The August 2023 update to the Precision Touchpad driver was likely one of the last breaths of Boot Camp on Intel. Microsoft’s support document that names Parallels as the authorized solution now gives Apple a ready-made answer to any Boot Camp revival requests: “Just use Parallels.”

That’s fine for most people who need Windows apps alongside macOS, but what if you’re not trying to dual-boot? What if you need a USB installer for a separate machine? The official Windows 11 download page still serves up ISOs to anyone—Mac users included—and those ISOs can be turned into bootable media using tools already present on macOS or easily installed via Homebrew. The community-tested methods below have been refined across thousands of forum posts and do-it-yourself guides, and they cover both Intel and Apple Silicon Macs because the underlying macOS tooling (Terminal, diskutil, hdiutil) is architecture-agnostic.

Before You Start: What You Need and What You’ll Face

Every method requires the same two ingredients: a genuine Windows 11 ISO downloaded from Microsoft’s official site, and a USB flash drive of at least 16 GB (8 GB can work but leaves little breathing room). USB 3.0 or USB-C drives shorten the wait considerably.

The biggest technical hurdle is FAT32’s 4 GB file-size limit. Windows 11 ISOs contain a file called install.wim (or install.esd) in the sources folder that frequently exceeds 4 GB. If you format the USB as FAT32—a requirement for many UEFI firmware implementations—you cannot have any file larger than 4 GB on the drive. The workaround is to split install.wim into smaller .swm segments that Windows Setup knows how to reassemble. This is the core insight behind the wimlib method.

Other key constraints: modern Windows 11 installations prefer UEFI and GPT partitioning; legacy BIOS compatibility demands MBR formatting and possibly an active partition flag. Apple Silicon Macs cannot use Boot Camp Assistant for anything—no USB creation at all. Intel Macs can still use Boot Camp Assistant, which handles the splitting for you in many cases. With those rules set, let’s walk through the proven approaches.

Method 1: Terminal + dd (Universal, Fast, Scary)

The dd command is available on every Mac and writes the ISO to the USB block-for-block. It’s the simplest conceptually: you point the tool at the ISO and the USB and wait. It works on Intel and Apple Silicon Macs identically because it’s purely a macOS-level operation.

Why use it: No extra software, minimal steps, exact replica of the ISO’s partitioning.

Verified workflow:

1. Insert the USB drive.
2. Open Terminal and run diskutil list. Note the whole-disk identifier (e.g., /dev/disk4). Triple-check this—the next steps will erase it.
3. Unmount the disk: diskutil unmountDisk /dev/diskN
4. Optionally, format the disk to MS-DOS (FAT32) with a GPT or MBR scheme:
   - GPT (UEFI): diskutil eraseDisk MS-DOS WIN11 GPT /dev/diskN
   - MBR (legacy): diskutil eraseDisk MS-DOS WIN11 MBR /dev/diskN
5. Write the ISO using the raw device for speed:
   sudo dd if=$HOME/Downloads/Win11_*.iso of=/dev/rdiskN bs=4m
6. For progress, press Control+T during the write to see a status snapshot. macOS’s built-in dd does not support status=progress. Alternatively, install GNU coreutils (brew install coreutils) and use gdd with status=progress, or pipe through pv.
7. If legacy BIOS is needed, mark the partition active with fdisk:
   - sudo fdisk -e /dev/diskN
   - fdisk prompt: flag 1, write, exit
8. Eject: diskutil eject /dev/diskN

Caveats: This raw write often works, but if the target PC’s UEFI insists on FAT32 and the ISO’s install.wim exceeds 4 GB, the installer might still fail. That’s where the next method takes over.

Method 2: wimlib + FAT32 Split (The UEFI Gold Standard)

When dd-produced media fails or you anticipate a FAT32-only UEFI system, the solution is to split the oversized WIM file into segments under 4 GB and manually copy the ISO contents onto a FAT32 USB. This is the most broadly compatible approach for modern PCs.

Why use it: Guarantees compatibility with UEFI firmware that won’t read NTFS; eliminates 4 GB limit entirely.

Step-by-step:

1. Install Homebrew if you don’t have it:
   /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
   (Follow the on-screen prompts to add brew to your PATH.)
2. Install wimlib: brew install wimlib
3. Format the USB as MS-DOS (FAT32) with MBR:
   diskutil eraseDisk MS-DOS WIN11 MBR /dev/diskN
4. Mount the Windows 11 ISO:
   hdiutil mount ~/Downloads/Win11_*.iso
5. Copy all contents from the mounted ISO to the USB, except sources/install.wim. For example:
   cp -rp /Volumes/CCCOMA_*/ /Volumes/WIN11/
6. Manually split install.wim:
   - Create a temp folder: mkdir ~/Desktop/wimtemp
   - Copy the WIM: cp /Volumes/CCCOMA_*/sources/install.wim ~/Desktop/wimtemp/
   - Run the split: wimlib-imagex split ~/Desktop/wimtemp/install.wim /Volumes/WIN11/sources/install.swm 3800
   The 3800 value (in MB) keeps each segment comfortably under 4 GB. Many practitioners use 3000–3800 to avoid boundary issues.
7. Eject the ISO and USB:
   hdiutil unmount /Volumes/CCCOMA_*
diskutil eject /dev/diskN

The result is a FAT32 USB that passes Windows Setup’s own integrity checks. This method is the go-to when Boot Camp Assistant isn’t available or when you need absolute certainty.

Method 3: Boot Camp Assistant (Intel Macs Only)

On Intel Macs, Boot Camp Assistant remains the easiest graphical route. It can automatically format the USB, copy files, and even download Windows support software. Simply launch Boot Camp Assistant from Applications > Utilities, check the box to create a Windows install disk, point it at your ISO and USB, and follow the prompts. The assistant handles the FAT32 split if needed.

But this option is vanishing quickly. Apple no longer ships Boot Camp on M-series Macs, and the Intel Mac installed base is aging. If you still own an Intel machine and Boot Camp works, it’s the path of least resistance. For everyone else, the command-line methods are the only game in town.

GUI and Virtual-Machine Alternatives

Not everyone is comfortable with Terminal. Two additional routes lower the barrier:

• balenaEtcher: A cross-platform flashing tool that writes ISOs with a simple GUI. It verifies the write, reducing corruption risk. However, it does a raw write just like dd, so if the target needs FAT32 and the WIM is oversized, the resulting USB may not boot. Use Etcher as a first attempt; if boot fails, fall back to wimlib.
• Virtual Machine method: Install a Windows 11 VM via Parallels, VMware Fusion, or UTM. Inside the VM, attach both the ISO and the physical USB, then use Windows-native tools like Rufus or the Media Creation Tool. Rufus can format the USB as NTFS or FAT32 and split WIMs automatically. This approach gives you the full Windows toolset from the comfort of macOS—no command-line wrestling required.

Quick Comparison: Which Method Should You Choose?

Troubleshooting the Most Common Pitfalls

Even with careful preparation, a few errors surface repeatedly.

• “Resource busy” during dd: The disk wasn’t unmounted. Run diskutil unmountDisk /dev/diskN and try again.
• No progress from dd: Press Control+T for a one-time status update, or install GNU coreutils (brew install coreutils) and use gdd status=progress, or pipe through pv.
• “Boot Camp Assistant cannot be used on this Mac”: You’re on Apple Silicon. Skip directly to command-line or VM methods.
• Windows Setup stalls at ~77% with missing file errors: Classic symptom of an oversized install.wim on a FAT32 drive. Redo the USB with wimlib splitting and a split size of 3000–3800 MB.
• USB not recognized by target PC: Try a different USB port (preferably USB 2.0 on older machines), ensure Secure Boot is either turned off or the USB is prepped for it, and confirm the partition scheme matches the boot mode (GPT for UEFI, MBR for legacy).

Security and Data Safety

A moment of distraction can destroy data. Always back up any USB drive before running diskutil eraseDisk or dd. Double-check the disk identifier with diskutil list—the output shows brand and size to help confirm. Prefer ISOs downloaded directly from Microsoft; avoid third-party sources that might have been tampered with. The Homebrew install command (curl \| bash) is widely trusted, but security-conscious users should review the script content before executing it.

Windows 11’s TPM and Secure Boot requirements are beyond the scope of USB creation. This guide builds standard installation media; bypassing hardware checks is a separate endeavor with its own support risks.

Boot Camp’s Absence Changes the macOS-to-Windows Dynamic

The death of Boot Camp doesn’t affect USB creation for external PCs, but it reshapes how Mac users interact with Windows. Virtualization (Parallels, VMware, UTM) is now the official path on Apple Silicon, and Microsoft’s blessing of Parallels as an authorized solution removes any ambiguity for business users. For the dwindling number of Intel Mac owners, Boot Camp remains a convenience that will likely receive no further feature updates.

Yet the ability to build Windows 11 installation media from macOS has never depended on Boot Camp—it depends on understanding the FAT32 limit and having the right tools. The steps outlined above have been battle-tested by Mac users who need to provision Windows machines for family, labs, or their own secondary devices. They work just as well on an M3 MacBook Air as on a 2015 MacBook Pro.

The Bottom Line

Creating a Windows 11 USB installer on macOS is a solved problem. The wimlib + FAT32 split method offers the highest UEFI compatibility, while dd provides a quick universal fallback. Boot Camp Assistant remains the easiest one-click option for those still on Intel hardware. GUI tools and virtual machines give less technical users a comfortable way in. The key is to choose the right method for the target PC and to respect the 4 GB filesystem limit that trips up so many first-timers.

With Boot Camp’s official exit, the focus now shifts to virtualization for Mac-native Windows needs, but the humble USB installer remains an essential tool—and macOS is fully capable of making one that works.