An Explorer crash while Open-Shell is installed does not prove Open-Shell caused it. Record whether the menu component or Classic Explorer is involved, identify the triggering action, and reproduce it with fewer shell customizations before submitting a report.
What to do
- Save work and record the Windows build, Open-Shell version, and the precise action that precedes the crash. Include whether it occurs in a normal folder or an application file picker.
- Export menu settings and test a supplied style. Review which installer components are enabled rather than treating Menu and Classic Explorer as one feature.
- Temporarily simplify other shell extensions or taskbar replacements using their documented settings or uninstallers. Make one reversible change at a time.
- Read the matching release notes and issue reports. Submit the smallest repeatable example, with private paths removed from logs or screenshots.
Check the result
Repeat the previously failing action several times with the minimal configuration. Restore components separately to distinguish a reproducible conflict from a one-time session failure.
Limits & precautions
Forcefully terminating Explorer can close windows and affect the desktop session. Do not delete loaded DLLs or replace Windows system files as a troubleshooting shortcut.
Questions & answers
Should I blame the menu if Explorer crashes?
No. Use a reproducible test and component isolation before attributing the cause.
Are application file dialogs the same as Explorer windows?
No. Record which interface fails because the integration and relevant fixes can differ.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.