Safe Mode vs Clean Boot for context menu diagnosis

Published October 2026, Windows 11 24H2 / 25H2 and Windows 10

When right-click diagnosis turns into guesswork, two Microsoft tools still earn their keep: Safe Mode and Clean Boot. They answer different questions. Safe Mode asks, “Does a minimal OS still show the bug?” Clean Boot asks, “Is a third-party service or startup app involved while Windows otherwise runs normally?”

Neither replaces ShellExView for naming the DLL. Both tell you whether you should be hunting shell extensions, drivers, or startup junk next.

What each mode proves

Important: Clean Boot does not automatically disable all shell extensions. Explorer can still load context menu DLLs in a Clean Boot session. If the menu is still slow after Clean Boot, that is a hint to use ShellExView, not proof that “Windows itself is broken.”

Primary DLL workflow: Disable shell extensions on Windows 11 and Find which shell extension is crashing Explorer.

Checklist A: before you reboot anything

Do these in a normal session if Explorer still responds:

1. Time right-click on a local file and on empty desktop (two numbers).
2. Note recent installs (GPU driver, archive tool, cloud sync, Acrobat).
3. Export ShellExView list or screenshot enabled non-Microsoft context menus (ShellExView download).
4. Check Event Viewer Application log for explorer.exe faults.
5. Pause cloud sync once and retime (quick A/B).

If you can already binary-search with ShellExView, do that before Safe Mode. Safe Mode is for instability or confirmation.

Checklist B: Safe Mode test

Enter Safe Mode (Windows 11)

1. Settings → System → Recovery → Advanced startup → Restart now.
2. Troubleshoot → Advanced options → Startup Settings → Restart.
3. Press 4 for Safe Mode or 5 for Safe Mode with Networking.

Alternatively: hold Shift while clicking Restart from the Start power menu, then follow the same Troubleshoot path.

What to test in Safe Mode

1. Right-click desktop and a local folder. Time both.
2. If the menu is fast/normal in Safe Mode but slow in normal mode, third-party code is involved (shell extension, driver, filter, startup app).
3. If the menu is still broken in Safe Mode, consider profile corruption, inbox component failure, disk errors, or policy-driven issues. Still verify, but widen scope beyond NirSoft lists.
4. Do not expect every Windows 11 compact menu feature to look identical in Safe Mode; judge delay and crash behavior, not pixel-perfect UI.

Exit Safe Mode by restarting normally (msconfig Safe Boot unchecked if you used that route).

Checklist C: Clean Boot test

1. Win + R → msconfig.
2. Services tab → check Hide all Microsoft services → Disable all.
3. Startup tab → open Task Manager → disable all startup items.
4. OK → restart.

Tests after Clean Boot

1. Retest right-click timings.
2. If lag is gone, re-enable half of the non-Microsoft services, reboot, retest (binary search on services).
3. When a service reintroduces lag, note the vendor. Then check whether that vendor also ships a shell extension; disable the Explorer handler with ShellExView even if you re-enable the service.
4. If lag remains under Clean Boot, focus on shell extensions and drivers that still load, not on Skype leftover startup entries.

Reverse Clean Boot when finished: msconfig → Normal startup, re-enable needed startup apps.

How to combine results (decision table)

ShellExView binary search after the mode tests

Once modes prove third-party involvement:

1. Hide Microsoft extensions (unless hunting OneDrive/Teams Microsoft-signed handlers).
2. Disable half of context menu handlers → Restart Explorer → test.
3. Narrow to one DLL.
4. Confirm with DLL checker.

This is faster than re-enabling 80 services one by one when the failure is clearly an Explorer menu DLL.

24H2 / 25H2 practical notes

• After Feature updates, redo a quick Safe Mode comparison only if a new lag appeared post-upgrade.
• GPU driver installers often restore desktop context menus; Clean Boot may still load those DLLs into Explorer.
• Do not stay on Clean Boot for daily work. It hides problems and breaks vendor updaters.

Minimal daily workflow (recommended)

1. Reproduce timings in normal mode.
2. ShellExView binary search if Explorer is stable.
3. Safe Mode only to confirm third-party blame when needed.
4. Clean Boot when you suspect antivirus/backup services rather than menu DLLs.
5. Return to normal configuration and keep only the final disable/service change.

For ongoing menu speed work after isolation, continue with Windows 11 context menu slow fix.

Related guides

• Disable shell extensions on Windows 11
• Windows 11 context menu slow fix
• Find which shell extension is crashing Explorer
• ShellExView download
• DLL checker