Powertoys: PT Run not running

[carlosmatioli]

Environment

Windows build number: Microsoft Windows [versão 10.0.18363.900]
PowerToys version: 0.19.2
PowerToy module for which you are reporting the bug (if applicable): PT Run

Steps to reproduce

Set any shortcut
Hit Shortcut

Expected behavior

PT Run should open and working fine

Actual behavior

The first time I used the PT Run after v 0.19.1 it worked just fine. But since yesterday (July 16th), it doesn't open, it doesn't matter wich Shortcut combination I use. Even ater I updated to 0.19.2, still doesn't work.
Ps: I'm not running it in Admin mode (my company network does not allow it).

Screenshots

[Luis1988]

Also not working on the same version here.

[saahmedm]

question, is the app in focus when PT doesn't show up running elevated or as admin? Or this doesn't launch even with no apps in the foreground / in focus

[carlosmatioli]

I tried in many scenarios. With another program window on focus, with no program in focus, with all windows minimized, right after initialization, with PowerToys Settings window open... Nothing works. The process doesn't even starts.

Ps.: I'm not and won't be running PT Run with admin privileges (is not allowed in my company IT system)

[Luis1988]

question, is the app in focus when PT doesn't show up running elevated or as admin? Or this doesn't launch even with no apps in the foreground / in focus

I also tried with and without focus on apps, I have administration rights and the PT don't show up

[shaul75]

Same problem. Though it stopped working for me even before updating to 0.19.2, I actually thought this update might fix it.

[sisibeloved]

Same problem. When I install back 0.19.0, all come to normal.

[saint4eva]

same problem here.

[saint4eva]

same problem here.

Restarted my system, and it is now working.

[zeeshanali1993]

same here not working tried as an admin, changes shortcut, used without app focus but same result.

[NenoLoje]

+1, same issue after updating PowerToys today

Update: The issue resolved itself, but I have no idea how. A few updates later (and me re-trying a few times) seemed to help.

[shwin320]

Do you get a popup message when you try to activate PowerToys Run the second time? I have a similar issue (Issue #5016), in which after PowerToys Run works the first time, each time afterward I try to activate it with a shortcut, I get a message, saying "You'll need a new app to open this ms-gamingoverlay link".

[carlosmatioli]

Do you get a popup message when you try to activate PowerToys Run the second time? I have a similar issue (Issue #5016), in which after PowerToys Run works the first time, each time afterward I try to activate it with a shortcut, I get a message, saying "You'll need a new app to open this ms-gamingoverlay link".

I don't even get any message. It simply doesn't open.

[AlexHunterCodes]

Yeah, I'm getting the same issue on 0.19.2. Running as non-admin, doesn't matter what is bound as the Run shortcut. It opens the normal Alt-Space shortcut if that is bound, or doing nothing if something else is bound. Run isn't glitching out like the Start Menu bug, it's like Run isn't being triggered at all.

[jefe340]

I am running it as admin and it does not work.
It worked fine when I installed it but when updating to version 0.19.2 it stopped working

[arjunbalgovind]

• Can you check task manager if the PowerLauncher process is running when you are trying to press the shortcut?
  
• Can you share the PT Run settings file (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\settings.json), and the log file for it (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs).
• To validate that the issue isn't specific to Alt+Space, can you try setting it to a couple of shortcuts like Win+Space, Ctrl+Space or Win+A?
• Do you have any keys remapped in Keyboard Manager such as Alt?
• Can you try disabling and re-enabling PT Run?

[jefe340]

I have tried other shortcuts and it did not work.
I also do not have any keys remapped in Keyboard Manager

EDITED by PT team for brevity and attached log as txt file:
userlog_jefe340.txt

[arjunbalgovind]

• Can you check task manager if the PowerLauncher process is running when you are trying to press the shortcut?
  
• Can you share the PT Run settings file (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\settings.json), and the log file for it (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs).
• To validate that the issue isn't specific to Alt+Space, can you try setting it to a couple of shortcuts like Win+Space, Ctrl+Space or Win+A?
• Do you have any keys remapped in Keyboard Manager such as Alt?
• Can you try disabling and re-enabling PT Run?

@carlosmatioli @Luis1988 @shaul75 @sisibeloved @zeeshanali1993 @AndrewAlexMac @jefe340 along with the above questions can you also check if running the PowerToys Run executable directly works? This can be done by opening C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe, and then try pressing the shortcut that you have set (such as Alt+Space).

[jefe340]

When I run PowerLauncher.exe it shows up in task manager and then
disappears.
This is what shows in Event Viewer
[image: image.png]
[image: image.png]
[image: image.png]

On Tue, Jul 21, 2020 at 7:01 PM Arjun Balgovind [e-mail]
wrote:

>

• Can you check task manager if the PowerLauncher process is running
  when you are trying to press the shortcut?
  [image: image]
  https://user-images.githubusercontent.com/32061677/88110809-ae043900-cb61-11ea-9b72-0e90cf0f04a6.png
• Can you share the PT Run settings file (can be found at
  C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys
  Run\settings.json), and the log file for it (can be found at
  C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs).
• To validate that the issue isn't specific to Alt+Space, can you try
  setting it to a couple of shortcuts like Win+Space, Ctrl+Space or Win+A?
• Do you have any keys remapped in Keyboard Manager such as Alt?
• Can you try disabling and re-enabling PT Run?

@carlosmatioli https://github.com/carlosmatioli @Luis1988
https://github.com/Luis1988 @shaul75 https://github.com/shaul75
@sisibeloved https://github.com/sisibeloved @zeeshanali1993
https://github.com/zeeshanali1993 @AndrewAlexMac
https://github.com/AndrewAlexMac @jefe340 https://github.com/jefe340
along with the above questions can you also check if running the PowerToys
Run executable directly works? This can be done by opening C:\Program
Files\PowerToys\modules\launcher\PowerLauncher.exe, and then try pressing
the shortcut that you have set (such as Alt+Space).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/5055#issuecomment-662149543,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKYXBWTX6HP5L7QHUESGALR4YM57ANCNFSM4O6GJCKA
.

[arjunbalgovind]

@jefe340 the images you have attached in this reply and the previous reply are not visible since you are replying by mail. Can you attach them directly in a reply in GitHub?

[jefe340]

On Tue, Jul 21, 2020 at 7:07 PM Jeffrey Damaso [e-mail]
wrote:

When I run PowerLauncher.exe it shows up in task manager and then
disappears.
This is what shows in Event Viewer
[image: image.png]
[image: image.png]
[image: image.png]

On Tue, Jul 21, 2020 at 7:01 PM Arjun Balgovind [e-mail]
wrote:

>

• Can you check task manager if the PowerLauncher process is
  running when you are trying to press the shortcut?
  [image: image]
  https://user-images.githubusercontent.com/32061677/88110809-ae043900-cb61-11ea-9b72-0e90cf0f04a6.png
• Can you share the PT Run settings file (can be found at
  C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys
  Run\settings.json), and the log file for it (can be found at
  C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs).
• To validate that the issue isn't specific to Alt+Space, can you try
  setting it to a couple of shortcuts like Win+Space, Ctrl+Space or Win+A?
• Do you have any keys remapped in Keyboard Manager such as Alt?
• Can you try disabling and re-enabling PT Run?

@carlosmatioli https://github.com/carlosmatioli @Luis1988
https://github.com/Luis1988 @shaul75 https://github.com/shaul75
@sisibeloved https://github.com/sisibeloved @zeeshanali1993
https://github.com/zeeshanali1993 @AndrewAlexMac
https://github.com/AndrewAlexMac @jefe340 https://github.com/jefe340
along with the above questions can you also check if running the PowerToys
Run executable directly works? This can be done by opening C:\Program
Files\PowerToys\modules\launcher\PowerLauncher.exe, and then try
pressing the shortcut that you have set (such as Alt+Space).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/5055#issuecomment-662149543,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKYXBWTX6HP5L7QHUESGALR4YM57ANCNFSM4O6GJCKA
.

Faulting application name: PowerLauncher.exe, version: 0.19.2.0, time stamp: 0x5e222541
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007fff4af0e162
Faulting process id: 0x38e8
Faulting application start time: 0x01d65fb33ec568d9
Faulting application path: C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe
Faulting module path: unknown
Report Id: 84eb67a9-d0fe-4c90-8f9c-d8c869538d7c
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: PowerLauncher.exe, version: 0.19.2.0, time stamp: 0x5e222541
Faulting module name: KERNELBASE.dll, version: 10.0.18362.959, time stamp: 0x7b90c1b5
Exception code: 0xe0434352
Fault offset: 0x000000000003a799
Faulting process id: 0x38e8
Faulting application start time: 0x01d65fb33ec568d9
Faulting application path: C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 700d382d-7714-4bc5-9787-6db51bddae10
Faulting package full name:
Faulting package-relative application ID:

Application: PowerLauncher.exe
CoreCLR Version: 4.700.20.20201
.NET Core Version: 3.1.4
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException: Provide value on 'System.Windows.Baml2006.TypeConverterMarkupExtension' threw an exception.
---> System.IO.IOException: Cannot locate resource 'images/app_error.png'.
at MS.Internal.AppModel.ResourcePart.GetStreamCore(FileMode mode, FileAccess access)
at System.IO.Packaging.PackagePart.GetStream(FileMode mode, FileAccess access)
at MS.Internal.IO.Packaging.PackagePartExtensions.GetSeekableStream(PackagePart packPart, FileMode mode, FileAccess access)
at System.IO.Packaging.PackWebResponse.CachedResponse.GetResponseStream()
at System.IO.Packaging.PackWebResponse.GetResponseStream()
at System.IO.Packaging.PackWebResponse.get_ContentType()
at System.Windows.Media.Imaging.BitmapDecoder.SetupDecoderFromUriOrStream(Uri uri, Stream stream, BitmapCacheOption cacheOption, Guid& clsId, Boolean& isOriginalWritable, Stream& uriStream, UnmanagedMemoryStream& unmanagedMemoryStream, SafeFileHandle& safeFilehandle)
at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy, Boolean insertInDecoderCache)
at System.Windows.Media.Imaging.BitmapFrame.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy)
at System.Windows.Media.ImageSourceConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at System.Windows.Baml2006.TypeConverterMarkupExtension.ProvideValue(IServiceProvider serviceProvider)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(MarkupExtension me, IServiceProvider serviceProvider)
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
at Wox.ReportWindow.InitializeComponent()
at Wox.ReportWindow..ctor(Exception exception)
at Wox.Helper.ErrorReporting.Report(Exception e)
at Wox.Helper.ErrorReporting.DispatcherUnhandledException(Object sender, DispatcherUnhandledExceptionEventArgs e)
at System.Windows.Threading.Dispatcher.CatchException(Exception e)
at System.Windows.Threading.Dispatcher.CatchExceptionStatic(Object source, Exception e)
at System.Windows.Threading.ExceptionWrapper.CatchException(Object source, Exception e, Delegate catchHandler)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run()
at PowerLauncher.App.Main(String[] args)

