Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| The Start button ignores clicks but the Windows key works | Check pointer input, overlays and taskbar customisation |
| Start opens but freezes or closes | Restart Explorer and remove conflicting shell tools |
| Start fails only in one account | Test that profile and its per-user startup software |
| Start and Settings both fail after an update | Install corrections, then repair Windows components |
Diagnose start menu repair before resetting Windows
Start depends on shared shell components, but this guide should stay narrow. Compare Start with Search and the taskbar; if those still respond, prioritize Start-specific registration, profile state, and shell extensions.
Press the Windows key to test whether Start opens without clicking the button. If the key works but the Start button does not, check pointer input, taskbar overlays, and shell customisation before repairing Start packages.
Record when the problem began and what changed immediately beforehand: a Windows update, display-driver change, new theme, Start-menu replacement, taskbar tweaker, debloat script, security utility, work policy or monitor reconnection. “The Start button ignores clicks but the Windows key works” suggests check pointer input, overlays and taskbar customisation, while “Start opens but freezes or closes” points toward restart explorer and remove conflicting shell tools. That timing is stronger evidence than a generic event-log warning.
Restart Windows Explorer once from Task Manager, then press the Windows key again. If Start immediately returns, investigate extensions or shell state instead of repeatedly re-registering apps.
Test Start in a new local account. If it works there, focus on the original profile's Start cache, per-user settings, or shell utilities; if it fails everywhere, move to system-wide repair.
“Start fails only in one account” means test that profile and its per-user startup software, while “Start and Settings both fail after an update” means install corrections, then repair windows components. Change one layer at a time and retest the same action. Avoid third-party registry cleaners, Start-menu repair packs and commands that re-register every Windows app without a verified reason; broad changes create fresh failures and erase the evidence that identifies the original cause.
If Start stopped working after a Windows update, install any newer corrective update first. On managed PCs, Start layout and app visibility can be controlled by policy, so record the build and contact the administrator instead of bypassing restrictions.
Restart the shell and remove simple conflicts
Save work, open Task Manager, select Windows Explorer and choose Restart. Then press the Windows key and click Start separately. Disconnect extra docks or monitors for one test and close overlays, screen recorders and shell replacements that can intercept the taskbar.
Open Settings with Windows + I, install pending Windows updates and restart from the Power menu. If Start broke immediately after a Start-menu replacement, taskbar patcher or debloat utility, disable or uninstall that exact tool before applying system-wide repairs.
1Test built-in access paths
- Press the Windows key.
- Press Ctrl + Esc as a second Start shortcut.
- Use Windows + I to confirm Settings can open independently.
2Check the Start configuration
- Open Settings > Personalization > Start.
- Change one ordinary Start option and retest.
- Avoid registry policies copied from another Windows build.
Separate profile damage from Windows-wide damage
Create a temporary local account and test Start there. If it works, review the original account's startup apps, shell customisers and recent profile changes. Back up that profile before any migration; do not delete it merely because the test account succeeds.
If Start fails for every account, run DISM /Online /Cleanup-Image /RestoreHealth in an elevated terminal, then sfc /scannow. Allow both to finish and restart. These commands repair protected Windows components; they do not repair unsupported shell modifications.
Use recovery only when timing proves it
Use System Restore when a suitable restore point exists from before the failure and the problem began after a system change. If a recent quality update is clearly responsible, check Windows release health and install any newer correction before considering uninstalling it.
An in-place repair install is a later option when Start, Settings and other shell components fail across accounts after DISM and SFC. Back up files and recovery keys first. Reset this PC is not the opening move for one broken Start menu.
Verify the repair before making more changes
Test Start opens, lists apps, launches a pinned item and closes normally three ways: with the pointer, with the documented keyboard shortcut and again after a full Restart. Confirm the feature still works after opening several apps and, when relevant, after disconnecting and reconnecting an external display.
Re-enable any shell enhancement, startup utility, or policy change used only for testing. Keep the one change that explains why Start recovered and reverse the rest.
Technical order checked against Microsoft's current Start menu guidance. Device-specific menus and driver availability vary by manufacturer.
Frequently asked questions
Why does the Windows key open Start but clicking does not?
The Start feature is running; pointer input, an overlay or taskbar customisation is the more likely boundary.
Will restarting Windows Explorer close my apps?
Most apps stay open, but the desktop and taskbar disappear briefly and File Explorer windows may close.
Should I reinstall Windows for a broken Start menu?
No. Test Explorer, updates, shell tools, another profile and system-file repair first.