You’re changing the properties of (size 0 bytes):
C:\Users\_name_\AppData\Local\Microsoft\WindowsApps\Microsoft.FlightSimulator_8wekyb3d8bbwe\FlightSimulator.exe
Which is different than (size ~270 MB):
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Now it could be this d.umm.y .exe of 0 bytes is a “proxy” allowing such manipulations, i.e. Windows is “exposing” this d.umm.y so that other Windows specific settings like “full screen optimizations” can still be user managed.
But it is easier to directly do it on the original .exe just to be sure:
open File Explorer and type the path above in the path field
right click on FlightSimulator.exe
change compatibility settings
Or just manually edit the registry:
I don’t know if this will work but you can try editing the registry value directly where the Application Compatibility settings are being saved.
Click Windows Start, type the following and press enter in order to open the Registry Editor:
regedit.exe
Find the full path to the .exe from this registry entry:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\FlightSimulator.exe
double click the (Default) key then copy the full path. It is the string shown in the “…
And actually it might be of no use at all:
This is a good question. I’ve been trying for some hours today and I don’t see any particular difference. I’m nearly certain it wouldn’t do anything because FS2020 is not running full screen (in the DirectX full screen point of view).
[update]
Please note Full Screen Optimization in Win10 is also designed to work with full screen borderless windows but it is possible it is not really making a difference at all with FS2020 specifically. Having said this, some of you might still find it is runn…