Windows key opens regular Windows 10 menu instead of OpenShell menu in v4.4.170

[tomasz1986]

Describe the bug

Please forgive me if this is a known problem, but after updating OpenShell from v4.4.169 to v4.4.170, the Windows key doesn't open the OpenShell menu any more. In other words, the key opens only the regular Windows 10 menu instead. The OpenShell menu can still be opened by clicking the Windows button with a mouse.

To Reproduce
Steps to reproduce the behavior:

1. Install OpenShell v4.4.170.
2. Press the Windows key on the keyboard.
3. The regular Windows 10 menu shows up.

Expected behavior
Pressing the Windows key should open the OpenShell menu instead of the regular Windows 10 menu.

Screenshots

Version:

• Open-Shell: 4.4.170
• OS: Windows 10 21H2 (2021 LTSC)

Additional context
Uninstalling v4.4.170 and installing v4.4.169 again brings back the correct behaviour while retaining all settings. Also, with v4.4.170 installed, it doesn't matter what the Windows key is set to do in the OpenShell settings, i.e. even when set to "Nothing", the key still opens just the regular Windows 10 menu.

[muhachris297]

that can be adjusted in the settings of OpenShell. right-click on the OpenShell start button and you can go into its settings from there.

On Fri, Jun 3, 2022 at 7:59 PM tomasz1986 ***@***.***> wrote: *Describe the bug* Please forgive me if this is a known problem, but after updating OpenShell from v4.4.169 to v4.4.170, the Windows key doesn't open the OpenShell menu any more. In other words, the key opens only the regular Windows 10 menu instead. The OpenShell menu can still be opened by clicking the Windows button with a mouse. *To Reproduce* Steps to reproduce the behavior: 1. Install OpenShell v4.4.170. 2. Press the Windows key on the keyboard. 3. The regular Windows 10 menu shows up. *Expected behavior* Pressing the Windows key should open the OpenShell menu instead of the regular Windows 10 menu. *Screenshots* *Version:* - Open-Shell: 4.4.170 - OS: Windows 10 21H2 (2021 LTSC) *Additional context* Uninstalling v4.4.170 and installing v4.4.169 again brings back the correct behaviour while retaining all settings. Also, with v4.4.170 installed, it doesn't matter what the Windows key is set to do, i.e. even when set to "Nothing", the key still opens just the regular Windows 10 menu. — Reply to this email directly, view it on GitHub <#1037>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVMB2XVHHBVWPUZ5R37QOETVNKL7XANCNFSM5X2PYSIQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- [image: Image] <https://chrismuha.com> [image: Image] <https://www.facebook.com/muhachris/> [image: Image] <https://twitter.com/intent/follow?original_referer=https%3A%2F%2Fchrismuha.com%2F&ref_src=twsrc%5Etfw%7Ctwcamp%5Ebuttonembed%7Ctwterm%5Efollow%7Ctwgr%5Emuhachris&region=follow_link&screen_name=muhachris> *Muha Computer Repair* *Chris Muha | Owner | Lead Technician* [image: call] 3159425304 [image: call] 3153381919 [image: email] ***@***.*** [image: web] chrismuha.com [image: web] 140 Woodgate Dr. Boonville NY, 13309 <https://goo.gl/maps/o2tnXKMEzguABML38> *ATTN. Chris Muha ​ ​ P.O. Box 311 ​ ​ Boonville NY, 13309 <https://goo.gl/maps/o2tnXKMEzguABML38>*

[tomasz1986]

Closing the issue, as I've now tried uninstalling v4.4.169, and only then installing v4.4.170, and now the Windows key works again. Previously, the installation of v4.4.170 was an upgrade over v4.4.169, and apparently the process didn't go as intended, as the broken Windows key behaviour persisted after rebooting Windows too.

I'd like to apologise for the noise 😓.

that can be adjusted in the settings of OpenShell. right-click on the OpenShell start button and you can go into its settings from there.

Yeah, as I mentioned in the first post, those settings had zero effect.

[muhachris297]

Closing the issue, as I've now tried uninstalling v4.4.169, and only then installing v4.4.170, and now the Windows key works again. Previously, the installation of v4.4.170 was an upgrade over v4.4.169, and apparently the process didn't go as intended, as the broken Windows key behaviour persisted after rebooting Windows too.

My bad, was working at the same time. I am glad doing what you did fixed the issue. That sounds like a registry issue with the development of the program that needs to be worked out with a patch update to the program.