{"id":9491,"date":"2025-10-14T19:07:13","date_gmt":"2025-10-14T19:07:13","guid":{"rendered":"https:\/\/pokecon.jp\/job\/?p=9491"},"modified":"2025-10-14T19:07:13","modified_gmt":"2025-10-14T19:07:13","slug":"fix-windows-11-24h2-rendering-and-freezing-issues-in-chromium-apps","status":"publish","type":"post","link":"https:\/\/pokecon.jp\/job\/9491\/","title":{"rendered":"Fix Windows 11 24H2 rendering and freezing issues in Chromium apps"},"content":{"rendered":"\n<\/p>\n
\n

The Windows 11 24H2<\/a> update has introduced significant enhancements, but for some users, it has also brought frustrating rendering and freezing issues, particularly with Chromium-based applications such as Discord, Visual Studio Code, and Google Chrome.<\/p>\n

These problems often manifest when alt-tabbing out of games, causing partial interface updates, frozen sections, or glitches that temporarily resolve when switching windows. This guide provides a clear, effective solution to these issues, drawing from a detailed Reddit post by user Maliwolf<\/a>, without resorting to workarounds like disabling hardware acceleration that can slow down performance.<\/p>\n

<\/svg><\/a>Understanding the Issue<\/h3>\n

After updating to Windows 11 24H2, many users have reported that Chromium-based apps exhibit rendering issues, such as partial freezing or glitching, especially when switching between a game and these applications. For example, scrolling through a Discord chat might update only a portion of the screen, leaving the rest frozen. In rare cases, the display updates solely around the mouse cursor. These issues, often described as “tearing” or “glitching,” have persisted for approximately seven months for early adopters of the update, affecting both AMD and NVIDIA hardware users.<\/p>\n

The root cause lies in the interaction between Microsoft\u2019s Desktop Window Manager (DWM) and Multiplane Overlay (MPO). MPO is a feature that reduces latency in borderless windowed gaming, but its dynamic switching between flip presentation models\u2014specifically, \u201cComposed: Flip\u201d and \u201cHardware Composed: Independent Flip\u201d\u2014can disrupt rendering in low-frame-rate applications like Discord. This back-and-forth behavior causes the observed freezing and rendering inconsistencies. Notably, applications like Firefox, which do not appear in tools like PresentMon, are unaffected, highlighting the issue\u2019s specificity to Chromium-based apps and certain Windows components.<\/p>\n

<\/svg><\/a>Why Common Workarounds Fail<\/h3>\n

Several workarounds have been suggested, but they come with significant drawbacks. Disabling hardware acceleration forces software rendering, which is inefficient and can slow down performance, an unacceptable compromise in 2025. Disabling MPO eliminates the latency benefits of borderless windowed mode, impacting gaming performance. Another suggestion, forcing the ANGLE backend to an alternative like OpenGL, is complex and not universally effective. These solutions fail to address the core issue within DWM\u2019s handling of MPO, making a more targeted fix necessary.<\/p>\n

<\/svg><\/a>The Solution<\/h3>\n

Fortunately, a straightforward registry adjustment can resolve these rendering and freezing issues without compromising performance. This fix, detailed in the Reddit post, involves setting the OverlayMinFPS<\/code> registry key to zero, which disables DWM\u2019s minimum frame rate requirement for assigning overlay planes. This ensures that low-frame-rate applications like Discord and Visual Studio Code remain in the \u201cHardware Composed: Independent Flip\u201d mode, stabilizing their rendering.<\/p>\n

Step-by-Step Guide to Apply the Fix<\/h4>\n
    \n
  1. \n

    Verify MPO Status (Optional)<\/strong>
    \nBefore proceeding, confirm that MPO is enabled on your system, as it is typically active by default. To check:<\/p>\n