Category: Main Games osu! Stable


osu! builds from the Stable release stream.

Stable is the most recent version of osu! that is not on test phase. It currently renders through OpenGL 3.x, that allows Wine to get the same performance as on Windows. It needs .NET Framework 4.5+ to work.

There are also Beta and Cutting edge release streams that allow to test the latest development features. However they change frecuently and older versions of them get rapidly obsolete. Its compatibility level on Wine is currently the same as Stable.

Application Details:

Version: Stable
License: Free to use
Votes: 5
Latest Rating: Gold
Latest Wine Version Tested: 3.18-staging

Maintainers: About Maintainership

Free Download Direct download link Free Download Download osu!

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

  • Installing the game with the new installer.
  • About all in-game functions
  • Playing using huion 420 and mouse.
  • Compatibility mode (which is DirectX).

What does not

  • Starting the game with shift held. Doesn't register it. (Not that it's an issue, I didn't find any gamebreaking issues.)


What was not tested

  • osu! supporter features.
  • Older installer.

Hardware tested


  • GPU:
  • Driver:

Additional Comments

The installer requires dotnet40. Try using winetricks. Please note that the Compatibility Mode may increase delay and framerate, even on Windows machines. It's even mentioned in the game itself to warn players. There were no issues with latency, but please keep in mind I used a low latency kernel (it should be alright on the generic kernel aswell).

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Oct 20 20183.18-stagingYes Yes YesGoldPham Truong Thanh Trung 
ShowUbuntu 18.10 "Cosmic" amd64 (+variants like Kubuntu)Nov 17 20183.0.3Yes Yes YesSilverCONBlaze 
ShowLive Wifislax 1.1Sep 02 20183.14-stagingYes Yes YesSilverEne 
ShowArch Linux x86_64Aug 05 20183.13Yes Yes YesGoldInvictus Tiberius 
ShowUbuntu 17.04 "Zesty" amd64 (+ variants like Kubuntu)Nov 08 20172.20Yes Yes YesGoldInvictus Tiberius 

Known Bugs

Bug # Description Status Resolution Other apps affected
30941 Could not install osu! using wine-mono UNCONFIRMED View
35568 Osu! fails to install (crash during post-installation in LSA SID translation/.NET runtime) NEW View
44184 osu!: installer stuck in a loop UNCONFIRMED View

Show all bugs

HowTo / Notes


Last update: 2018-06-12.

Please follow carefully these steps in order to successfully install and run osu!

This guide explains detailedly How to install osu! manually (without front-ends like PlayOnLinux), step by step. You should also check the Franc[e]sco's guide if you want to perform a more optimized-convenient installation.

Note: remember to keep Wine up to date. "$HOME" is an equivalent to "/home/«your_user_folder»/".

This section explains how to install Stable, Beta, Cutting Edge and Lazer versions. If you want to run Fallback, or even older versions, please read its own guide here.

1) Create a new Wine prefix (if you don't want to use your default prefix):

$ env WINEPREFIX=$HOME/.wineosu wineboot --init

If Wine prompts for installing Mono, click Cancel.

2) Download winetricks (it will make .NET Framework installation a lot easier):

$ wget  ''
$ chmod +x ~/winetricks

3) Install .NET Framework 4.6.2 (and optionally install "corefonts"):

$ env WINEPREFIX=$HOME/.wineosu ~/winetricks dotnet462 corefonts

4) Download and install osu!:

  • Stable version (Beta and Cutting edge must be selected at osu!'s Options menu after Stable is installed):
  • $ wget '!install.exe'
    $ env WINEPREFIX=$HOME/.wineosu wine 'osu!install.exe'

    It's highly recommended to change the installation path to "C:\osu" so you can easily find osu! files later. Then you will find them on '$HOME/.wineosu/drive_c/osu!'. Make sure to use only ASCII characters for the path to avoid installation problems.

    BUG 44184: there's currently a bug that doesn't allow osu! to start. The installer will restart endlessly every few seconds. To resolve this simply close the installer and create an empty file called "discord-rpc.dll" at osu!'s installation folder. Then osu! will start normally.

  • Lazer version:
  • osu!lazer can't be installed using its default installer because it needs non-administrator privileges. Instead, download the "osulazer-full.nupkg" file from and extract it inside your wine-prefix's drive_c. The last version that seems to be working is 2017.1124.0.

5) Creating a shortcut: 

