Unexpected error when opening link from an email

[ggrinton]

Microsoft PowerToys version

0.82.0

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

General, PowerToys Run

Steps to reproduce

I clicked on a YouTube link in an email. Mail program is Microsoft 365 Outlook.
Have only seen this once,
Cannot reproduce.

✔️ Expected Behavior

Browser window showing YouTube clip.

❌ Actual Behavior

My Chrome browser window opened correctly, showing the expected YouTube clip.
The error message window from PowerToys opened on top of it, with the window title "Something went wrong".

Log file attached. I note it contains a number of other unrelated errors.
2024-07-13.txt

Error window shows the following:
Version: 0.82.0.0 OS Version: Microsoft Windows NT 10.0.19045.0 IntPtr Length: 8 x64: True Date: 13/07/2024 3:46:00 PM 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.Shell.WindowChromeWorker._ExtendGlassFrame() at System.Windows.Shell.WindowChromeWorker._UpdateFrameState(Boolean force) at System.Windows.Shell.WindowChromeWorker._HandleDwmCompositionChanged(WM uMsg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Shell.WindowChromeWorker._WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(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)

Other Software

No response

[davidegiacometti]

/dup #31226

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!