uninstall and (.msi files)

K4Z00 · Post by **K4Z00** » Thu Jul 03, 2008 5:01 pm

installed a program that initially worked ok, but has recently started misbehaving. on trying to uninstall it with the wine uninstaller, it just won't go. in fact the uninstall wizard just seems to install the program again, even if i delete it from program files.

i have tried to delete all it's associated files etc. but then when trying a fresh install the wizard must still see the original installation, as it only offers modify/remove/repair. i notice in the wiki that the wine uninstaller "does not work with programs installed with a .msi file". and there is a .msi file associated with this program.

so the questions.
1. how can i completely uninstall this program, and all it's associated entries?
2. is it ok to delete the temp folder just as in windows?
3. what stops the program from being totally uninstalled?

edit: i'm googling as i go...is it the user.reg. it has entries for the program in question?

thanks!

vitamin · Post by **vitamin** » Thu Jul 03, 2008 5:26 pm

K4Z00 wrote:so the questions.
1. how can i completely uninstall this program, and all it's associated entries?

http://wiki.winehq.org/FAQ#head-9893ae5 ... af2e69b391

K4Z00 wrote:2. is it ok to delete the temp folder just as in windows?

No it's not ok. You can delete the content inside. And most programs should handle that.

K4Z00 wrote:3. what stops the program from being totally uninstalled?

Not implemented parts of Wine or bugs. It's a low priority - non one wants/needs to properly implement it / fix it.

K4Z00 · Post by **K4Z00** » Thu Jul 03, 2008 5:38 pm

thanks vitamin for the ever prompt reply!
is it worth deleting the entries in the user.reg file too?

there are 2 specific entries for the program
edit: (and it is still showing in the wine uninstaller)

K4Z00 · Post by **K4Z00** » Thu Jul 03, 2008 6:42 pm

ok have deleted contents of temp folder, and deleted all entries manually, and via the wiki using the 4 terminal commands config/menus etc.

however when i run the installer, it is still detecting a previous install, and offering modify/remove/repair. none of which do anything useful!

any other suggestions or ideas most welcome, other than that, will delete those registry entries tomorrow.

being as there was/is only this one program installed, google result suggests rm -rf .wine/

will this delete the whole wine folder and write a new one when i install a new windows program? or is this idea pants?

K4Z00 · Post by **K4Z00** » Thu Jul 03, 2008 7:27 pm

ok ran regedit from terminal
\hkey_local_machine\software\microsoft\windows\currentversion\uninstall
deleted entries pertaining to program
and it's done

vitamin · Post by **vitamin** » Fri Jul 04, 2008 12:17 am

K4Z00 wrote:thanks vitamin for the ever prompt reply!
is it worth deleting the entries in the user.reg file too?

there are 2 specific entries for the program
edit: (and it is still showing in the wine uninstaller)

Some one been "fixing" that entry on wiki. It's missing the first step:

Code: Select all

rm -rf ~/.wine

That should take care of everything installed under Wine. And no you should not pick pieces from the ~/.wine dir, like registry. Just remove everything. If you don't want to loose some applications - make a separate WINEPREFIX for them.

Hartmut Figge · Post by **Hartmut Figge** » Fri Jul 04, 2008 12:28 am

vitamin:

Code:
rm -rf ~/.wine

Yes, but i prefer 'mv ~/.wine ~/.wine-s1' ...

And no you should not pick pieces from the ~/.wine dir, like
registry.

... because then it is possible to reuse e.g. old savegames.

Hartmut

James McKenzie · Post by **James McKenzie** » Sat Jul 05, 2008 12:46 pm

Hartmut Figge wrote:

vitamin:

Code:
rm -rf ~/.wine

Yes, but i prefer 'mv ~/.wine ~/.wine-s1' ...

I prefer mv ~/.wine{,.<insert appropriate name here>}

This moves the file and maintains the .wine part with the .<insert
appropriate name here> portion appended.

And no you should not pick pieces from the ~/.wine dir, like
registry.

... because then it is possible to reuse e.g. old savegames.

It is never a good idea to edit the registry unless you know absolutely
what you are doing. I've done registry recoveries and they are
unusually messy. Moving the .wine directory is much easier and cleaner.

code:

cd
mv .wine{,.backup}
wineboot
cd <installation directory of new program>
wine setup.exe (alt. wine install.exe)

If the program requires specific packages I use Dan Kegel's winetricks
(gecko is broken on Wine 1.1, but there is a fix and workaround that
does the install).

James McKenzie

Hartmut

Hartmut Figge · Post by **Hartmut Figge** » Sat Jul 05, 2008 1:51 pm

James McKenzie:

[...]

cd
mv .wine{,.backup}
wineboot

The above step if have never used.

cd <installation directory of new program>
wine setup.exe (alt. wine install.exe)

If the program requires specific packages I use Dan Kegel's winetricks

And perhaps some data from the backup is convenient. Was for me sometimes.

Hartmut