If osu! didn't create a shortcut after setup, try first launching the game from terminal:

$ env WINEPREFIX=$HOME/.wineosu wine 'C:\osu!\osu!.exe'


  • env WINEPREFIX=$HOME/.wineosu is the path of your wine-prefix (if you didn't modified this, don't worry about)
  • 'C:\osu!\osu!.exe' is the path (inside your wine-prefix) where osu! is installed.

If you didn't changed anything when executed 'osu!install.exe', the command line should look like this:

$ env WINEPREFIX=$HOME/.wineosu wine 'C:\Users\«your_user_name»\Local Settings\Application Data\osu!\osu!.exe'

Set «your_user_name» to your current user name on your Linux/Unix host system.

Once you can launch the game, you can create the shortcut. Create a new text file and put the following:

[Desktop Entry]
Exec=env WINEPREFIX=$HOME/.wineosu wine "C:\\Users\\«your_user_name»\\Local Settings\\Application Data\\osu!\\osu!.exe"

You have to change single quotes ' ' to double quotes " " and append an extra inverted-slash \ to the existing ones.

Save this file as 'osu!.desktop'. Now you can double-click on it to open osu! (you can also set an icon for the shortcut later).

Usual workarounds to improve ingame experience

Last update: 2018-03-14.

Select ALSA driver for Wine: it slightly reduces the audio latency:

$ env WINEPREFIX=$HOME/.wineosu winetricks sound=alsa

If you need PulseAudio again:

$ env WINEPREFIX=$HOME/.wineosu winetricks sound=pulse

Installing low-latency Linux kernel:

  • Reduces drastically the audio latency.
  • Fix beatmap thumbnails freezing the game.
  • Fix game freezing when selecting songs too fast.

On Ubuntu-based distros you can use:

$ sudo apt install linux-lowlatency

If you want to revert to generic kernel:

$ sudo apt install linux-generic

Installing GDI+: it fixes some graphical glitches but also prevents CJK fonts to be displayed correctly (this is not necessary and does not affect in any way to Lazer version).

Beware that GDI+ installer is big! (more than 500mb). You can instead grab a copy of gdiplus.dll from a Windows 7 installation and copy it to your Wine prefix, and then add manually a Native override for gdiplus.

$ env WINEPREFIX=$HOME/.wineosu winetricks gdiplus

Open winecfg:

$ env WINEPREFIX=$HOME/.wineosu winecfg

Go to Libraries tab and verify if there's an override for gdiplus. It not, add gdiplus and set it to Native. Close all dialogs by clicking OK.

Install corefonts and cjkfonts: It fixes chinese/japanese/korean characters no displaying correctly:

$ env WINEPREFIX=$HOME/.wineosu winetricks corefonts cjkfonts

The installation of cjkfonts might fail due to outdated links to Takao and Baekmuk fonts. Use the commands below to download them from another source and copy them automatically:

$ wget ''
$ mv ./ $HOME/.cache/winetricks/takao/
$ wget ''
$ mv ./fonts-baekmuk_2.2.orig.tar.gz $HOME/.cache/winetricks/baekmuk/ttf-baekmuk_2.2.orig.tar.gz

$ env WINEPREFIX=$HOME/.wineosu winetricks corefonts cjkfonts

Open winecfg:

$ env WINEPREFIX=$HOME/.wineosu winecfg

Go to Libraries tab. If there is an override for gdiplus, set it to Builtin then Native. Close all dialogs by clicking OK.

About GDI+ and CJKFonts: beware that if you change gdiplus override to Native then Builtin, graphical glitches will be fixed but CJK fonts will not be displayed correctly. On the other hand, if you set gdiplus override to Builtin then Native, CJK fonts will (mostly) show correctly, but some things will be not visible, like some simbols in the Options menu.

