An XML export should be a readable settings file saved to a location your account can access. A failed import may be a damaged file, the wrong file type, or references to resources that are no longer present. Keep the current configuration before experimenting.
What to do
- Create a fresh export to a normal local folder through Backup > Save to XML File. Give it a distinctive filename and confirm it is not an empty file.
- Keep the original backup unchanged. Inspect a copy with a text editor to check that it contains XML rather than a downloaded web page or an error message.
- Use Backup > Load from XML File with an export from a known Open-Shell installation. Restore custom skins, button images, and paths separately.
- When only part of the layout returns, compare the menu style and resource locations instead of repeatedly loading the same file. Record source and destination program versions.
Check the result
Export the restored configuration to a new file and reopen the menu. Check layout, shortcuts, and custom assets separately so a successful import is not mistaken for a complete migration.
Limits & precautions
Do not hand-edit an only copy of your backup or import unknown XML on a managed PC. A settings file can reference commands, private folder names, and network locations.
Questions & answers
Does a successful XML import copy the application too?
No. Open-Shell must already be installed; the file contains preferences, not the installer.
Is a missing skin proof that the XML is corrupt?
No. The skin may simply be absent or stored at a different path.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.