PowerToys 🚀 - [Tracker] Alt + Space not working at all [Powertoys Run doesn't launch]

I had it happen a couple times that after playing a game (SWAT 4) with Nvidia's DSR feature (changing resolution to above native while game is running) at 2x native resolution, the Run window wouldn't show up until restarting PowerToys. I initially opened a separate issue for this but since I suddenly can't reproduce it I decided to close it for now and see what comes out of this issue.

martinsstuff on 25 May 2020

Restarting PowerToys doesn't help. It didn't work for me from the start. And I don't think it's a graphics card issue as I don't have one on my laptop.

NeoGenesis1986 on 25 May 2020

Same issue here, new installed powertoys to try out PowerToys Run, but searchbar not popping up when pressing Alt + Space. Tried different shortcut, restarting pc, run as admin and restarting powertoys, but no change.

From another thread:
Starting Power Launcher.exe (located in C:\Program Files\PowerToys\modules\launcherPowerLauncher.exe ) manually works.
I'll try reinstalling and installing powertoys.

deanso on 25 May 2020

@NeoGenesis1986 @deanso
open the Task Manager and check under the Details tab if the PowerLauncher.exe process is running.

enricogior on 25 May 2020

Same here. It was working fine in 0.18. I updated to 0.18.1 and now Windows Menu pops up. I tried to restart Power Toys.

PowerLauncher.exe is not running, just PowerToys.exe

EDIT: when starting PowerLauncher.exe manually, it works fine. Maybe it's an autostart problem?

Sov3rain on 25 May 2020

👍7

@Sov3rain
can you check if in the PowerToys Settings, the PowerToys Run module is ON?

enricogior on 25 May 2020

👍2

@enricogior Yes it's ON. I tried to disable/enable it but no change.

Sov3rain on 25 May 2020

@Sov3rain
can you do a test?

exit PowerToys
check in the Task Manager if PowerLauncher.exe is still running (it should)
terminate PowerLauncher.exe
restart PowerToys
if PowerLauncher.exe is not running open the Event Viewer and check under Windows Logs -> Application if there is any error related to PowerLauncher.exe

Thanks.

enricogior on 25 May 2020

🎉2

@enricogior

exit PowerToys

check in the Task Manager if PowerLauncher.exe is still running (it should)

Yes it is.

terminate PowerLauncher.exe

restart PowerToys

Power Launcher is not restarting with PowerToys.

if PowerLauncher.exe is not running open the Event Viewer and check under Windows Logs -> Application if there is any error related to PowerLauncher.exe

No error related to Power Launcher in the event viewer.

Sov3rain on 25 May 2020

👍1

@Sov3rain
I was hoping some error was present in the Event log, it would have helped.
Thank you.

enricogior on 25 May 2020

I have the same problem.
I dont know if can help but: if i have powertoys run ENABLE nothing append if i use the shortcut Alt+spacebar. When i DISABLE powertoys run and use the same shortcut searchbox appear and work well.

PietroGiustacori on 25 May 2020

@PietroGiustacori
that's interesting. Can you verify in Task Manager -> Details if PowerLauncher.exe exits when you enable it in the Settings and that it runs when you disable it?
Thanks.

enricogior on 25 May 2020

@enricogior
Sorry but i remember a thing, before i start PowerLauncher.exe by searching it in the folder PowerToys>modules>launcher and nothing append i i enable o disable Powertoys Run in Power Toys setting. If i not manually start PowerLauncher.exe nothing append.
Enable o disable PowerToys run in the settings not have any results.

PietroGiustacori on 25 May 2020

Same issue with Windows 10, version 1909

bars949 on 25 May 2020

In windows 10 alt + space these are standard hotkeys. Perhaps with the next update, the priority was increased?

bars949 on 25 May 2020

Same here, after the last update looks like PowerLauncher.exe do not start at all. If launch manually both Alt + Space or Ctrl + Space is working correct

Makishima on 25 May 2020

I found a problem with myself. It was in this thread: https://github.com/microsoft/PowerToys/issues/3456 but I did not change anything there. perhaps after rebooting the value is lost again. But by setting alt + space there, performance is restored.

bars949 on 25 May 2020

I had the same issue. Disabling Administrator mode then restarting PowerToys fixed it for me.

aboalwi on 26 May 2020

👍22 🎉4 😕1

I had the same issue. Disabling Administrator mode then restarting PowerToys fixed it for me.

Tried this too, not fixed.

Sov3rain on 26 May 2020

I found a behaviour that maybe can help devs.

I had this problem when updating PowerToys from an existing version already in place (I had 0.18 and updated to 0.18.1 on my work laptop) while on my personal one I installed straight the 0.18.1 and the keyboard shortcut is doing fine.

I fixed on the work laptop as stated in this thread with starting manually PowerLauncher.exe

So I guess that in the updating process is breaking something in terms of PowerLauncher.exe autorun.

EDIT: I forgot to mention Windows versions and it came to my mind after @holzfuss' comment.
Work Laptop (where there was the issue with update): Windows 10 v1909
Personal Laptop (no issue but installed 0.18.1 straight) Windows 10 v1903
So it may be also thanks to my Windows version

SedyBenoitPeace on 27 May 2020

I installed 0.18.1 on my Win10 v19.09, no previous version, no update.
Alt + Space doesn't do anything.
PowerLauncher.exe ist not running.

holzfuss on 28 May 2020

We made a fix for a different issue, that may also effect this issue if you are running PowerToys with administrator privileges.
If you want to test an unsigned private build, it's available here https://github.com/microsoft/PowerToys/issues/3646#issuecomment-636096648
Thank you!

enricogior on 29 May 2020

👍1

@enricogior it works !!! Now PowerLauncher.exe is running like in v0.18. Thanks !!!

daplon on 29 May 2020

👍2

@enricogior any chance to get hotfix released before v0.19 release?

gmahender on 1 Jun 2020

toggled on and off - works now

rholland on 1 Jun 2020

👍1

@gmahender
yes, we are going to release 0.18.2 with this hotfix.

enricogior on 1 Jun 2020

This should be fixed with 0.18.2 which was just released.

crutkas on 5 Jun 2020

0.18.2 release does not solve this issue for me (same for unsigned build linked above). Always running PowerToys elevated; toggled Run on/off, changed shortcuts, etc. Works fine after running PowerLauncher.exe from admin PoweShell prompt.

bojordan on 5 Jun 2020

@bojordan you May have a different bug then. Please file a new issue so we can work with you on it.

crutkas on 5 Jun 2020

👎1

@bojordan Try Reinstall 0.18.2 and remove all in folder "%localappdata%/Microsoft/PowerToys/PowerToys Run", then restart your PC.

First time I restart my PC, it takes a little time to load (imagine it was creating the folders that must be deleted). But next restart, it load fast and works.

daplon on 5 Jun 2020

👍1

bonjour à tous, confronté au même problème la solution suivante a résolu le problème.

Dans les propriétés de l'application powertoys (onglet comptabilité) j'ai décoché "exécuter en tant qu'administrateur".

cela devait faire conflit avec cette même option aussi cochée dans les paramètres de powertoys.

en espérant que cela vous aide.

damien1977 on 10 Jun 2020

I just did all the microsoft updates to get a preview build, then installed winget and then powertoys for the first time ever, and I can say it still does not works and do the exact same things as in the first message of this issue.

irevoire on 10 Jun 2020

Running 0.18.2 and having this problem too. Was working the previous version but didn't test this since I upgraded until today to realise it isn't working.
Not sure if my windows update broke it or was it something else that did.

Qibbles on 14 Jun 2020

Killing the process and reopening PowerToy solved my problem

spacedog4 on 16 Jun 2020

Add PowerLauncher.exe in startup program it works for me.
Just create shortcut from C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe and create the shortcut to desktop and then add it to shell:startup by run it from windows + R. Copy paste the shortcut from PowerLauncher.exe to the startup folder like this:

And yeah, it works!

saldiwe on 17 Jun 2020

👍2

I had the same issue. Disabling Administrator mode then restarting PowerToys fixed it for me.

Disabling Adminstrator mode fixed it for me ,too

StrangeAlways on 26 Jun 2020

😄2 👍2

Disabling Adminstrator mode fixed it for me ,too

winver => 2004 OS build 19041.329
PowerToys: v0.19.0

Steps to reproduce
Install PowerToys
Restart as administrator
Type Alt+SPACE (default shortcut)

Actual result
The active applications "windows menu" is presented
= Same as before installing PowerToys

Expected result
PowerRun gets displayed

Workaround
Disabling Adminstrator mode fixed it for me ,too

tveyben on 1 Jul 2020

I had the following problem: when I pressed the Windows key, nothing happens.
I (apparently) found a solution:
I use Kaspersky antivirus. So I changed the Application Manager to not monitor the Powertoys app.
Check if your antivirus is somehow blocking the software.

viniciuscolacino on 3 Jul 2020

@viniciuscolacino I don't have any 3rd party antivirus but then I have the same issue and disabling run as administrator makes it working for me.

samtholiya on 9 Jul 2020

Had the same problem. Disabling 'run as administrator' makes it work for me.

YaYaTurre on 13 Jul 2020

This was an issue for me on first install of powertoys non administrator mode. Toggling on and off didn't work. Once I restarted powertoys for the first time it works fine on v0.19.1. I don't think powertoys finishes initializing on first open.

Keydex on 26 Jul 2020

Windows 10 build 2004
Powertoys 0.19.2
PowerRun do not run at all. Truying admin/not admin, several keyboard shortcuts, manual run of powerlauncher.exe, reinstalling .NET packages. Everytime i get an error in windows logs.
Sometime like this:
_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
acheOption, Guid& clsId, Boolean& isOriginalWritable, Stream& uriStream, UnmanagedMemoryStream&
nmanagedMemoryStream, SafeFileHandle& safeFilehandle)
at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream,
itmapCreateOptions 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)_

