Did you try GE 10.3 as reported in #8848 ?

I didn't tried it, but I don't think GE 10.3 would help me, since in JP release, the game will not even open any window, while #8848 (global release) says at least window will open and can see Cygames logo.

Tried

• GE-Proton10-4
• GE-Proton10-3
• GE-Proton10-8
• proton10.0-1 (beta)
• Experimental
• Hotfix
• Adding japanese fonts into the drive_c/windows/Fonts folder
• Adding environmental variables: LC_ALL=ja_JP.UTF-8 TZ=Asia/Tokyo
• Launching the game while connected to japanese vpn and without

linux: 6.15.2.arch1-1
nvidia GTX 1060 6 GB
nvidia-dkms: 575.57.08-3

full log without any modifications
steam-3564400.log

32522.191:0078:0084:err:module:import_dll Library WDFLDR.SYS (which is needed by L"C:\\windows\\SYSTEM32\\usrdrv017864.sys") not found
32522.193:0078:0084:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\usrdrv017864": c0000142

The game window doesn't show up and it just crashes.

after asking a friend (they're on windows 11) to send their WdfLdr.sys (and placing it in drive_c/windows/system32/drivers/), it also began to ask for WppRecorder.sys

34412.648:0074:0080:err:module:import_dll Library WppRecorder.sys (which is needed by L"C:\\windows\\system32\\drivers\\WDFLDR.SYS") not found
34412.650:0074:0080:err:module:import_dll Library WDFLDR.SYS (which is needed by L"C:\\windows\\SYSTEM32\\usrdrv017864.sys") not found
34412.650:0074:0080:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\usrdrv017864": c0000142

after adding WppRecorder.sys (into the same folder as WdfLdr.sys) it stopped giving the above errors however the game still crashes.

steam-3564400.log - log with the above .sys files

there are also some other errors though:

(with the WdfLdr.sys and WppRecorder.sys added)

34512.180:0030:0034:err:service:process_send_command service protocol error - failed to read pipe r = 0  count = 0!
34512.677:00c4:00d0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\winebth": c0000142
34513.440:0020:0164:err:vrclient:initialize_vr_data Failed to initialize VR info.
34515.632:0148:018c:err:service:device_notify_proc failed to get event, error 1726

(without adding any .sys files)

32522.191:0078:0084:err:module:import_dll Library WDFLDR.SYS (which is needed by L"C:\\windows\\SYSTEM32\\usrdrv017864.sys") not found
32522.193:0078:0084:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\usrdrv017864": c0000142
32524.110:0020:0150:err:vrclient:initialize_vr_data Failed to initialize VR info.
32526.430:0134:0178:err:service:device_notify_proc failed to get event, error 1726

The global release doesn't have any logs related to WdfLdr.sys, here are the errors global release has despite launching just fine:

37584.523:0098:00a4:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\winebth": c0000142
37585.325:0020:0138:err:vrclient:initialize_vr_data Failed to initialize VR info.
37588.760:013c:0140:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
37588.764:013c:0140:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems

(global release log for comparison)
steam-3224770.log

Those who want to reproduce but are not in japan will need to make a new steam account with japanese vpn, otherwise you won't be able to download the game. If you can't find the game in steam just try to open it through the browser (you will still need to use japanese vpn).

The global release launches just fine for me (haven't tried to fully play it but it at least launches and I'm able to download the game content).

Edit:
I have fully updated my system and the game still crashes.
Linux: 6.15.4-arch2-1
nvidia-dkms: 575.64.03-1

Temporary workaround - Use at your own risk:
<Link removed by moderator>

It has worked for me and I'm not responsible if you will get banned or if your computer explodes 👍
Launches just fine under GE-Proton10-8

Hello @justvam, the workaround you posted is legally problematic and has been removed.

Is there still no workaround for this? Running into the same issue with various proton versions.