You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating to build 26100/26200.7019 (KB5067036 aka the 2025-10 Preview CU for Windows 11 24H2/25H2), the default CustomBlur method no longer works properly, instead only showing clear transparency (no blur, no aero, just the color).
Title bars & window frames affected by the Override DWMAPI effect does not exhibit this issue.
Update to version 2.3.2.
Do note that at the moment this is still in beta, so do expect other issues. The fix may also require you to install the 26200 (25H2) enablement package - KB5054156.
Screenshots & Demo:
OBS_2025-10-30_17-32-43_Mica.mp4
Additional information:
OS Version Tested : 26200.7019
Software Version : 2.3.1
What other third-party software do you use:
None
Additional context:
From other related reports, it seems whatever change that caused this and similar bugs was introduced a few updates before this one, so the affected builds could range from 26x00.6972 to 26x00.7019+. Other reports with this same issue:#597, #595, #608, #609, #617, #618
Describe the bug:
After updating to build 26100/26200.7019 (KB5067036 aka the 2025-10 Preview CU for Windows 11 24H2/25H2), the default CustomBlur method no longer works properly, instead only showing clear transparency (no blur, no aero, just the color).
Title bars & window frames affected by the Override DWMAPI effect does not exhibit this issue.
To Reproduce:
Just install update KB5067036.
UPDATE - To fix:
Update to version 2.3.2.

Do note that at the moment this is still in beta, so do expect other issues. The fix may also require you to install the 26200 (25H2) enablement package - KB5054156.
Screenshots & Demo:
OBS_2025-10-30_17-32-43_Mica.mp4
Additional information:
What other third-party software do you use:
None
Additional context:
From other related reports, it seems whatever change that caused this and similar bugs was introduced a few updates before this one, so the affected builds could range from 26x00.6972 to 26x00.7019+.
Other reports with this same issue: #597, #595, #608, #609, #617, #618