PowerToys Run throws NullReferenceException (UWPApplication.Launch) when launching “Settings” on Windows 11 24H2 (26100)

[GustavAkaMeGusta]

Microsoft PowerToys version

Version: 0.91.1.0

Installation method

PowerToys auto-update

Area(s) with issue?

PowerToys Run, Settings

Steps to reproduce

1. Start PowerToys.
2. Invoke PowerToys Run with the keyboard shortcut (Ctrl + Space for me).
3. Type: settings
4. Press Enter.

✔️ Expected Behavior

The “Settings” window for PowerToys opens.

❌ Actual Behavior

PowerToys Run crashes immediately and a Windows dialog shows a
System.NullReferenceException from Microsoft.Plugin.Program.Programs.UWPApplication.Launch().

Additional Information

Version: 0.91.1.0
OS Version: Microsoft Windows NT 10.0.26100.0
IntPtr Length: 8
x64: True
Date: 18.06.2025 22:51:53
Exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Plugin.Program.Programs.UWPApplication.<>c__DisplayClass64_0.b__0()
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Microsoft.Plugin.Program.Programs.UWPApplication.Launch(IPublicAPI api, String queryArguments)
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
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

[cinnamon-msft]

/dup #39090

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