Win10 Start-key not working

[rsBNT]

On Windows 10, Bug.N somehow disabled the start button, so when clicking the button on bottom left, nothing happens. Also when clicking the windows button on the keyboard, nothing happens.

The logfile shows:

2017-07-20 11:30:00 DEBUG[2] Manager_onShellMessage( wParam: 1, lParam: 0x909f6 ) 2017-07-20 11:30:00 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 1, aWndId: 0x10264 2017-07-20 11:30:01 DEBUG[2] Manager_onShellMessage( wParam: 2, lParam: 0x909f6 ) 2017-07-20 11:30:01 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 1, aWndId: 0x60936 2017-07-20 11:30:01 DEBUG[2] Manager_onShellMessage( wParam: 1, lParam: 0xa09f6 ) 2017-07-20 11:30:02 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 1, aWndId: 0x10264 2017-07-20 11:30:02 DEBUG[2] Manager_onShellMessage( wParam: 32772, lParam: 0x0 ) 2017-07-20 11:30:02 DEBUG[2] Manager_onShellMessage( wParam: 2, lParam: 0xa09f6 ) 2017-07-20 11:30:03 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 1, aWndId: 0x60936 2017-07-20 11:30:03 DEBUG[2] Manager_onShellMessage( wParam: 32772, lParam: 0x0 ) 2017-07-20 11:30:03 DEBUG[2] Manager_onShellMessage( wParam: 1, lParam: 0xb09f6 ) 2017-07-20 11:30:03 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 1, aWndId: 0x10264 2017-07-20 11:30:03 DEBUG[2] Manager_onShellMessage( wParam: 32772, lParam: 0x0 ) 2017-07-20 11:30:03 DEBUG[2] Manager_onShellMessage( wParam: 2, lParam: 0xb09f6 ) 2017-07-20 11:30:04 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 1, aWndId: 0x10264 2017-07-20 11:30:04 DEBUG[2] Manager_onShellMessage( wParam: 32772, lParam: 0x0 ) 2017-07-20 11:30:04 DEBUG[2] Manager_onShellMessage( wParam: 2, lParam: 0xc09f6 ) 2017-07-20 11:30:04 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 1, aWndId: 0x10264 2017-07-20 11:30:04 DEBUG[2] Manager_onShellMessage( wParam: 32772, lParam: 0x0 ) 2017-07-20 11:30:04 DEBUG[2] Manager_onShellMessage( wParam: 2, lParam: 0xd09f6 ) 2017-07-20 11:30:05 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 1, aWndId: 0x10264 2017-07-20 11:30:05 DEBUG[2] Manager_saveState 2017-07-20 11:30:05 DEBUG[2] Manager_saveState: D:\bin\bugn\data_Layout.ini 2017-07-20 11:30:05 DEBUG[2] Manager_saveState: D:\bin\bugn\data_WindowState.ini 2017-07-20 11:30:05 DEBUG[2] Manager_onShellMessage( wParam: 32772, lParam: 0x60108 ) 2017-07-20 11:30:06 DEBUG[1] Manager_applyRules: class: #32770, title: Reload, wndId: 0xf09f6, rule #: 3 2017-07-20 11:30:06 DEBUG[1] Manager_onShellMessage: Manager_monitorCount: 2, Manager_aMonitor: 1, m: 2, aWndId: 0xf09f6 2017-07-20 11:30:06 DEBUG[2] Manager_onShellMessage( wParam: 32772, lParam: 0x60108 )

Weird thing: after quitting Bug.N, the bevavior sticks, cant get the startmenu to open.

[joten]

I could not reproduce the issue using Windows 10 and the current bug.n code from GitHub (no Config.ini) with AutoHotkey 1.1.27.00 (32-bit). Which versions are you using? Do you have any Config_rule in your Config.ini?

At least logging off and in to Windows should get the Start menu back.

[akadaedalus]

I was able to reproduce this. It is not a problem with a single screen, but when I hook my laptop to multiple screens, the start key doesn't work.

The weird thing is if I configure it to show the taskbar on all displays, the start menu displays ONLY on the second screen's task bar if you click the windows icon with a mouse.

Let me know how I can help debug this. I reproduced this with an empty config.

It's also possible to get the menu back by switching the multiple display settings, e.g. from extend to duplicate and back.