I know, I was experimenting using those steps to see how it actually behaves. Which brings back to my point, right. If you have Navigraph installed where the installer injects the code into the specific location in content.xml. And the Navblue update also edits the same content.xml Then the integrity of that content.xml would be thrown out the window.
So if navigraph installer makes a backup copy prior to installing the mod for the purpose of being able to uninstalling the mod. Then the installer would need to restore the original content.xml when you decided to use the installer to “remove” the navigraph mod.
Now, if the navigraph was installed “before” the navblue update patch. The backup content.xml that it has would be the version that’s before the patch. Then once the navblue update patch comes it, it edits the content.xml again. Now you have a different content.xml file between in the sim after the update versus the one that’s backed up by the navigraph installer.
So when you uninstall the navigraph mod using the installer, it restores an older version of the content.xml file, which may cause the entire navdata to be missing because it no longer match with the latest navdata anymore. Which is why I said in my original post. That prior to a sim update (just to be safe, any form of a sim update). I always use the installer to remove the navigraph mod, do the sim update. And once I’m done with evertyhing. I install the navigraph mod using the installer again.