Tips on how you can try to get a Windows program to run under Crossover
The first place to start is searching our Compatibility Center database
to see if the program you're trying to install is listed there. Those app entry pages show if any other users have gotten the same program to run, and if so how functional it was. There could be more information under the Tips and Forums tabs of the app entry too.
Installing additional dependencies
Your Windows application may need additional libraries installed in order to run. Because there is no Windows OS in Crossover these libraries aren't already installed by default like they would be in a full Windows environment.
You can install dependencies the same way you install any Windows programs in Crossover. Click the Install a Windows Application
If you don't know exactly which dependencies you might need you can to do some guesswork based on the error messages your program is displaying. Very commonly needed packages include:
- Core Fonts
- Microsoft Visual C++
- Microsoft Visual Basic
- Microsoft XML Parser
- Windows OLE Components
- Internet Explorer 7
Select a dependency and then expand the Will install into..
section and choose the existing bottle you want to install into.
Advanced users can gather a debug log
of a misbehaving program to try and identify any missing components or incorrect settings. There are often errors in the logs referring to different libraries or frameworks and installing those components could help.
that in most cases our support staff will not be able to examine unsolicited logs for an unsupported program.
Adjust settings in Wine Configuration
The Wine Configuration tool allows you to make changes to bottle settings. This tool is quite powerful and incorrect settings may damage the bottle and require it to be deleted
and your program reinstalled.
The main troubleshooting steps that one can accomplish with Wine Configuration include:
- Changing DLL overrides (Libraries tab)
Crossover by default tries to handle all API commands your Windows program wants to use. Here you can force Crossover to pass the API commands to use a native Windows DLL instead. For example if your Windows application installs a custom DLL called SOMEAPP.DLL
you can add that DLL here and tell Crossover to default to using the native DLL instead of trying to translate the API command using Wine's replacement DLLs.
To add a new DLL type in the name of the DLL in the New override for library:
field and press Add
. You can also change existing overrides by selecting a DLL in the Existing overrides:
list and clicking Edit
. The Native
option uses the native Windows DLL and the Builtin
setting uses Wine's replacement.
- Emulate a Virtual Desktop (Graphics tab)
This makes any programs in the bottle display at a certain size. The effect is that a program will think that it's running full-screen, but it's actually running in a window on your desktop. This helps alleviate window management problems in some programs. Click on Emulate a virtual desktop
and set the desired size. Stick to a 4:3 aspect ratio like 800x600 or 1024x768.
- Map a new drive letter (Drives tab)
Crossover creates and maps three drive letters by default in each bottle. The C:
drive points to the root of the bottle, the Y:
drive to your home folder, and Z:
points to the root of your hard drive. External drives or removable drives like CDs, DVDs, and USB sticks are automatically generated a drive letter when mounted by the OS.
In some cases a program might want its CD/DVD mounted before it'll run as a type of copy protection. Here you can click Add
and choose the D:
drive and set it to be your CD/DVD.
Edit registry keys
Finally you can try editing the bottle's registry keys
and see if that has any effect.
This is mostly useful for games and if registry keys are needed they're often mentioned on the program's app entry