Other known problems:

  • Alt+tab doesn't work when Fullscreen is enabled: if you can't use Alt+Tab hotkey, disable Fullscreen mode ingame. osu! doesn't need Fullscreen on Linux because graphical latency will be the same as Windowed (However, on KDE Plasma 5, Alt+Tab when Fullscreen is enabled always work, so you don't need to worry about that).
  • My system is frozen!: this is more common on Unity desktop when you press the "Alt" key when Fullscreen is enabled. It also happens sometimes when you select maps very fast. Press Ctrl+Alt+F1 (to enter to a tty) login and enter the following to force closing osu!:
    $ pkill osu

    Press Ctrl+Alt+F7 to return to your desktop environment.

  • I started osu but my cpu usage is at 100% and nothing happens: same as frozen system. Open a terminal and execute pkill osu command.
  • I can't switch to Windowed mode from Fullscreen/Borderless/Letterbox: on KDE Plasma, you can't select Windowed mode if you started the game on Fullscreen/Borderless. Close the game and go to your osu! folder. Open the osu!.«user».cfg file, find the "Fullscreen" and "Letterboxing" options and set them to "0", then find the "Width" and "Height" options and set them to a value lower than your monitor's resolution:
    Fullscreen = 0
    Letterboxing = 0
    Width = 800
    Height = 600

Please leave us a comment in Comments section below if you still have problems installing or running osu!.

Rules for filing a Test Result report

Last update: 2017-11-29.

We need some minimum information to consider a report usefull. Reports not following the next rules will be rejected:

  • What works? Mention at least 5 things that you're sure that work fine (of course, if the game runs, otherwise simply set app's rating as Garbage).
  • What does not work? Mention only things that you're sure that don't work right.
  • Workarounds. Mention whatever you did in order to get osu! working, regardless it is on the Installation guide or not. Vanilla Wine only. If you used PlayOnLinux, don't fill a report here. If the game doesn't work properly for you but you didn't followed the Installation guide carefully, your report will be rejected.
  • What was not tested? Mention only things that you don't tested or tested so slightly that is irrelevant. Is also valid to say something like "Only working/not working things were tested" if you think that you skipped too many things.
  • Additional Comments. Mention at least the exact osu! build number you tested. It can be found inside the game just at the end of the Options menu. It usually looks like b20171106.5 or 2017.1030.0. It can also be found on "osu!.«user».cfg" file (find the LastVersion value).
  • English please (of course).


  • Don't rate the game as Platinum. We know that osu! doesn't work without workarounds :)  (in other words, put every detail you can if you are really rating the game as Platinum).
  • On Additional Comments, add any extra comment you want to add to the report, like specific system configuration , benchmarks, etc. If you did a test on many PCs with different systems, also mention them.
  • Please fill Hardware tested fields correctly. Leaving this as Unknown is not really useful. (However, if you can't find any information about your hardware, leave it as Unknown).
  • As more detailed the report, the better. However, avoid putting long list of debug/log information. Fill a bug report on Bugzilla instead.
  • Remember to follow the Installation guide, step by step, before considering that you've failed to get osu! running. This is important because the guide has been designed to work for any system.
  • If you only want to mention a specific thing instead of write a detailed report, leave a comment on Comments section. We will be warned about it by the system.

For more information about how to fill a report, see AppDB Test Results Guidelines.

If osu! Doesn't Recognize Your Internet Connection

If osu! doesnt't recognize internet connection and you have internet connection, install 32-Bit GNUTLS Package. In Arch Linux,

sudo pacman -S lib32-gnutls


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Gnome intellihide panels showing up
by André on Friday November 9th 2018, 11:23
On gnome desktop, sometimes (randomly) when i alt+tab the game, both panels (that were set to intellihide) were showing up if i touch the edge of the screen. To fix this just run the game on a virtual desktop with your fullscreen resolution.
Game is laggy and crashes.
by Robert on Thursday August 2nd 2018, 11:01
Everything was going well up until today when I wanted to play osu!, and it has a lot of lag spikes which make it unplayable. A few seconds into a map, or even barely loading the map, the game crashes.
RE: Game is laggy and crashes.
by Robert on Thursday August 2nd 2018, 11:22
Since I play osu! on a Seagate Expansion Drive, I thought of the fact that the USB was loose. So, I retightened it and it works perfectly! :)))))))))))))
New bug?
by Ena on Sunday June 3rd 2018, 12:21
I followed the instructions above and osu downloaded and installed properly, but on the first open it displays a message saying "osu was unable to obtain a graphics context. If this is the first time you've seen this please try restarting your PC. If this is a fresh install, you may be missing graphics drivers."
After you click ok, a window will pop up; its called "oh no!" and it will display the error (shown below):