Sometimes this:
_Faulting application name: PowerLauncher.exe, version: 0.19.2.0, time stamp: 0x5e222541
Faulting module name: KERNELBASE.dll, version: 10.0.19041.388, time stamp: 0x3cc24707
Exception code: 0xe0434352
Fault offset: 0x0000000000023e49
Faulting process id: 0x2360
Faulting application start time: 0x01d6642aeeb4fba1
Faulting application path: C:\Program Files\PowerToys\modules\launcherPowerLauncher.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: cb09272d-6b39-4ba1-807b-4c421a17f58c
Faulting package full name:
Faulting package-relative application ID:_

Sometimes this:
_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: 0x00007ffdaee3dd52
Faulting process id: 0x2360
Faulting application start time: 0x01d6642aeeb4fba1
Faulting application path: C:\Program Files\PowerToys\modules\launcherPowerLauncher.exe
Faulting module path: unknown
Report Id: a69df079-a29d-490a-8600-7fbb8d1ab388
Faulting package full name:
Faulting package-relative application ID:_

P.S. It was worked until update, don't remember 0.19 or 0.19.1

KifReact on 27 Jul 2020

Rollbacked to version 0.18.2 - works good for me.

KifReact on 27 Jul 2020

@alekhyareddy28 / @somil55 I know we fixed the app_error in .20, do we but that error is hiding a diff issue. then