Faulting application name: PowerLauncher.exe, version: 0.19.2.0, time stamp: 0x5e222541
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007fff4aede172
Faulting process id: 0x2964
Faulting application start time: 0x01d65fb33887094f
Faulting application path: C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe
Faulting module path: unknown
Report Id: 8fb435c8-d767-43f6-8663-d86a4cbb8839
Faulting package full name:
Faulting package-relative application ID:

[jefe340]

EventViewer_PowerToys.txt

[kingp0dd]

I opened an issue at
https://github.com/microsoft/PowerToys/issues/4914#event-3573567443

Just want to report that PT Run is now running fine without the issues I described.
PT v0.19.2 Not Run as Admin

[Luis1988]

• Can you check task manager if the PowerLauncher process is running when you are trying to press the shortcut?
  
• Can you share the PT Run settings file (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\settings.json), and the log file for it (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs).
• To validate that the issue isn't specific to Alt+Space, can you try setting it to a couple of shortcuts like Win+Space, Ctrl+Space or Win+A?
• Do you have any keys remapped in Keyboard Manager such as Alt?
• Can you try disabling and re-enabling PT Run?

@carlosmatioli @Luis1988 @shaul75 @sisibeloved @zeeshanali1993 @AndrewAlexMac @jefe340 along with the above questions can you also check if running the PowerToys Run executable directly works? This can be done by opening C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe, and then try pressing the shortcut that you have set (such as Alt+Space).

I tried to execute PowerLauncher.exe directly and it shows up and disappears at the Task List Manager. At the log file, there is an error.
2020-07-22.txt

[jefe340]

Same thing happens with me

