Why preserve configuration before changes
Application settings live in specific files that control behavior, paths, and features. Editing them during troubleshooting can introduce new issues or erase working setups.
Keeping copies lets you restore the prior state quickly or compare differences to isolate what changed.
This approach supports a repeatable process where you first secure the current state, then apply test changes, and finally decide whether to keep results or revert based on direct evidence from the files themselves.
Locate and copy key files on Windows
For ASP.NET applications on IIS, the main configuration file applicationHost.config sits in %systemroot%\System32\inetsrv\config. Individual web.config files reside in the root of each site or application folder.
Copy these files to a separate folder or external drive before making edits. learn.microsoft.com recommends regular backups so you can revert if an update breaks the application.
Begin by confirming the exact folder locations for the applications you plan to examine. Use File Explorer for a visual check or command-line tools for scripted duplication. Label each backup folder with the current date and the original path so later comparison stays straightforward.
- Identify the exact paths for your installed applications
- Use File Explorer or command-line copy to duplicate the files
- Name the backup folder with the date and original location for easy reference
Back up settings for other Windows tools
The MSIX Packaging Tool stores its configuration in settings.xml under the user's AppData\Local\Packages folder. Copy this file to a network share or external location before changing tool settings.
Windows Backup can preserve personalization, folders, and some preferences when signed in with a Microsoft account, though it does not cover every application-specific file.
Review the tool documentation to confirm the precise location of any settings file. After copying, open the duplicate to verify it is readable. When restoring, place the file in the matching folder on the same or a newer version of the tool so the saved values load without mismatch.
- Check the tool's documentation for the exact settings file path
- Verify the backup copy opens correctly before proceeding with changes
- Restore by copying the file back to the same location on the same or newer tool version
Handle device and app settings on Apple platforms
Backups created with Apple Configurator or iCloud include device settings, Home Screen layout, and app data. These backups do not contain apps or media synced from a computer.
You can back up one device, then restore that backup to other managed devices to duplicate a known configuration.
Choose encrypted backups when the data includes sensitive information. After the process finishes, confirm success through the backup tool interface. Apply the backup only to devices that meet the same or newer software version requirement to avoid compatibility gaps during restore.
- Use encrypted backups when sensitive data is involved
- Confirm the backup completed successfully before testing changes
- Restore only to devices running the same or newer software versions
Test with clean defaults after backup
Once copies exist, rename or move the original configuration files to force the application to create fresh defaults. Compare the new defaults against your backup to see which settings differ.
This method isolates whether a problem stems from a corrupted file or from a specific setting value.
After removing the original file, restart the application or service so the fresh defaults load. Note any values you later copy back from the backup. Retain the backup copies until the original issue is fully resolved and no further rollbacks are needed.
- Restart the application or service after removing the original file
- Document any settings you re-apply from the backup
- Keep the backup until you confirm the issue is resolved
Limitations and next steps
Not every application stores settings in plain files; some use registries, databases, or cloud sync. Windows Backup and Apple device backups cover only supported items.
If the problem persists after restoring a known-good configuration, review logs or consider a clean reinstall of the affected software.
When an application relies on non-file storage, the backup step still provides a baseline for the items that do reside in files, but additional investigation of logs or reinstall steps may be required to address remaining issues.