Before updating Open-Shell, export the existing settings and read the target release notes. Keep a record of the installed version and Windows build. Checking that the layout survives is a separate step from checking that the installer completed.
What to do
- Open the settings dialog and export an XML backup. Copy custom skins and Start button images to a safe folder without changing their original filenames.
- Review the release channel and version number. The project latest-stable link and the newest chronological pre-release may point to different builds.
- Close open configuration dialogs and run the chosen project installer. Follow restart instructions when requested; do not repeatedly launch setup while a previous instance is active.
- After signing in, compare your menu style, pinned items, keyboard controls, and custom assets with the backup notes. Import an XML file only when a setting genuinely needs restoring.
Check the result
Open the settings About information or installed-app entry to confirm the version. Test the same frequently used shortcuts as before the update, not just the visual appearance.
Limits & precautions
A settings export is not a complete rollback of program binaries or Windows changes. Keep the prior installer and a recovery plan when evaluating a preview release.
Questions & answers
Is the highest version number always stable?
No. GitHub labels pre-release builds separately; check the release badge.
Should I reset settings after every update?
No. First test the existing configuration and reset only to isolate a reproducible problem.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.