#=z1U64elhN$6ScXutjLe68OMafNiDW: No available GL context found. ---> OpenTK.Graphics.GraphicsContextException: Failed to initialize EGL, error BAD_ALLOC.
at OpenTK.Platform.Egl.EglWindowInfo..ctor(IntPtr handle, IntPtr display, IntPtr surface)
at OpenTK.Platform.Egl.EglAnglePlatformFactory.CreateWindowInfo(IAngleWindowInfoInternal window_info, Int32 major, GraphicsContextFlags flags)
at OpenTK.Platform.Egl.EglAnglePlatformFactory.CreateGLContext(GraphicsMode mode, IWindowInfo window, IGraphicsContext shareContext, Boolean directRendering, Int32 major, Int32 minor, GraphicsContextFlags flags)
at OpenTK.Graphics.GraphicsContext..ctor(GraphicsMode mode, IWindowInfo window, IGraphicsContext shareContext, Int32 major, Int32 minor, GraphicsContextFlags flags)
at #=zN5FEz26lyeeReWfdrjnq99Map8xE.#=zegPSY_c=(Int32 #=zbrLuJSw=, Int32 #=zxzJ1FKg=, GraphicsContextFlags #=zzeNMliw=)
at #=zl1FmSAdVU5XcZFWz2wwT96w=.#=zh4G6cmQDc_G1(GraphicsContextFlags #=zzeNMliw=)
--- End of inner exception stack trace ---
at #=zl1FmSAdVU5XcZFWz2wwT96w=.#=zh4G6cmQDc_G1(GraphicsContextFlags #=zzeNMliw=)
at #=zl1FmSAdVU5XcZFWz2wwT96w=.#=zh4G6cmQDc_G1(GraphicsContextFlags #=zzeNMliw=)
at #=zl1FmSAdVU5XcZFWz2wwT96w=.#=zh4G6cmQDc_G1(GraphicsContextFlags #=zzeNMliw=)
at #=zl1FmSAdVU5XcZFWz2wwT96w=.OnHandleCreated(EventArgs #=z_Pvg3ZA=)
at #=zYTfEQdWXPSgMtNA4bKQNAjWhu_TZ.OnHandleCreated(EventArgs #=z_Pvg3ZA=)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmCreate(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at #=zekbVG2TReeQyJ70gKx_9C2k=.WndProc(Message& #=z_sw5Hvg=)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The update log looks like this:

6/3/2018 5:17:47 PM: Running repair (False)
6/3/2018 5:17:48 PM: Force update requested
6/3/2018 5:17:49 PM: CallbackStatus updated to Checking
6/3/2018 5:17:49 PM:
6/3/2018 5:17:49 PM: Beginning update thread
6/3/2018 5:17:49 PM: Stream: Stable40
6/3/2018 5:17:49 PM:
6/3/2018 5:17:49 PM: Running cleanup..
6/3/2018 5:17:49 PM: Cleanup successful!
6/3/2018 5:17:49 PM: Requesting update information...
6/3/2018 5:17:50 PM: discord-rpc.dll: CHANGED (cached)

