microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
111.27k stars 6.55k forks source link

Alt + Space not working at all [Powertoys Run doesn't launch] #3650

Closed NeoGenesis1986 closed 3 years ago

NeoGenesis1986 commented 4 years ago

Environment

Windows build number:  [Version 10.0.18362.836]
PowerToys version: v0.18.1
PowerToys: PowerToys Run

Steps to reproduce

With PowerToys installed and running, press Alt + Space from any screen.

Expected behavior

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

Actual behavior

window menu (Restore / Move / Size / Minimize / Maximize / Close) shows up in the top left corner of the focused window if the focus is on a window or nothing at all if the focus is on the desktop.

Screenshots

capture

WinkelCode commented 4 years ago

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.

NeoGenesis1986 commented 4 years ago

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.

deanso commented 4 years ago

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\launcher\PowerLauncher.exe ) manually works. I'll try reinstalling and installing powertoys.

enricogior commented 4 years ago

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

Sov3rain commented 4 years ago

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?

enricogior commented 4 years ago

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

image

Sov3rain commented 4 years ago

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

enricogior commented 4 years ago

@Sov3rain can you do a test?

Thanks.

Sov3rain commented 4 years ago

@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.

enricogior commented 4 years ago

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

pietro-tp commented 4 years ago

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.

enricogior commented 4 years ago

@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.

pietro-tp commented 4 years ago

@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.

bars949 commented 4 years ago

Same issue with Windows 10, version 1909

bars949 commented 4 years ago

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

Makishima commented 4 years ago

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

bars949 commented 4 years ago

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 commented 4 years ago

image

aboalwi commented 4 years ago

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

Sov3rain commented 4 years ago

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

Tried this too, not fixed.

SedyBenoitPeace commented 4 years ago

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

holzfuss commented 4 years ago

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.

enricogior commented 4 years ago

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!

daplon commented 4 years ago

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

gmahender commented 4 years ago

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

rholland commented 4 years ago

toggled on and off - works now

enricogior commented 4 years ago

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

crutkas commented 4 years ago

This should be fixed with 0.18.2 which was just released.

bojordan commented 4 years ago

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.

crutkas commented 4 years ago

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

daplon commented 4 years ago

@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.

damien1977 commented 4 years ago

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.

irevoire commented 4 years ago

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.

Qibbles commented 4 years ago

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.

spacedog4 commented 4 years ago

Killing the process and reopening PowerToy solved my problem

resaldir commented 4 years ago

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:

image

image

image

And yeah, it works!

image

randornot commented 4 years ago

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

Disabling Adminstrator mode fixed it for me ,too

tveyben commented 4 years ago

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

viniciuscolacino commented 4 years ago

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.

samtholiya commented 4 years ago

@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.

YaYaTurre commented 4 years ago

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

Keydex commented 4 years ago

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.

Kif-Fando commented 4 years ago

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.getContentType() 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\launcher\PowerLauncher.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\launcher\PowerLauncher.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

Kif-Fando commented 4 years ago

Rollbacked to version 0.18.2 - works good for me.

crutkas commented 4 years ago

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

crutkas commented 4 years ago

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

MyCupOfTeaOo commented 4 years ago

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

DeanNotDin commented 4 years ago

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:

crutkas commented 4 years ago

We just pushed 0.20. Please try this

humbuni commented 4 years ago

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