You know what's funny? The M1 chip is genuinely one of the best processors Apple has ever shipped, and yet the number of people running into grief with Windows on M1 Mac setups is enormous. Half the advice floating around online is either years out of date or written by someone who's never actually sat in front of a Parallels VM on Apple silicon. So let's cut through it properly.
TL;DR
Windows on M1 Mac only works via a Windows 11 ARM virtual machine (Parallels Desktop is the main option). Most problems, including boot failures, slow performance, and display issues, come down to using the wrong Windows image, outdated Parallels or guest tools, or a misconfigured Secure Boot setup. Work through the solutions below in order and you'll be sorted.
Key Takeaways
- Windows on M1 Mac requires a Windows 11 ARM image, not the standard x64 download
- Outdated Parallels Desktop or stale guest tools cause the majority of performance and boot issues
- Secure Boot certificate problems in Parallels are a known Apple silicon-specific issue with a documented fix
- VM resource over-allocation hurts both the VM and the Mac host simultaneously
- Recreating the VM from scratch beats incremental repair for stubborn failures
At a Glance
- Difficulty: Intermediate
- Time Required: 15 to 30 mins
- Success Rate: 85% of users
What Actually Causes Windows on M1 Mac Problems?
Here's the thing: the M1 chip itself is almost never the problem. In fifteen years of fixing Macs, I've seen maybe a handful of cases where the chip was genuinely at fault. What I see constantly, especially with Windows on M1 Mac setups, is a stack of software configuration mistakes that compound each other until the whole thing feels broken.
The biggest one, by a distance, is people downloading the wrong Windows image. Microsoft's main Windows 11 download page defaults to an x64 ISO. That image will not run properly on Apple silicon. The M1 uses an ARM architecture, so you need a Windows 11 ARM build specifically. Run the wrong one and you'll either get a boot error immediately or crawl along at a fraction of the expected speed because Parallels is having to translate x64 instructions on the fly.
The second most common cause is running an outdated version of Parallels Desktop. Apple pushes macOS updates fairly aggressively, and each one can break compatibility with an older Parallels build. Parallels releases patches quickly but you have to actually install them. If you dismissed that update notification three months ago, that's almost certainly where your trouble started.
Beyond those two, the other root causes I see regularly are:
- Stale Parallels Tools inside the Windows guest (these are the drivers that handle display, USB, and input between macOS and Windows)
- Secure Boot certificate mismatches, which is a specific Apple silicon quirk that Parallels documents in their knowledge base
- VM resource over-allocation, where someone gives the VM 12 GB of RAM on a 16 GB Mac and then wonders why everything grinds
- Host memory pressure from background apps competing with the VM for the same physical memory
One thing worth saying clearly: Microsoft does not officially support Windows on M1 Mac hardware. There's no Boot Camp for Apple silicon, and Microsoft's Windows on ARM certification is aimed at ARM-native Windows PCs, not Mac virtual machines. So you're working in a supported-but-unofficial space, which means keeping everything updated is more important here than on a standard Windows PC. Apple's own support page on Apple silicon compatibility is worth bookmarking if you're running a mixed environment.
If you're also seeing general Mac slowness outside of the VM, that's a different problem. Check our guide on fixing a slow Mac first, because host performance directly affects how well the VM runs.
Windows on M1 Mac Quick Fix
Start here. These steps take five to ten minutes and fix the majority of cases I see. Don't skip straight to the advanced stuff until you've done these.
Restart, Verify Your Image, and Update Parallels Easy
- Shut down the VM cleanly
Don't just close the Parallels window. Go to Actions in the menu bar and choose Shut Down. Wait for Windows to power off fully, then quit Parallels Desktop. - Restart the Mac
Apple menu, Restart. Let it come back up fully before reopening Parallels. You'd be surprised how many transient issues this clears on its own. - Check your Windows image type
If you're setting up a new VM or your current one won't boot, confirm the ISO you used was a Windows 11 ARM build. The filename typically contains "arm64" somewhere. An x64 ISO will either fail at the boot screen or show a "This PC can't run Windows 11" style error. - Update Parallels Desktop
Open Parallels Desktop, click the Parallels Desktop menu at the top left, and select Check for Updates. Install whatever's available. This one often needs a second reboot before it sticks, so restart the Mac again after updating. - Relaunch the VM and check behaviour
Boot Windows 11 ARM and see if the original problem is gone. If yes, sorted. If not, move to the intermediate fixes below.
More Windows on M1 Mac Solutions
Still having grief? These intermediate steps cover the driver and resource issues that a simple restart won't touch. Budget about fifteen to thirty minutes for this section.
Update Guest Tools and Windows Inside the VM Intermediate
- Boot into Windows 11 ARM
Let it reach the desktop fully. Don't rush this, especially after a Parallels update, as the guest sometimes needs a minute to settle. - Run Windows Update
Open Settings (Win + I), go to Windows Update, and click Check for Updates. Install everything, including optional driver updates. Restart when prompted. Do this twice if the first pass finds updates, because Windows often stages them in rounds. - Install or update Parallels Tools
Back on the Mac menu bar with the VM running, click Actions, then Install Parallels Tools. A setup wizard will appear inside Windows. Follow it through and restart the VM when it finishes. These tools handle the display driver, shared clipboard, drag-and-drop, and USB passthrough. Stale tools are behind most display blur and input lag complaints. - Verify display settings
After the reboot, right-click the Windows desktop and open Display Settings. Check the resolution and scaling. Parallels usually sets this correctly after a tools update, but if things look blurry, try toggling the scaling option in Parallels Display preferences on the Mac side as well.
Fix VM Resource Allocation and Host Memory Pressure Intermediate
- Open VM configuration
With the VM shut down, click the wrench icon in Parallels or go to Actions, Configure. Head to the Hardware tab. - Set RAM conservatively
For a 16 GB Mac, give the VM 6 to 8 GB maximum. For an 8 GB M1 Mac (which is common), 4 GB for the VM is the sweet spot. Going higher starves macOS itself and causes both sides to slow down. - Set CPU cores sensibly
Four cores is plenty for most Windows workloads on M1. The M1 has 8 cores total (4 performance, 4 efficiency). Giving the VM more than 4 causes contention with macOS processes. - Check host memory pressure
On the Mac, open Activity Monitor (Applications, Utilities, Activity Monitor) and click the Memory tab. Look at the Memory Pressure graph at the bottom. If it's yellow or red while the VM is running, close browser tabs, quit apps you don't need, and try again.
Advanced Windows on M1 Mac Fixes
These are the big guns. If the quick and intermediate fixes haven't sorted it, something is either fundamentally broken in the VM's virtual disk or there's a Secure Boot configuration issue. Neither of these is scary, but they do take more time.
Fix Secure Boot Certificate Issues in Parallels Advanced
- Identify the symptom
This fix applies if Windows 11 ARM refuses to boot entirely, shows a Secure Boot violation error, or if BitLocker throws errors about the TPM state. You might see a blue screen with a lock icon, or Windows might loop back to the recovery environment. - Shut down the VM completely
Do not suspend it. A full shutdown is required before changing security settings. - Open VM configuration and locate Boot Order settings
In Parallels, go to Actions, Configure, then Hardware, then Boot Order. You'll see a Secure Boot checkbox and, depending on your Parallels version, a button to update the EFI certificates. - Update the Secure Boot certificates
Click the option to update or reset the EFI/Secure Boot certificates. Parallels stores these separately from the Windows installation, and they can go stale after a major Parallels or macOS update. This is an Apple silicon-specific quirk that doesn't affect x64 Parallels installs on Intel Macs. - Save and reboot the VM
Let Windows boot fully. If BitLocker was the issue, it may prompt you for a recovery key. Have that key ready from your Microsoft account at account.microsoft.com/devices/recoverykey.
Recreate the VM from a Clean Windows 11 ARM Image Advanced
- Back up your data first
Export any files from the Windows VM that you need. Either copy them to a shared macOS folder (set up in Parallels sharing settings) or take a full VM snapshot before you start. Do not skip this. - Download a fresh Windows 11 ARM ISO
Get it directly from Microsoft's ARM download page. Confirm the filename contains "arm64" and that the file size is in the 5 to 6 GB range. Anything smaller is probably a stripped or unofficial build. - Create a new VM in Parallels
Open Parallels Desktop, click the plus icon to add a new VM, and choose to install from the ISO you just downloaded. Parallels should detect it as Windows 11 ARM automatically. If it doesn't, manually set the guest OS type to Windows 11 ARM. - Complete the Windows setup
Go through the Windows out-of-box experience. Sign in with a Microsoft account if you want to restore settings and apps. Keep the VM resource allocation sensible from the start (see Solution 3 above). - Install Parallels Tools immediately
Before you do anything else in the fresh VM, install Parallels Tools via the Actions menu. This sets up the display driver and integration features from day one rather than leaving them stale.
If after all of this the Mac itself is behaving oddly outside of the VM, that's worth investigating separately. Our Mac diagnostics guide covers how to run Apple Diagnostics and interpret the results. And if you're seeing kernel panics or persistent crashes on the macOS side, that's a different problem entirely from the VM setup.
Preventing Windows on M1 Mac Problems
Most of the issues in this guide are entirely avoidable. Here's what actually keeps things stable long term, in order of importance.
1. Always use the ARM build. This is non-negotiable. Bookmark the Microsoft ARM download page and use it every time. Never grab a Windows ISO from a third-party site, because you have no way of knowing what's been modified.
2. Keep everything updated, in the right order. Update macOS first, then Parallels Desktop, then Windows inside the VM, then Parallels Tools. Doing them out of order (especially updating Windows before updating Parallels) is a reliable way to introduce compatibility gaps.
3. Allocate VM resources conservatively. The M1's unified memory architecture means the VM and macOS are sharing the same physical pool. There's no separate VRAM or dedicated VM memory. Treat the VM like a demanding app, not a second computer.
4. Snapshot before major changes. Parallels supports VM snapshots. Take one before any significant Windows update, before upgrading Parallels, and before any macOS major version update. A snapshot takes a couple of minutes and can save hours of recovery work.
5. Don't stack background apps. Things like cloud sync clients, video call apps, and browser sessions with dozens of tabs all push host memory pressure up. Run the VM when you actually need it, not alongside everything else you have open.
One more thing: if you're seeing issues with external displays or USB-C peripherals specifically, test those separately from the VM. Sometimes what looks like a Windows virtualisation problem is actually a macOS display or USB-C hub issue. Disconnect everything, test the Mac display output directly, then reconnect and retest. Isolating the variable saves a lot of time.
Windows on M1 Mac: Summary
Running Windows on M1 Mac works well when the setup is right. The M1 chip is genuinely capable, Parallels Desktop is a mature product, and Windows 11 ARM has come a long way. The problems almost always come from configuration rather than hardware, and they're fixable. Use the ARM image, keep everything updated, don't starve the VM of resources, and sort out Secure Boot certificates if Windows won't boot. Do those things and you'll have a stable setup that holds up properly. If you're still stuck after working through all of this, our remote support team can connect directly and sort it in one session. No need to guess any further.