crutkas on 27 Jul 2020

@KifReact we're days from shipping 0.20 (July 31). Please try that and if it still is broke, please file new issue

crutkas on 27 Jul 2020

Disabling Adminstrator mode fixed it for me ,too
winver => 2004 OS build 19041.329
PowerToys: v0.19.0
Steps to reproduce
Install PowerToys
Restart as administrator
Type Alt+SPACE (default shortcut)

Actual result
The active applications "windows menu" is presented
= Same as before installing PowerToys

Expected result
PowerRun gets displayed

Workaround
Disabling Adminstrator mode fixed it for me ,too

me too

MyCupOfTeaOo on 28 Jul 2020

👍1

I'm experiencing the same issue, Administrator mode didn't fix it for me.
Also, launching PowerLauncher.exe doesn't do the trick.

EventViewer log:
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: 0x00007ffdce01e172 Faulting process id: 0x30d8 Faulting application start time: 0x01d66711c9a446db Faulting application path: C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe Faulting module path: unknown Report Id: 00bf69ae-304f-4dd8-b057-28b118d1dde3 Faulting package full name: Faulting package-relative application ID:

DeanNotDin on 31 Jul 2020

We just pushed 0.20. Please try this

crutkas on 31 Jul 2020

👍2

Still not working on 0.20.0. Please let me know if there's information I can provide to help

humbuni on 31 Jul 2020

Updated to 0.20, rebooted - works for me.
Win 10 build 2004

KifReact on 31 Jul 2020

0.20.0, Windows 10 Version 1903 (Build 18362.30)

Crashes as normal user. Runs as Administrator (but runs apps as that user as well).

3 Errors in Event Log:

First:

