-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing context menu while RMB on windows icon. #3843
Comments
Your issue description sounds like the issue that I reported with #3844. I'd recommend checking if KB5045935 has been installed via Windows Update and if yes either rolling back to a recent System Restore Point or trying to uninstall KB5045935 then rebooting. I'd also recommend disabling "Get the latest updates as soon as they're available" in Settings app>Windows Update if you have that enabled. |
please check if you have the latest pre-release installed: https://github.com/valinet/ExplorerPatcher/releases |
@cpresco: I wish, but this appears to not be the case. @pyrates999 I've just installed it succesfully but it changed nothing. EDIT: Disabling .net also didn't help. |
Then please wait for a developer to respond. |
@kamykson I highly recommend enabling System Restore Points in Windows 11 if you don't have that enabled. I understand that won't help you in this specific situation but in the future having a System Restore Point available to roll back to can be invaluable when trying to recover from something that has stopped functioning especially after a Windows Update has been installed. |
Duplicate of #3837 |
Hello.
I'm used to using rmb on start/windows button on taskbar. Normally it shows context menu with shortcuts. I have windows 11 23h2 and EP up to date. Since couple of days RMB doesn't work. I didn't change anything in windows nor EP. When I started troubleshooting this problem, I noticed that the problem disappears when taskbar style is set to default (win11 style) while I normally use win 10 style. Is it a bug or new stupid feature?
The text was updated successfully, but these errors were encountered: