Program Compatibility/Emulation Settings on Windows for ARM

Theresias · 16th August 2021, 20:18

Anybody aware of a way to change the emulation settings, for a specific shortcut on Windows for ARM, similar to what is described on the following MS page? I am trying to implement a workaround for customers, as long as there is no permanent fix on the application side.

https://docs.microsoft.com/en-us/win...troubleshooter

Anders · 16th August 2021, 21:30

\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags in the registry maybe? Probably in the Layers subkey. If not, search the registry for the .exe name.

I doubt it is stored in the shortcut itself but to be sure you could compare a before and after file with fc.exe.

Theresias · 17th August 2021, 21:59

Good call! This revealed an undocumented parameter (neither Google, nor Bing show a result). The Layers subkey contained "ARM64CHPEDISABLED" which should be it.

Thank you! Much appreciated.

16th August 2021, 20:18	#1
Theresias Member Join Date: Jun 2006 Posts: 50	Program Compatibility/Emulation Settings on Windows for ARM Anybody aware of a way to change the emulation settings, for a specific shortcut on Windows for ARM, similar to what is described on the following MS page? I am trying to implement a workaround for customers, as long as there is no permanent fix on the application side. https://docs.microsoft.com/en-us/win...troubleshooter

16th August 2021, 21:30	#2
Anders Moderator Join Date: Jun 2002 Location: ${NSISDIR} Posts: 5,484	\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags in the registry maybe? Probably in the Layers subkey. If not, search the registry for the .exe name. I doubt it is stored in the shortcut itself but to be sure you could compare a before and after file with fc.exe. IntOp $PostCount $PostCount + 1

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

17th August 2021, 21:59	#3
Theresias Member Join Date: Jun 2006 Posts: 50	Good call! This revealed an undocumented parameter (neither Google, nor Bing show a result). The Layers subkey contained "ARM64CHPEDISABLED" which should be it. Thank you! Much appreciated.