I am in the process of writing an installer for a freeware FSX addon I've developed and was wondering how others have managed the EXE.XML startup file. At present, I've written the installer to create a new EXE.XML if it doesn't already exist ( it doesn't by default ?) or backup and modify the existing file to add the tags I need to start the addon. The problem I have is what to do when the user uninstalls the addon. It's easy enough to delete the current EXE.XML and restore the backup but what if the user had installed other addons and modified the EXE.XML in the meantime? The restored backup would then be an old version and the user would be left wondering why their other addons suddenly stopped working. I'm trying to make the install/uninstall process as simple and as automated as possible for the user but I can't see how to make the uninstall 100% foolproof without asking them to modify the file manually. Does anyone have any thoughts or opinions on this?