CrossOver for Mac: What It Can't run (and What to Use Instead)

CrossOver can run plenty of Windows software on a Mac without installing Windows. Pick an app with a strong compatibility rating, and it can be a much lighter way to get that one Windows program running.

Problems start when an app expects parts of Windows that CrossOver can't provide. A Windows app might open but have broken features. An installer might work until it reaches a Windows service or driver. A game may get past the launcher and fail when its anti-cheat system loads. On Apple silicon, processor architecture adds another compatibility question.

So before buying CrossOver or spending hours trying different bottle settings, check what the application actually requires.

This guide looks at the categories that cause the most trouble, what has changed on Apple silicon, and when running Windows 11 in a virtual machine such as Parallels Desktop for Mac is the better fit.

How CrossOver works on a Mac

CrossOver is based on Wine, the open-source compatibility layer. It doesn't boot a copy of Windows in the background. Instead, Wine implements Windows APIs so compatible Windows applications can run on macOS.

That's why CrossOver doesn't require a Windows installation or Windows license. It also avoids the CPU and memory overhead of keeping an entire Windows virtual machine running just to use one application.

The limitation comes from the same design.

Windows applications can depend on much more than the visible program. They may expect particular Windows frameworks, services, graphics APIs, drivers, browser components, or other system behavior. When CrossOver can't provide something the application expects, compatibility can range from a small glitch to an installer that won't finish.

There's no useful rule that says a certain age or type of Windows program will always work. Check the specific application and version.

The CodeWeavers compatibility database is the best place to start. Don't stop at the medal rating. Look at the tested version, recent reports, and any notes about features that don't work. A good result for an older release doesn't automatically apply to the version you're installing today.

Windows apps that can cause problems in CrossOver

Microsoft 365, Access and Office workflows

Basic Office use isn't a particularly good reason to run Windows software on a Mac in the first place. Microsoft already provides native Mac versions of Word, Excel, PowerPoint, and Outlook. The situation changes when a company depends on something that's specific to the Windows version of Office.

Microsoft Access is an obvious example because there is no native Access application for macOS. Some organizations also rely on Windows-only Excel add-ins, COM components, VBA code tied to Windows dependencies, or an older Office application that must behave exactly as it does on a company PC. Those are poor workflows to assume will work in CrossOver without testing.

Office compatibility also changes between releases, so a report that Word or Excel worked under one CrossOver and Office version doesn't tell you that your current Microsoft 365 setup will behave the same way. If the requirement is simply editing a spreadsheet or Word document, use the Mac version of Office. If the requirement is a Windows-specific Office workflow, check the exact application and dependencies first.

For Access, Windows-only Office integrations, and business-critical legacy setups, running Office inside Windows 11 with Parallels Desktop is usually a more predictable approach because Office is running in Windows rather than through a Wine compatibility layer.

See our guide to running legacy Office macros on Mac for a closer look at that particular case.

SOLIDWORKS, AutoCAD, Revit, and other engineering software

CAD applications are a good example of why a simple “Windows app: yes or no?” compatibility rating doesn't tell the whole story. Programs such as SOLIDWORKS, AutoCAD and Revit combine the application itself with graphics requirements, licensing systems, plug-ins, and other Windows components. Compatibility can also change considerably between releases.

CodeWeavers has compatibility entries for multiple versions of SOLIDWORKS, for example, but the existence of an entry isn't the same as official application support or a guarantee that every feature works. For professional CAD work, that's an important difference. Getting an application to launch isn't enough if a required plug-in, rendering feature, or licensing component fails halfway through a project.

A Windows virtual machine gives these applications access to Windows itself rather than recreating Windows APIs on macOS. On Apple silicon Macs, Parallels Desktop runs Windows 11 on Arm, so you should still check the software vendor's Windows on Arm requirements before committing to a setup.

For production work, verify the exact CAD release, required plug-ins, and hardware requirements. Don't assume either CrossOver or a VM can run a particular engineering workflow solely because the main application opens.

Games, DirectX 12, and anti-cheat

DirectX 12 isn't a simple dividing line between CrossOver and Parallels. CrossOver's D3DMetal graphics backend supports DirectX 11 and DirectX 12 translation for compatible games. Some DX12 titles work. Others don't, and compatibility can change with the game, launcher, and CrossOver release. Anti-cheat software is often a harder obstacle. Some multiplayer games use low-level anti-cheat technology that expects Windows kernel functionality. A compatibility layer can't necessarily provide that environment. This is why a game can appear technically capable of running and still stop at its anti-cheat or launcher.

Check the CodeWeavers compatibility database for the exact title rather than deciding based on “DX11” or “DX12” alone.

