Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Try exiting out of the Steam client and starting the launcher from the '..\SteamApps\common\Divinity Original Sin 2\bin\SupportTool.exe' executable.
If the launcher doesn't start from the executable, try deleting the config.xml file in the '..\Divinity Original Sin 2\bin' folder, as well as 'C:\Users\<UserName>\AppData\Local\LarianLauncher' (copy and paste %LocalAppData%\LarianLauncher into Windows Explorer to quickly open that folder).
After that, try verifying local files: in the Steam library, right click on the game and select Properties, switch to the Local Files tab and then click on the 'Verify Integrity of Game Cache...' button.
If that doesn't help, try reinstalling .Net Framework 4.
C:\Program Files (x86)\Steam\SteamApps\common\Steamworks Shared\_CommonRedist\DotNet
or
https://www.microsoft.com/net/download/dotnet-framework-runtime
If that doesn't at least get the launcher starting from the executable, there is also a Microsoft .NET Framework Repair Tool[support.microsoft.com], or if that doesn't help, Cleanup Tool[blogs.msdn.microsoft.com].
It is possible to bypass the launcher UI to get it to automatically start the Definitive Edition of the game.
In the Steam library right click Divinity: Original Sin 2 and select Properties, then switch to the General tab, click on the 'Set Launch Options...' button, paste in the line below and click Ok.
--rail_connect_cmd=
I had the same crash on launch issue and this is the only solution that fixed my issue. Thanks!
Also the Microsoft app store has a crash report reader (WinDbg preview), that helped me find the program causing the failure.