How to run Windows on Mac with a virtual machine (2026)

To run Windows on a Mac without restarting, install a virtual-machine app and a Windows version that matches your Mac’s processor. Apple Silicon Macs normally use Windows 11 Arm64; Intel Macs use Windows 11 x64. Check your Windows app and its drivers before buying software: getting to the Windows desktop does not prove that your whole workflow will work.

Start with Apple menu → About This Mac. A “Chip” field identifies Apple Silicon; a “Processor” field identifies Intel. Then use the route table below. A VM runs Windows alongside macOS and shares your Mac’s resources. It does not turn the Mac into a PC with identical graphics or hardware support.

Vendor documentation checked: 8 October 2026. Setup labels and supported features can vary by VM version, Mac model and macOS release.

Choose your Windows-on-Mac route

Your Mac or requirement	Practical route	Check before installing
Apple Silicon: everyday Windows apps	Windows 11 Arm64 in Parallels Desktop or VMware Fusion	Arm app/driver compatibility; your VM’s graphics and integration features.
Intel Mac	Windows 11 x64 in a compatible VM app	Exact Mac, macOS and VM-version support. Parallels 27 is Apple Silicon only; Intel support continues in version 26.
A free VM app	Fusion, UTM or VirtualBox, depending on your requirements	Windows still needs licensing. Free tools have different support and feature limits.
Existing Intel Windows VM moving to Apple Silicon	Usually create a fresh Arm64 VM and reinstall compatible apps	Copying an x64 VM does not convert its architecture. Whole-system emulation is a separate exception.
A critical x64-only workflow or incompatible driver	Consider a suitable Windows PC or a remote Windows environment	Verify the application, peripherals, network access and licensing for the alternative.

The processor distinction is documented by Broadcom for Fusion. For the Intel transition, Parallels explains its version 26 and 27 support. Choose the current build that supports your hardware rather than assuming the newest major version works on every Mac.

Why use a virtual machine instead of Boot Camp?

A VM lets you switch between Mac and Windows apps without rebooting. Boot Camp is a separate dual-boot approach: Apple’s Boot Camp instructions cover Windows 10 on supported Intel Macs. Boot Camp is not available on Apple Silicon, and that Apple article is not an official Windows 11 installation route.

Windows 10 Home and Pro reached the end of standard support on 14 October 2025, according to Microsoft’s lifecycle page. An old Boot Camp installation needs its own lifecycle plan; do not treat Windows 10 as an automatically safe fallback for an older Mac.

• Convenience: macOS and Windows stay available at the same time.
• Snapshots: revert a VM state after a change, subject to your VM app’s features.
• Integration: clipboard, display resizing and file sharing depend on the product and guest architecture.
• Trade-off: both systems compete for memory and CPU, and virtual graphics have limits.

Check app compatibility before you buy

Windows 11 Arm can run many x86 and x64 applications through Windows’ app-emulation layer. Drivers are different: hardware and software that depend on drivers need compatible Arm64 drivers. Microsoft’s Windows on Arm FAQ explains the distinction, including peripherals, antivirus and anti-cheat software.

Dependency	What to ask or test	A useful pass condition
Your Windows application	Does its publisher support Windows 11 Arm and a VM? Test the exact version and required add-ins.	Open a real sample file, edit it, save it and export the format you actually use.
Printer, scanner, USB dongle or specialist device	Is a suitable Windows Arm driver available, and does your VM support the connection?	Complete the actual scan, print or licence-dongle operation.
VPN, endpoint security or sign-in tooling	Does IT approve this guest architecture and deployment?	Connect and authenticate using the approved configuration.
Game or graphics application	Check its graphics API, anti-cheat and VM policy.	Launch the required title or project; reaching the desktop is not enough.
Developer tools	Check nested-virtualisation and architecture requirements.	Build and run the project, including its containers or emulators.

This is a suggested validation checklist, not a claim that TechVertu has tested your software. Keep the trial VM until these checks pass, and ask the publisher about anything that remains uncertain.

System requirements for running a Windows VM on Mac

Minimum requirements

Check the VM app’s host requirements separately from Windows’ guest requirements. Microsoft’s Windows 11 VM requirements include at least 4 GB RAM, 64 GB storage and two virtual processors, with Secure Boot capability and virtual TPM. Those figures describe the guest; macOS still needs resources of its own. Use the vendor’s Windows 11 configuration rather than bypassing checks.

The Parallels system-requirements table lists supported macOS versions and hardware for each release. Its version 27 requirements include Apple Silicon, a minimum of 8 GB host RAM and supported macOS releases beginning with Sonoma 14.7. An installer falling back to an older product version is not the same as current-version support.

