ARM Isn't Always the Answer
Sometimes an Intel- or AMD-powered PC is still the better choice.
CheckMyARM has an awkward confession to make.
Sometimes we think you should buy a computer that isn't ARM.
That probably shouldn't be surprising. The point of CheckMyARM isn't to convince everyone to buy a Snapdragon PC. It's to help people figure out whether one makes sense for them.
And sometimes it doesn't.
Windows on ARM has improved dramatically. Modern Snapdragon PCs can run an enormous amount of ordinary Windows software, native ARM applications are becoming increasingly common, and Microsoft's Prism emulation can run many existing x86 and x64 applications remarkably well.
Meanwhile, the advantages that attracted people to ARM in the first place are very real.
Excellent efficiency can mean extraordinary battery life. Lower power consumption can mean less heat and less cooling. Less cooling can mean quieter computers. And modern ARM processors can deliver .
That's a pretty compelling package.
But there's a question hiding underneath all of those advantages:
How much do you care about them?
Because a compromise only makes sense when you're getting something you value in return.
Buy the benefit, not the architecture
Imagine someone who carries a laptop everywhere.
They work on airplanes. They spend hours in conference rooms without outlets. They use the computer on the couch, at coffee shops, in hotel lobbies, and occasionally outside. They hate carrying a charger. They notice fan noise. They notice heat.
Give that person a lightweight computer that performs well, stays cool and quiet, and lasts dramatically longer away from an outlet, and you've meaningfully changed their experience.
Now imagine someone else.
Their laptop leaves its dock twice a year.
Battery life is already fine. They don't particularly care whether the fan occasionally runs. Their desk has an outlet approximately fourteen inches away.
The same ARM advantages are still technically advantages.
They just aren't worth as much.
That's important because Intel- and AMD-powered Windows PCs still have one enormous advantage of their own:
They live at the center of the Windows PC ecosystem we've been building for decades.
More software was originally built for them. More hardware was designed around them. More drivers exist for them. There are more models, more configurations, more upgrade options, and fewer architecture-specific questions to ask.
If ARM gives you something you genuinely value, investigating those questions may be an excellent trade.
If it doesn't?
Why volunteer for them?
Portable isn't necessarily unplugged
Gaming makes this distinction unusually easy to see.
There are plenty of games you can play on a Windows ARM PC. Some run natively, many conventional Windows games can run through emulation, and cloud gaming can make the architecture of your local processor almost irrelevant.
So "ARM can't game" isn't a useful conclusion.
But someone buying a computer primarily for high-end local gaming has a different set of priorities.
They may want a powerful discrete GPU. They may care about maximum sustained CPU and graphics performance. They may have a large existing Windows game library. They may use VR hardware, mods, specialty controllers, or competitive games with anti-cheat systems.
And some anti-cheat systems rely on kernel drivers that aren't available for Windows on ARM. Microsoft explicitly warns that games and other applications depending on unsupported anti-cheat drivers may not work on ARM-based Windows PCs.[1]
Then there's the battery.
A serious gaming laptop is absolutely portable. You can carry it to a friend's house, hotel, tournament, LAN party, or wherever else you'd like to turn electricity into heat at alarming speed.
But you're probably going to plug it in when you get there.
That makes it portable without necessarily making unplugged endurance particularly important.
If the workload you're buying the computer for already assumes wall power, one of ARM's most obvious advantages becomes less valuable. GPU performance, game compatibility, and the freedom to install whatever everyone decides to play Friday night may matter more.
Again, that doesn't make ARM bad at gaming.
It means your version of gaming determines whether ARM's advantages are worth the trade.
97% compatible can still be 0% suitable
Compatibility percentages sound reassuring.
Suppose someone told you:
99.9% of Windows applications work on ARM.
Great.
Unless your job is in the other 0.1%.
An engineer doesn't particularly care that Chrome, Spotify, Word, Slack, and 10,000 other applications work if the CAD package required for work doesn't.
As of publication, Autodesk says its desktop products cannot be installed on Windows ARM systems and directs customers to use an x64 computer instead.[2]
That's not a minor compatibility footnote if AutoCAD is the reason you own the computer.
The same principle applies to an accountant with one mandatory financial package, a musician with one irreplaceable plugin, a scientist with one instrument-control application, or an employee with one required corporate security tool.
This is why raw compatibility percentages can be misleading.
And the inverse matters too.
If 97% of someone's software works and the missing 3% consists entirely of things they don't need, that person may have no meaningful compatibility problem at all.
Don't let somebody else's missing 3% become your problem.
But don't let somebody else's 97% convince you that yours doesn't matter.
Applications are the easy part
One reason modern Windows on ARM works as well as it does is that Microsoft has gotten remarkably good at making ordinary Windows applications run.
Windows 11 can .[3]
That's a big deal.
But there is a line emulation doesn't cross:
Microsoft is explicit about this. Kernel-mode drivers must be built natively for ARM64. Windows does not emulate them.[3][4]
That sounds like an obscure technical distinction until you realize how many apparently unrelated compatibility questions it explains.
A specialized peripheral may depend on a driver.
A VPN or endpoint-security product may depend on a driver.
An anti-cheat system may depend on a driver.
A virtualization product may depend on a driver.
Professional audio equipment may depend on a driver.
Suddenly several different "ARM compatibility problems" turn out to share the same underlying boundary.
But there's an equally important other side to this:
If you don't use anything that depends on an unsupported driver, you don't have that problem.
Someone whose needs are mainstream and well understood may be able to verify everything important surprisingly quickly.
These applications?
Fine.
These peripherals?
Fine.
This printer, mouse, dock, webcam, and headset?
Fine.
Done.
The existence of an unsupported laboratory instrument you've never heard of is not a reason for you to avoid ARM.
Compatibility is personal.
"Works" has levels
Devices add another wrinkle.
Sometimes Windows recognizes a piece of hardware perfectly well using a built-in driver.
The mouse moves. The webcam produces video. The audio interface makes sound.
It works.
But what about the manufacturer's configuration software?
Can you remap the mouse buttons?
Adjust the webcam?
Change audio-routing settings?
Save hardware profiles?
And what happens when the manufacturer releases a firmware update?
This isn't hypothetical. Elgato's current Windows-on-ARM compatibility information shows exactly this kind of mixed ecosystem: some hardware and software are fully compatible while other associated applications or driver-dependent functions have more limited support.[5]
Focusrite provides an equally useful example of how quickly the answer can change.
In August 2025, Focusrite added Windows-on-ARM support to its USB driver and control software, bringing ARM support to a large range of its audio interfaces. But Focusrite still cautions that some DAWs and bundled software may lack native ARM support, and some older or differently connected products remain unsupported.[6]
So a better compatibility question isn't always:
Does the device work?
It may be:
Does the hardware work?
Do all the features I care about work?
Can I configure and maintain it?
Your computer may be yours. Your requirements may not be.
Corporate computers introduce a particularly easy trap.
You may know exactly which applications you use.
Your employer may have other ideas.
Endpoint security. VPN software. Data-loss prevention. Device control. Authentication software. Smart-card middleware. Management agents. Monitoring tools.
Some major enterprise products already support Windows on ARM. That's worth emphasizing: this is not a blanket "corporate software doesn't work on ARM" warning.
For example, major enterprise security and connectivity vendors now offer ARM64 support for products including endpoint protection and VPN clients.[7]
But your employer doesn't require "a VPN."
They require their VPN.
They don't require "endpoint security."
They require a particular product, version, configuration, and perhaps a collection of additional modules that must all function correctly.
If your company dictates that stack, .
The same applies to universities, government environments, regulated industries, clients, and anyone else who gets a vote in what your computer must run.
Sometimes the most important compatibility requirement isn't something you chose at all.
You run virtual machines. Great. What's in them?
Virtualization is another place where broad ARM advice gets misleading quickly.
Windows on ARM can absolutely . Microsoft supports Windows 11 ARM virtual machines, and modern development environments can make ARM a perfectly capable platform for many virtualization and container workflows.[4]
So:
"I use virtualization"
doesn't tell us very much.
What are you virtualizing?
If your workflow uses ARM-native Linux environments, Windows ARM virtual machines, WSL, containers available for ARM, and modern development tooling, you may be perfectly happy.
If your job depends on an existing collection of x64 virtual machines, architecture-specific appliances, kernel modules, low-level tools, or other assumptions about an Intel/AMD host environment, you have more homework to do.
Microsoft specifically notes that the lack of kernel-driver emulation particularly affects virtualization scenarios.[3]
The problem isn't virtualization.
It's the workload you inferred when you said "virtualization."
That's an important distinction because the same applies to other supposedly "heavy" workloads.
ARM processors aren't somehow disqualified because a task is computationally expensive.
The meaningful questions are more specific:
Does the workload require a particular GPU?
CUDA?
An x64-only library?
A specialized driver?
A particular plugin?
A certified hardware configuration?
An existing virtual appliance?
Those are compatibility questions.
"Heavy compute" isn't.
Sometimes the application works and your workflow doesn't
Professional software can be particularly deceptive because the application itself may be only one layer.
Adobe provides a useful example.
Its Windows-on-ARM support has expanded considerably, and applications including After Effects now run natively on ARM systems. But Adobe notes that third-party plugins still need compatible ARM versions; plugins compiled only for Intel-based Windows systems don't simply become ARM plugins because the host application does.[8]
So:
After Effects works.
Excellent.
Do the six plugins your workflow depends on?
A musician may face a similar chain:
DAW → plugins → control software → audio interface → driver
An engineer may have:
CAD application → extension → hardware SDK → specialized peripheral
A developer may have:
IDE → toolchain → library → container → test environment
That's another reason CheckMyARM cares about what you actually do, rather than merely counting installed applications.
Sometimes you just want a weird computer
There's another advantage Intel and AMD have that isn't really about compatibility at all:
choice.
The modern Windows-on-ARM catalog is growing quickly. Snapdragon systems now include conventional laptops, convertibles, larger-screen machines, mini desktops, and all-in-one PCs.
That's excellent progress.
But Intel- and AMD-powered PCs still occupy a vastly larger product universe.
And the stranger your requirements become, the more that matters.
Want an 18-inch laptop?
A specific NVIDIA GPU?
64GB or 96GB of memory?
Multiple internal drives?
A particular collection of ports?
A workstation-class machine?
Replaceable memory?
A desktop with PCIe expansion?
A computer you'll rebuild and upgrade for years?
There may be an ARM machine that satisfies some of those requirements.
There are simply far more Intel/AMD machines from which to find the exact combination.
That's not an architectural failure.
It's what happens when one ecosystem has been the center of the Windows PC industry for decades and another is still growing.
Sometimes old is the problem
That enormous ecosystem matters at both ends of the technology timeline.
Consider an old but perfectly functional specialized peripheral.
Maybe it's a professional audio interface, scientific instrument, industrial controller, scanner, programmer, medical device, or some obscure USB box whose purpose makes perfect sense to the three people on Earth who own one.
Its manufacturer may have stopped updating the driver years ago.
That doesn't mean the hardware is bad.
It may work flawlessly.
But if it depends on an x86/x64 driver, and the manufacturer never creates an ARM64 version, Windows application emulation can't rescue it.[3][4]
The product doesn't need to be broken.
It just needs to be finished.
If your livelihood depends on one, that's a very good reason to stay with the architecture it already supports.
Sometimes new is the problem too
Here's the fun inversion.
The mature Intel/AMD ecosystem doesn't only give you access to old things.
Sometimes it gets you the newest toys, too.
Memory is a good example.
Most Snapdragon X systems use fast, power-efficient LPDDR5X memory soldered directly to the system board. The Snapdragon-powered Lenovo ThinkCentre neo 50q QC desktop, for example, currently offers 16GB or 32GB of soldered LPDDR5X with no memory slots.[9]
At publication time, we haven't identified a shipping Snapdragon X Windows PC with user-upgradeable system memory.
That doesn't mean efficient memory has to be soldered.
is a newer modular memory standard that packages power-efficient LPDDR5X into replaceable, upgradeable modules. Micron says LPCAMM2 can consume substantially less power than conventional DDR5 SODIMMs while still allowing memory upgrades.[10]
Framework's 2026 Intel-powered Laptop 13 Pro uses LPCAMM2 and supports replaceable memory configurations up to 96GB.[11]
So the choice is no longer necessarily:
efficient memory or upgradeable memory.
The wider PC ecosystem is finding ways to offer both.
That's an important reminder that platform advantages don't remain exclusive forever.
ARM raised the bar
In fact, one of the best things ARM has done for Windows PCs may have nothing to do with whether you buy one.
It made the competition better.
Intel has been unusually candid about this.
When describing the development of its Core Ultra 200V "Lunar Lake" processors, Intel said it faced new competition delivering roughly comparable performance at much lower power.
Its response was to focus aggressively on efficiency.
"The story was efficiency," one Intel architect explained. Intel says the resulting processor can use as much as 40% less power than its predecessor.[12]
That's competition doing exactly what competition is supposed to do.
Snapdragon showed Windows buyers that excellent performance didn't have to mean mediocre battery life.
Intel responded.
AMD is chasing the same goal.
And the result is that some current Intel- and AMD-powered laptops now deliver battery life and efficiency that would have looked distinctly ARM-like not very long ago.
That doesn't erase ARM's advantages. Performance per watt, unplugged performance, heat, battery capacity, workload, display technology, and system design all complicate direct comparisons.
But it changes the question.
Suppose a Snapdragon laptop lasts 15 hours doing what you do.
That's excellent.
Suppose a comparable Intel laptop lasts 13.
If you regularly need hour fourteen, those extra two hours may be transformative.
If your workday ends at hour eight, perhaps they aren't.
Meanwhile, if the Intel machine gives you a particular GPU, replaceable memory, an application you need, or simply greater confidence that some future requirement will work, the balance may tip the other way.
Buy the benefit, not the architecture.
Ironically, one reason an Intel or AMD laptop may now be a better answer for you is that ARM helped make it a better laptop.
What happens when we remove the battery?
This question is getting more interesting because Windows ARM desktops now exist.
Qualcomm and its partners are bringing Snapdragon X into mini PCs, compact desktops, and all-in-one systems.[13]
And ARM still has potential advantages there.
Efficiency matters on a desktop. Heat matters. Noise matters. Small computers benefit from low power consumption. Organizations deploying thousands of machines may care quite a bit about electricity. Integrated NPUs and other platform features may be attractive.
But one obvious ARM advantage disappears completely:
There is no battery to save.
A desktop also has much more freedom to solve heat with bigger heatsinks and larger, slower-moving fans. It can have a bigger power supply. Conventional desktop platforms can offer discrete graphics, replaceable memory, PCIe cards, enormous storage flexibility, and all sorts of specialized configurations.
That doesn't mean ARM desktops don't make sense.
It means they provide a useful thought experiment.
Take away battery life and mobility.
Which ARM advantages are still valuable to you?
If the answer is "several," keep looking.
If the answer is "not many," the enormous Intel/AMD ecosystem becomes harder to ignore.
Maybe you don't want to think about any of this
That's allowed.
Maybe you don't care about instruction sets, emulation, drivers, performance per watt, or what kind of silicon is hiding underneath your keyboard.
You want to buy a Windows computer and assume Windows things work.
Intel- and AMD-powered PCs still give you the broadest path through the existing Windows ecosystem with the fewest architecture-specific questions to ask.
If they already provide enough battery life, enough performance, acceptable heat and noise, and the hardware you want at a price you like, choosing one isn't technologically conservative.
It may simply be rational.
Of course, if you're still reading this, we'll assume you're at least interested enough to keep investigating.
"For now" is doing a lot of work here
Almost everything in this article has an expiration date.
Focusrite added ARM drivers.
Adobe added native applications.
Game compatibility improves.
Anti-cheat systems gain ARM support.
Virtualization improves.
New form factors appear.
Intel and AMD improve their efficiency.
And new ARM competitors are coming.
If you're curious just how much is moving at once, that's the story behind The ARM's Race Is Heating Up.
The Windows-on-ARM ecosystem we're describing in 2026 is not the ecosystem that will exist forever.
That's why we wouldn't tell someone:
ARM isn't for gaming.
Or:
ARM isn't for professionals.
Or:
ARM isn't for corporate users.
Those statements are too broad today and will only become less useful.
The better question is:
Is ARM right for what you need this computer to do, with the hardware and software available now?
Sometimes the answer is yes.
Sometimes the remaining compromises are tiny compared with the benefits.
Sometimes there aren't any meaningful compromises at all.
And sometimes the battery life, efficiency, portability, cool operation, and quiet experience simply aren't valuable enough to justify even a little additional uncertainty.
That's okay.
ARM isn't the goal.
Neither is Intel.
Neither is AMD.
The goal is choosing the computer whose strengths line up with the things you actually need it to do.
Sometimes that's an ARM PC.
And sometimes an Intel- or AMD-powered PC is still the better choice.
Sources & Further Reading
[1] Microsoft Support - Windows Arm-based PCs FAQ. Discusses Windows-on-ARM compatibility limitations, including games and applications that rely on drivers such as anti-cheat components.
https://support.microsoft.com/en-us/windows/experience/platform-variants/windows-arm-based-pcs-faq
[2] Autodesk Support - Installation issues for Autodesk products on Windows running on ARM processors. Autodesk states that its covered desktop products aren't supported on Windows ARM systems and directs users to x64 hardware.
[3] Microsoft Learn - Add support for Arm devices to your Windows app. Explains x86/x64 application emulation and the requirement that kernel drivers be native ARM64; specifically notes virtualization as an area affected by this limitation.
https://learn.microsoft.com/en-us/windows/arm/add-arm-support
[4] Microsoft Learn - Frequently asked questions about support for Windows on Arm. Confirms that kernel-mode drivers must be native ARM64 and provides guidance on Windows ARM development and virtualization.
https://learn.microsoft.com/en-us/windows/arm/faq
[5] Elgato - Windows on ARM compatibility. Product-by-product compatibility guidance demonstrating that hardware, associated software, and driver-dependent functionality can have different ARM support states.
https://help.elgato.com/hc/en-us/articles/29935411773837-Windows-on-ARM-compatibility
[6] Focusrite - Compatibility with Windows on Arm. Documents Windows ARM support for Focusrite USB drivers and control software while noting remaining DAW, bundled-software, and product-specific limitations.
[7] Palo Alto Networks - GlobalProtect for ARM64-Based Windows Devices. One example of a major enterprise product providing native Windows ARM64 support, illustrating why corporate compatibility should be checked by product and required stack rather than assumed categorically.
https://docs.paloaltonetworks.com/globalprotect/release-notes/6-0/features-introduced-in-gp-app
[8] Adobe - Windows on ARM support. Tracks native and emulated support across Adobe applications and documents architecture requirements affecting applications and plugins.
https://helpx.adobe.com/x-productkb/multi/windows-arm-support.html
[9] Lenovo PSREF - ThinkCentre neo 50q QC. Specifications for a current Snapdragon X desktop, including integrated graphics and 16GB/32GB soldered LPDDR5X memory with no memory slots.
[10] Micron - LPCAMM2. Documents modular LPDDR5X memory designed to combine lower power consumption with replaceable, upgradeable memory.
https://www.micron.com/products/memory/lpddr-modules/lpcamm2
[11] Framework - Framework Laptop 13 Pro / LPCAMM2. Documents Framework's use of upgradeable LPDDR5X LPCAMM2 memory; current specifications support replaceable memory up to 96GB.
https://frame.work/laptop13pro
[12] Intel Newsroom - Intel Unlocks New Laptop Efficiency with Speed. Intel's account of developing Core Ultra 200V in response to new competition offering similar performance at substantially lower power, including its stated focus on efficiency and reduced power consumption.
https://newsroom.intel.com/client-computing/power-efficient-core-ultra-200v-series-mobile
[13] Qualcomm - Snapdragon desktops. Current Snapdragon X desktop positioning and systems, demonstrating Windows ARM's expansion beyond laptops.
https://www.qualcomm.com/snapdragon/laptops-and-tablets/desktop