Repair is appropriate when installed program files or components appear incomplete; it is not the first answer to every cosmetic setting problem. Establish whether the problem affects menu activation, an optional Explorer extension, or a particular customization.
What to do
- Write down the installed version, Windows build, and the action that fails. Save an XML backup before changing installation state.
- Test a built-in menu style and temporarily exit overlapping shell-customization tools. A broken third-party skin should not be mistaken for missing program files.
- Use the installer maintenance options for the installed release when available. If reinstalling is required, remove the program normally and restart when requested before installing again.
- Test a minimal configuration before importing old preferences. Reintroduce custom assets one at a time so a returned failure points to a specific setting or file.
Check the result
Open the settings dialog, launch a local app, and open Explorer. Verify the repaired component directly; a completed installer does not certify unrelated features.
Limits & precautions
A repair operation may need administrator rights. Never delete system DLLs, reset all Windows permissions, or use a third-party registry cleaner as a substitute.
Questions & answers
Should I repair a bad custom skin?
First switch to a built-in skin. Repairing binaries will not necessarily fix a custom resource file.
When should I report a bug?
Report a repeatable failure that remains with a minimal configuration, including version and Windows build.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.