Recommended specifications

For ordinary office work, a Mac with 16 GB RAM or more gives more room for both systems; heavier projects may need more. Treat this as planning guidance, not a universal performance guarantee. Use the app vendor’s requirements and observe memory pressure during your normal workload. Our laptop RAM guide explains how workload affects memory needs.

Budget storage for Windows, applications, updates, working files and snapshots—not just the download or virtual disk’s starting size. A dynamically growing disk can become much larger. Keep free space on the Mac and maintain a separate backup.

Comparing virtual-machine software for Mac

VM app	Where it fits	Important limits
Parallels Desktop	Paid option for guided Windows installation and Mac integration.	Check edition limits and current Intel/Apple Silicon support. Windows is licensed separately.
VMware Fusion	Free for personal, educational and commercial use; useful when its feature set fits.	No x86 guest OS on Apple Silicon. Windows shared folders and Unity are not universally available.
VirtualBox 7.2	Open-source base package with Intel and Apple Silicon host builds.	Arm hosts require Arm guests; feature parity and automated setup differ. Extension Pack terms are separate.
UTM	Free direct download; useful for manual virtualisation or selected emulation scenarios.	No Windows 3D acceleration according to UTM. Emulation and virtualisation have different performance.

1. Parallels Desktop

Parallels offers a guided Windows download and installation route and features such as Coherence for integrating Windows apps into the Mac desktop. Check its current editions and pricing for your region rather than relying on an old annual price. The VM-app purchase does not include a Windows licence.

Microsoft’s Windows-on-Mac options page describes the Parallels Windows 11 Pro/Enterprise route. Its listed versions and chip names are narrower than the current Parallels compatibility table, so check the vendor’s current requirements for newer releases and hardware. Do not assume that every hypervisor has identical Microsoft authorisation or vendor support.

2. VMware Fusion

Broadcom made Fusion free for all users, including commercial use. Windows is not included, and free access does not mean paid support ticketing is included.

Fusion is a practical alternative if its features cover your needs. Broadcom’s feature matrix linked above lists DirectX 11 support, snapshots and clipboard integration, but does not list Windows shared-folder support on Apple Silicon or Unity in current listed versions. Check that matrix instead of expecting Intel and Arm guests to behave identically.

3. VirtualBox

VirtualBox is no longer an Intel-only option: Oracle’s VirtualBox 7.2 manual includes Apple Silicon hosts and Windows 11 Arm guests. Arm hosts cannot run x86 guest operating systems. Arm setup lacks unattended installation and differs from Intel configuration; do not reuse an old x86 settings recipe.

4. UTM

UTM is available as a free direct download, with a paid App Store distribution. It distinguishes virtualisation, where the guest architecture matches the host, from emulation of another architecture. Its website states that Windows lacks 3D acceleration, which makes it a poor default for demanding Windows games or graphics work.

For a normal Apple Silicon Windows installation, choose Arm64 virtualisation. Use x86 emulation only when the specific legacy requirement justifies its limitations; do not confuse it with Windows’ x86/x64 app emulation inside an Arm guest.

Windows licensing: what the VM app does not include

Downloading Windows and installing a VM app are separate from obtaining the right Windows licence. A free hypervisor does not make Windows free, and a paid hypervisor is not a Windows licence.

• For the Parallels Windows 11 Pro route, Microsoft requires a separate licence for each instance. Pro product keys are architecture-agnostic: x64 versus Arm does not require a special Arm key.
• Microsoft describes Enterprise on this route as a Pro licence followed by an Enterprise upgrade through a volume licensing agreement. Business subscription rights depend on the actual agreement and deployment.
• If you plan to reuse a licence from another computer, check its acquisition and transfer terms. Do not assume an OEM/preinstalled licence transfers to your Mac VM or that successful activation proves entitlement.

Use Microsoft’s licence terms and your organisation’s licensing administrator for the applicable rights. Our Windows 11 Home vs Pro and Pro vs Enterprise guides help explain editions; edition features and licence entitlements are separate questions.

Step-by-step guide: installing Windows with Parallels Desktop

Back up important Mac files first. Confirm the processor architecture, host support, licence and app checklist above. These steps follow the vendor’s documented workflow; exact screens may change.

Step 1: Download and install Parallels Desktop

Get the installer from the official Parallels site. Use a release that supports your Mac and macOS; Intel users should check version 26 rather than install an Apple Silicon-only release. Follow the installer and use the trial or your purchased VM-app licence.

Step 2: Obtain Windows installation media

On Apple Silicon, use the guided Windows download or Microsoft’s Windows 11 Arm64 ISO. On Intel, use the Windows 11 x64 ISO. “Arm64” and “x64/AMD64” are different installer architectures; the x64 download is not the normal Apple Silicon route.

