After a Windows update, record the new build and test Open-Shell before restoring a large custom configuration. Distinguish a menu that will not start from a compatibility task, a changed Explorer component, or a custom resource that no longer looks correct.
What to do
- Before a planned feature update, export settings and keep custom assets plus your current installer version. Preserve a way to reach standard Windows Start.
- After updating, run winver and note the new build. Launch the menu with a supplied style and test app search and a local folder.
- Read the Open-Shell release notes for changes relevant to that build. Do not install the highest-numbered preview solely because Windows changed.
- When the project upgrade task is relevant in a managed environment, have an authorized administrator review the documented procedure instead of suppressing repeated elevation prompts.
Check the result
Check sign-in startup, mouse and keyboard activation, and Explorer behavior separately. Report the precise failing action and whether it happens without custom skins.
Limits & precautions
Compatibility statements are not a promise for every future Windows update. Avoid disabling Windows security updates as a permanent workaround for a shell customization problem.
Questions & answers
Should I reset everything after an OS update?
No. First record the new build and test the existing configuration against a minimal baseline.
Does the website test every Windows release?
No. These are documentation-led checks, not a certification across all Windows builds.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.