![]() There are three types of settings that can be applied to each application: compatibility mode, display settings, and privilege level. The name of the string is the path to the file and the data is specific to the desired compatibility setting(s): Note that if settings are written to the HKLM (all users) location, users cannot change the affected settings in the file properties GUI unless they are an administrator.įor each item that has custom compatibility settings, a string is made. The registry key differs depending on if the setting applies to an individual user or to all users.įor an individual user: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layersįor all users: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers It is actually the same location used to store application-level display and privilege level settings too ( more on that in a moment). I learned that these compatibility entries are written in a straightforward fashion to the Windows Registry. I needed to find a way to do this from the command line. Ironically the installed application itself ran fine in Win 10 without being in compatibility mode, but the installer wouldn’t. While recently designing an SCCM application, I ran into an issue where an EXE installer had to be executed in Windows 7 compatibility mode while running on Windows 10. ![]() Successfully Tested On: Windows 7 Enterprise SP1, Windows 8 Enterprise, Windows 8.1 Enterprise, Windows 10 Enterprise versions 1507 - 2004, Windows 10 Long-Term Servicing Branch (LTSB) versions 1507 & 1607, Windows 10 Long-Term Servicing Channel (LTSC) version 1809 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |