1. Wine Installation Hangs Machine
2. Wine Installation Hangs Mac Download
3. Wine Installation Hangs Mac Pro
4. Mac Hangs On Boot
5. Wine Installation Hangs Mac 2017

Before going too far, be sure to run CrossOver's diagnostic tool. Open a terminal and run the command:
/opt/cxoffice/bin/cxdiag

Before you install Wine, make sure that there is no previous Wine installation on your system, either from a package or from source. If you haven't yet installed Wine, you should be fine. Many Linux distributions come with an included Wine package, but due to Wine's rapid development rate these are usually old and often broken versions. WIndows 10 hangs during installation on MacBook Pro. Once I got a message about 'attempting to recover installation' but as soon as it rebooted it hung up again. Then I got a message a 'preparing to install your previous operating system' (or something like that) but again no dots and it just sat there. It always boots to Windows no. I have a 2013 iMac desktop running mavericks. For the second time now when I have upgraded software the iMac hangs on the Apple screen during restart. What has worked for me both times is to unplug the machine from all cables.

or
~/cxoffice/bin/cxdiag
Output from that will be a list of libraries CrossOver typically looks for. If you are having trouble finding those libraries, please look at our more specific information available HERE.

Distro-specific issues

Although we do not provide support for all of the following distributions, we are collecting useful information for each.
Which Linux Distros are supported?
Ubuntu
Mint
Debian
Fedora
Other Unsupported Distro FAQs
Arch
CentOS
OpenSuse
ElementaryOS

CrossOver Installation

Will CrossOver interfere with my existing Wine installation?
CrossOver hangs during ClamAV virus scan
Install and use multiple versions of CrossOver on Linux

Menu Problems

How can I change the size of my menu font?
Start menu items do nothing
Get CrossOver Menu items to appear on Xfce

Sound

Troubleshooting Sound Problems

Video

Mesa 3D Graphics Library
Manually set the VideoMemorySize of your graphics card
How does Linux handle multiple monitors
Second monitor goes blank when starting a Windows application
How to manually disable CMST (Command Stream) in the registry

Bottles, Associations, Fonts

How can you map a document type to open in a native application?
Why do my CrossOver applications report time a hour faster or slower than my system?
How can I turn off anti-aliased fonts?
'Create Package from this Bottle' fails with no error message
How do I map a drive?
Enabling subpixel rendering/anti-aliasing in CrossOver
How to manually change file associations in a bottle
How can I get CrossOver to recognize new fonts added to a bottle?
Cannot open image files after installation of Office 2007
How to move bottles outside of ~/.cxoffice
Open .exe files with cxrun rather than cxinstaller
Control Panels are missing from a bottle

Virus Scan

Windows Virus Scans
Disable a Virus Scan on Linux

KDE issues

Crossover issues seg fault when installed from .bin file on KDE

Wine Installation Hangs Machine

CrossOver applications lose focus under KDE
CrossOver segfaults on KDE 4.8
Missing CrossOver XI menu icons on KDE
KDE 4.5 and earlier - Windows Applications Menu issues

Miscellaneous

How to upgrade my Steam bottle to Windows 7 and get rid of the XP warning
Will CrossOver work with my security patches? (grsec, libsafe, etc)
Using CrossOver over an NX session
Printing landscape still results in a portrait output
How can I run an application from the command line?
Mapping a Samba share to be writable by CrossOver
Applications installed within CrossOver in Virtual Box do not print
Mount a SMB file share to the filesystem so Crossover can access it
Note that these are not distributions we do any regular testing on.
How do I install CrossOver on ElementaryOS?
How do I install CrossOver on PCLinuxOS?
Does CrossOver work on Jolicloud Linux?
Enable Full Desktop Mode on an Eee PC

Deprecated Articles

Installing CrossOver on Linux x86_64 Distributions
KDE 4.5 and earlier - CrossOver and/or Windows Applications Menu issues
I am using KDE and the Windows Applications menu is missing
ClamAV claims vcredist_x86 contains a virus
'Broken pipe' or 'deprecated' errors
Attempt to unlock mutex that is not locked
Missing CrossOver XI menu icons on KDE
Older games with 4:3 aspect ratio are stretched in full screen
I am using KDE and the Windows Applications menu is missing
ATI initialization crash
How can I get my mouse wheel to work in CrossOver?
Apps in upgraded bottles fail with 'unimplemented function' error

Translations of this page:Français

Installing Wine

Before you install Wine, make sure that there is no previous Wine installation on your system, either from a package or from source. If you haven't yet installed Wine, you should be fine. Many Linux distributions come with an included Wine package, but due to Wine's rapid development rate these are usually old and often broken versions. It is best to uninstall your distribution's included package versions and update to the latest Wine version available here.

Links to binary packages for Wine for some of the major distros can be found at the WineHQ downloads page. In addition, full source code is available for both the current Wine development tree and every Wine release here. For help with installing from a package or from source, please consult the Getting Wine chapter of the User's guide.

How to help get applications working in Wine

If you want to help get an application working in Wine, the first thing you should do is register yourself in the AppDB and fill out a test report, so others know what works/doesn't work. Also, be sure to vote for your favorite application so developers know where to concentrate their efforts.

If the application that you want working is not listed in the AppDB there is an easy to use form available for you to add it. If the application is in the database, but lacks a maintainer, you should consider volunteering. If you are familiar with Wine, own a legal copy of the application, and have a desire to test it, help get or keep it working, and help other users, please apply by clicking the link in the application's page. Each application should have a supermaintainer, and, if different versions of the application are substantially different (such as in Adobe Creative Suite), each subversion should have a maintainer.

If you are the developer or publisher of the application, you obviously have a very big incentive to help get your application working under Wine. Fortunately, there are many options available to you other than reporting bugs and hoping someone will fix them. By far the easiest way is to file a bug at Bugzilla, along with a small testcase to add to the Wine test suite. Another options is to send copies of your software to Wine developers and hope they'll take an interest in getting it working. An alternative option, perhaps more effective, albeit expensive, is to pay Wine developers for their work on your application, either directly through a negotiated contract or indirectly by posting a bounty. CodeWeavers, a major Wine developer, offers a special section for pledges at their compatibility center website. The most direct method, however, is to help develop Wine itself and contribute code directly, which is exactly what Corel did for !WordPerfect several years ago. In any case, making a post on the Wine developers email list can go a long way.

If your application doesn't work

Wine Installation Hangs Mac Download

If your application experiences problems in a particular area, or fails to even run at all, there are a number of steps you can take to help us. The most important thing is to find out where exactly the application is failing. To diagnose application problems, the first step is to run the program from the console using Wine, rather than from a GUI shortcut. This will allow Wine to output error messages to the console, the understanding of which are key to solving the problem and getting the application to work.

An application may not work because Wine doesn't yet fully implement one of the DLL files the application is trying to use. If you encounter a DLL not found error, or see a lot of 'FIXME:' messages while running the application in Wine, this is likely the case. When this occurs, you can try using native (non-Wine) DLL files in place of Wine's builtin ones. Check the AppDB page for the program. There may be special configuration options or instructions for installing native DLL files there that you can try to get the application working. For further configuration help, please see the Running Wine section of the User Guide.

If the application still doesn't work, it's probably due to a bug or deficiency in Wine and we'd like to hear about it. Please see the reporting bugs page for instructions on how to best report bugs with applications. Alternatively, if you're a programmer, we'd really like it if you tried to help us directly; please check out the primary Developers page and the Developer Hints if you're interested.

If your application does work, but with some difficulty

Sometimes, applications run under Wine but don't function quite as smoothly as they do in windows. They may have display errors, a feature may be broken, or they may run unusually slow. These applications should receive a lower rating from their maintainers ('bronze' or 'garbage') in the Application's Database, depending on the degree of difficulty encountered.

If you have found a way to make an application work that is more complicated than simply installing it, please share that information by posting on the application's page in the database. If you are the maintainer for the application, please post the instructions in a 'howto' which will appear inside green bars at the top of the application's page.

Wine Installation Hangs Mac Pro

If your application used to work, but has since broken in a new version of Wine

Mac Hangs On Boot

Wine is a large and complex project, composed of many files written by different authors. Sometimes, an attempt to change a file and expand support for one application will unexpectedly cause another application to stop functioning. These changes are known as regressions, and they are unfortunately sometimes found in the Wine source code because the author of a patch that causes a regression is unaware of it. Since the Wine developers can't possibly test every application with every patch, we have to rely on the community to inform us of when regressions occur so that the problem can be easily identified and ultimately fixed. Without community involvement, regressions can go unfixed for potentially very long periods of time.

If your application has experienced a regression, please try and provide us with as much information as you can about when and how it broke. This allows us to isolate the exact thing we screwed up in the code and provide a fix. Please provide as much as you know about which version of Wine worked, and which version didn't, including the version number and how you installed it (from source, binary packages, etc.) Finally, please post these things in a bug.

Wine Installation Hangs Mac 2017

If possible, you should also try to isolate the exact patch which broke your application. This takes quite a bit of time, but minimal effort and computer skills, and it is the best way to get your application working again. When it comes to fixing regressions, the only thing more helpful to the Wine developers than knowing exactly which patch caused a regression is receiving a fix for the patch itself. For help with isolating problem patches, please see the documentation on Regression Testing.