I have version 3.0.1.
RE: New bug?
by Invictus Tiberius on Tuesday June 12th 2018, 8:44
Hi. This usually happens when there's no graphics hardware available. Verify you have correctly installed graphic drivers. I can't replicate this on my PC, so search for some info on google. You can also check Franc[e]sco's guide; he updated the guide some time ago and it is very complete.
Crashes when type korean characters in game
by Ian Snyder on Thursday May 3rd 2018, 1:05
osu! freezes when I type any Korean characters on osu! settings and beatmap search. However, It didn't freeze in bancho.
I'm using Ubuntu 18.04 LTS and Wine 3.0 from ubuntu repository.

Have any idea of this problem?
fixes graphical & font glitches
by osaka-takumi on Wednesday May 2nd 2018, 11:11
install Windows fonts on Linux
Please delete the internal font folder of wine
Otherwise font glitches will not be Fixed.
gdiplus override to Native, graphical glitches & CJK fonts will be fixed

by bbadadadadad bitch on Thursday April 26th 2018, 16:08
ssssorry nevermind got it aaa
cant get framework
by bbadadadadad bitch on Thursday April 26th 2018, 16:06
whenever i try to dowloaded it just fails on me, of course i open the dowloader on wine but since the machine i have doesnt work with it, cant seem to have it.
by osaka-takumi on Thursday February 22nd 2018, 5:44
osu!direct is very goood working
osu install problem
by Supashake YT on Wednesday February 21st 2018, 23:35
When I the osu installer is downloading osu, after the download countdown for what folder you want to put it in is done, it says 'An error occurred, please check you internet connection' even though my internet connection is fine

by Howard Zhang on Sunday January 21st 2018, 9:57
How do I launch it. Running osu!.exe doesn't work
RE: How to launch the game
by Invictus Tiberius on Sunday January 21st 2018, 11:42
Hi. osu! should create a shortcut when installing but if it is not your case, use the following command:

$ env WINEPREFIX=$HOME/.wineosu wine 'C:\«path_to_the_game»\osu!.exe'

Where "$HOME/.wineosu" is the absolute path to your wine-prefix and 'C:\«path_to_the_game»\" is a folder inside the wine-prefix where osu! is installed.

Be sure you followed all the guide to get it properly installed (I checked all steps for Wine 3.0-rc6 and it is working). Please leave us another comment if you are still in trouble.
RE: How to launch the game
by Howard Zhang on Monday January 22nd 2018, 20:16
Hey it did create a shortcut in the folder where osu! was installed. But when I click it, my mouse does the spiny thing and then it just stops.

And I didn't quite understand the command line. so do I put env WINEPREFIX=$HOME/.wineosu wine "c:\home/Umbryft/.wineosu/dosdevices/c:/users/Umbryft/Local Settings/Application Data/osu!\osu!.exe
RE: How to launch the game
by Howard Zhang on Monday January 22nd 2018, 20:22
I just checked task manager and it says it's running, but it doesn't pop up. But I should also tell you that after initial installation, osu ran fine. It was only after I closed it out it wouldn't pop up again. I would usually just use the env WINEPREFIX=$HOME/.wineosu wine 'osu!install.exe' command to get it up and running again but it stopped working so I don't know.

P.S. I forgot to add this in my last comment and I don't know how to edit it so I'm just adding It here I hope you don't mind hx.
RE: How to launch the game
by Invictus Tiberius on Wednesday January 24th 2018, 11:15
Hi, sorry for answering late. I updated the guide by adding an additional step explaining How to create a shortcut for osu! I hope it would be useful. If you can't still launch osu!, ask again. Anyways, I will try to explain some details here:

env WINEPREFIX=$HOME/.wineosu
Wine use this part to know what folder on your file system will be used as the "C:\" unit. Remember that Wine needs to "emulate" a Windows-like environment for your applications.

wine 'C:\Umbryft\Local Settings\Application Data\osu!\osu!.exe'
Inside the indicated "C:\" unit folder, Wine will execute the program that match to the indicated path, in this case, "osu!.exe". When using a terminal, you can put that path inside single quotes ' ', but in a ".desktop" shortcut, you need to use double quotes " " and append an additional inverted slash "\" to the existent:

env WINEPREFIX=$HOME/.wineosu wine "C:\\Users\\Umbryft\\Local Settings\\Application Data\\osu!\\osu!.exe"