PowerToys Run Crashes when Opening Speed Launcher with Alt+Space Keyboard Shortcut

[clindsay-ol]

Microsoft PowerToys version

0.82.0.0

Installation method

PowerToys auto-update

Running as admin

No

Area(s) with issue?

PowerToys Run

Steps to reproduce

Attempt to use PowerToys Run with the Alt+Space shortcut after starting without admin privileges after updating to 0.82.0.0

✔️ Expected Behavior

PowerToys Run speed entry dialogue opens and begins parsing input

❌ Actual Behavior

Crashed, generated error message popup window which solicited the creation of this bug report.

Other Software

No clearly demonstrable link between error message and other software on system has been observed.

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• PowerToys Run crashes when typing Alt-Space (#33629), similarity score: 0.89

Closed similar issues:

• PowerToys Run (#18439), similarity score: 0.84
• Crashed PowerToys Run (#17978), similarity score: 0.83
• Crash when invoking Powertoys run (#24459), similarity score: 0.83
• PowerToys Run crashes when activated via keyboard command combinations (#25241), similarity score: 0.82

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[clindsay-ol]

Attached here is the log file that the error message requested be attached to this bug report:
2024-07-03.txt

I have also incuded my logs from yesterday, which is when I updated to version 0.82.0.0, just in case they happen to be valuable:
2024-07-02.txt

[clindsay-ol]

The error message also requested I attach the following output:

Version: 0.82.0.0
OS Version: Microsoft Windows NT 10.0.22000.0
IntPtr Length: 8
x64: True
Date: 7/3/2024 10:06:40 AM
Exception:
System.ArgumentException: Value does not fall within the expected range.
   at Wox.Plugin.Common.Win32.NativeMethods.DwmSetWindowAttribute(IntPtr hwnd, Int32 attr, UInt32& attrValue, Int32 attrSize)
   at PowerLauncher.ViewModel.MainViewModel.ToggleWox()
   at PowerLauncher.ViewModel.MainViewModel.<OnHotkey>b__147_0()
   at System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout)
   at System.Windows.Threading.Dispatcher.Invoke(Action callback)
   at PowerLauncher.ViewModel.MainViewModel.OnHotkey()
   at PowerLauncher.ViewModel.MainViewModel.ProcessHotKeyMessages(IntPtr wparam, IntPtr lparam)
   at PowerLauncher.MainWindow.ProcessWindowMessages(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 MS.Win32.HwndWrapper.WndProc(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)

[crutkas]

/dup #33504.

think we have a fix

[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!