MPO in Windows: How Multiplane Overlay Works and When to Disable It

Leave MPO in the Windows default state. Then Windows, DWM, the driver and the GPU can automatically select hardware planes where they are supported. Constant use of MPO is not required in this case. Temporarily disabling MPO is worth doing only to diagnose reproducible flickering, black frames, hangs or stutters. First check the configuration through GameReadyX in BoosterX and fix a known driver issue if one is found.

Status: the MPO device and the role of hardware planes are documented by Microsoft. The reading of OverlayTestMode and the disabling behavior of the value 5 are confirmed by our static check of three versions of the Windows system component. Access to the parameter was observed in previously collected traces of Windows 11 24H2 and 25H2. Performance, power consumption and physical latency on a real GPU were not measured in this study.

Short answer

MPO is a WDDM hardware planes mechanism that can reduce DWM work and send a frame to the display by a more direct path. The Windows default state leaves the system both output options, while forced disabling returns ordinary composition. Disabling MPO is worth doing only to diagnose a reproducible output problem.

What MPO is

With ordinary composition, DWM assembles window surfaces into the final desktop frame. Multiplane Overlay (MPO) allows several suitable surfaces to be sent as separate hardware planes directly to the graphics card’s display output block. Such a plane can be an application surface, video, or a DWM buffer chain (swap chain).

This does not mean that every window constantly uses a separate plane. Windows queries the capabilities of the driver and hardware, and then checks the specific combination of format, size, scaling, position, color space and other constraints. If the combination is unsuitable, the system falls back to ordinary composition.

Microsoft describes MPO as part of WDDM starting with Windows 8.1. In the modern flip model, DWM can allocate a hardware scanout plane to an application. This allows Independent Flip to be preserved even when other content appears on top of the application. Under suitable conditions, DWM performs less composition work, and the application frame is directed to the display by a more direct path.

Why Windows default is better than permanent disabling

The Windows default state leaves both MPO and ordinary composition available to the system. DWM chooses the output method for a specific frame and falls back to ordinary composition if the hardware plane is unavailable.

Forced disabling removes this option for the entire system. Possible consequences:

• the application loses the Hardware Composed: Independent Flip path;
• additional composition work returns to DWM or the GPU;
• the amount of copying, memory load and power consumption may increase;
• a windowed game or video may lose the advantage of the hardware plane;
• the result depends on the GPU, driver, display, HDR, VRR and the set of open windows.

Microsoft recommends the flip model and DirectFlip as a more efficient way to output frames. NVIDIA also states that MPO can improve performance, reduce power consumption and reduce latency in windowed games. These advantages depend on conditions and are not guaranteed on every computer.

Therefore, “leave MPO enabled” in this article means do not set a global prohibition. The actual use of a plane is still determined by Windows dynamically.

The claim being verified

We verified four claims:

1. Windows does indeed read OverlayTestMode as a graphics composition parameter.
2. The value 5 prohibits the use of MPO candidates in the versions of Windows studied.
3. Without forced configuration, the choice remains with Windows.
4. The existence of such a switch does not prove that applying it increases FPS or reduces input latency.

Scope of the study

Environment	Check	Result
Windows 10 22H2, component 10.0.19041.1949	Static check of the system component	The value 5 turns the selection of MPO candidates into a refusal
Windows 11 24H2, component 10.0.26100.863	Static check and previously collected system trace	The parameter is read; the value 5 disables the verified overlay paths
Windows 11 25H2, component 10.0.26100.7689	Static check and previously collected system trace	The parameter is read; the value 5 preserves the disabling behavior

For Windows 10 22H2 and Windows 11 26H1 there are no suitable system traces. The static check of Windows 10 does not confirm the actual execution of this code. Future builds must be checked separately.

Methodology

The study combines three independent classes of data:

• Microsoft documentation on WDDM, DXGI flip model, DirectFlip and MPO;
• a static check that the versions of Windows studied read the parameter and handle the value 5 separately;
• previously collected system traces confirming that DWM accesses the parameter in Windows 11 24H2 and 25H2.

The user-facing behavior of MPO diagnostics in GameReadyX was checked separately: the decision matrix passed 10 out of 10 selected automated tests. These tests include the default state, forced disabling, an unknown value, missing data and known old driver configurations.

