The Windows PC market appears to be in flux at the moment. With the end of support coming this month for Windows 10, companies are trying to decide whether to finally jump to Windows 11, move to another platform entirely, or maybe stick with Windows — but ditch Intel for Arm processors.

What’s an IT buyer to do?

When Microsoft first announced Copilot+ PCs last year, it focused largely on hardware based on Qualcomm’s Snapdragon X Elite processors and its neural processing unit (NPU). (The move was seen partly as a response to Apple’s shift to its own Arm-based M-series chips in Macs.)

Microsoft has long hoped to see success for Windows 11 on Arm — especially after Windows RT and Windows 8 failed to gain traction — and lined up a range of PC makers to back the shift. (It also had a workable emulator for x86 code to support legacy applications.) Apple had already shown such a shift was possible, even beneficial, for end users. 

For IT decision-makers and buyers eyeing the current landscape, the question becomes: are laptops and even desktops running on Arm truly viable options, whether they run Windows, MacOS, ChromeOS, Linux or even unseen OSes like the rumored laptop version of Android? 

Is your organization ready for a new Wild West in the PC market? Here’s a rundown of what to keep in mind in answering that. 

What do workers need?

The first question to ask is what software do your users need to run. A quick inventory of what goes onto a typical new hire’s PC will give you an answer. If it’s standard workplace fare like Microsoft 365, a web browser and links to cloud-based tools, then chances are that an Arm-based PC could work — as long as there aren’t company- or industry-specific apps to worry about. 

It’s also important to determine just how well those apps and services will run. This is particularly true for anything that relies on emulation, whether that’s an app or any drivers, libraries or other dependencies. You’ll want to test any software that is in common use. 

I should note that this isn’t like Apple’s Rosetta Stone 2, which translated older code in real time rather than using emulating processor calls and instruction sets. If something will run in emulation, test whether the functionality and any performance hit is worth a switch. You might end up deciding that Arm-based hardware is interesting, but fails to meet your corporate needs at this time. 

Beyond Windows?

Though I’m focused here on Windows, you might want to treat this exercise as a chance to consider jumping to a new platform like Mac, Linux or Chrome. 

The same kind of testing and compatibility checks apply, and the more cloud oriented you are, the better your chance of a successful migration. The more legacy software your company runs, the more of an uphill climb any platform shift would be. 

Macs are an obvious consideration, but they aren’t the only option. If you’re truly cloud- and web-based, Chromebooks, Linux-based hardware or even iPads — now that they’re  more than oversized iPhones — could be real alternatives. Even Android might be worth considering from a mobile or notebook/desktop perspective. 

Specialized software needs

As any IT pro knows, the basic software workers use is often the tip of the iceberg when it comes to support. Whether it’s video production, web/print design, scientific or medical tools, or developer needs, there are always additional solutions you have to enable, purchase and manage. 

Broadly speaking, Arm-based laptops might work fine for many organizations, even if specific users need different hardware for specialized roles. Any group that relies on special tools that run locally deserves extra consideration and involvement in buying decisions and testing. 

Security and management 

Snapdragon processors have security concerns that will differ from x86 chips, Apple Silicon or the processors in Android devices or Chromebooks. You’ll need security software that addresses those differences. Depending on your vendor, this might pose no problem at all — or it might well make adoption of Arm-based devices running Windows a no-go. You’ll need to understand what your vendors currently offer and what’s on their roadmap, and you need specifics. 

Just because a vendor supports Arm for Apple or mobile, don’t assume that also means Windows gets support. This also isn’t an area where you can rely on emulation; you’ll need security tools designed for the environment you’re considering. If those tools aren’t available, or their future development is in doubt, chose alternates — or stick to close to what you use currently. 

Device management is another factor. In theory, most PC management tools should provide at least the basics of configuration, restrictions and reporting. But you’ll probably want more than just basic tools and you’ll want to know if your MDM software is designed to support and manage Windows on Arm. 

Again, don’t treat any move to Arm as simply more Windows devices. Treat it as an entirely new platform to manage, secure and support. In many ways, that’s really what this is. 

Support for your support staff

Make make sure you can equip your IT help desk and other tech support staffers with  any new machines. Although they might look like other Windows PCs, they are different from the ground up. The processor, RAM, and GPU are going to be treated as a single unit. They will run a different variation of Windows. So, when it comes to pre-existing software and files, your tech support operation is going to need a solid understanding of what’s different and how to keep things running smoothly. 

They’ll also have to explain to users that Windows and the applications they’re used to might behave differently going forward. 

Make the jump or hold off?

I can’t tell you outright that this is the time to deploy Windows on Arm hardware or move to a new platform — that’s going to vary widely from one organization to another. But given the options now available on the Windows side of the equation — and the non-Windows alternatives — it is definitely the time to consider your roadmap without being locked in by the past.

As exciting as Arm-based laptops (and desktops) are, they might not be right for every company at the moment. Buyers might decide to hold off on any purchases for now and then revisit the situation later — after vendors have had more time to build support for them. 

Remember, Windows on Arm isn’t like Apple Silicon

While the rise of Arm hardware might look similar to the transition Apple made five years ago to Apple Silicon, the two are not the same. Microsoft doesn’t have singular control over hardware (outside of its Surface line) as Apple does. Nor does it or Qualcomm (or anyone else) control the level of integration of components outside the processor and NPU. 

As a result, any jump from Intel hardware to Arm won’t be as smooth and uniform as Apple’s shift to its own chips has been. And that alone might persuade IT teams to stick with the familiar, at least for now. There’s no need to rush through what is, let’s face it, a complex process. But at least admins have some guidance now on what to consider.