Step 3: Create your Windows virtual machine

Parallels’ Apple Silicon installation instructions describe Control Center → + → Get Windows 11 from Microsoft → Continue → Install Windows when other VMs already exist. A first installation may offer Windows automatically. If using an ISO, select the image-file installation route and choose the correct architecture.

Step 4: Configure virtual-machine settings

Start with the Windows 11 profile and the vendor’s automatic resource settings. Ensure the guest meets its requirements. Leave enough memory and CPU capacity for macOS; allocating every core or nearly all host RAM can make both systems slower. Increase resources only when the workload and edition limits justify it.

Review shared folders and clipboard settings before adding business data. Share a dedicated working folder where possible rather than the entire Mac home directory. Choose a storage location with enough space for growth and backups.

Step 5: Complete Windows installation

1. Follow Windows setup and review its account, privacy and licence prompts.
2. Check Windows activation under Settings → System → Activation using the licence for the installed edition.
3. Check that Parallels Tools is installed, then run Windows Update and update the VM app.
4. Restart, test your application and peripherals, and take a baseline snapshot if supported. Make a separate backup as well.

Setting up a Windows VM with VMware Fusion

Installation process

Follow Broadcom’s Fusion download and installation instructions. Obtain the installer through the official channel, check host compatibility and follow the installation prompts. Use the current free distribution and follow its activation or registration prompts.

Creating a new virtual machine

On Apple Silicon, Broadcom documents File → New → Get Windows from Microsoft to obtain Windows 11 Arm. Use UEFI, configure the encryption required for the virtual TPM and retain the encryption credential securely. Create the virtual disk and complete Windows setup. On Intel, use compatible x64 installation media and the corresponding guest configuration.

Optimisation settings

Install VMware Tools from Virtual Machine → Install VMware Tools and restart the guest. Tools provide display and integration drivers; they do not turn an unsupported Windows app or Intel-only driver into an Arm-compatible one. Use the feature matrix above to choose a file-transfer method supported by your host and guest.

VirtualBox installation guide for Mac

Getting started with VirtualBox

Install the official package for your Mac’s architecture. Start with the base app and matching Guest Additions.

Creating your Windows VM

Create a VM with the matching Windows ISO and required guest resources. Complete the Windows installer manually on Arm.

Critical configuration steps

Follow the current manual’s guest-specific settings. Arm controls differ from Intel controls. Check support if Windows rejects the configuration.

The Extension Pack is separate from Guest Additions. Only add it if you need one of its features, and review Oracle’s Extension Pack licence for your use case. Do not assume the base package’s open-source terms cover every optional component.

Setting up Windows with UTM

UTM’s Windows guide describes + → Virtualize → Windows. Select a matching ISO, set resources and enable its drivers/SPICE-tools installation option. Create the disk, save the VM and start the Windows installer. Install the guest tools for input, display and networking support. For this standard route, use Arm64 on Apple Silicon or x64 on Intel; choose Emulate only deliberately.

Performance optimisation tips

Universal optimisation strategies

• Use the VM vendor’s starting settings, then measure the application you actually need.
• Check Mac memory pressure and guest utilisation before adding RAM or CPU.
• Keep enough host disk space and use reliable storage for the VM.
• Install updates and the correct guest tools; test changes one at a time.
• A snapshot is a rollback point, not an independent backup if the Mac’s storage fails.

Parallels-specific optimisation

Use the profile that suits the workload and stay within your edition’s resource limits. Coherence affects presentation and workflow; it does not remove the guest’s architecture or graphics limitations.

VMware Fusion optimisation

Check Tools and supported graphics settings before increasing resources. If an expected integration feature is absent, check the current Intel-versus-Apple-Silicon matrix first. Extra memory cannot add a feature the product does not provide.

VirtualBox performance tweaks

Use matching Guest Additions. Compare one supported setting change at a time using the same workload.

Troubleshooting common issues

Issue 1: The virtual machine will not start

Check the host/guest architecture first, then the VM app’s macOS support, disk space and Windows configuration. An x86-versus-Arm error in Fusion calls for the correct guest image; it is not fixed by assigning more CPU cores. In UTM, an EFI shell may mean the installer was not booted or the ISO architecture is wrong.

Issue 2: Poor graphics performance

Check that guest tools loaded and that the application’s graphics API is supported. A working Windows desktop is not proof of DirectX 12 support or GPU passthrough. If the required graphics feature is missing, reduce expectations or choose a different execution environment.

Issue 3: Network connectivity problems