No new experiment on a physical GPU was performed. A virtual GPU is not used as evidence of MPO promotion, frametime, power consumption or click-to-photon latency.

What OverlayTestMode=5 does

OverlayTestMode forcibly changes DWM behavior and is not documented by Microsoft. In the three versions of Windows studied, the value 5 prohibited the use of MPO hardware planes. On NVIDIA’s official page, separate files for disabling and restoring MPO are also available; a reboot is required after the change.

When interpreting the result, keep in mind:

• OverlayTestMode=5 changes the global composition policy, not an individual game;
• the presence or absence of the value does not show whether an MPO plane was used by a specific application at a specific moment.

Other numeric values are not a public stable Microsoft interface. Their meaning changed between the versions studied, so the Wiki does not recommend applying them as “optimization levels”.

Where similar problems were observed

Flickering or stutter by itself does not prove an MPO problem. Microsoft states that screen flickering is usually related to the display driver or an incompatible application and recommends first checking for a driver update, rollback or reinstall.

Vendor and period	Publicly described case	What follows from it
NVIDIA 461.09	NVIDIA reported MPO support starting with 461.09. With V-Sync globally off, tearing could appear in windowed applications: a separate MPO plane was output independently. NVIDIA also published files for disabling and restoring MPO.	MPO changes frame output in windowed mode. The vendor allowed temporary disabling as a workaround, but this is not grounds for disabling MPO on modern drivers.
AMD 22.11.2	The release notes list system stuttering and interface flickering when two videos are played simultaneously in Chromium, as well as problems with video, VRR and multiple displays. In 23.2.1, one of the Chromium and multiple display cases is listed among the fixed ones.	Update the driver first. AMD does not name MPO as the cause of these problems, so the effectiveness of disabling it here is not confirmed.
Intel 30.0.100.x	In a public Intel discussion, growth in DWM memory consumption, hangs and Chromium problems on old driver versions, including 30.0.100.9955, were investigated. User results differed.	The connection of these old DWM and driver problems with MPO has not been established. It is worth checking for an update or an OEM driver first. There are no grounds to disable MPO automatically.

Problem reports often combined several conditions: browser hardware acceleration, video, multiple displays with different refresh rates, VRR, HDR, a windowed game and a specific driver version. A workaround for one such configuration may not suit another.

How GameReadyX makes its decision

GameReadyX in BoosterX shows MPO diagnostics based on the available configuration:

• the current Windows default state or forced configuration;
• the Windows build;
• detected GPUs;
• graphics driver versions;
• a match with verified cases of incompatibility of old configurations.

If there is no confirmed reason for a global prohibition, GameReadyX leaves MPO in Windows default. If MPO has already been forcibly disabled without a found basis, the check offers to restore the default state. Unknown values and incomplete information are not overwritten automatically.

For old AMD and Intel configurations, GameReadyX reports a driver problem. A registry change is not offered: the primary materials confirm the symptoms but do not establish MPO as their cause. Automatic disabling is offered only for a specific old NVIDIA scenario for which the vendor published such a workaround.

GameReadyX checks a known configuration without measuring the current frametime and without detecting flickering on the screen. To confirm the cause of a symptom, after the recommendation you need to compare its reproduction with the original and the changed setting.

How to investigate a problem safely

1. Reproduce the symptom and record the exact scenario: application, window mode, display, HDR, VRR and refresh rate.
2. Launch GameReadyX in BoosterX and open the MPO diagnostics.
3. If a known old driver version is found, update it first. If the problem appeared immediately after an update, compare with the previous stable version.
4. Do not change the driver, MPO, HDR, VRR and window mode at the same time. Otherwise the cause of the improvement will remain unknown.
5. Apply temporary disabling of MPO only if GameReadyX indicates a documented workaround or the symptom reproduces consistently after ordinary diagnostics.
6. Reboot Windows and repeat the same scenario.
7. If there is no improvement, immediately restore Windows default.

The frame output method can be checked through PresentMon. The Hardware Composed: Independent Flip mode means that a hardware MPO plane has been provided to the application. An ordinary FPS counter and the registry state do not show this.

