Ubisoft Connect (UPlay, Ubisoft Game Launcher)

App uses auto-update.

Application Details:

Version: Latest
License: Free to use
Votes: 5
Latest Rating: Silver
Latest Wine Version Tested: 6.14-staging

Maintainers: About Maintainership

Link Official site Free Download Direct Link to Installer

Test Results

Selected Test Results

What works

Ubisoft Connect (formerly UPlay) installs, processes login

interface language changed

Install a game, Launch a game, uninstall a game.

What does not

Login stalls with an undrawn window outline (fixed with corefonts)

chat window opens but does not display anything but a circling wait prompt. Waited for a minute or two and closed the window.


winetricks corefonts workaround is required

What was not tested

buying / activating games.

Hardware tested


  • GPU: Intel
  • Driver: open source

Additional Comments

Test conducted in a VM, so the installed game was not expected to be playable. Only the fact that it starts was checked.

installer is UbisoftConnectInstaller.exe; size 149863048; md5sum is 93ab...4d8a

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
CurrentLinux Mint 20.2 "Uma"Aug 06 20216.14-stagingYes Yes YesSilverVladimir Bespalov 
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Jun 01 20205.9-stagingYes Yes NoPlatinumAdrian Avramescu 
ShowUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Feb 15 20205.1-stagingYes Yes YesGoldAdrian Kalla 
ShowDebian GNU/Linux Testing "bullseye"Nov 24 20194.20-stagingYes Yes NoPlatinumJacob Hrbek 
ShowFedora 30 x86_64Sep 14 20194.16Yes Yes YesSilverMicky 

Known Bugs

Bug # Description Status Resolution Other apps affected
3548 .lnk file is created on the desktop together with the program icon... NEW View
32342 Multiple applications and games using 'Webkit' or 'Blink' web browser engine crash on startup ('Arial' and 'Times New Roman' font face name validation) STAGED View
33673 UPlay 3.x/4.x slight lag on navigation with builtin gdiplus CLOSED ABANDONED View
34733 Fail to sync to the Uplay Cloud CLOSED DUPLICATE View
37915 Multiple games and applications need proper handling of Vista+ 'PROCESS_QUERY_LIMITED_INFORMATION' right (UPlay games, MS Visual Studio 2015 installer) CLOSED FIXED View
38067 Uplay launcher hangs on exit CLOSED ABANDONED View
38134 Uplay v5.x: can't log in (Uplay hangs with the login screen) CLOSED FIXED View
38523 Uplay launcher startup fails CLOSED INVALID View
39345 Ubisoft Uplay crash when Win version is set to Vista and > (libcef problem) UNCONFIRMED View
39870 Uplay crashes at start CLOSED DUPLICATE View
40271 Can't start UPlay: "Connection Lost" error CLOSED FIXED View
40980 Uplay launcher needs native Arial font or its replacement for launching CLOSED DUPLICATE View
41652 Uplay cannot connect/login to Server CLOSED FIXED View
43319 Steam Store/Uplay/Epic Games Launcher no longer display text in Windows 7 mode (libcef applications) CLOSED FIXED View
43326 Uplay (July 2017) needs dwmapi.DwmSetIconicLivePreviewBitmap CLOSED FIXED View
46120 Uplay hangs while filling in fields CLOSED FIXED View
46626 UPlay fails to start : "Error at hooking API LoadStringA" (UPlay's hooking engine can't handle ENDBR32 instruction inserted at non-hotpatch API entries due to distro build environments '-fcf-protection') CLOSED FIXED View
49006 Wrong detection the Windows' version by Ubisoft Connect UNCONFIRMED View

Show open bugs

HowTo / Notes

Required workarounds

install corefonts via winetricks - otherwise login screen would not show

winetricks corefonts

Wine versions before 4.7 failed on Fedora; Please use the latest winehq version

Optional workarounds

optionally install winbind or similar package that provides ntlm-auth to eliminate some warnings during startup

sudo apt-get install winbind       # for ubuntu/debian


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

2 Applications - please clearly separate
by oliver z. on Monday February 11th 2019, 12:41
For me, it seems like here are 2 applications involved. One is the current developed uplay version. Available on their homepage. And an very old, "legacy" uplay, which is not anymore developed ( means: no security updates! nor bugfixes).
When creating an entry, please clearly state what _exact_ version is used. The old crappy legacy one (which does not work with new content like anno 1800 beta), or the new one which is simply total incompatible to wine 4.0