Confirm the Mac has a connection, the virtual adapter is connected and guest network drivers are installed. Check VPN and firewall policy with IT for work devices. Shared/NAT networking is a sensible starting point for ordinary access; bridging should be a deliberate choice, not the default fix for every problem.

Issue 4: Apple Silicon compatibility issues

Prefer an Arm64 build of the application where offered, then check the exact x86/x64 version and required add-ins. If a peripheral, security tool or VPN fails, ask its vendor about Arm64 driver support. Reinstalling Windows does not create a missing driver.

Issue 5: Activation problems

Check that the installed edition matches the licence, the VM has internet access and any organisational activation requirements are met. A clone or hardware-identity change may need reactivation. Ask Microsoft or your licensing administrator rather than using unofficial activation scripts.

Advanced features and use cases

Development environment setup

Parallels’ current Apple Silicon limitations state that nested virtualisation, Hyper-V-based workloads, WSL2 and VBS are not available in its Windows guest. Do not assume these work because Windows Pro includes the features. A separate Linux VM may suit some projects; otherwise validate a suitable remote or physical Windows environment.

Gaming on virtual machines

Parallels lists graphics support at DirectX 11.1 and OpenGL 4.3; some newer games will not work. Fusion’s published matrix lists DirectX 11. UTM’s Windows 3D limit is another reason to check the title before installing. Anti-cheat compatibility and publisher VM policies can block a game independently of frame rate.

There is no universal percentage for performance relative to a physical PC. Game, hardware, graphics API, VM version and guest architecture change the outcome. Our Windows gaming comparison discusses performance variables, but PC benchmarks do not establish Mac-VM performance.

Running legacy software

Parallels has a separate preview x86 whole-system emulator for selected Intel VMs on Apple Silicon. Its documentation describes edition, firmware and performance restrictions. Treat it as a limited migration/testing route, not the normal Windows 11 Arm setup or a guaranteed way to run an old production application.

An existing Intel VM cannot simply become an Arm VM. A fresh supported guest with compatible app installations is usually easier to maintain; copy data only after backing it up. Do not expose an unsupported Windows XP or Windows 7 guest to ordinary browsing or business use merely because it starts.

Security best practices

Essential security measures

• Update the host, VM app, guest OS and applications.
• Use Windows Security or an approved compatible protection tool. On Arm, check any third-party security driver support.
• Limit shared folders, clipboard sharing and USB access to what the task needs.
• Keep a separate backup and test recovery. Snapshots depend on the underlying VM storage.
• Shared/NAT networking is not a complete security boundary; the guest can still communicate through allowed connections.

Data protection strategies

Protect the Mac and VM storage, retain encryption/recovery credentials securely, and review which Mac folders the guest can access. A guest with write access to shared files can affect those files. For Windows file and drive protection options, see our Windows file-protection guide.

For work use, confirm approved storage, authentication and backup rules with IT before copying company data into the guest. A VM is not automatically a compliant business environment.

Cost comparison and recommendations

Total cost of ownership in the first year

Route	Costs to include	Budget check
Parallels	Current edition/renewal or purchase terms + Windows licence + app licences	Promotions, edition limits, support and upgrade terms can change.
Fusion	Windows licence + app licences + setup/support time	The hypervisor is free; Windows and application licences remain separate.
VirtualBox	Windows licence + app licences + any required optional-component rights	Base-package and Extension Pack terms differ.
UTM	Windows licence + app licences; optional paid distribution	Free direct download does not include Windows.
Remote Windows environment	Cloud/remote access licensing, configuration and ongoing service costs	A different deployment and network dependency, not a local VM.

Recommendations by user type

• Everyday Windows-app use: trial a guided Parallels installation and validate your required app before purchase.
• Budget-conscious users: evaluate Fusion first if its feature matrix meets your needs; consider UTM or VirtualBox for a compatible manual setup.
• Intel Mac owners: prioritise a VM release supported on your macOS and hardware rather than the newest release number.
• Developers: validate architecture, build tools, containers and nested virtualisation before committing.
• Critical incompatible workflows: compare a suitable Windows PC or approved remote Windows deployment.

If a Cloud PC is an alternative, our Windows 11 vs Windows 365 guide explains the local operating system versus hosted Cloud PC distinction. Remote access has its own network, peripheral and licensing checks.

Frequently asked questions

Conclusion

Choose the architecture first, then the VM app. A good setup is one that runs your actual application, supports the devices it needs and has the right licences—not simply one that boots Windows. Start with a supported configuration, test the workflow and keep both the Mac and Windows guest maintained.

If keyboard shortcuts behave differently between systems, our Mac, Windows and Linux function-key guide can help you check the host-side controls.