First distinguish a menu that is not running from a menu that opens through a different mouse or keyboard action. Test the settings shortcut, the Controls mapping, and a built-in style before reinstalling or deleting configuration data.
What to do
- Open Settings for Open-Shell Menu from the installed shortcuts. If that opens, record the version and save the current settings to XML.
- Try the Start button and Windows key separately. Inspect Controls so you know which action should open Open-Shell and which should open the Windows menu.
- Use a supplied menu style without an imported skin or custom button. Temporarily test without another Start-menu replacement controlling the same input.
- If the installed shortcut is missing or setup appears incomplete, use the matching installer maintenance options. Keep your backup and record any error message rather than repeatedly rerunning setup.
Check the result
Launch an app from the menu and repeat the activation test after signing in again. Record whether the failure concerns startup, keyboard input, the mouse button, or all three.
Limits & precautions
An Explorer restart can close windows and interrupt work; save work before troubleshooting the desktop session. Do not force-delete shell-extension files or disable Windows security protections.
Questions & answers
Does a working settings dialog mean the menu must work?
No. It shows that the settings component can start; activation and runtime behavior still need testing.
Should I reset settings first?
Export them first. Test a small change or built-in style before a full reset.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.