On Wed, Jul 22, 2020 at 2:30 AM Luis1988 [e-mail] wrote:

>

• Can you check task manager if the PowerLauncher process is running
  when you are trying to press the shortcut?
  [image: image]
  https://user-images.githubusercontent.com/32061677/88110809-ae043900-cb61-11ea-9b72-0e90cf0f04a6.png
• Can you share the PT Run settings file (can be found at
  C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys
  Run\settings.json), and the log file for it (can be found at
  C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs).
• To validate that the issue isn't specific to Alt+Space, can you try
  setting it to a couple of shortcuts like Win+Space, Ctrl+Space or Win+A?
• Do you have any keys remapped in Keyboard Manager such as Alt?
• Can you try disabling and re-enabling PT Run?

@carlosmatioli https://github.com/carlosmatioli @Luis1988
https://github.com/Luis1988 @shaul75 https://github.com/shaul75
@sisibeloved https://github.com/sisibeloved @zeeshanali1993
https://github.com/zeeshanali1993 @AndrewAlexMac
https://github.com/AndrewAlexMac @jefe340 https://github.com/jefe340
along with the above questions can you also check if running the PowerToys
Run executable directly works? This can be done by opening C:\Program
Files\PowerToys\modules\launcher\PowerLauncher.exe, and then try pressing
the shortcut that you have set (such as Alt+Space).

I tried to execute PowerLauncher.exe directly and it shows up and
disappears at the Task List Manager. At the log file, there is an error.
2020-07-22.txt
https://github.com/microsoft/PowerToys/files/4958240/2020-07-22.txt

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/5055#issuecomment-662269215,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKYXBRYOCQ4RD36FOKALM3R42BP7ANCNFSM4O6GJCKA
.

[carlosmatioli]

Can you check task manager if the PowerLauncher process is running when you are trying to press the shortcut?

I checked this before openning the issue, and it doesn't open or run any process.

Can you share the PT Run settings file (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\settings.json), and the log file for it (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs).

See .zip attached. PowerToys Run.zip

To validate that the issue isn't specific to Alt+Space, can you try setting it to a couple of shortcuts like Win+Space, Ctrl+Space or Win+A?

Also tried with many shortcuts, and none worked.

Do you have any keys remapped in Keyboard Manager such as Alt?

No key or keyboard shortcut remaped

Can you try disabling and re-enabling PT Run

When I disable and re-enable the PT Run, the Launcher process starts, stay for a while open, and then closes. In the mean time, I try to use the shortcut, but PT Run don't open.

@carlosmatioli @Luis1988 @shaul75 @sisibeloved @zeeshanali1993 @AndrewAlexMac @jefe340 along with the above questions can you also check if running the PowerToys Run executable directly works? This can be done by opening C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe, and then try pressing the shortcut that you have set (such as Alt+Space).

I also tried this before openning the issue and today, and also didn't work.

[alekhyareddy28]

@carlosmatioli, @Luis1988, can you please go to this folder (C:\Users\USERNAME\AppData\Local\Microsoft\PowerToys\PowerToys Run\Cache) and see if there are any txt files (eg: Image_version.txt, Pinyin_version.txt, Win32_version.txt etc). If so can you please share the contents of those files?

Also, can you try to delete the Cache folder and see if it works?

[Luis1988]

@carlosmatioli, @Luis1988, can you please go to this folder (C:\Users\USERNAME\AppData\Local\Microsoft\PowerToys\PowerToys Run\Cache) and see if there are any txt files (eg: Image_version.txt, Pinyin_version.txt, Win32_version.txt etc). If so can you please share the contents of those files?

Also, can you try to delete the Cache folder and see if it works?

Only one file has content and it's Pinyin_version.txt with "v0.19.2".

After that, I try to delete the file, and in the Cache folder I just have:

With the same content in the previous file.

I am gonna try if I can reinstall PowerToys

[Luis1988]

Hello again, I tried to reinstall the program deleting the folder C:\Users\USERNAME\AppData\Local\Microsoft and C:\Program Files\PowerToys after uninstalling and it worked the tool.

[carlosmatioli]

@carlosmatioli, @Luis1988, can you please go to this folder (C:\Users\USERNAME\AppData\Local\Microsoft\PowerToys\PowerToys Run\Cache) and see if there are any txt files (eg: Image_version.txt, Pinyin_version.txt, Win32_version.txt etc). If so can you please share the contents of those files?
Also, can you try to delete the Cache folder and see if it works?

I deleted the Cache folder, started the app by clicking in the PowerLauncher.exe, and it didn't opened also.
I attached both Cache before and after the Cache folder clear, for analysis.
Cache_AfterClear.zip
Cache_BeforeClear.zip

[carlosmatioli]

Hello again, I tried to reinstall the program deleting the folder C:\Users\USERNAME\AppData\Local\Microsoft and C:\Program Files\PowerToys after uninstalling and it worked the tool.

@alekhyareddy28, I tried the sugestion mentioned above by @Luis1988, and it worked for me. I restarted the Windows, changed the keyboard shortcut to Win +Z, and for now is working fine.
Of course is not the definitive solution, but for now solves my problem. My only fear is that the problem happens again in the future.
_Ps. 1: Any customization done in the FancyZones or other modules of PT will be lost._

_Ps. 2: Lt me know if I can or should close the issue_

Thanks for everyone that contributed with the diagnosis and solution.

[alekhyareddy28]

@carlosmatioli, @Luis1988, can you please go to this folder (C:\Users\USERNAME\AppData\Local\Microsoft\PowerToys\PowerToys Run\Cache) and see if there are any txt files (eg: Image_version.txt, Pinyin_version.txt, Win32_version.txt etc). If so can you please share the contents of those files?
Also, can you try to delete the Cache folder and see if it works?

Only one file has content and it's Pinyin_version.txt with "v0.19.2".

After that, I try to delete the file, and in the Cache folder I just have:

With the same content in the previous file.

I am gonna try if I can reinstall PowerToys

Just to clarify @Luis1988, the other _version.txt files were empty?
And deleting the Cache folder did not fix your issue?

[alekhyareddy28]

@carlosmatioli, can you please take a look at your Event Viewer log and see if there are any crashes logged against PowerLauncher? You might have to scroll down as you said it's working fine now. Thanks.

And then go to Windows logs (on the left) followed by Application. That should give you the list of errors as well as some information logs.

[carlosmatioli]

@carlosmatioli, can you please take a look at your Event Viewer log and see if there are any crashes logged against PowerLauncher? You might have to scroll down as you said it's working fine now. Thanks.

And then go to Windows logs (on the left) followed by Application. That should give you the list of errors as well as some information logs.

See attached two ocurrencies of the error. This is repeated man times, probably when I tried to start PTRun.

PTRun Log.zip

today, after I unninstalled and reinstalled Power Toys, no error had happenned so far.

[alekhyareddy28]

@ryanbodrug-microsoft, @crutkas, @saahmedm, I've added this to 2008 milestone. Please correct me if I'm wrong about it's priority/adding it there.

[alekhyareddy28]

Update: There was a missing img which was causing PT Run to crash. Please open a new issue if the issue still persists in the next release (0.20).

[ryanbodrug-microsoft]

Update: There was a missing img which was causing PT Run to crash. Please open a new issue if the issue still persists in the next release (0.20).

@alekhyareddy28 Based on the repro steps of the original issue. I don't think your fix addresses the same thing. Are you sure this is fixed?

[alekhyareddy28]

Update: There was a missing img which was causing PT Run to crash. Please open a new issue if the issue still persists in the next release (0.20).

@alekhyareddy28 Based on the repro steps of the original issue. I don't think your fix addresses the same thing. Are you sure this is fixed?

@ryanbodrug-microsoft, I asked the user who created this issue to share the event viewer log and the app_error.png missing was the reason for the crash.

You can see the event viewer log in this comment - https://github.com/microsoft/PowerToys/issues/5055#issuecomment-663205672

I could remove the resolution fix label for this issue if we want to find out what in the dispatcher thread caused that exception but I doubt we have much to go on. That's why I mentioned that they could create a new issue with that information as they would now be seeing an error reporting pop up window with more information on what exactly in the dispatcher is throwing the exception. Thoughts?

[alekhyareddy28]

This is what the user shared -

