msi leaves files behind after uninstall
I have an msi that among other things puts and .ini file in the windows directory. When the user uses the software, this .ini file gets edited and some info is written to it.
When I remove the .msi from the machine, it removes everything (Program Files), but it leaves this .ini in the windows directory.
Is this b/c the file is edited, so the package no longer thinks it's one of the original files? I really need to remove this file b/c it's specific to the user.
Any help would be appreciated.
I'm using WPS 4.2
Thanks
When I remove the .msi from the machine, it removes everything (Program Files), but it leaves this .ini in the windows directory.
Is this b/c the file is edited, so the package no longer thinks it's one of the original files? I really need to remove this file b/c it's specific to the user.
Any help would be appreciated.
I'm using WPS 4.2
Thanks
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
cdorhout
19 years ago
Well, I figured to get around this problem, I would just create a script that deletes that .ini before install. If the package had been on that machine before, the .ini would get deleted before the package was installed again.
Does anybody know where I should call my script to run it before the .msi starts the file copy. I know if you want a script to run at the end, you put it in Execute Deferred right before Finalize, but I don't know where to put scripts to run at the beginning.
Does anybody know where I should call my script to run it before the .msi starts the file copy. I know if you want a script to run at the end, you put it in Execute Deferred right before Finalize, but I don't know where to put scripts to run at the beginning.
Posted by:
Gastro
19 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.