Participant

Answered

Adobe Acrobat - native Windows on ARM (arm64) support

Forum|Forum|2 months ago
July 24, 2026
13 replies
3071 views

At Qualcomm's annual Snapdragon Technology Summit in November of 2022 Adobe took the stage and commited to a native version of Acrobat for Windows on ARM (arm64). It’s almost four years later and I cannot find any recent updates.

What has happened with that commitment? Is it delayed? Has Adobe renegged on that commitment? I cannot find any guidance on the topic in recent years.

Correct answer Amal Jaiswal

Hi @geschinger

Thanks so much for the extra detail, that's really helpful context.

As suggested in my previous response, Acrobat and Acrobat Reader are still listed on Adobe's own Copilot+ PC compatibility page as apps that run via emulation rather than natively on Windows ARM devices like your Surface Pro 11. So you're not missing an update, there genuinely hasn't been a native arm64 build released yet, even though other Creative Cloud apps (Photoshop, Lightroom, and more recently Premiere, After Effects, Audition, and Media Encoder) have made that jump https://adobe.ly/3RgeD6c

I don't have an ETA or roadmap commitment I can share publicly for Acrobat specifically. You may share your voice on Adobe's Feature Request board for native Acrobat on Windows ARM here https://adobe.ly/4yMoQYO .The product team does track volume there, and it's separate from support tickets, so it helps make the case internally, especially from Snapdragon Elite users hitting the battery/performance cost you're describing.

A couple of things in the meantime that might help with the sluggishness:

Make sure you're on the latest Acrobat release, since emulation performance has improved in some recent updates.
If you ever see Acrobat crash or throw runtime errors (not just slowness), that's sometimes tied to a Visual C++ runtime mismatch on ARM64 machines, and Adobe has a small repair tool for that. Happy to point you to it if you run into that.

Thanks again for your patience.

~Amal

michael248

Participating Frequently

My Reader is now version 26.002.21931 and I didn’t even do anything.

https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/continuous/dccontinuousaug2026qfe2.html#dccontinuousaugtwentytwentysixqfetwo

4599459: 32-bit Adobe Acrobat and Reader is not installing on ARM devices.

michael248

Participating Frequently

Apparently this thread was being ignored, someone complained about it 4 days ago on this link

And got a reply that we have been waiting for...

S

stunning_mindsetf0a2

Participant

I have the same issue on a Win11 VM running on an Apple M4. A clean 32-bit install from Windows Store is 26.001.21662. The only update that will install is AcroRdrDCUpd2600121789_MUI.msp.

Meenakshi Negi

Community Manager

Hi stunning_mindsetf0a2,

Thank you for reaching out and reporting this.

This has been reported to the team. Once we have more information on this, we will update you.

We appreciate your patience.

Thanks,

Meenakshi

A

Awesome_Charm7782

Participant

This is a widespread issue. Like @michael248 mentioned, Windows ARM64 devices cannot be updated to the latest version of Acrobat. Leaving us stuck on a version with high severity vulnerabilities. Please advise.

P

petert28481812

Participant

One year ago the x86-64 version installed on Windows Arm just fine. Some time in the the winter it stopped working but the x86-32 version could still be installed.

Now not even that version can be installed.

There’s no mystery why everyone is switching to Canva and the alternatives. Adobe isn’t the company it thinks it is.

michael248

Participating Frequently

Patience is running thin. I’ve been using the 32bit version as per your “advice” since your non-launch of your promised support for arm64.

Today, the update for Reader update is claiming that my OS (Windows 8.1 64-bit) isn’t supported. Great job.

michael248

Participating Frequently

Both versions of 26.002.21900 updater and the 26.002.21901 full installer are showing the same errors. (32bit)

dkstrauss

Participant

ADOBE - this is ridiculous. Four years ago you committed to ARM; you already have a native version of Adobe Acrobat Pro on MacOS; and I dare say Acrobat Pro is used by far more owners, especially professionals in the law, accounting, and medical professions, than any other Adobe product. It is long past time you get with the program and release an ARM native version and stop relying on Prism as a half-baked solution.

Amal Jaiswal

Community Manager

Hi there

Please share your voice on Adobe's Feature Request board for native Acrobat on Windows ARM here https://adobe.ly/4yMoQYO .The product team does track volume there, and it's separate from support tickets, so it helps make the case internally strong.

~Amal

Amal Jaiswal

Community Manager

Hi @geschinger

Hope you're doing well and thanks for reaching out.

Before I point you in the right direction, it would help to understand your situation a bit better so I can give you the most accurate guidance:

Which device and processor are you on? (e.g. Surface Pro with Snapdragon X Elite, another Copilot+ PC, or an older ARM device?)
Which version of Acrobat are you trying to run: Acrobat Pro, Acrobat Standard, or Acrobat Reader? And are you on a subscription (Creative Cloud) or a perpetual license?
What specific behavior are you seeing? Is Acrobat not installing at all, installing but crashing, running slowly, or are you simply trying to understand whether a native build exists before you buy/upgrade?

The reason I ask is that the answer looks a bit different depending on your setup. What I can confirm right now is that only the 32-bit (x86) version of Acrobat runs on Windows ARM devices, and it does so in emulation mode, not natively. For more information, please check the help page: ARM processor support on Windows | Adobe Help Adobe

As for the 2022 Qualcomm stage commitment, as of March 2026, Adobe's Copilot+ PC compatibility page lists Acrobat and Acrobat Reader in the "runs via emulation" category, while several other Creative Cloud apps have already achieved full native ARM status. That page is the most current public source: Adobe apps compatibility with Microsoft Copilot+ PCs Adobe

I'll be raising this thread internally, but your answers above will help me determine whether this is a feature request (native ARM build) or an active bug (emulation mode not working correctly for you), which go to very different teams.

Hope this information will help

~Amal

geschingerAuthor

Participant

Hello Amal,

Surface Pro 11 with SnapDragon Elite. I use Adobe Acrobat Pro which runs a bit sluggishly via the Prism emulation and ultimately trying to get rid of apps that aren’t native to avoid the battery penalty.

Over the past few years I’ve seen Adobe release native versions of apps for arm64 like Photoshop and Lightroom but it has been silence on a native version of Acrobat since that Nov 2022 commitment.

Thanks,
Greg

Amal Jaiswal

Correct answer

Community Manager

Hi @geschinger

Thanks so much for the extra detail, that's really helpful context.

As suggested in my previous response, Acrobat and Acrobat Reader are still listed on Adobe's own Copilot+ PC compatibility page as apps that run via emulation rather than natively on Windows ARM devices like your Surface Pro 11. So you're not missing an update, there genuinely hasn't been a native arm64 build released yet, even though other Creative Cloud apps (Photoshop, Lightroom, and more recently Premiere, After Effects, Audition, and Media Encoder) have made that jump https://adobe.ly/3RgeD6c

I don't have an ETA or roadmap commitment I can share publicly for Acrobat specifically. You may share your voice on Adobe's Feature Request board for native Acrobat on Windows ARM here https://adobe.ly/4yMoQYO .The product team does track volume there, and it's separate from support tickets, so it helps make the case internally, especially from Snapdragon Elite users hitting the battery/performance cost you're describing.

A couple of things in the meantime that might help with the sluggishness:

Make sure you're on the latest Acrobat release, since emulation performance has improved in some recent updates.
If you ever see Acrobat crash or throw runtime errors (not just slowness), that's sometimes tied to a Visual C++ runtime mismatch on ARM64 machines, and Adobe has a small repair tool for that. Happy to point you to it if you run into that.

Thanks again for your patience.

~Amal

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.