Category: Main Games Tom Clancy's The Division UPlay 1.8.3

Tom Clancy's The Division

No Screenshot

Submit Screenshot

Latest version available.

Application Details:

Version: UPlay 1.8.3
License: Retail
Votes: 0
Latest Rating: Gold
Latest Wine Version Tested: 4.3

Maintainers: About Maintainership

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

This is an update that supersedes my test results from February 26th, 2019.

These test results are for The Division, ver 1.8.3 on uplay.

I only tested Singleplayer gameplay and the Underground DLC as singleplayer.

What does not

Installation of the uplay client requires corefonts to be installed. Otherwise there is only a transparent uplay client window.

The in-game overlay crashes the game when it tries to login to the Ubisoft servers when loading.


This is the way that worked for me

1. Make a new separate prefix for The Division only. I called it wine-division-64

2. From now on do every step below pointing wine to this prefix with
WINEPREFIX=$HOME/.wine-division-64 (or whatever you called your prefix)

3. Install corefonts and the latest dxvk with winetricks

4. Install the uplay client, start it from the commandline and point it to your existing The Division installation, otherwise download and install The Division.

5. Disable the in-game overlay in the uplay client. Otherwise the game might crash when it tries to login to the Ubisoft servers

6. Start The Division with the uplay client

7. When you start the uplay client from command line and clicked on "Play The Division" and see the following output on the command line and the command line output stops there:

01b2:fixme:heap:RtlSetHeapInformation 0x6d0000 0 0x22e740 4 stub

and The Division does not start within 30 to 60 seconds after you clicked on start, then it just hangs somewhere.
In this case kill the TheDivision.exe process and start it again with the uplay client.

On wine 4.3 this happened to me 3 or 4 times before The Division finally started.

8. Occasionally when I quit the division it does not terminate correctly with

"017f:err:ntdll:RtlpWaitForCriticalSection section 0x7fc5e3698ec8 "?" wait timed out in thread 017f, blocked by 0114, retrying (60 sec)"

showing up in the console.

This line gets repeated every 60 seconds.

In that case I could only Ctrl-Alt-F2 to a new console and kill the TheDivision.exe process from there.

What was not tested

Anything related to multiplayer gameplay.

Hardware tested


  • GPU: AMD
  • Driver: open source

Additional Comments

Once there is sufficient date in the dxvk-cache I do not see a difference compared to an installation on windows.

System information

- AMD FX 8320
- AMD Radeon RX580
- amdgpu open-source driver

- openSUSE Tumbleweed 20190301 64-bit
- Kernel 4.20.12-1-default
- Mesa 18.3.4 with LLVM 7.0.1
- Plasma 5.15

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
CurrentopenSUSE Tumbleweed (rolling release)Mar 04 20194.3No, but has workaround Yes YesGoldFreigeist 
ShowopenSUSE Tumbleweed (rolling release)Feb 26 20194.2-stagingNo, but has workaround Yes YesGoldFreigeist 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs