PowerToys Run crashes due to COMException: Desktop composition is disabled
Microsoft PowerToys version
0.91.1.0
Installation method
Microsoft Store
Area(s) with issue?
PowerToys Run
Steps to reproduce
- Launch PowerToys Run on Windows 10 (build 22620.0)
- Observe crash and error message
- No user interaction possible after crash
✔️ Expected Behavior
PowerToys Run should launch normally and display the search interface, regardless of desktop composition status.
❌ Actual Behavior
System.Runtime.InteropServices.COMException (0x800705B4): [Desktop composition is disabled] at WindowsDesktop.WpfWindow.ApplyBackdrop() ...
Additional Information
No response
Other Software
No response
The following issues might be duplicates:
- #43412
- #31226
AI-generated content by genai-issue-dedup may be incorrect.
Hello @mdsabab8557-alt,
thank you for reporting the issue.
Looks like #31226, but with a different HRESULT... 0x800705B4 is WIN_32 facility + ERROR_TIMEOUT status.
@mdsabab8557-alt
Could you please provide us with the entire log? I've never seen the stack track like this.
/bugreport
I have the same issue with version 0.95.0.0
Here is the complete log file as zip 2025-11-11 - Kopie.zip
I also got this error @jiripolasek
Bug Stacktrace is :
C:\Users\t-vimathur\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs\0.93.0.0\2025-11-12.txt
IntPtr Length: 8
x64: True
Date: 11/12/2025 10:50:41 AM
Exception:
System.Runtime.InteropServices.COMException (0x80263001): {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. (0x80263001)
at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
at System.Windows.Appearance.WindowBackdropManager.UpdateGlassFrame(IntPtr hwnd, WindowBackdropType backdropType)
at System.Windows.Appearance.WindowBackdropManager.ApplyBackdrop(IntPtr hwnd, WindowBackdropType backdropType)
at System.Windows.Appearance.WindowBackdropManager.SetBackdrop(Window window, WindowBackdropType backdropType)
at System.Windows.ThemeManager.ApplyStyleOnWindow(Window window, Boolean useLightColors)
at System.Windows.ThemeManager.OnSystemThemeChanged()
at System.Windows.SystemResources.SystemThemeFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Same here @jiripolasek
Screen went black for like 40 second and looks like my display driver is all messed up after that.
C:\Users\<USERNAME>\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs\0.95.1.0\2025-11-12.txt
Version: 0.95.1.0
OS Version: Microsoft Windows NT 10.0.26200.0
IntPtr Length: 8
x64: True
Date: 12-11-2025 18:13:00
Exception:
System.Runtime.InteropServices.COMException (0x80263001): {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. (0x80263001)
at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
at System.Windows.Appearance.WindowBackdropManager.UpdateGlassFrame(IntPtr hwnd, WindowBackdropType backdropType)
at System.Windows.Appearance.WindowBackdropManager.ApplyBackdrop(IntPtr hwnd, WindowBackdropType backdropType)
at System.Windows.Appearance.WindowBackdropManager.SetBackdrop(Window window, WindowBackdropType backdropType)
at System.Windows.ThemeManager.ApplyStyleOnWindow(Window window, Boolean useLightColors)
at System.Windows.ThemeManager.OnSystemThemeChanged()
at System.Windows.SystemResources.SystemThemeFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Hello @k3b, @Grimoors, @akash1047
This issue is often caused by the graphics card or its drivers. Hopefully, the next version of PowerToys Run will handle this error more smoothly. See #31226 for more details.
The original OP had a similar issue, possibly caused by a different source or error code. I’ll keep this issue open to hear from @mdsabab8557-alt and see if it turns out to be a new problem.
Also encountered this exception today when waking up from standby. Maybe it's useful for you to have another log file, here is mine:
Happens to me only after resuming after hybernate. My error message is more like the one in this issue: https://github.com/microsoft/powertoys/issues/43441
Also the error occurs since version 0.95.x and had never been seen before that version.
Switching to another computer via VM switch causes the problem.
Also, my Teams crashes now when I turn on the camera.
[2025-11-18 12:02:17.9012] [ERROR] [P:_work\1\s\src\modules\launcher\Plugins\Microsoft.Plugin.Program\Programs\PackageWrapper.cs::58] -------------------------- Begin exception -------------------------- Message: Error status: UNKNOWN Program path: Path could not be determined Exception thrown in called method: Void <ThrowExceptionForHR>g__Throw|38_0(Int32) Possible interpretation of the error: Exception MSTeams Possible resolution: Not yet known
Exception full name : System.ArgumentException Exception message : Value does not fall within the expected range. Exception stack trace: at WinRT.ExceptionHelpers.<ThrowExceptionForHR>g__Throw|38_0(Int32 hr) at ABI.Windows.ApplicationModel.IPackageMethods.get_InstalledLocation(IObjectReference _obj) at Windows.ApplicationModel.Package.get_InstalledLocation() at Microsoft.Plugin.Program.Programs.PackageWrapper.GetWrapperFromPackage(Package package) Exception source : WinRT.Runtime Exception target site: Void <ThrowExceptionForHR>g__Throw|38_0(Int32) Exception HResult : -2147024809
Seems to be fixed since 0.96.0
Updated to the latest version. I will monitor.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.