Application: PowerLauncher.exe
CoreCLR Version: 4.700.20.26901
.NET Core Version: 3.1.6
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFC15231D5B 
(00007FFC150A0000) with exit code c0000006.

Second:

Faulting application name: PowerLauncher.exe, version: 0.20.0.0, time stamp: 0x5e222541
Faulting module name: coreclr.dll, version: 4.700.20.26901, time stamp: 0x5ec48a29
Exception code: 0xc0000006
Fault offset: 0x0000000000191d5b
Faulting process id: 0x1d2c
Faulting application start time: 0x01d667781a371984
Faulting application path: C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.6\coreclr.dll
Report Id: 91e9721c-8aed-450c-a2b1-6a75debbe2db
Faulting package full name: 
Faulting package-relative application ID:

Third:

Problem signature:
P1: PowerLauncher.exe
P2: 0.20.0.0
P3: 5e222541
P4: coreclr.dll
P5: 4.700.20.26901
P6: 5ec48a29
P7: c0000006
P8: 0000000000191d5b
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE20.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C69.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C99.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C99.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CB9.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PowerLauncher.ex_92abc6cfaad68c66716a8787d2d2cbac2ef52b30_723435b4_8c344a63-e06c-4276-8fab-894aefa357c0

Analysis symbol: 
Rechecking for solution: 0
Report Id: 91e9721c-8aed-450c-a2b1-6a75debbe2db
Report Status: 268435456
Hashed bucket: 4ec2ddfd37bd25011f4eb20c9fa137fc
Cab Guid: 0

cantpitch on 31 Jul 2020

@humbuni Can you please share the logs located %userprofile%/appdata/local/microsoft/powertoys/powertoys run/logs?

somil55 on 31 Jul 2020

Sure:

2020-07-31.txt

cantpitch on 31 Jul 2020

👍1

Here's the whole file for today: 2020-07-31.txt

humbuni on 1 Aug 2020

on 0.20, power launcher exe doesn't run. Manually running it results in the process being terminated immediately after launching. Hotkey never works.

Reinstalled, same issue. Complete clean install, same issue.

Disabling administrator for power toys finally works.

fazlee712 on 1 Aug 2020

@somil55, @cantpitch log has a ton of exceptions.

@cantpitch, looking at your logs, you're running it on a hub, correct?

System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'Timer'.
   Source: System.ComponentModel.TypeConverter
   TargetAssembly: System.ComponentModel.TypeConverter, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
   TargetModule: System.ComponentModel.TypeConverter.dll
   TargetSite: Void set_Enabled(Boolean)
   at System.Timers.Timer.set_Enabled(Boolean value)
   at System.Timers.Timer.Start()
   at PowerLauncher.MainWindow.OnVisibilityChanged(Object sender, DependencyPropertyChangedEventArgs e)
   at System.Windows.UIElement.RaiseDependencyPropertyChanged(EventPrivateKey key, DependencyPropertyChangedEventArgs args)
   at System.Windows.UIElement.OnIsVisibleChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
   at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
   at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
   at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
   at System.Windows.UIElement.UpdateIsVisibleCache()
   at System.Windows.PresentationSource.RootChanged(Visual oldRoot, Visual newRoot)
   at System.Windows.Interop.HwndSource.set_RootVisualInternal(Visual value)
   at System.Windows.Interop.HwndSource.set_RootVisual(Visual value)
   at System.Windows.Window.SetRootVisual()
   at System.Windows.Window.SetRootVisualAndUpdateSTC()
   at System.Windows.Window.SetupInitialState(Double requestedTop, Double requestedLeft, Double requestedWidth, Double requestedHeight)
   at System.Windows.Window.CreateSourceWindow(Boolean duringShow)
   at System.Windows.Window.CreateSourceWindowDuringShow()
   at System.Windows.Window.SafeCreateWindowDuringShow()
   at System.Windows.Window.ShowHelper(Object booleanBox)
   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 on 1 Aug 2020

oops, @humbuni logs are full of errors and is running on a hub.

@cantpitch your logs didn't seem to have anything, does your event viewer logs maybe have anythign?

crutkas on 1 Aug 2020

@cantpitch your logs didn't seem to have anything, does your event viewer logs maybe have anythign?

I posted my event viewer logs in https://github.com/microsoft/PowerToys/issues/3650#issuecomment-667342577

I can share the Windows Event Reporting Crash archive if you like.

cantpitch on 2 Aug 2020

