Windows 10 FullScreen Exclusive Optimization
Posted: 17 Jan 2019, 17:29
I hope Blur Busters guru's know what it is and what it does, because I couldn't find a good explanation about it anywhere online. It exists only for Windows 10 versions 1709-15063 (Spring Creator's Update, RS2, I think) and newer. It definitely makes activation of Exclusive Fullscreen mode quicker/snappier, but people report:
- it causes stutters
- it's an additional overlay
- it not true Fullscreen Exclusive mode
I had some issues when it was first introduced in 1709-15063 and stuck to Win10 1607 for a while, but I think MS improved it in 1809-17763 (RS5). I moved from Win10 1607-14393 LTSB to Win10 1809-17763 LTSC recently and not looking back.
I also recall Blur Busters review/explanation of G-Sync results of either FullScreen Mode or Borderless test, where input lag was reduced in Win10 1709 compared to 1607. I'll link to it if If I find it...
For those who want it disabled without having to go through every .exe compatibility mode attributes, you can use this WMI script I got from MyDigitalLife forums that auto-disables FullScreen Optimization mode for every .exe launched a single time. That means it disables FSE when you launch the same .exe the second time - https://drive.google.com/file/d/1wX08vP ... sp=sharing .
I personally do not use that script and enjoy FSE in 1809-17763, but I also eradicate Game Mode, Xbox-stuff, and most importantly get rid of Windows game detection by using NTLite to erase them (2 controlling items - Xbox component and Media Game Explorer components, NTLite free version removes them). Microsoft also has this KnownGameList.bin file that attaches itself to explorer.exe and must be removed with tricks from main Windows\GameDVR and UserName\AppData\Roaming\Microsoft\Windows\GameDVR directories. I was never able to decrypt/decipher that file.
So what do BlurBusters know about FSE? Does it relate to that GameKnownList.bin file? Does it all have any effect on G-Sync/V-Sync motion smoothness?
- it causes stutters
- it's an additional overlay
- it not true Fullscreen Exclusive mode
I had some issues when it was first introduced in 1709-15063 and stuck to Win10 1607 for a while, but I think MS improved it in 1809-17763 (RS5). I moved from Win10 1607-14393 LTSB to Win10 1809-17763 LTSC recently and not looking back.
I also recall Blur Busters review/explanation of G-Sync results of either FullScreen Mode or Borderless test, where input lag was reduced in Win10 1709 compared to 1607. I'll link to it if If I find it...
For those who want it disabled without having to go through every .exe compatibility mode attributes, you can use this WMI script I got from MyDigitalLife forums that auto-disables FullScreen Optimization mode for every .exe launched a single time. That means it disables FSE when you launch the same .exe the second time - https://drive.google.com/file/d/1wX08vP ... sp=sharing .
I personally do not use that script and enjoy FSE in 1809-17763, but I also eradicate Game Mode, Xbox-stuff, and most importantly get rid of Windows game detection by using NTLite to erase them (2 controlling items - Xbox component and Media Game Explorer components, NTLite free version removes them). Microsoft also has this KnownGameList.bin file that attaches itself to explorer.exe and must be removed with tricks from main Windows\GameDVR and UserName\AppData\Roaming\Microsoft\Windows\GameDVR directories. I was never able to decrypt/decipher that file.
So what do BlurBusters know about FSE? Does it relate to that GameKnownList.bin file? Does it all have any effect on G-Sync/V-Sync motion smoothness?