I play the game through steam using just the proton environment (not the native steam build) using the battle.net launcher. The game doesn’t launch post patch. Is the proton build not updated??? I haven’t had this issue before for a season. Super lame tbh.
+1 here. Luitris & ProtonGE latest.
Worked before battle.net update today.
It would appear Steam Deck is having the same issue so its a Proton problem for sure.
Why are you posting here? Blizzard does not support linux
Literally does lmao, do some reading.
Nope. Blizzard does not officially support linux. do some reading. This is also LITERALLY why there is no dedicated BNET app for linux. Nor are the games downloadable for linux. They have to be emulated. Therefore, there is no official suppot.
same here tried multiple proton/wine versions and repair game but didnt help
Same I think it’ll be fixed as the officially supported steam deck is also not working. I’m trying a fresh install atm.
At least its not “Error 37” ;D
Plz blibli, I wanna play :’(
debian 13. same problem
Same here, and seemingly with every other D4 user on Linux, be it steam deck or desktop.
The crash log also seems to be the same for most which is the following;
<BlizzardError.ProjectId>4
<BlizzardError.Summary:>
BREAKPOINT
<:BlizzardError.Summary>
<BlizzardError.Assertion:>
Thread 0x000007d4 "Main Thread" [Stack Base: 0x0000000000110000 Used Space: 24224/1048576 bytes]
DBG-ADDR<00006FFFFB024A05>("diablo_iv_loader.dll")
DBG-ADDR<00006FFFFA3E95C6>("diablo_iv_loader.dll")
DBG-ADDR<00006FFFFFF20B64>("ntdll.dll")
00006FFFFFF20E18 ntdll.dll RtlUserThreadStart+0
<:BlizzardError.Assertion>
<BlizzardError.DebugModules:>
DBG-MODULE<0000000140000000 03aba000 "Diablo IV.exe" "D:\Jenkins\Agent\static-workspace\cibuild-0\branches\3_1_0\bin\Release\Fenris_er.pdb" 0 {64306232-4d49-4716-92d57d14760a1cb3} 1 1782256640>
DBG-MODULE<0000000180000000 00002000 "sfc.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 4127465160>
DBG-MODULE<00006FFFF90C0000 0000c000 "netutils.dll" "" 0 {a0283386-7585-4e57-f8070cbfe6e1c52a} 1 1781817246>
DBG-MODULE<00006FFFF90E0000 00028000 "netapi32.dll" "" 0 {34de232f-bdeb-9336-4572be3289fa5354} 1 1781817246>
DBG-MODULE<00006FFFF9120000 00013000 "MSV1_0.dll" "" 0 {5f1ad7ab-8ff5-0675-b26d788335471888} 1 1781817246>
DBG-MODULE<00006FFFF9150000 0000e000 "Kerberos.dll" "" 0 {7ac40472-c361-904c-bb74918f47db7912} 1 1781817246>
DBG-MODULE<00006FFFF9170000 00023000 "Secur32.dll" "" 0 {79dbeb64-5142-cfa6-ae40a0ffbc9cdbf8} 1 1781817246>
DBG-MODULE<00006FFFF91B0000 0000c000 "sfc_os.dll" "" 0 {d14e92b0-d45d-fd7f-84ddd581babe28c1} 1 1781817246>
DBG-MODULE<00006FFFF91D0000 0001e000 "jsproxy.dll" "" 0 {6c13c6bd-209b-6f7b-661501c19af6787c} 1 1781817246>
DBG-MODULE<00006FFFF9200000 00048000 "WINHTTP.dll" "" 0 {2f0c56cf-5029-ad86-8838ce9d89b0bb0c} 1 1781817246>
DBG-MODULE<00006FFFF9260000 0000b000 "SensApi.dll" "" 0 {ffccd9a8-15ec-7d58-554c529c16a74585} 1 1781817246>
DBG-MODULE<00006FFFF9280000 00c23000 "vivoxsdk.dll" "C:\build\output\unity\vivox-sdk\artifacts\vivoxsdk\release_Win_x64_VS2019_Win7_nonlump\vivoxsdk.pdb" 0 {3ef670e8-ce00-498b-90cdc0fce1184d24} 1 1743609474>
DBG-MODULE<00006FFFF9EC0000 0007b000 "bink2w64.dll" "C:\devel\projects\bink\build\bink2w64.pdb" 0 {09236cfc-b3f4-4320-9e93e68c7b20eaf2} 1 1571776386>
DBG-MODULE<00006FFFF9F50000 00026000 "Tolk.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1650460376>
DBG-MODULE<00006FFFF9F90000 00010000 "WSOCK32.dll" "" 0 {c87700e3-0ba7-0e1a-91075a67f217fa34} 1 1781817246>
DBG-MODULE<00006FFFF9FB0000 0000c000 "XINPUT9_1_0.dll" "" 0 {4256077b-0ecc-71b3-e1db9e58cf15f315} 1 1781817246>
DBG-MODULE<00006FFFF9FD0000 0000d000 "wevtapi.dll" "" 0 {c604adfa-6123-f7cb-fe32a45def4838f6} 1 1781817246>
DBG-MODULE<00006FFFF9FF0000 00017000 "VCRUNTIME140.dll" "d:\agent\_work\1\s\\binaries\amd64ret\bin\amd64\\vcruntime140.amd64.pdb" 0 {727b4067-d5ac-4c1e-ae5ae565c1588ab6} 1 1569614034>
DBG-MODULE<00006FFFFA020000 00099000 "MSVCP140.dll" "d:\agent\_work\1\s\\binaries\amd64ret\bin\amd64\\msvcp140.amd64.pdb" 0 {ece81d3b-94b1-4a75-ba77e4e5ebc8735b} 1 1569614039>
DBG-MODULE<00006FFFFA0D0000 00052000 "CUESDK.x64_2015.dll" "C:\projects\Corsair SDK Lighting Effects Windows\WorkingDirectory\build-RelWithDebInfo\2015\src\win_x64\CUESDK_x64\RelWithDebInfo\CUESDK.x64_2015.pdb" 0 {273eb5bc-af1b-41ed-b17dd83f8a8f0978} 1 1545058627>
DBG-MODULE<00006FFFFA140000 02340000 "diablo_iv_loader.dll" "D:\Jenkins\workspace\eidolon-generator_main\fen_retail_workspace\__build\vs2022\RelWithDebInfo\loader.pdb" 0 {7fc81e0d-1818-fcfc-4c4c44205044422e} 1 1772221093>
DBG-MODULE<00006FFFFC4B0000 0015f000 "COMCTL32.dll" "" 0 {171169ce-01b7-7921-947ab212cedf1630} 1 1781817246>
DBG-MODULE<00006FFFFC6C0000 00012000 "HID.DLL" "" 0 {6d3f0b62-1ab5-de9f-1c820593ee3a5518} 1 1781817246>
DBG-MODULE<00006FFFFCC80000 0000e000 "dwmapi.dll" "" 0 {3a3703c9-94fd-186a-0c5a1d3d53a6a22c} 1 1781817246>
DBG-MODULE<00006FFFFCFA0000 00027000 "msacm32.dll" "" 0 {b756aab7-8ab7-c14b-95bd93549590896d} 1 1781817246>
DBG-MODULE<00006FFFFCFE0000 000c9000 "WINMM.dll" "" 0 {4b2d55e4-2313-bb77-21d4d24935d8eff2} 1 1781817246>
DBG-MODULE<00006FFFFD7A0000 0009e000 "dbghelp.dll" "" 0 {9eecc000-dec7-8496-9eb96e6a667f2404} 1 1781817246>
DBG-MODULE<00006FFFFDA50000 00030000 "WINTRUST.dll" "" 0 {2d8e7a3b-1489-cec4-ad4f75363aab241b} 1 1781817246>
DBG-MODULE<00006FFFFDA90000 0000d000 "VERSION.dll" "" 0 {8f35e10d-93d5-30ec-471d81ff5b74a298} 1 1781817246>
DBG-MODULE<00006FFFFDCB0000 0001e000 "bcrypt.dll" "" 0 {84a715a6-3109-9c32-022e5d1588fe0880} 1 1781817246>
DBG-MODULE<00006FFFFDCE0000 000ef000 "CRYPT32.dll" "" 0 {6df1445c-966c-89a6-214020eb594c2f88} 1 1781817246>
DBG-MODULE<00006FFFFE210000 0000b000 "PSAPI.DLL" "" 0 {dfd1194b-0fe8-d56f-90499e79c9ec8909} 1 1781817246>
DBG-MODULE<00006FFFFE230000 000ef000 "OLEAUT32.dll" "" 0 {c09b57dc-a584-c498-1baabea317f37a75} 1 1781817246>
DBG-MODULE<00006FFFFE5B0000 0001c000 "coml2.dll" "" 0 {2982fa9f-8228-d803-a80f4fb5b60db70b} 1 1781817246>
DBG-MODULE<00006FFFFE5E0000 00057000 "combase.dll" "" 0 {8f63b3f4-4e3a-4370-503b6944930724ca} 1 1781817246>
DBG-MODULE<00006FFFFE650000 000c7000 "ole32.dll" "" 0 {fbc1cd67-533a-789f-e327849f3e87be5c} 1 1781817246>
DBG-MODULE<00006FFFFE730000 0001a000 "shcore.dll" "" 0 {2d9ea117-1493-f0e6-a8c92cfc36d07d1e} 1 1781817246>
DBG-MODULE<00006FFFFE760000 00058000 "SHLWAPI.dll" "" 0 {3154ebef-7fd4-9c24-ab913d3a6343201c} 1 1781817246>
DBG-MODULE<00006FFFFE7D0000 00962000 "SHELL32.dll" "" 0 {24115ada-0a24-71da-69a5f01848aff783} 1 1781817246>
DBG-MODULE<00006FFFFF240000 0000e000 "nsi.dll" "" 0 {ada39084-30e9-be54-5f60903906a2dc46} 1 1781817246>
DBG-MODULE<00006FFFFF260000 00017000 "dnsapi.dll" "" 0 {97f2959f-71af-7645-c7a686b8aa55cdab} 1 1781817246>
DBG-MODULE<00006FFFFF290000 00035000 "iphlpapi.dll" "" 0 {0919e4d6-e72d-5375-4ff6a516b9e424dc} 1 1781817246>
DBG-MODULE<00006FFFFF350000 00021000 "IMM32.dll" "" 0 {e7291b46-9625-cc17-65a50fe5a1d8768a} 1 1781817246>
DBG-MODULE<00006FFFFF390000 0003a000 "win32u.dll" "" 0 {b8c14d5c-bf59-287c-57fa9a969ffb2277} 1 1781817246>
DBG-MODULE<00006FFFFF3E0000 00099000 "gdi32.dll" "" 0 {3266e7b6-bfe0-7700-0bf71e752a189126} 1 1781817246>
DBG-MODULE<00006FFFFF490000 001e5000 "user32.dll" "" 0 {cb752b1e-42e8-a456-34cffc5838340e15} 1 1781817246>
DBG-MODULE<00006FFFFF760000 00092000 "SETUPAPI.dll" "" 0 {956cb70c-509d-3a58-fe8243dd387a32b8} 1 1781817246>
DBG-MODULE<00006FFFFF810000 0002c000 "ws2_32.dll" "" 0 {0733bb81-751e-2257-5ebb72442a6f2999} 1 1781817246>
DBG-MODULE<00006FFFFF850000 00025000 "sechost.dll" "" 0 {3dfbc25d-2470-c4ef-10b40e77dd9f95f1} 1 1781817246>
DBG-MODULE<00006FFFFF890000 000fc000 "ucrtbase.dll" "" 0 {ab630a45-2faf-f4ad-d8b8dcc49f4255fa} 1 1781817246>
DBG-MODULE<00006FFFFF9A0000 0000e000 "cryptbase.dll" "" 0 {b3163dc6-0d98-c20a-009e0e7e22f9cdb2} 1 1781817246>
DBG-MODULE<00006FFFFF9C0000 00096000 "rpcrt4.dll" "" 0 {6b10e371-496c-e1fa-ebcc93747b617020} 1 1781817246>
DBG-MODULE<00006FFFFFA70000 000c7000 "msvcrt.dll" "" 0 {1747efea-73a4-267c-9adaecc30a21c2c7} 1 1781817246>
DBG-MODULE<00006FFFFFB50000 00043000 "advapi32.dll" "" 0 {d96555b3-aacd-b6ed-5e9b0b2ccdd4a0de} 1 1781817246>
DBG-MODULE<00006FFFFFBB0000 002ce000 "kernelbase.dll" "" 0 {4d8a7156-3e43-1331-9d74a9c80d0302f8} 1 1781817246>
DBG-MODULE<00006FFFFFE90000 0006a000 "kernel32.dll" "" 0 {246c56aa-2a35-c51d-74741277d46ecf3b} 1 1781817246>
DBG-MODULE<00006FFFFFF10000 000d7000 "ntdll.dll" "" 0 {eb49a596-51c4-e00b-4fa05d0ab979eedd} 1 1781817246>
<:BlizzardError.DebugModules>
<BlizzardError.HashBlock:>
DBG-OPTIONS<FunctionsOnly>
DBG-ADDR<00006FFFFB024A05>("diablo_iv_loader.dll")
DBG-ADDR<00006FFFFA3E95C6>("diablo_iv_loader.dll")
DBG-ADDR<00006FFFFFF20B64>("ntdll.dll")
DBG-ADDR<00006FFFFFF20E18>("ntdll.dll")
DBG-OPTIONS<>
<:BlizzardError.HashBlock>
Same here. Steam, Mint 22.3. Worked before the update. Not launching after.
Excerpt from crash.txt, which might or might not be relevant
<BlizzardError.Assertion:>
Thread 0x00000564 “Main Thread” [Stack Base: 0x0000000000120000 Used Space: 22480/1048576 bytes]
DBG-ADDR<00006FFFFBF24A05>(“diablo_iv_loader.dll”)
DBG-ADDR<00006FFFFB2E95C6>(“diablo_iv_loader.dll”)
DBG-ADDR<00006FFFFFF4F8C0>(“ntdll.dll”)
00006FFFFFF4FB78 ntdll.dll RtlUserThreadStart+0
<:BlizzardError.Assertion>
All crash.logs are identical aside the thread ID.
For me battle.net behaves like this:
Play
↓
Launching
↓
Playing
↓
Play
No game window ever appears.
Things that still work
-
World of Warcraft launches normally.
-
Diablo II: Resurrected launches normally.
-
Battle.net itself works normally.
-
Scan & Repair reports no problems.
What I’ve tried
-
Scan & Repair
-
Checked for updates
-
Rebooted
-
Latest system updates (
pacman -Syu) -
Tested multiple runners:
-
Proton-CachyOS Latest
-
GE-Proton Latest
-
Proton-EM Latest
-
UMU-Proton Latest
-
DW-Proton Latest
-
All behave exactly the same.
Battle.net logs
Battle.net successfully launches Diablo IV:
LaunchBinary: uid=fenris
Launched .../Diablo IV.exe
pid: ####
It then reports the game as running for roughly 9 seconds before:
Game is no longer running: fenris
Game finished versioning fenris
Proton logs
DXVK initializes for Battle.net normally.
There are no VKD3D errors, no Vulkan errors, and no Wine crash dialog.
It appears Diablo IV.exe exits before graphics initialization.
EDIT: If someone has found a workaround it would be a good time to share 
Crossover on Mac also seems to be having issues, having the same launch issue.
Same here, as is everyone else in Linux - Will Not Start After Latest Patch - #30 by Psyolia-21243 - Technical Support - Diablo IV Forums
I have the same problem
Well i am in the same boat. nothing i try is working,
I mean - they do - Steam Deck verified game.
It’s steam deck verified, if you don’t know what it means don’t pretend you do.
It clearly shows you are posting about things you are totally clueless about, makes no sense.