Choose your language

Choose your login

Support

How can we help?

PaperCut's AI-generated content is continually improving, but it may still contain errors. Please verify as needed.

Lightbulb icon
Lightbulb icon

Here’s your answer

Sources:

* PaperCut is constantly working to improve the accuracy and quality of our AI-generated content. However, there may still be errors or inaccuracies, we appreciate your understanding and encourage verification when needed.

Lightbulb icon

Oops!

We currently don’t have an answer for this and our teams are working on resolving the issue. If you still need help,
User reading a resource

Popular resources

Conversation bubbles

Contact us

ARM64 printing guide

How PaperCut solves the ARM64 printing problem

The complete guide to ARM64 printing, including why ARM64 devices don’t seem to print properly and how to fix it.

Solving ARM64 printing

ARM64 and the new PC era

Windows 10 computers hold a [https://www.techpowerup.com/338670/windows-11-finally-overtakes-windows-10-as-the-most-dominant-operating-system]( 5% share) of today’s global market, equating to approximately 600 million computers. So when end-of-life for Windows 10 occurred in October 2025, it sparked a massive hardware refresh across the globe, marking the emergence of a new era for PCs. These new PCs feature an ARM64 chip that enables longer battery life, reduces heat generation, and improves performance.

The initial wave of Microsoft’s CoPilot+ devices (launched in 2024) were primarily powered by ARM64 chips (there are now options for newer chip releases from Intel for x64 architecture), which use Microsoft’s AI SDK and are built for advanced, on-device artificial intelligence. The advantages of “multi-day battery life” and “on-device AI” for personalized learning that these ARM64 devices offer are starting to transform schools and institutions, and form part of Snapdragon’s strategy for growth in Education over the coming year.

The impact of ARM64 on printing

The printer driver landscape is changing — traditional manufacturer drivers are incompatible with the new ARM64 architecture, and Microsoft is moving to a modern driverless print stack that eliminates the complexity of proprietary drivers.

Printer manufacturers are adapting to the change, and PaperCut has met with almost all of them. We found that some are preparing specific ARM64 printer drivers for their existing printers, whilst others are focused on Windows Protected Print (WPP) and Printer Support Apps (PSAs) for the next generation of printing.

Also, some of the printer manufacturers that are producing ARM64 drivers to unblock printing for users do not plan to offer ARM64 drivers for their older printer models. They are instead working towards driverless solutions with Printer Support Apps (PSAs).

SysAdmins need to be aware that with the rollout of ARM64 computers and a mixture of available ARM64-compatible and non-compatible printer drivers, printing for end-users could be a problem that they need to solve now.

Why ARM64 breaks printing today

At the core, x64 and ARM64 are completely different processor designs. Although you can use emulation software (Prism) to enable most x64-based applications to run successfully on ARM64 computers, it doesn’t enable printer drivers to work. That’s mainly because Prism is designed to only translate and run user-mode code, which doesn’t include the majority of printer drivers.

All of this means companies and educational institutions with plans to roll out the new wave of ARM64 consumer hardware, or who already have users with ARM64 laptops, will struggle to use their existing printers to print.

The Windows Server challenge

Many organizations still rely heavily on server-hosted print queues. The primary hurdle in these environments is ensuring seamless connectivity for users printing from ARM64 devices to these traditional x64 server environments. Review PaperCuts recommendations to optimize ARM64 printing for your Windows environment.

PaperCut's solution: one queue, any architecture

PaperCut makes printing work with ARM64.

Both our cloud-based PaperCut Hive and PaperCut Pocket Print Queue Deployment solution, and our on-premise PaperCut NG and MF Print Deploy solution, offer a simple way to deploy a printer driver that works on ARM64 computers.

The PaperCut server simply identifies the end-user client’s architecture and automatically deploys and installs a compatible printer driver. The System Administrator then uses the admin console to manage printer driver compatibility across different client architectures, which avoids manual administrative workarounds.

This solution provides SysAdmins with a seamless printer driver deployment experience when administering a mixed fleet of end-user computer architectures.

End-users don’t need to know the details about their computer; they simply receive the right printer driver, wherever they are located, so they can print.

No ARM64 driver - no problem

If you have end-users working on ARM64 computers and a printer fleet where an ARM64 printer driver is unavailable, keeping users printing is as easy as selecting PaperCut’s built-in Global Printer Driver in the admin console. Your organization can continue to use the existing printer fleet, even after rolling out new ARM64 laptops.

PaperCut’s Global Print Driver is compatible with most printers and compatible on x64 and ARM64 architectures across our product portfolio. For complex finishing options such as booklet finishing and advanced tray selection, the best option is the driver from your manufacturer. However when that driver is not available, our Global driver still enables the finishing capabilities and compatibility most users require every day.

For more information on ARM64 and PaperCut’s product portfolio, take a look at Windows ARM64 Support across the PaperCut portfolio.

Future-proof your printing: from legacy to modern

Whilst manufacturers are making the shift toward the modern print stack changes introduced from Microsoft, adoption is still in its infancy and many manufacturers are already starting to release Print Support Apps in preparation for this change. Eventually, the modern printing future will emerge — focused on IPP printing and the simplicity of driverless printing, which offers enhanced security through reduced complexity and attack surface.

In the meantime, however, printer drivers will be around for a little longer, and the immediate need is for ARM64 printing to work. PaperCut has already solved this and equipped customers for the transition. For customers adopting PaperCut solutions today, the good news is that PaperCut has plans to ensure that as this shift becomes the standard, we provide seamless compatibility between the legacy driver world and the new modern print stack.

The ultimate enabler for IT admins and MSPs

The ARM64 hardware refresh is one of the biggest market shifts in years, and printing has been a key perceived blocker for adoption. This is where PaperCut transforms from a print management solution into a critical print enabler.

For our partners and IT teams, you now have the “unlock” you need to confidently deploy new ARM64 computers to your users and customers.

PaperCut MF's Print Deploy ARM64 solution

PaperCut’s MF Print Deploy ARM64 solution is available now. Please monitor the official release notes for the most up-to-date information and version details.

FAQ

Why is printing on Microsoft Surface laptops and other modern ARM64 devices a challenge?

The emergence of a new PC era, highlighted by devices like the initial wave of Microsoft's CoPilot+ computers, brings powerful ARM64 chips to the market. However, this architecture completely breaks traditional printing because standard x64 printer drivers are incompatible with ARM64 designs. Even with emulation software, which only translates user-mode code, most traditional printer drivers simply will not function.

How does the ARM64 transition contribute to legacy fleet challenges?

While manufacturers are adapting, many do not plan to offer manufacturer / native ARM64 drivers for their older printer models. This creates significant legacy fleet challenges for IT admins who are rolling out new ARM64 computers but still need end-users to print to existing, older printers.

What is the industry doing to solve this? (WPP, PSAs, and Driverless Printing)

Microsoft is actively moving toward a modern driverless printing stack that eliminates the complexities of proprietary drivers. To bridge the gap, manufacturers are focusing on developing Windows Protected Print (WPP) solutions and Print Support Apps (PSAs) for the next generation of printing rather than just patching old drivers.

How does PaperCut handle everyday printing on ARM64 laptops?

PaperCut serves as a critical print enabler by utilizing a "one queue, any architecture" approach. Whether you use PaperCut Hive, Pocket, NG, or MF, the server automatically identifies the user's architecture and deploys the correct compatible driver. PaperCut's Global Print Driver works across both x64 and ARM64 architectures, making everyday printing on ARM64 laptops seamless for the end user.

What about advanced printing (stapling and hole punching etc) on ARM64 laptops?

For complex requirements—like booklet finishing or advanced tray selection—the best option is still to use the manufacturer / native ARM64 drivers if they are available. However, when those drivers aren't an option, PaperCut’s Global Print Driver still successfully manages the finishing capabilities necessary for the everyday printing needs of end users.

What are the best practices / recommendations for ARM64 printing?

The primary recommendation is to avoid manual administrative workarounds. IT admins and MSPs should use deployment solutions like PaperCut MF’s Print Deploy or PaperCut Hive to automatically manage driver compatibility across mixed environments. This approach future-proofs your infrastructure, smoothly handling both non-compatible legacy fleets and the modern shift toward Windows Protected Print (WPP) and Print Support Apps (PSAs).

My Windows Print Server won't let me upload ARM64 drivers. How do I fix the "Missing Windows Media" error?

Traditional x64 Windows Servers don't natively contain the ARM64 system files (like ntprint.inf) required to share these drivers. To unblock this, you can copy the ntprint.inf folder from an ARM64 laptop to your server’s driver store. This allows your legacy server to "speak" ARM64 and host the drivers your new fleet needs.

Should I use Print Server queues or Direct Print for my ARM64 rollout?

While PaperCut supports both, Direct Print via Print Deploy is the most reliable way to bypass the "driver gap." It allows the driver to be installed locally on the laptop, avoiding the architectural limitations and "Point and Print" errors often found when connecting ARM64 clients to legacy x64 print servers.

Does PaperCut's ARM64 support work for offline or remote printing?

Yes. PaperCut Print Deploy installs the architecture-specific driver locally on the workstation during the initial connection, the user can continue to print normally even if they are offline or disconnected from the server.

Further reading