The legacy one starts with corefonts installed. The new one just crashes with a wierd message and some bytes displayed.
Failing to use Uplay with Wine 3.20 Staging
by Benoît Smith on Thursday November 15th 2018, 18:39
Distro : Linux Mint 19. Wine version : 3.20 Staging.

Installing Uplay in a fresh prefix (with the Windows 7 default setup), then running it to show the login screen seems to run fine... Then, as soon as I strike a key to enter my Uplay username, the whole Wine desktop freezes to death. I tried a few times - same result.

Here is the whole output: (the last line is produced as the desktop freezes).
RE: Failing to use Uplay with Wine 3.20 Staging
by Vladimir Bespalov on Friday November 16th 2018, 2:24
Looks like it is 3.20 regression.
I`ve tested vanilla 3.20 and 3.19 in ubuntu 18.4; 3.19 works, 3.20 hangs.
launching uplay and getting past the log in screen
by grayson bills on Tuesday October 9th 2018, 22:19
i was wondering what can i do on a macbook pro to use and get past the bugs and all that usng wine and uplay
RE: launching uplay and getting past the log in screen
by Vladimir Bespalov on Wednesday October 10th 2018, 1:16
Well, you can start with installing wine-staging, winetricks, installing corefonts using winetricks - and trying to install and run uplay.
If it breaks on the way - you can try to collect the console output and post it here.
Updating my test data above (sorry if it's not the right place)
by Benoît Smith on Sunday October 7th 2018, 16:37
Installing Winbind fixed the following error:
"p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/ /usr/lib/i386-linux-gnu/pkcs11/ Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
002c:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution."
Also, I set the rasapi32 library as "native", which fixed some other errors.
However, that didn't fix the non-connection problem.
I read that it was declared fixed as of Wine 3.13 Staging. I wonder what's missing in my configuration to get Uplay work with Wine 3.17 Staging (since Linux Mint 17.3 is supposed to be based on Ubuntu 14.04).
Please feel free to move that comment where it belongs.
Uplay.exe crash
by Jussi Tawaststjerna on Thursday August 16th 2018, 19:06
ubuntu 18.04.1 64bit, wine-staging 3.13 (64bit, win7, dxvk 0.65)

bought far cry 3: blood dragon with steam and ran into uplay updating and then crashing. windows xp, legacy-uplay -> game launches but FPS is surprisingly low + slowdowns etc. wanted to test x64 + win7 + newer uplay. crash crash crash.

uplay installs but on launch it's "unrecoverable error", exits. i started to investigate the crash with strace to see what is happening, and ... ... it didn't crash....

running "strace -o /dev/null -e trace=network -f wine64 Uplay.exe" actually, slowly, gives me a Uplay login screen and login succeeds. everything after login works. slowly.

of course, game performance is total garbage as the strace slows uplay and the game's uplay-DLL's down significantly :) .... but it works.

posting this so that someone wiser than me might find this useful, perhaps.
RE: Uplay.exe crash
by Vladimir Bespalov on Saturday August 18th 2018, 2:15
Can you please try the follwing on the clean ubuntu system:
1) install cabextract and winehq-staging (see )
2) download winetricks ( see ) and install corefonts package
3) install latest uplay from

If that installation crashes for you - please post the crash logs (wine logs + debug.log from "Ubisoft Game Launcher" directory)
Maybe we can make something out of it.

Also can you please try to run FC3 independently from uplay launcher, to separate uplay-specific bugs from FC3-specific ones?

Thank you.
Got working
by Siren Watcher on Tuesday October 17th 2017, 7:33
So... Tried all the things below.

Set winecfg to XP.
Uninstalled current uplay. Downloaded & installed legacy uplay.
Tried setting cryptnet.dll to "native" in winecfg -> libraries.

Wouldn't work.

Got working with:
RE: Got working
by SoulEvan on Saturday October 28th 2017, 16:15
1. Install the ttf-mscorefonts over the applicationinstaller.
2. Use the Application "PlayOnLinux" to install the newest uplay client (64 Bit / Wine 2.19-staging).
3. Edit the Wine.cfg to Windows 10.
4. Start Uplay.
5. Enjoy
by Giovanni Ongaro on Monday September 4th 2017, 6:20
Previous FIX works for wine staging
by Giovanni Ongaro on Monday September 4th 2017, 6:18
Here is a quick fix for UPLAY
launch winecfg and set windows version to XP on uplay.exe uplayservice.exe uplaywebcore.exe
restart uplay it will say that the current version is not compatible and let you download the legacy uplay
launch wine uninstaller and disinstall current uplay
install legacy uplay
uplay WILL no more UPDATE
You should be able to login and play