Windows 11 fullscreen optimization check is about verifying which presentation path a specific game actually uses. Windows includes legacy Fullscreen optimizations behavior and a separate Optimizations for windowed games option. Those names sound similar but do not refer to the same single global switch, and blanket advice to disable them for every title is unreliable. Check one game, one API and one display mode at a time. The steps below show where Windows exposes each option and how to compare identical scenes before keeping a change.
Distinguish fullscreen optimizations from windowed game settings
A game’s executable may expose Properties > Compatibility > Disable fullscreen optimizations, a legacy compatibility override. Windows 11 also has Settings > System > Display > Graphics > Optimizations for windowed games, which Microsoft documents for many DirectX 10/11 games running in windowed or borderless modes. The latter can use the flip presentation model and may enable modern features such as variable refresh rate or Auto HDR when supported. A DX12 game has its own presentation behavior and should not automatically be assumed to benefit from the DX10/DX11 switch.
Check what the game is doing now
- Save your existing graphics settings. Note the executable path, whether the game runs fullscreen, borderless or windowed, and the monitor’s active refresh rate in Advanced display.
- Open Settings > System > Display > Graphics. Under graphics defaults, locate Optimizations for windowed games if your Windows version exposes it. Record whether it is enabled; do not change it yet.
- Select the game in Custom options for apps or add its actual executable, choose Options, and inspect the per-app windowed optimization setting. Microsoft documents a per-app control that can override system-wide defaults; use that app entry to make a reversible comparison. Save and fully restart the game after changes.
- If evaluating the legacy executable compatibility checkbox, right-click the game’s actual
.exe, open Properties > Compatibility, and record the existing Disable fullscreen optimizations state. Some launchers start a different executable than the one in a desktop shortcut. - Capture the same gameplay route in each configuration using frame-time metrics, not just a subjective impression. Restore the baseline if any option worsens smoothness, VRR, HDR or overlays.
Understand the results
If turning off the windowed optimization worsens a DX11 game’s latency, leave the default enabled. If a title exhibits unusual capture or overlay glitches only in optimized borderless mode, a per-game exception may be appropriate. If there is no measurable difference, do not call one setting a universal latency cure. The desktop compositor, driver, graphics API and game engine all influence the output path.
Avoid misleading tests
An in-game ‘Fullscreen’ label is not proof of exclusive fullscreen presentation. Many modern titles use borderless flip-model presentation even when the UI calls the mode fullscreen. Alt-Tab speed, overlay behavior and visual continuity can offer hints, but a frame presentation trace is stronger evidence. Tools built on Windows ETW or PresentMon can characterize presentation timing; they still do not independently measure physical button-to-photon delay.
Which option to keep
For most properly working DX10/DX11 borderless titles, leave Windows 11’s documented windowed optimization on. Change one app at a time only when you have a reproducible problem and a return path. The right answer for a legacy DX9 game or an anti-cheat-constrained application may differ, so confirm API and game version before recommending a tweak.
Hold Auto HDR constant during the A/B test
Microsoft documents that Auto HDR can automatically enable Optimizations for windowed games, so an off/on A/B test is not controlled unless the HDR state stays fixed. For a DirectX 10/11 windowed or borderless game, record Auto HDR, the global and per-app settings, refresh rate and graphics API, then restart the title after each change. The feature can change the game’s presentation path to the flip model, but a title already using that path may show no measurable difference. On an HDR monitor, a change in brightness or color is a display effect, not proof of reduced button-to-photon latency. If the toggle returns to On, inspect Auto HDR before attempting risky registry edits.
Check app-level precedence before calling a system setting broken
Microsoft’s DirectX developer documentation explains that a graphics preference configured for an individual executable can take priority over the system-wide preference, and a per-app Reset returns that entry to defaults. Therefore two games can behave differently while the global Optimizations for windowed games switch is unchanged. Record the executable’s exact path and each game’s Graphics entry; test the per-app setting with Auto HDR held constant, fully restart the game, and use Reset to restore the baseline when the test is over. Do not diagnose exclusive fullscreen solely from Alt+Tab timing, nor assume the legacy executable Disable fullscreen optimizations checkbox and the DirectX 10/11 borderless flip-model toggle are the same mechanism.
Write down the settings location: In Windows 11 Settings > System > Display > Graphics, select the actual game executable, open its Options and inspect the per-app graphics preference. A per-app choice can supersede a general preference; record both before comparing fullscreen and borderless sessions. Apply a single setting change, completely exit the title and relaunch before capturing the same benchmark route.
When testing a DirectX 10/11 game’s windowed optimizations, leave the resolution, HDR state, refresh rate, FPS cap and driver constant. If the game uses a different graphics API, do not assume this particular Windows toggle is the cause of a frame-time change. A visible reduction in tearing or improved stability is a valid observation; “lower input latency” still requires a separately appropriate measurement.
Keep Windows graphics preferences and Auto HDR in the test log
For a supported DirectX 10/11 title in borderless mode, check Settings > System > Display > Graphics > Optimizations for windowed games and record the global state. Next select the game under Custom options for apps, open Options and check whether a per-app setting overrides it. Restart the game after changing the setting. Microsoft documents that Auto HDR can automatically activate windowed optimizations, so record HDR state rather than treating the two settings as independent.
Run the same scene in exclusive fullscreen and borderless with matching resolution, refresh rate, FPS cap, VRR and V-Sync. A meaningful report includes game/API, Windows build, settings screenshot, several captures and the observed frame-time distribution. If the title is native DirectX 12, do not assume the DX10/DX11 optimization toggle changed its rendering path.
Audit checklist
Record Windows build, GPU driver, graphics API, monitor Hz, game executable, per-app optimization state, Auto HDR, VRR and frame-time result. A screenshot of one toggle without this context cannot prove that a game gained FPS or reduced input lag.
