Open-Shell Menu and ExplorerPatcher address different portions of the Windows shell. Open-Shell provides classic Start-menu styles and optional Explorer components; ExplorerPatcher documents a broader set of shell behavior changes. Do not assume that combining them is automatically required or compatible.
What to do
- Identify whether the unmet requirement concerns Start, the taskbar, or File Explorer. Compare that requirement with each project’s current feature documentation.
- Read compatibility notes for your exact Windows build and record the installed versions of all shell tools. A configuration that worked on another build is not proof for yours.
- Export settings and test one change at a time. Keep Windows recovery and the normal menu accessible before experimenting with a combination.
- When an issue appears, reproduce it with a single tool and supplied defaults. Report the minimal failing configuration to the relevant project.
Check the result
Test the specific shell action that motivated the change, then sign in again and repeat it. Check for duplicate controls, unexpected input handling, or Explorer instability.
Limits & precautions
This page does not recommend a universal tool stack or supply unsupported compatibility patches. Changes to Windows internals can require project updates as Windows evolves.
Questions & answers
Is ExplorerPatcher another name for Open-Shell?
No. They are separate projects with different scope and components.
Should everyone install both?
No. Start with the smallest supported configuration that meets the actual requirement.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.