Apple's move to its own silicon changed everything about running Windows on a Mac. For years the answer was simple: install Boot Camp, dual-boot into an x86 copy of Windows, and forget about it. That door closed the moment the M1 shipped. Boot Camp is gone on Apple Silicon, and the only Windows that runs at native speed is the ARM build. If you bought a Mac in the last four years and still expect the old workflow, you are in for a surprise.
Here is the fact that trips people up: Windows 11 on ARM can now run most 64-bit x86 applications through a built-in translation layer called Prism, and Microsoft finally sells ARM licenses to individuals. That means a MacBook Air with an M-series chip can run Photoshop, older accounting software, and even a surprising number of games. The catch is that how you get Windows onto the machine matters more than ever, because the virtualization software you pick determines your performance, your GPU access, and whether Windows Update keeps working next year.
This guide compares the real options to run Windows on a Mac virtual machine in 2026, with concrete pricing, a hands-on install walkthrough, and honest tradeoffs from someone who has broken every one of these setups at least once. If you are on an older Intel Mac, I will cover that path too, because the rules are completely different.
Key Takeaways
- On Apple Silicon (M1 through M4), you run Windows 11 ARM inside a VM. Native x86 Windows and Boot Camp no longer exist on these machines.
- Parallels Desktop is the smoothest experience and the only officially Microsoft-authorized option, but it is subscription-priced.
- VMware Fusion is now free for personal use and a strong pick if you tolerate more manual setup.
- UTM is free, open-source, and flexible, but expect to spend real time configuring it.
- Budget 60GB minimum of disk and ideally 16GB of RAM before you start; 8GB Macs will struggle.
- x86 Windows apps run through Microsoft's Prism translation layer, so expect a performance hit on heavy legacy software.
Why Boot Camp Died and What Replaced It
Boot Camp let Intel Macs boot directly into a full x86 copy of Windows. It worked because Intel Macs and Windows PCs shared the same processor architecture. When Apple switched to ARM-based silicon, that shared foundation disappeared.
Apple Silicon Macs can only boot ARM operating systems natively. Microsoft, for its part, sells Windows 11 for ARM. So the modern approach is a virtual machine: a self-contained Windows environment that runs as a program inside macOS, using a hypervisor to talk to the Mac's hardware.
The practical upshot:
- Apple Silicon Macs (M1–M4): VM running Windows 11 ARM. No dual boot.
- Intel Macs: You can still use Boot Camp for dual boot, or run an x86 VM. Both work, but Apple has stopped selling Intel Macs, so this path is fading.
If you are the sort of person who likes low-level control over how the OS talks to hardware, you might also enjoy tools like Windows Symlink Creator Pro once Windows is up and running, for managing file links across shared folders between macOS and the guest.
The Three Real Options to Run Windows on a Mac Virtual Machine
In 2026 there are three serious contenders. Everything else is either abandoned or a niche experiment.
1. Parallels Desktop
Parallels is the polished, hand-holding option. It downloads and installs Windows 11 ARM for you in a couple of clicks, sets up shared folders automatically, and integrates Windows apps into the macOS Dock. It is also the only virtualization product Microsoft has explicitly authorized for running Windows 11 on Apple Silicon.
The downside is money. Parallels moved to a subscription model, and the Standard edition runs around $100 to $130 per year depending on promotions. There is a one-time-purchase option in some regions, but it does not get feature updates.
2. VMware Fusion
Broadcom made VMware Fusion free for personal use, which is a genuine gift. It runs Windows 11 ARM well, supports 3D acceleration, and does not nag you. The setup is more manual than Parallels: you download the Windows ARM image yourself and configure a few settings.
For a lot of technically comfortable users, Fusion is now the value winner. Free, capable, and backed by an enterprise-grade hypervisor.
3. UTM
UTM is the open-source darling. It is built on QEMU, costs nothing (a paid App Store version funds development but the binary is free from their site), and can virtualize or emulate. That emulation mode is the party trick: UTM can run x86 Windows on Apple Silicon by emulating the whole processor. It is slow, but it works when nothing else will.
The tradeoff is effort. UTM expects you to understand what you are configuring. If you like tinkering, it is fantastic. If you want Windows working in ten minutes, look elsewhere.
Parallels vs VMware Fusion vs UTM: Side by Side
Here is how the three stack up on the criteria that actually matter day to day.
| Criteria | Parallels Desktop | VMware Fusion | UTM |
|---|---|---|---|
| Price (personal) | ~$100–130/year | Free | Free |
| Setup difficulty | Very easy | Moderate | Advanced |
| Windows 11 ARM auto-install | Yes, one click | Manual image | Manual image |
| x86 emulation option | No | No | Yes (slow) |
| 3D / GPU acceleration | Excellent | Good | Limited |
| macOS integration | Best in class | Good | Basic |
My honest recommendation: if your time is worth anything and Windows is part of your job, pay for Parallels. If you are budget-conscious and comfortable in a settings panel, VMware Fusion is the smart pick. UTM is for hobbyists, x86-only legacy apps, and people who genuinely enjoy the process.
A Worked Example: Setting Up Windows 11 ARM in VMware Fusion
Let me walk through a real setup on an M2 MacBook Pro with 16GB of RAM and 512GB of storage. I will use the free VMware Fusion because it hits the sweet spot of cost and capability, and because the manual steps teach you what the automated tools hide.
Before you start: Fusion's Windows VM will consume roughly 25GB after install and grow toward 60GB or more with apps and updates. I had 180GB free, so no problem. On a 256GB Mac, you would want to be careful.
- Download VMware Fusion. Register for a free Broadcom account and grab the latest Fusion release for Apple Silicon. Install it like any Mac app.
- Get the Windows 11 ARM image. Fusion can pull an ARM insider image directly through its wizard, or you can build an official ISO using Microsoft's tools. In the app, choose Get Windows from Microsoft if the option appears; otherwise select Install from disc or image.
- Create the VM. Fusion suggests defaults. I bumped memory to 8GB (half my Mac's RAM) and set 4 CPU cores. Leave the disk at 64GB unless you know you need more.
- Skip the network prompt during install. Windows 11 wants an internet connection to force a Microsoft account. To create a local account, disconnect the VM's network adapter temporarily in Fusion's settings, then proceed through setup.
- Install VMware Tools. Once Windows boots to the desktop, mount the VMware Tools disc from the Fusion menu and run the installer. This unlocks proper display resolution, shared clipboard, and drag-and-drop. Skipping this step is the number one reason people complain the VM feels "laggy."
- Enable shared folders. Point a shared folder at your Mac's Documents or a project directory so files move freely between the two systems.
- Activate Windows. Enter a valid Windows 11 ARM license key. You can run unactivated for testing, but you lose personalization options and get a watermark.
Total time on my machine: about 35 minutes, most of it waiting on downloads and Windows Update. When it finished, an x86 app I needed for an old client (a 2019-era invoicing tool) installed and ran through Prism translation without a single error, though it launched about two seconds slower than on a native PC.
Performance Expectations and the Prism Reality Check
Here is where people set themselves up for disappointment. Windows 11 ARM runs ARM-native apps beautifully. Microsoft Edge, the Office suite, and modern Visual Studio builds all fly. The problem is legacy x86 software.
Prism, Microsoft's translation layer, converts x86 instructions to ARM on the fly. It is genuinely good, far better than the older WOW64 emulation. But translation costs cycles. Expect:
- ARM-native apps: 90–100% of what you would get on a comparable PC.
- x86 64-bit apps via Prism: roughly 60–80% performance, higher power draw, occasional compatibility gaps.
- x86 32-bit apps: supported but slower, and some drivers or kernel-level tools simply will not run.
- Anti-cheat games: frequently blocked. Kernel-level anti-cheat and virtualization do not mix.
If your entire reason for wanting Windows is one heavy x86 application, benchmark it before you commit. And if that app touches sensitive data, treat the VM like any other endpoint. Our writeup on vetting open-source software supply chains before you install is worth reading before you throw random tools into a fresh Windows image.
Keeping Your Windows VM Secure and Backed Up
Cover image: My updated workspace, aka I Finally Got a Third 22' LCD by creecher94, licensed under BY 2.0 via Openverse.