What is confirmed

• MPO is part of the Windows graphics subsystem and is supported through WDDM and the graphics driver.
• MPO allows several planes to be presented in hardware when a specific configuration is supported.
• Windows selects MPO dynamically; an enabled capability does not mean constant use.
• OverlayTestMode=5 disables MPO in the three versions of the system component studied.
• DWM accessed this parameter in the Windows 11 24H2 and 25H2 traces studied.
• Vendor documentation confirms certain old output and driver problems, as well as the existence of a workaround involving disabling MPO.
• By default, GameReadyX preserves or restores Windows default if no confirmed workaround is found.

What is not confirmed

• That disabling MPO increases FPS on an ordinary modern system.
• That disabling MPO reduces input latency or click-to-photon latency.
• That any flickering, black frame, stutter or growth in DWM memory is caused by MPO.
• That the old NVIDIA workaround applies to current AMD, Intel or NVIDIA drivers.
• That the same driver version behaves the same on different GPUs, displays and Windows builds.
• That values of OverlayTestMode other than 5 have a stable meaning between versions of Windows.

Limitations

The study has no paired runs on a physical GPU and no measurements of FPS, frametime, power or latency. The system traces confirm that the parameter is read, but do not prove the actual assignment of an MPO plane. The static check is limited to three versions of the system component.

The public AMD and Intel materials describe driver symptoms but do not establish MPO as their cause. From them one cannot conclude that disabling MPO will eliminate the problem.

The study and the tools used belong to the BoosterX developer, who provides the diagnostics and the ability to change the MPO state, so the developer has a direct interest in the results. The methodology and the limits of applicability are described above, and the conclusions can be verified against open data and the listed public sources. The negative result on performance and the recommendation to keep Windows default are stated explicitly.

BoosterX practical recommendation

The permanently recommended state: Windows default. Do not disable MPO for the sake of “FPS optimization”, reducing input lag or on the basis of someone else’s list of tweaks.

If reproducible stutters, flickering, black frames or failures with video and multiple displays appear, start with GameReadyX. Fixing or rolling back a problematic driver is preferable to a global workaround. Leave MPO disabled only when the same symptom disappears after a controlled comparison and returns after restoring default.

Restoring the state

In GameReadyX, select restoration of Windows default and reboot the computer. The forced configuration will be removed, and Windows will again be able to select hardware planes on its own.

If you changed the setting in another way, use the corresponding official restoration tool from the same vendor. Do not substitute a random number into OverlayTestMode.

Public primary sources

• MPO Support, Microsoft Learn - MPO in WDDM, capability checks and interaction with the DWM swap chain.
• For best performance, use DXGI flip model, Microsoft Learn - DirectFlip, Independent Flip and the hardware MPO plane.
• DXGI flip model, Microsoft Learn - reduction of copies and system load in the flip model.
• IDXGIOutput6::CheckHardwareCompositionSupport, Microsoft Learn - querying hardware composition capabilities.
• Troubleshoot screen flickering in Windows, Microsoft Support - primary diagnostics of the driver and an incompatible application.
• What is Multi-Plane Overlay (MPO) in Windows 11, NVIDIA - the purpose of MPO, possible effectiveness and official disable/restore files.
• V-Sync OFF Not Recommended as a Global Setting Starting with Driver Version 461.09, NVIDIA - the appearance of MPO support in 461.09 and the change in windowed presentation behavior.
• AMD Software: Adrenalin Edition 22.11.2 Release Notes, AMD - old Chromium, VRR, video and multi-display symptoms.
• AMD Software: Adrenalin Edition 23.2.1 Release Notes, AMD - the fixed Chromium multi-display case and the package version.
• Intel DWM memory investigation, Intel Community - a public investigation of an old driver branch and differing results.
• PresentMon console documentation, upstream project - interpretation of Hardware Composed: Independent Flip.

Public sources and wording verified: 2026-08-24.

Change history

• 2026-09-20: the conflict-of-interest disclaimer was strengthened to the full wording with the ownership of the study and tools.
• 2026-08-24: first publication; added the results of the internal check of Windows 10 22H2, Windows 11 24H2 and 25H2, the boundaries of vendor cases and the GameReadyX recommendation.