A Windows VM isn't a universal gaming workaround either. Parallels Desktop currently supports DirectX up to version 11, not general DirectX 12 support, and Windows 11 on Arm introduces compatibility restrictions of its own. Kernel-level anti-cheat can still be a problem.

If your main goal is one particular Windows game, research that title before choosing CrossOver or Parallels. Gaming compatibility on a Mac is too game-specific for a blanket recommendation.

Software that depends on Windows services or drivers

This is where the difference between a compatibility layer and a virtual machine becomes much more important. Some Windows programs install a service that runs in the background. Others depend on system drivers or interact closely with Windows security and hardware. That can include certain VPN clients, endpoint security products, backup software, device utilities, database components, and specialist business applications.

CrossOver isn't a complete Windows operating system, so software that expects this kind of system-level Windows environment can run into a hard limit. A Windows VM is a better candidate for those applications because Windows services and supported Windows drivers can run inside the guest operating system. There is still an important qualification on Apple silicon: Windows 11 on Arm requires compatible drivers. An old x86 Windows driver doesn't become Arm-compatible just because the application is running inside a VM.

If a Windows application's setup instructions tell you to install a driver or enable a Windows service, check that dependency before trying CrossOver.

Older business and industry-specific Windows applications

A lot of Windows software still in daily use was built for one company, one piece of equipment, or one narrow industry. These applications don't always have useful public compatibility reports. They may also depend on an old .NET runtime, database client, USB device, Internet Explorer-era component, or licensing utility that isn't obvious until installation. That makes an “untested” CrossOver rating genuinely untested. It doesn't mean the application will fail, but it also isn't much reassurance when employees need the program to work on Monday morning.

If CrossOver already has a strong, recent compatibility report for the exact application, test it. For an obscure business application with several Windows dependencies, a VM usually gives you fewer compatibility variables to investigate.

What Apple silicon changes

Apple's move from Intel processors to its own Arm-based chips changed how Windows software runs on a Mac. Current Apple silicon Macs use Arm processors. Much of the Windows software people want to run was originally compiled for Intel's x86 or x64 architecture.

CrossOver has historically relied on Rosetta 2 as part of the process of running x86 Windows software on Apple silicon. CodeWeavers has also been working on native ARM64 support as Apple changes the future of Rosetta, and its 2026 CrossOver Preview introduced native ARM64 macOS support. That makes older descriptions of CrossOver as permanently requiring the same “double translation” stack increasingly misleading. The architecture is changing. What hasn't changed is the need to check the application.

Parallels takes a different route. On Apple silicon, it runs the Arm version of Windows 11 in a virtual machine. Arm-native Windows applications can therefore run in their native Windows architecture. Windows 11 on Arm also includes Microsoft's own emulation for many x86 and x64 applications. Microsoft identifies Parallels Desktop as an authorized solution for running Arm versions of Windows 11 on Apple silicon Macs. That doesn't turn an Apple silicon Mac into an x86 Windows PC. Software that depends on unsupported drivers, hardware, or other architecture-specific components can still fail under Windows 11 on Arm.

CrossOver on Intel Macs

CrossOver's Mac architecture is also changing as CodeWeavers focuses development on Apple silicon and ARM64.

If you're using an older Intel Mac, check the system requirements for the current CrossOver release before buying or upgrading. Don't assume instructions written for an earlier CrossOver version still apply.

We've covered the change in more detail in what CrossOver's move away from Intel Mac support means.

Intel Mac owners considering Parallels should also check the current Parallels Desktop and macOS support matrix. Older hardware can run into host OS support limits even when the Windows application itself would otherwise work.

When a full Windows VM makes more sense

Suppose your accounting department needs an old Windows client that talks to a local database service. Or an engineering application relies on a Windows licensing component. Maybe an Access database uses integrations that were never built for macOS.

In cases like these, troubleshooting CrossOver can turn into a hunt for the missing piece of Windows the application expects.

Parallels Desktop runs Windows itself. Applications therefore have access to Windows frameworks, services, and other supported system components inside the VM. Windows 11 on Arm compatibility still applies, but you're no longer asking Wine to reproduce the Windows environment for the application. CrossOver remains a sensible choice for a known-compatible program, particularly when you don't otherwise need Windows.

Consider a full Windows VM when your workflow depends on:

• Windows services or Windows-specific system components
• Microsoft Access or Office integrations that require Windows
• Several Windows applications with different dependencies
• Specialist business software that hasn't been well tested in CrossOver
• An application whose required features fail even though the program itself launches in CrossOver

There's also a practical benefit to having Windows available as Windows. Parallels Desktop can run Windows alongside macOS, and you can move between Mac and Windows applications without rebooting the computer. Clipboard and file sharing reduce friction when a workflow crosses both operating systems.

If one supported Windows application is all you need, that extra environment may be unnecessary. If Windows itself is part of the application's requirements, it's a different calculation.