Application: PowerLauncher.exe
CoreCLR Version: 4.700.20.26901
.NET Core Version: 3.1.6
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException: O valor fornecido em 'System.Windows.Baml2006.TypeConverterMarkupExtension' iniciou uma exceção.
 ---> System.IO.IOException: Não é possível localizar o recurso 'images/app_error.png'.
   at MS.Internal.AppModel.ResourcePart.GetStreamCore(FileMode mode, FileAccess access)
   at System.IO.Packaging.PackagePart.GetStream(FileMode mode, FileAccess access)
   at MS.Internal.IO.Packaging.PackagePartExtensions.GetSeekableStream(PackagePart packPart, FileMode mode, FileAccess access)
   at System.IO.Packaging.PackWebResponse.CachedResponse.GetResponseStream()
   at System.IO.Packaging.PackWebResponse.GetResponseStream()
   at System.IO.Packaging.PackWebResponse.get_ContentType()
   at System.Windows.Media.Imaging.BitmapDecoder.SetupDecoderFromUriOrStream(Uri uri, Stream stream, BitmapCacheOption cacheOption, Guid& clsId, Boolean& isOriginalWritable, Stream& uriStream, UnmanagedMemoryStream& unmanagedMemoryStream, SafeFileHandle& safeFilehandle)
   at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy, Boolean insertInDecoderCache)
   at System.Windows.Media.Imaging.BitmapFrame.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy)
   at System.Windows.Media.ImageSourceConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
   at System.Windows.Baml2006.TypeConverterMarkupExtension.ProvideValue(IServiceProvider serviceProvider)
   at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(MarkupExtension me, IServiceProvider serviceProvider)
   --- End of inner exception stack trace ---
   at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
   at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
   at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
   at Wox.ReportWindow.InitializeComponent()
   at Wox.ReportWindow..ctor(Exception exception)
   at Wox.Helper.ErrorReporting.Report(Exception e)
   at Wox.Helper.ErrorReporting.DispatcherUnhandledException(Object sender, DispatcherUnhandledExceptionEventArgs e)
   at System.Windows.Threading.Dispatcher.CatchException(Exception e)
   at System.Windows.Threading.Dispatcher.CatchExceptionStatic(Object source, Exception e)
   at System.Windows.Threading.ExceptionWrapper.CatchException(Object source, Exception e, Delegate catchHandler)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at System.Windows.Application.Run()
   at PowerLauncher.App.Main(String[] args)

[crutkas]

seems a lot like: https://github.com/microsoft/PowerToys/issues/2820, note: 'images/app_error.png'

@alekhyareddy28 's fix would deal with the crash, but not the reason the exception was thrown in the first place. I'm wary of calling this fixed since the repro steps of this issue are on launch of Run, as opposed to shutdown or log out. The root cause of the error may still make Run unusable for the user. IMHO its okay to keep the Resolution-Fix-Committed label, but we should make sure we capture an issue for the root cause before this actually gets closed.

[alekhyareddy28]

@carlosmatioli, are you still facing this issue after upgrading to 0.20.1?

[carlosmatioli]

@carlosmatioli, are you still facing this issue after upgrading to 0.20.1?

@alekhyareddy28 , installed release 0.20.1 and all worked as expected.

[alekhyareddy28]

@carlosmatioli, are you still facing this issue after upgrading to 0.20.1?

@alekhyareddy28 , installed release 0.20.1 and all worked as expected.

Thank you for letting us know.

[zeeshanali1993]

• Can you check task manager if the PowerLauncher process is running when you are trying to press the shortcut?
  
• Can you share the PT Run settings file (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\settings.json), and the log file for it (can be found at C:\Users\UserName\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs).
• To validate that the issue isn't specific to Alt+Space, can you try setting it to a couple of shortcuts like Win+Space, Ctrl+Space or Win+A?
• Do you have any keys remapped in Keyboard Manager such as Alt?
• Can you try disabling and re-enabling PT Run?

@carlosmatioli @Luis1988 @shaul75 @sisibeloved @zeeshanali1993 @AndrewAlexMac @jefe340 along with the above questions can you also check if running the PowerToys Run executable directly works? This can be done by opening C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe, and then try pressing the shortcut that you have set (such as Alt+Space).

Done running

[AlexHunterCodes]

Just attempted these on 0.20.1 and noticed that Run is now working correctly for me, even when bound to keys which have been remapped by Keyboard Manager.

[RogerAntonio]

On the latest version, it is still not working for me so I had to add PowerLauncher.exe to Windows StartUp.
Only after doing this it starts working as intended.