Updating that 0.20 (along with turning the feature off and on and remapping the keys to something other than alt+space and then returning it to default) solved it for me!

DeanNotDin on 2 Aug 2020

@humbuni issue is fixed and it was #5400

crutkas on 5 Aug 2020

Confirmed it's fixed

humbuni on 6 Aug 2020

Seems to be broken again on current build 0.20.1

Powertoys Run does not launch with hotkey combination. Switching from non-admin mode to administrator mode makes it run once, but then it stops working again in admin or non-admin mode.

gannon345 on 8 Aug 2020

I agree - broken in 0.20.1
I have never had problems previously.
I suspect it changed with the latest updates that were applied by Windows:
KB4565483 and KB4565633

2020-08-17 15:06:14.9963|FATAL|UnHandledException|

Exception

System.Runtime.InteropServices.COMException: UCEERR_RENDERTHREADFAILURE (0x88980406)
Source: PresentationCore
TargetAssembly: PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
TargetModule: PresentationCore.dll
TargetSite: Void SyncFlush()
at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(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)

Environment

Command Line: "C:\Program Files\PowerToys\modules\launcher\PowerLauncher.dll" 11444
Timestamp: 08/17/2020 15:06:14
Wox version: 1.0.0
OS Version: Microsoft Windows NT 10.0.18363.0
IntPtr Length: 8
x64: True
CLR Version: 3.1.4
Installed .NET Framework:
- v2.0.50727 2.0.50727.4927 SP2
- v3.0 3.0.30729.4926 SP2
- v3.5 3.5.30729.4926 SP1
- v4 Client 4.8.03752
- v4 Full 4.8.03752
- v4.0 Client 4.0.0.0

ggrinton on 17 Aug 2020

I just held down windows key to see shortcuts then after that it worked 😂 I have no idea how that fixed it but it did.

Some-T on 22 Aug 2020

👍8

,me too facing same issue please help any developer here?????

Aditya753b on 7 Sep 2020

I've also had this issue for some weeks. Powertoys is updated and runs on Microsoft Windows 10 Pro
version 10.0.18363 build 18363. I have tried enabling/disabling administrator mode, restarting Powertoys, whatnot. No dice, whatsoever. Powerlauncher.exe is running. Changing the shortcut to e.g. CTRL + Space doesn't do anything either.

lelas on 9 Sep 2020

Just did a clean install of v0.21.1 and Run, FancyZones, and Color Picker do not function on boot. Manually running PowerLauncher.exe causes the run feature to begin functioning and manually running ColorPicker.exe causes that feature to begin functioning. FancyZones will not work, even after opening the zone editor.

FileExplorerPreview works fine out of the gate, so does the shortcut guide. I have enabled and disabled administrator mode, keyboard manager, and each feature without success. Win 10 Pro 2004 19041.508 USA English on a Dell Precision something or other laptop.

CapinWinky on 10 Sep 2020

@CapinWinky are you running PT as admin?

crutkas on 11 Sep 2020

Facing same issue. I cannot alt + space when on Chrome. However when I minimise Chrome, PT Run works?

When minimising Chrome

EDIT: Has been now working in Chrome after a restart of laptop.

zamanmh1 on 17 Sep 2020

I can confirm I am having the same issues as outlined above.

Environment
Windows build number: 10.0.19041.488 (WinBuild.160101.0800)
PowerToys version: v0.23.0
PowerToys: PowerToys Run

Steps to reproduce
With PowerToys installed and running, press Alt + Space from any screen. Including desktop with no apps running.

Expected behavior
PowerToys Run popup shows up to start typing a command or a search term

Actual behavior
Nothing happens at all

NapAlot on 7 Oct 2020

Is the app in focus admin where PT is not?

crutkas on 9 Oct 2020

