The following files are *not* deleted when doing an uninstallation of mozilla: C:\WINNT\MozillaUninstall.exe C:\WINNT\mozregistry.dat C:\WINNT\mozver.dat at least MozillaUninstall.exe should be deleted. I'm not 100% sure about the other files.

More files not deleted after installing the 2000052409 build: C:\PROGRAM FILES\MOZILLA\SEAMONKEY\CHROME\all-locales.rdf C:\PROGRAM FILES\MOZILLA\SEAMONKEY\CHROME\all-packages.rdf C:\PROGRAM FILES\MOZILLA\SEAMONKEY\CHROME\all-skins.rdf

added Dan to the CC list.

Yes, I made this worse last night by registering chrome -- but it was better than having the build not working. By comparison this bug is trivial. There is also bin/chrome/user-*.rdf (two I think) and variable files in bin/chrome/overlayinfo/* depending on what was registered. Note that we can log what we installed initially for uninstall, but we will not be uninstalling anything users add on after the fact, either skin, chrome, or components. Eventually we will, but not in 6.0

Couldn't we just delete everything in the: C:\Program Files\Mozilla\Seamonkey\ directory? Some uninstallers asks if they didn't delete the entire directory what to do with the directory. The user is then presented with some options like: Delete entire directory Leave directory as is. That would be a cool and easy fix for the problem!

We're leaving a few chrome files behind, which prevents the program directory from getting deleted. Is this a beta2 stopper or can we get to it in beta3?

Putting on [nsbeta2-] radar. Not critical to beta2.

*** Bug 45265 has been marked as a duplicate of this bug. ***

No point in going to all that trouble of creating an uninstaller if we're leaving files behind... Henrik's suggestion of a "zap the rest?" dialog is nice, but maybe in a later version.

Another example of not all files removed could be this: A user start the Mozilla installer for the first time on his/her computer. Installs Mozilla but presses Exit in the Profile Manager dialog. Now the user haven't created any profiles. He uninstalls the product, beleaving that all files are removed.... but NOPE. The following files exists: c:\winnt\mozver.dat c:\winnt\mozregistry.dat c:\winnt\MozillaUninstall.dat c:\winnt\Mozilla\registry.dat This is the way a windows machine gets filled up with garbage! Please dont let mozilla add to this...

The uninstaller should be deleted after a reboot (because it's *running* when you're uninstalling and cannot delete itself). The two registries in the windows directory are covered by bug 46320. The remaining issue is Mozilla/registry.dat (the new location for mozregistry.dat) which unfortunately isn't going to get solved by nsbeta3

A lot of uninstallers deletes itself. How do they do that? I just installed "K-Meleon" and the uninstaller (uninstall.exe) deletes itself after running....

*** Bug 51763 has been marked as a duplicate of this bug. ***

Not sure how K-Meleon does it. Where can I get a copy of it to test it out? And which Windows OS did you do this on? However, the other files that reside within the seamonkey dir should be deleted at the end of the uninstall process. Marking this bug P2 for those files and because it's trivial.

I'm not sure about the k-melion uninstaller. Just as long as the mozilla uninstaller gets deleted after reboot. But the other files should be deleted.

Bring on nsbeta1 radar for reconsideration.

al the files seems to be deleted now, or what? installer build 20010130

verified on build 2001022705

mozilla 1.4.1 on windows 2000 pro : The files MozillaUninstall.exe and mozver.dat are not deleted after unistall. ( I have no permission to reopen this bug, otherwise I would )

so find/file a new bug. But: Do Not lump those two together. the first is definitely maybe a bug, the second is only possibly a bug. If you file, be sure to list all mozillas that _are_ and _ever have been_ on your computer. netscape4, 6 and 7 count, as do any other derivatives (doczilla, komodo, ...). Be sure to indicate which are currently dead / orphanned / moved / manually deleted / alive / running / lost / stolen / misplaced / ....

I think it would be better to install mozilla on a new & clean system, then deinstall it and check if any of files are left behind. If I find time to do it, I will and will report.