Skip to main content
December 21, 2025
Answered

FIle NEF and denoise on windows on arm

  • December 21, 2025
  • 2 replies
  • 173 views

Lightroom (Cloud) and Adobe Converter on Windows on ARM are unable to read NEF files; specifically, they can neither export nor edit them. With the latest update, it is now possible to upload them to the cloud, which wasn't even working before. Furthermore, the Denoise feature on Windows on ARM—specifically on a 13-inch Surface Pro 11 with the Snapdragon [X Elite/Plus] processor—takes nearly 4 minutes!!!

To make matters worse, everything works much better on an Android tablet or even a simple smartphone.

This is absolutely ridiculous.

Correct answer Anshul_Saini

Thanks for your patience, @matteo_8161, while I checked this internally with the engineering team. I wanted to share a clear and transparent update based on their input.

Here’s what’s going on:

• Nikon High-Efficiency (compressed) NEF files are currently not supported on Windows ARM64. This is a known limitation and is documented on HelpX. Because of this, Lightroom (Cloud) and the Adobe DNG Converter are unable to fully read, edit, or export these files on Windows on ARM devices.

• Why Denoise takes ~4 minutes on Windows ARM: On Windows ARM systems, AI Denoise is currently forced to run on the CPU, not the GPU. This is due to stability and memory issues with the existing Windows on ARM GPU drivers. CPU processing is significantly slower, so the behavior you’re seeing is expected and is being actively tracked by our engineering team.

• Why phones/tablets seem faster: Mobile devices do not use the same AI Denoise engine. They rely on classic noise reduction, which is much lighter and not directly comparable.

I understand this is frustrating, especially given the hardware you’re using. I wanted to be upfront with the technical reasons rather than speculate.

If you’d like to help give this more visibility, I strongly encourage you to upvote and share your experience in this existing community thread. The more feedback and upvotes it gets, the more it helps with prioritization:

https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/p-win-arm-snapdragon-reports-nef-as-an-invalid-file-in-add-photos/td-p/14767580

Thanks again for taking the time to report this and for your patience as Windows-on-ARM support continues to evolve.

Best regards,
Anshul Saini

2 replies

Anshul_Saini
Community Manager
Anshul_SainiCommunity ManagerCorrect answer
Community Manager
December 23, 2025

Thanks for your patience, @matteo_8161, while I checked this internally with the engineering team. I wanted to share a clear and transparent update based on their input.

Here’s what’s going on:

• Nikon High-Efficiency (compressed) NEF files are currently not supported on Windows ARM64. This is a known limitation and is documented on HelpX. Because of this, Lightroom (Cloud) and the Adobe DNG Converter are unable to fully read, edit, or export these files on Windows on ARM devices.

• Why Denoise takes ~4 minutes on Windows ARM: On Windows ARM systems, AI Denoise is currently forced to run on the CPU, not the GPU. This is due to stability and memory issues with the existing Windows on ARM GPU drivers. CPU processing is significantly slower, so the behavior you’re seeing is expected and is being actively tracked by our engineering team.

• Why phones/tablets seem faster: Mobile devices do not use the same AI Denoise engine. They rely on classic noise reduction, which is much lighter and not directly comparable.

I understand this is frustrating, especially given the hardware you’re using. I wanted to be upfront with the technical reasons rather than speculate.

If you’d like to help give this more visibility, I strongly encourage you to upvote and share your experience in this existing community thread. The more feedback and upvotes it gets, the more it helps with prioritization:

https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/p-win-arm-snapdragon-reports-nef-as-an-invalid-file-in-add-photos/td-p/14767580

Thanks again for taking the time to report this and for your patience as Windows-on-ARM support continues to evolve.

Best regards,
Anshul Saini

December 21, 2025

*I should specify that I am using a Nikon Z8, which only uses compressed NEF files

Anshul_Saini
Community Manager
Community Manager
December 23, 2025

Hi @matteo_8161,

 

Thanks for calling this out and for the extra context about using a Nikon Z8 with compressed NEF files on Windows on ARM.

This behavior is well-documented and explains what you’re seeing.
Nikon High-Efficiency raw compression modes are not supported on:
– Windows ARM64
– ARMv7 and x86 for Android

The long Denoise times you mentioned on Snapdragon systems are consistent with current ARM performance characteristics for AI workloads. While things are improving, parity with Intel/M-series systems is not there yet.

We’re tracking this with the product team. If you’re able to:
• Share a sample compressed NEF from your Z8
• Share any error messages or screenshots

That helps us validate current behavior against the latest builds and track progress more accurately.

Best regards,
Anshul Saini