Also, is PowerLauncher.exe running? (check the Task Manager's Details tab)

enricogior on 9 Oct 2020

Reporting my personal experience: I've first installed as of v0.23.2. Running as administrator. Haven't been able to get it to work at all. PowerLauncher.exe is running (holding ~100MB of RAM). Initially after installing, the shortcut key would show the context menu similar to @zamanmh1, but minimizing chrome didn't effect it. After a reboot, Alt+Space now seems to do nothing.

^

I wrote the above, and got distracted and went and got coffee. When I came back, PowerLauncher's memory usage had gone up by about 50MB, and now it _works_. I'm stumped.

nitz on 9 Oct 2020

@nitz How long did you give it to initialize before you tried the keystrokes? The querying of all the apps and icon indexing takes a few seconds.

crutkas on 10 Oct 2020

@crutkas before the reboot, at least 20 minutes. I spent plenty of time playing with a few of the other tools before I circled back to the launcher.

After the reboot? Well I tried a couple of times right after boot, as well as while I was writing my initial reply there. I was definitely confused because the ram usage wasn't changing at all, not even a KB. Then I went and made a cup of coffee, so the k-cup machine took what 3 minutes? Then when I sat back down it was working. 🙃

nitz on 10 Oct 2020

Seems to be working now as of the 0.23.2 update.

On Fri, Oct 9, 2020 at 11:29 PM Chris Dailey notifications@github.com
wrote:

@crutkas https://github.com/crutkas before the reboot, at least 20
minutes. I spent plenty of time playing with a few of the other tools
before I circled back to the launcher.

After the reboot? Well I tried a couple of times right after boot, as well
as while I was writing my initial reply there. I was definitely confused
because the ram usage wasn't changing at all, not even a KB. Then I went
and made a cup of coffee, so the k-cup machine took what 3 minutes? Then
when I sat back down it was working. 🙃

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/3650#issuecomment-706491335,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6GHFB5FAOWGSVWQGNFKFDSJ7WMFANCNFSM4NI3SURQ
.

gannon345 on 10 Oct 2020

👎1

Here's an interesting one: PowerLauncher.exe and PowerToys are running. ALT+Space does nothing. I exit PowerToys. ALT+Space starts working (as in, launching the Run input window). I re-launch PowerToys - ALT+Space stops working again. This is with 0.23.2.

EranBoudjnah on 12 Oct 2020

@EranBoudjnah

I exit PowerToys. ALT+Space starts working

When exiting PT, PowerToys.exe and PowerLauncher.exe are not running anymore. It should be impossible for Alt + Space to open PT Run.
Are you sure you are exiting PowerToys or are you just closing the Settings app window?

enricogior on 17 Oct 2020

@EranBoudjnah

I exit PowerToys. ALT+Space starts working

When exiting PT, PowerToys.exe and PowerLauncher.exe are not running anymore. It should be impossible for Alt + Space to open PT Run.
Are you sure you are exiting PowerToys or are you just closing the Settings app window?

100% certain. Right clicked the tray icon and clicked Exit. Launched PowerToys again and it stopped working.
After a reboot both live happily together again, by the way.

EranBoudjnah on 17 Oct 2020

@EranBoudjnah
are you running 0.23.2?
We had a bug that was causing PowerLauncher.exe to take 10 seconds before exiting, so in case of quitting PowerToys and restarting it right away it was causing a race condition and prevent PT Run to work.

In 0.23.2 you should see these two processes quit almost istantly when you quit PowerToys

Then, if you restart PowerToys after the two processes have exited, you should see them appear again and PT Run should work (it may take a few seconds for PT Run to reacted to ALT + Space since it may still initializing, we have a fix in the progress for that)

enricogior on 21 Oct 2020

@EranBoudjnah
are you running 0.23.2?
We had a bug that was causing PowerLauncher.exe to take 10 seconds before exiting, so in case of quitting PowerToys and restarting it right away it was causing a race condition and prevent PT Run to work.

In 0.23.2 you should see these two processes quit almost istantly when you quit PowerToys

Then, if you restart PowerToys after the two processes have exited, you should see them appear again and PT Run should work (it may take a few seconds for PT Run to reacted to ALT + Space since it may still initializing, we have a fix in the progress for that)

Thanks @enricogior - I am running 0.23.2. I'm afraid I can't offer much useful feedback at this point, though, since the reported behavior stopped after rebooting... Unfortunately, there was definitely an issue on 0.23.2 (right after upgrading to it, in fact) up until rebooting.

EranBoudjnah on 21 Oct 2020

@EranBoudjnah
OK, good to know it's not reproducing anymore. We have some fixes for 0.25, hopefully they will remove the original problem.

enricogior on 21 Oct 2020

👍2

This is why I changed it to Win+Q because that does the same thing as Win+S and if PT Run is not active, you still have a search function.

Jay-o-Way on 25 Oct 2020

Powertoys: [Tracker] Alt + Space not working at all [Powertoys Run doesn't launch]

Environment

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

Most helpful comment

All 84 comments

Exception

Environment

Related issues