How to uninstall wine
How to uninstall wine
How to remove wine completely
How can I remove the wine folder and all the applications in that folder?
I’ve tried via synaptic but it keeps showing up in the application menu.
11 Answers 11
In my case Wine did not get effectively uninstalled using the command:
So I did the following (make sure to copy the exact commands):
After deleting the files run command:
Do the following to correct any installation error.
and you are done.
Run these to get rid of menu entries instead of (or in addition to) using «Edit Menus».
First answer is the easy form to get this, but it’s incomplete, the complete code is:
If you’ve installed wine from the official Ubuntu repositories:
If you’ve installed wine from their official PPA:
Next, clean the context menu, menu entries, etc:
It needs to reboot the system:
I tried more ways from here and others but didn’t work so i did the following and it worked if you installed it from Winehq site you just need to do 1- alt+Ctrl to open the terminal 2- Type in it sudo apt-get remove winehq-devel Note: if it said that not found try other winehq type to remove what you have install as sudo apt-get remove winehq-stable Or sudo apt-get remove winehq-staging 3- Type y mean yes to remove it, in the removing in will download some files and a new windows will appear just click tab from your keyboard to click on ok and then yes 4- when it finish do sudo apt-get update then sudo apt-get upgrade 5- it will ask you to do sudo apt autoremove you are done now You can reinstall it or do what you want to do now If you installed it by Ubuntu software you can remove it by using it too
In 11.04 and below (GNOME Classic)
When you install wine, it creates a «wine» menu in your applications menu, and this menu is partly user specific. To remove the menu entries, right click on your menu and click edit menus.
11.04 and up (Unity Desktop).
How to uninstall wine
Updated: April 29, 2019
Sounds like a noob question, does it not? Well, turns out, some things aren’t trivial. In fact, the whole WINE framework isn’t trivial. There are many ways you can go about trying to install and configure Windows software on Linux machines. You have 32-bit and 64-bit WINE, there’s UI (but it’s weird) and command line, you can also use winetricks, and then some.
WINE uninstaller
Wait! There’s WINE 64-bit too!
Manual deletion
/.wine, and navigate to your virtual C: drive (
/.wine/drive_c). From that point, it’s just a regular Windows tree, and you can delete folders, including the contents of Program Files. Of course, this isn’t the ideal way, because you will still have orphaned menu entries and shortcuts.
What you can do in that case is delete entries from user.reg and system.reg files. We talked about these files when we tweaked Notepad++, so you should be familiar with their existence and purpose. These files act as sort of registry database for your installed WINE software. If you remove data from these files, you effectively unregister applications. Search for the relevant entries (grep) in these two files and delete what you no longer need. This can be a tedious process, but it will allow you to clean up your WINE setup without deleting everything. For instance:
Delete everything
Conclusion
Another mildly obscure tutorial comes to an end. But I’d like to believe it’s been useful, because most of WINE stuff isn’t trivial. You do need a fair degree of lateral thinking to understand all the bits and pieces, the hybrid model that’s not quite Linux and not quite Windows.
Linux Mint Forums
Welcome to the Linux Mint forums!
[SOLVED] How to Completely Uninstall Wine?
[SOLVED] How to Completely Uninstall Wine?
Post by Radish » Tue Nov 17, 2015 3:51 pm
I installed Wine using the «Software Manager». I decided I wanted to uninstall it. I used the «Software Manager» to do this.
At the bottom of the Software Manager window there is an item titled «1 ongoing actions». The problem is that it is stuck showing «99%».
I take it to mean that, for whatever reason, the uninstall has been unsuccessful.
Could someone tell me:
1) Is it safe to, now, shutdown the Software Manager (even though it is stuck at 99%)?
2) How do I completely uninstall Wine?
Post by richyrich » Tue Nov 17, 2015 4:59 pm
Post by Radish » Wed Nov 18, 2015 12:47 pm
First of all I should say that I waited for an hour for the Software Manager to finish uninstalling Wine (if it wasn’t done by that time it was probably never going to be done). Okay.
When I got richyrich’s response (many thanks) I went to Synaptic Package Manager. There were two Wine items marked as being installed:
a) Wine1.6 1:1.6.2-0ubuntu4
b) Wine1.6-amd64 1:1.6.s-0ubuntu4
I right-clicked the first one and it said it would need to completely remove the following two packages:
1) Wine1.6-amd64
2) Wine1.6-i386:i386
Which as far as could see, once I allowed Synaptic to mark them, was the equivalent of marking the ‘a’ and ‘b’ packages mentioned above for complete removal. Fine. (Though I did wonder about the discrepancy over the naming of the components.)
I applied the change and Wine did get removed.
Does anyone have any idea of what is going on with this? Where did the offer of additional components go?
One last question: The version of Wine offered in Mint is 1.6. However, when I look on the internet the latest version seems to be 1.7.55. Why doesn’t Mint included the latest version? (Maybe it’s better for what I’m trying to do than using the older version.)
Post by richyrich » Wed Nov 18, 2015 1:10 pm
Post by Flemur » Wed Nov 18, 2015 2:54 pm
/.wine directory, which holds most of the wine config and doesn’t get deleted when you uninstall or purge the wine packages.
As for the TreePad fonts, run
/.wine, it’s not part of the linux OS wine install.
Post by Radish » Thu Nov 19, 2015 9:18 am
/.wine directory, which holds most of the wine config and doesn’t get deleted when you uninstall or purge the wine packages.
Okay, I’m going to go for a test un-install and then re-install. However, I’ve looked and searched in the File System using the «Search» function and I cannot find the directory «-/.wine». (I did have «Shown Hidden Files» enabled when I looked and searched.)
Where is it, how do I find it?
Post by richyrich » Thu Nov 19, 2015 9:30 am
It is in your /home/username/ directory. See below mine inside my richyrich directory. (click to enlarge)
Post by Radish » Thu Nov 19, 2015 9:57 am
Could you clarify something for me for future reference (and/or maybe Flemur could if he is around)?
Flemur said to find the directory «-/.wine». So when I looked visually for that folder I started looking for a folder «-» (i.e. hyphen) and thought the «.wine» folder would be in the «hyphen» folder.
Now I’m thinking that was an obvious mistake on my part. Does that mean the «-/» is Linux-speak shorthand for look in «/home/username»? Or was Flemur just being idiosyncratic in the way he expressed the directory path? I’m a newbie at this so need to learn bit by bit.
Post by duneelliot » Thu Nov 19, 2015 10:04 am
Post by Radish » Thu Nov 19, 2015 10:37 am
Okay, thanks very much, duneelliot.
I just tried copying and pasting Flemur’s original directory path into a text file and, yes, it clearly shows as a tilde in the text file. Think the problem is that I’m finding text in Firefox to be a bit on the blurred side (unlike what I get when using Firefox in Windows). In Firefox it shows to me as a hyphen.
Post by Flemur » Thu Nov 19, 2015 12:02 pm
) = your home directory. Works in terminals or a file browser, too.
Post by Radish » Thu Nov 19, 2015 2:07 pm
I did an un-install of Wine and then deleted the
/.wine folder did work. This time I copied down the items that I declined to install during my first ever install of Wine. Messages were are follows:
Note: it is recommended to use your distributions packages instead.
See httt://wiki.winehq.org/Mono for details.
In Software Manager found this package «wine-mono0.0.8». So I assume that is was what being referred to and that I could install later if I so wished.
Wine could not find a Gecko package which is need for applications embedding HTML to work correctly. Wine can automatically download and install it for you.
Note: it is recommended to use your distributions packages instead.
See http://wiki.winhq.org/Gecko for details.
In Software Manager I found two packages for this:
1) wine-gecko2.21
2) wine-gecko2.21:i386
So, again, something that I could install later if I so wished. At least now I know what I missed the first time and what the components are.
I did try, as Flemur suggested, installing Winetricks and then the «corefonts» to see if that would help text display in TreePad. Unfortunately, it made no difference at all (but still worth the try). As it stood one of the first things I did after installing Mint was to install «mscorefonts». As far as I’m aware this makes those Microsoft fonts available system-wide in Mint for applications that can use them (but do correct me if I’m wrong on that). Certainly TreePad was still able to display my TreePad documents in Microsoft’s «Times New Roman» (even before installing Winetricks corefonts). So in my troubles with legibility of Times New Roman in TreePad I guess I’ll just have to chose an alternative Microsoft font for my documents that displays better than Times New Roman does. I need to use a Microsoft font as I will be working with TreePad docs across Linux and Windows systems and I use Treepad Business Edition an awful lot (brilliant program).
In any case I think the original purpose of this thread has been met so I’ll mark it as [SOLVED] for now. Many thanks for all the help.
Re: [SOLVED] How to Completely Uninstall Wine?
Post by Radish » Fri Nov 20, 2015 9:25 am
2) To install the fonts in Windows see this webpage: http://www.google.com/get/noto/help/install/
3) Once the fonts are installed Noto Sans (and any other Noto family fonts you installed) will now be available in Windows for use in Treepad. Now you can work with Treepad between Linux Mint and Windows with minimal hassle concerning matching fonts and text legibility.
Ubuntu Documentation
Wine allows you to run many Windows programs on Linux. Its homepage can be found at WineHQ.org. They also have an Ubuntu page with installation and build advice.
If you are running the latest release of Wine which is v1.6, you can get further assistance on the #winehq IRC channel on irc.freenode.net. First,
please consider if you really need to run the specific Windows program because in most cases, its equivalent can be provided by an OpenSource program. Also, consider using Qemu instead of Wine if you need a complete Windows installation.
Installing Wine
Ubuntu versions of Wine (Recommended)
Newer versions of Wine (Not Recommended)
sudo apt-key add winehq.key
sudo apt-add-repository 'https://dl.winehq.org/wine-builds/ubuntu/'
Note, however, that these are development packages (ie beta software), and may suffer from regressions and other problems not present in the stable version of Wine included with Ubuntu. You should avoid using them unless the current stable version of Wine does not support or is incompatible with the application you wish to use.
If you are using an older version of Wine and want support from WineHQ, you will need to upgrade to the latest development version first. If you do this, however, please file associated Wine bugs at winehq’s Bugzilla Page rather than in Launchpad.
Initial Setup
You also have the option of configuring Wine via the Configure Wine option in the Applications-> Wine menu.
This will create a hidden folder (.wine) in your home directory containing the fake C: drive as well as registry files similar to those used in Windows. Once this directory is created, the Wine Configuration Window will appear. This window will allow you to customize a variety of settings for Wine, including which Windows Version that is emulated, drive mappings, DLL overrides, as well as application specific settings. Click the Ok button to close the window.
Installing Windows Applications With Wine
Type wine the-name-of-the-application.extension (e.g. wine realplayer_installer.exe).
To start/run Windows programs using Wine
After installing an application using the directions above, those applications can be started and used by entering wine programname.exe (e.g. wine realplayer.exe). When done, close the application as one would normally. You must run the installed executable, which will by default be in the virtual Windows drive created by Wine, at
/.wine/drive_c. Generally programs will install themselves somewhere under Program Files inside the virtual Windows drive, following Windows conventions.
Instead of having to always enter the terminal or use the Wine file browser, you may also create a desktop icon, and start a Wine application using that icon. To do this, right click on the desktop and select «Create a launcher.» If you wish, select an icon from the list of available icons (or browse to an icon you would like to use), fill out other information that is requested (Name, generic name, etc.). For the command, type in wine the-location-of-the-program.exe (e.g. wine /home/john/.wine/realplayer.exe). The most important part of creating a launcher is the command, the generic name is not as important. Just make sure you de-select «Run in terminal.» This completes the process.
In some cases the application requires to be running from a certain location. In this case create launcher with command
Of course you will need to replace USER and Appdir with the proper data.
If you desire to have an icon on the panel, create a launcher on the panel of choice. Do this by right-clicking the panel, selecting «Add to Panel,» and selecting «Custom Application Launcher.» This will ask you for the same information as before.
Uninstalling Wine Applications
Open up a terminal window and type the command below.
What this will do is open up a program similar to the Windows add/remove programs control panel, allowing you to uninstall applications from a Wine installation. Running uninstall programs directly via Wine should also work normally. Alternatively, you could also simply delete the folder of the application. However, as when done in Windows, this method will be unclean and will not remove the program’s configuration from the Wine registry like using an uninstaller will.
Configuring Wine
On the command line or in Run Application, type winecfg
Adding CD and DVD drives to Wine
Go to the drives tab in winecfg. Hit the Autodetect button.
If you find that this does not work correctly for you, then follow these instructions:
Navigate to the drives tab
Click on Add.
In the path bar, type
Click Show Advanced button below the Browse. button and set the Type to
If you have more than one CD/DVD device you will need to identify each one differently. Use /media/cdrom0 for the first CD/DVD device, /media/cdrom1 for the second one, and so on. If in doubt, type the following command in your terminal.
What this command will do is check your CD/DVD device details after Wine is installed.
Adding applications to the menu
It is good procedure before setting up the menu entry to launch the new Windows program from the command line to make sure the program runs properly. To do this type this command in the terminal.
For example the command would be wine «C:\Program Files\World of Warcraft\WoW.exe» Once you are satisfied that you have the correct details, use the normal menu editing process to add a new entry. When you get to the Command field of the entry editor be sure to copy and paste the line you used to launch the program from the terminal. Finish and save the new entry. Test to make sure the new Windows program loads via the menu.
Changing application specific settings
Type this command into your terminal.
Using Windows Themes/Skins In Wine
Color Scheme
You can change the wine color scheme to closely match the default Ubuntu colors with this Terminal command.
You may also want to create a backup copy in your Home folder with this command via terminal.
Replace the [Control Panel\\Colors] section with
Using Theme/Skins
Wine has basic handling for Windows theme/skin files in the «msstyles» format. There is a large number of these themes on Deviant Art. To use these you must make a folder in Wine’s virtual Windows drive, then tell Wine to use the theme.
Firstly go into Wine’s virtual drive, which is usually «.wine/drive_c» in your Home folder (this is hidden, you may need to select View->Show Hidden Files in the file manager). Inside this folder go into the «windows» folder then make a new folder in there called «Resources». Enter this new folder and make a new folder called «Themes». Inside here you should make a folder for each theme you want, and put the files ending in «.msstyles» directly into them. For example, the full path to a theme file called sample.msstyles might be «/home/username/.wine/drive_c/windows/Resources/Themes/Sample/sample.msstyles».
Next you need to tell Wine to use your theme, so once again run this command in the terminal.
In the configuration window select the tab Desktop Integration and un-check out the Theme: box, which should now have your theme in it’s menu. After selecting the theme click Apply at the bottom to see how it looks (they don’t always display properly), then if you are happy click ok and you’re done!
Fullscreen issues with overlapping Panel
If that does not work, then you will have to turn off the panels prior to running the application and restarting it afterwards, until a better workaround can be found. In Ubuntu the commands are gnome-session-remove gnome-panel and gnome-panel & respectively. In Xubuntu I understand they are killall xfce4-panel and xfce4-panel.
Instructions for using wine over remote X11 sessions
If you’re (trying) to use wine over a forwarded X11 session (ie Ubuntu is on one computer; you’re connected to it by ssh or another connection and you already have X11 forwarding set up to display regular Ubuntu applications on your remote computer) and the windows opened by wine are lacking fonts etc, the answer is here
Instructions for specific Windows programs
Some Windows programs have been tested on Ubuntu. They are listed below:
Creating file associations
If you want certain files to open in a windows application by clicking on them, the best way is to create a script. For example I want Adobe Flash project files (*.fla) to open in Adobe’s Flash editor if I double click it.
You can for example create a file using this terminal command.
Now paste the following example script in it, save and close gedit.
Make sure the file is executable with this command.
After you completed this go to an *.fla file right click it, properties, go to the “open with” pane, click add, add this line into your terminal and select the radio button.
Now if everything went ok, you can doubleclick the file and it will be openend in Flash 8.
Troubleshooting
Error: Cannot change screen BPP from 32 to XX
In some cases (mostly games) the application does not start and you get error: Cannot change screen BPP from 32 to 16 (or some other number).
In such case editing xorg.conf and CTRL-ALT-Backspace helps as is described on http://ubuntuforums.org/showthread.php?t=649283
‘dhtmled.ocx’ is missing or invalid
It seems that in Ubuntu Karmic Wine(v1.0.1) registry isn’t configured correctly to use ActiveX component dhtmled.ocx. On some application this can cause error like this: «Component ‘dhtmled.ocx’ or one of it’s dependencies not correctly registered: a file is missing or invalid». So we must tell Wine where to find this file.
1. Download registry file:
3. Import the downloaded registry settings
file->import registry file->open
Screen flickers to black when starting an application
This is sometimes caused by a problem with the video driver not handling XRandR well. To see if this is actually a problem with XRandR, in a console, run:
See Wine Bug #15214 and Wine Wiki page UsefulRegistryKeys.
Related Wiki Pages
Wine (последним исправлял пользователь grantbow 2019-11-27 22:56:38)
The material on this wiki is available under a free license, see Copyright / License for details
You can contribute to this wiki, see Wiki Guide for details
How to uninstall wine
Translations of this page: 
Français ; Not all ported. Translators, please see Discussion page.
This FAQ, or Frequently Asked Questions, covers general topics about Wine. For questions related to Wine software development, see the Developer FAQ.
Contents
1 General questions
1.1 Who is responsible for Wine?
Wine is available thanks to the work of many people around the world. Some companies that are or have been involved with Wine development are CodeWeavers, Bordeaux, TransGaming, Corel, Macadamian and Google. See Acknowledgements and Wine History.
1.2 Does Wine hurt Linux or other free operating systems?
Wine increases the usefulness of Linux, makes it easier for users to switch to free operating systems, and for Windows developers to make applications that work on them. This greatly raises Linux marketshare, drawing more commercial and community developers to Linux.
1.3 Is Wine an emulator? There seems to be disagreement
There is a lot of confusion about this, particularly caused by people getting Wine's name wrong and calling it WINdows Emulator.
That said, Wine can be thought of as a Windows emulator in much the same way that Windows Vista can be thought of as a Windows XP emulator: both allow you to run the same applications by translating system calls in much the same way. Setting Wine to mimic Windows XP is not much different from setting Vista to launch an application in XP compatibility mode.
A few things make Wine more than just an emulator:
"Wine is not just an emulator" is more accurate. Thinking of Wine as just an emulator is really forgetting about the other things it is. Wine's "emulator" is really just a binary loader that allows Windows applications to interface with the Wine API replacement.
1.4 What is the difference between Wine, CrossOver, and Cedega?
Wine is the base of the project, where most of the work is being done. Wine is not perfect, but tens of thousands of people nevertheless use "vanilla" Wine successfully to run a large number of Windows programs.
CrossOver XI (formerly CrossOver Office) is a product made by a company called CodeWeavers that is based directly on Wine with a few tweaks and proprietary add-ons. Unlike the biweekly Wine releases, CrossOver releases are rigorously tested for compatibility with CodeWeavers' supported applications in order to prevent "regressions". CodeWeavers employs a large proportion of the Wine developers and provides a great deal of leadership for the project. All improvements to Wine eventually work their way into CrossOver.
For more information, see Wine History.
1.5 How does the Wine version numbering system work?
1.6 Do I have to use the command line?
Normally you do not have to use the command line to use Wine in Linux. You can use a graphical interface for most things, much like on Windows. In many cases you can right-click an installer and select "Open with Wine", or just double-click it. You can start installed programs using the shortcut icon or menu.
However, there are several situations when you might need to use the command line. The most common reason is to get debug output when your program does not run properly. You might also want to use utilities such as regedit that do not have menu shortcuts (note that you can create them using whatever tools your DE provides).
This does not hold true for Mac OS X Wine usage, which is all command line currently, unless you use a third party application.
1.7 What applications run well with Wine?
Thousands of applications work well. As a general rule, simpler or older applications tend to work well, and the latest versions of complex applications or games tend to not work well yet. See the Wine Application Database for details on individual applications. If your application is rated Silver, Gold or Platinum, you're probably okay; if it's rated Bronze or Garbage, Wine isn't really ready to run it for most users. If there aren't any reports using a recent version of Wine, however, your best bet is to simply try and see. If it doesn't work, it probably isn't your fault, Wine is not yet complete. Ask for help on the forum if you get stuck.
1.8 How can I help contribute to the Wine project, and in what ways?
You can contribute programming or documentation skills, or monetary or equipment donations, to aid the Wine developers in reaching their goals.
One area where every Wine user can contribute to this project is by sending high quality bug reports to our Bugzilla and helping the developers with any followup questions that they may have about your bug. It is impossible and impractical for a developer to have a copy of every program on the market, so we need your help even after your initial bug report. If a developer has a good idea what might be causing the bug, he or she may ask if you can try a patch and see if it fixes the problem. If the patch works and then makes its way into our main development tree, the bug report will be closed, your help will be appreciated by everyone and your problem will be fixed.
For a list of ideas of how you can help, please consult the Contribute section of the main page.
1.9 I think I've found a bug. How do I report this to WineHQ?
Bug reports should be submitted to our online Bugzilla system. To increase developer productivity and facilitate a resolution to submitted bugs, please read the Wiki article on Bugs. A poor bug report may be marked INVALID and closed, leaving you no closer to resolving your problem. High quality bug reports are an essential part of making Wine better.
Please note that you should generally avoid submitting bug reports if you have used any third party applications or native DLL overrides.
1.10 Where can I get further help?
In addition to this wiki, check the Wine HQ Documentation and the users forum. If you're an ISV looking at porting an application with Winelib you can also try wine-devel.
For help with a specific application, search the Application Database, a place where users share their experiences by submitting test data, tips and tricks, and asking questions.
The IRC channel: #WineHQ on irc.freenode.net. Knowledgeable Wine users hang out there, and often developers will lurk there too. See IRC for more important information.
2 Installing Wine
2.1 What are the system requirements for Wine?
Wine, along with the operating system you use to run it, generally requires less disk space and memory than Windows itself. If you're not currently running a Windows application, Wine won't consume any resources at all other than about 20 megabytes of disk space.
Ideally, if an application runs fine in Windows, it should run fine on the same hardware using Wine, provided native drivers for your hardware are installed and equivalent to the Windows drivers. Open source Linux graphics drivers in particular are often inadequate to run games that work fine on the same hardware in Windows. If there is no native driver for your hardware, Wine will not be able to use it.
2.1.1 Does Wine run on all Unix filesystems?
Mostly. Wine is written to be filesystem independent so MS Windows applications should work on virtually any full-featured UNIX filesystem. The key exception is that not all filesystems / drivers support every feature of fat32 or NTFS. One example is that the ntfsv3 drivers do not support shared-write mmap, a feature that cannot be emulated and is used by applications such as Steam.
One other point is that Wine is a weird application in ways and some programs work better on case-insensitive filesystems (see Case Insensitive Filenames for more details).
2.1.2 Will Wine run only under X?
Until recently with projects such as Wayland, serious alternatives to x11drv weren't even on the horizon so development has focused on X. However, Wine's interface with the graphics driver is designed to be abstract so supporting future graphics systems will hopefully be straight-forward.
2.2 Which version of Wine should I use?
Short answer: Use the version that works best with the particular applications you want to run. In most cases, this will be the latest development version; however, in some cases it may take some experimenting to find it.
Longer answer: Wine development is rapid, with new releases in the development branch every two weeks or so. Functionality will usually be best with the most recent development version, however, there are cases where changes to existing code in Wine cause applications that worked well in older versions to not work in the new one (these are called regressions), as well as problems caused by the introduction of new, but as-yet-incomplete and untested, functions.
A good rule of thumb is to start with the version of Wine installed with your distro and see if that works with the applications you want to use. If it does, good! If it doesn't, upgrade. In most cases the upgrade should be to the latest development version, but it is a good idea to check Bugzilla and the AppDB for any known regressions and/or new bugs. If you find an existing bug marked STAGED, this means there is a patch for the problem in wine-staging (the experimental branch), and you should try the latest version in that branch. If there are known bugs without a STAGED patch or easy workaround, upgrade to the most recent version of Wine known to work for your application.
While Wine does have a "stable" branch, the term "stable" refers to the branch as a whole, which is infrequently updated, and (for the minor stable releases) only with bugfixes promised not to break functionality. Users of a development or staging release can achieve the same degree of stability by simply not upgrading. Note that user support for the stable branch is limited to the ability to file AppDB test reports. Users who ask for help on the forum/IRC or file bug reports for the stable branch will be asked to retest in the current development release.
The current stable, development, and staging releases are listed on the WineHQ home page. See Wine User's Guide#Wine from WineHQ for a description of the three branches and the version numbering system.
2.3 How do I install Wine?
2.4 How do I solve dependency errors when trying to install Wine?
If your package manager complains about unmet dependencies when trying to install Wine, work your way backwards. Try installing whatever package your package manager complains has unmet dependencies, see what your it complains about, then try to install that. Keep working your way backwards until you solve whatever is blocking everything else.
A common problem on Ubuntu-based system is having installed a PPA version of a library that is newer than what is available in the standard repository. PPA packages may not be multiarch compatible and/or may not have i386 packages built, and since Debian/Ubuntu-based systems require the i386 and x86_64 versions of a package to be exactly the same, the user is unable to install the i386 version needed by Wine because no matching version can be found. The solution is to either change the installed version of the library back to the one from the standard repository so you can install both the 32 and 64 bit packages, or find an i386 package whose version exactly matches the one already installed.
2.5 I have a problem installing my distro's Wine package and need help
WineHQ only supports the binary packages that we build (available here, only the ones listed under 'WineHQ Binary Packages'). Consult your distro's support channels for help using your package manager and interpreting any error messages you may be receiving if you're having problems with distro packages. If you are an experienced user and believe there is a problem with the package itself and/or the repository, please report it to your distro's Wine package maintainer.
2.6 Can I install more than one Wine version on my system?
Yes, but you will have to build Wine yourself (see Building Wine), as it is not possible to have multiple distro packages installed. The easiest way to do this is to run Wine from the build directory (don't do make install ). If you want to actually install multiple versions, use --prefix when building Wine to designate a different install directory for each version, e.g.
then install it with
On Linux, you may need to set LD_LIBRARY_PATH, like so:
Note that regardless of whether you install multiple versions or run them from the build directory, you will still have to designate which version of Wine you wish to use when running applications. It is also recommended that applications being run with different Wine versions be installed into separate wineprefixes.
2.7 Is there a 64 bit Wine?
Yes. 64 bit Wine has been available on Linux since 1.2. WineHQ binary packages are available for 64 bit, and most major distros package it for users. Normally, installation should be as simple as installing the Wine package for your distribution through your package manager. Check the Download page. If you are building Wine from source, see Building Wine for instructions on how to build 32 bit Wine on a 64 bit system and instructions on how to build 64 bit Wine in a shared WoW64 setup.
A few things to note:
2.8 Where can I find old Wine binary packages?
Old WineHQ binary packages are kept in their respective directories in the the WineHQ download server.
Consult your distro for information on obtaining old versions of distro Wine packages.
2.9 How do I install Wine on my netbook (eeePC, Acer Aspire One, etc.)?
If you have replaced the customized distro that came preinstalled on your netbook (Xandros, Linpus, etc.) with one of the mainstream distros that provide up-to-date Wine packages, you should be able to install Wine as normal for that distro.
If you are still using Xandros (eeePC), Linpus (Acer Aspire One) or any other customized distro, you will have to ask on your netbook's support forum. Only other users of those distros can advise you on what, if any, binary packages will work on your system, where to find them, and how to install them.
You can also try building Wine from source following the instructions in Building Wine, but you will still need to consult your netbook's support forum regarding satisfying dependencies on your particular system.
2.10 Installing on Apple
2.10.1 How do I install Wine on my Mac?
2.10.2 Can I use Wine on an older Mac without an Intel chip?
No, not even in Linux. Older Macs used PowerPC processors are incompatible with code compiled for x86 (Intel and AMD) processors, unless the code is run under CPU emulation. Wine Is Not a (CPU) Emulator, nor does it include one. The Darwine project was an effort to do just that, but it has not been maintained in many years.
3 Compiling Wine
3.1 How do I compile Wine from source?
3.2 How do I apply a patch?
You have to build Wine from source; see above.
4 Uninstalling
4.1 How do I uninstall Wine?
Uninstalling Wine itself will not revert your Wine settings or uninstall your Windows apps, which are permanently stored in your user's home directory. Do not uninstall Wine if you only wish to remove all of your settings and apps. For instructions on removing your Wine settings and apps, see #How do I wipe the virtual Windows installation?
4.2 How do I uninstall individual Windows applications?
You can run Wine's uninstaller command; this is like Windows' "Add/Remove Programs" function. To uninstall 64 bit applications, including wine-mono, you need to run it with wine64. The uninstaller should remove menu and desktop entries. but it's not well tested; it might not work with all apps. See below for a reliable way to remove *all* Windows apps.
4.3 How do I clean the Open With List?
To clean Open With List, please carefully paste the following commands into a terminal:
4.4 How do I wipe the virtual Windows installation?
You can remove your virtual Windows installation and start from scratch by deleting the hidden .wine directory in your user's home directory. This will remove all of your Wine settings and Windows applications. The simplest and safest way to do this is through your file manager. Simply set your file manager to show hidden files, browse to your home directory, and delete .wine the same way you would any other directory. If you want to keep it as a backup, you can rename or move it instead. To the host system, a wineprefix is just another directory that can be deleted, moved, renamed, etc., the same as any other directory.
If you prefer to do it from the command line, carefully paste the following commands into a terminal:
To rename it from the command line instead of deleting it:
Your Windows applications, though deleted, will remain in your system menu (remaining desktop files and icons are located in
To remove these leftover menu entries, carefully paste the following commands into a terminal:
5 Installing and Running Windows Applications
5.1 I have lots of applications already installed in Windows. How do I run them in Wine?
Short answer: you have to install them in Wine just like you did in Windows. Applications usually have a setup or installer program.
Long answer: some applications can be copied from Windows to Wine and still work, but don't try this unless you like tinkering under the hood of your car while it's running.
Wine is not designed to interact with an existing Windows installation. If you have any data you need from a Windows installation, browse your Windows filesystems in your normal file manager and copy the data to another location.
Do not try to configure Wine to point to your actual Windows C:\ drive. This will break Windows and require a Windows reinstall. We have tried to make this hard to do, so you probably cannot do it by accident. If you do manage this, Wine may or may not continue to operate, but your Windows install will be 100% dead due to critical parts of it being overwritten. The only way to fix Windows after this has happened is to reinstall it.