Kernel32 dll ошибка wine

Я установил Wine из исходников, потом решил удалить её тк вышел релиз который был в менеджере пакетов. Перед этим удалил старую версию, зашел под рутом и удалил папку с wine. Теперь последняя версия 1.1.13 не запускается
Ошибка: wine: could not load kernel32.dll, status c0000135
Пробовал ставить другие другие втч из из исходников тоже самое.

Из сообщения понятно, что не удается загрузить kernel32.dll…найти его думаю можно в инете, только вот в какой папке он должен лежать ?

Что можете посоветовать ?
Всем заранее спасибо

Не совсем так.

Нужно удалить собранный вайн из системы (make uninstall), а потом поставить вайн из пакета.
Окружение можно пересоздать (удальть старое) или обновить, запустив wineprefixcreate

Но у меня уже нет собранного мною пакета…или мне ещё раз собрать установить, а потом удалить

wineprefixcreate выводит следующее

sergey@sergey-laptop:~$ wineprefixcreate
Note: wineprefixcreate is deprecated and shouldn’t be needed anymore.
WINEPREFIX creation and updates now happen automatically when needed.

wine: could not load kernel32.dll, status c0000135

srg[ru] писал(а): ↑

20.01.2009 01:18

Но у меня уже нет собранного мною пакета…или мне ещё раз собрать установить, а потом удалить

wineprefixcreate выводит следующее

sergey@sergey-laptop:~$ wineprefixcreate
Note: wineprefixcreate is deprecated and shouldn’t be needed anymore.
WINEPREFIX creation and updates now happen automatically when needed.

wine: could not load kernel32.dll, status c0000135

нет достаточно снова собрать — make — а потом сразу make uninstall

з.ы:
Старайтесь не ставить программы (в том числе wine) make install — если у вас пакетный дистрибутив — самое лучшее собрать после make бинарник
Еще один способ получать самые свежие версии вайна — юзать PlayOnLinux — там есть возможность подставлять свежую версию вайна под стартовый скрипт программы

ничего так и не получилось….и я на время забросил это, т.к. нашел альтернативы программам ))

Только вот сейчас заметил что из под KDE, wine запускается ,а в GNOME выдает ошибку

интересно разобраться почему ??? wine особо не нужен

Darion писал(а): ↑

20.01.2009 02:08

в исходниках wine есть не только install скрипт но и uninstall скрипт — вот сначала нужно запустить его, затем уже ставить пакет из менеджера пакетов.

Извините за тупизм, но как правильно удалить wine в suse 11.1, какая команда нужна для этого?

I get this msg when I try to load up Doom Eternal using Proton 5.09 or 5.13-1 using the command line.

[user@ws Proton 5.0]$ ./proton run ‘/home/user/.wine/drive_c/DE/DOOMEternalx64vk.exe’
esync: up and running.
wine: could not load kernel32.dll, status c0000135

It used to work up until now. Ive already reinstall wine, steam and DoomEternal w/o success. kernel32.dll is in the folders:

/home/user/.wine/drive_c/windows/system32/
/home/user/.steam/steam/steamapps/compatdata/323910/pfx/drive_c/windows/system32/

Thanks for your kind help and information in advance!

SOLUTION.
I had the same error message trying to run a setup.exe with wine to install a windows game on linux. As google led me here tracking down the error, I am leaving my solution in this thread.

In my case, the problem was that I had created a WINEPREFIX variable, but had forgotten to use the export command:

$ WINEPREFIX=~/gamefolder
$ wine setup.exe

-> error could not load kernel32.dll …
Reason: the WINEPREFIX variable is not accessible to subprocesses.

So my solution was:

$ export WINEPREFIX=~/gamefolder
$ wine setup.exe

using «export», the WINEPREFIX variable is accessible to subprocesses.
-> installation works smoothly.

Maybe the problem was similar here with proton. In any case I’d not recommend the «sudo» solution as it looks like an unsafe workaround for me.
Installing or playing games with wine/proton should usually not require admin privileges. Please remember that also games can be exploited to gain root level access to your computer.

edit: this worked for proton 5.0-1 just fine

I wasnt able to reproduce this issue through steam itself, even tried with a non updated proton environment (installed a game that wasnt on the pc before), however it happens on a not through steam launched proton environment
cd "/ext/ssd/SteamLibrary/steamapps/common/Proton 5.13"
STEAM_COMPAT_DATA_PATH=/ext/ssd/proton ./proton waitforexitandrun taskmgr

results in
user:~% ./protonextern5.sh
Proton: Upgrading prefix from 5.0-1 to 5.13-1 (/ext/ssd/proton/)
esync: up and running.
wine: configuration in L"/ext/ssd/proton/pfx" has been updated.
user:~% ./protonextern5.sh
esync: up and running.
wine: could not load kernel32.dll, status c0000135

same for a new proton environment outside steam, however it populates it with files/symlinks and kernel32.dll is there, but the symlink is broken (see attachment). should be a full path instead of a relative one?

I have this issue as well.
Yesterday was playing Phasmophobia on Proton 5.0-9.

Tried today with Proton 5.13-1 and get this:

Proton: 1602710188 proton-5.13-1b
SteamGameId: 739630
Command: [‘/mnt/01D4F6F0309CE6C0/Program Files (x86)/Steam/steamapps/common/Phasmophobia/Phasmophobia.exe’, ‘-vrmode’, ‘none’]
Options: {‘forcelgadd’}
ERROR: ld.so: object ‘/home/hunter/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object ‘/home/hunter/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object ‘/home/hunter/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object ‘/home/hunter/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
esync: up and running.
ERROR: ld.so: object ‘/home/hunter/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
180.006:0028:002c:trace:loaddll:build_module Loaded L»C:windowssystem32ntdll.dll» at 000000007BC00000: builtin
180.009:0028:002c:err:module:import_dll Loading library kernelbase.dll (which is needed by L»C:windowssystem32kernel32.dll») failed (error c0000020).
wine: could not load kernel32.dll, status c0000135
180.011:0020:0024:err:environ:run_wineboot failed to start wineboot c0000135
180.014:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32ntdll.dll» at 7BC00000: builtin
180.018:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32kernelbase.dll» at 7B000000: builtin
180.019:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32kernel32.dll» at 7B620000: builtin
180.022:0020:0024:trace:loaddll:build_module Loaded L»C:Program Files (x86)Steamsteam.exe» at 7E7A0000: builtin
180.040:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32ucrtbase.dll» at 7E600000: builtin
180.040:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32sechost.dll» at 61B00000: builtin
180.040:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32advapi32.dll» at 7E6F0000: builtin
180.045:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32gdi32.dll» at 7E490000: builtin
180.048:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32rpcrt4.dll» at 6FDC0000: builtin
180.060:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32version.dll» at 65980000: builtin
180.060:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32setupapi.dll» at 6A900000: builtin
180.060:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32user32.dll» at 7E270000: builtin
180.060:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32ole32.dll» at 65200000: builtin
180.077:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32shcore.dll» at 64B40000: builtin
180.077:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32shlwapi.dll» at 68C40000: builtin
180.077:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32shell32.dll» at 7D860000: builtin
180.278:0020:0024:trace:loaddll:build_module Loaded L»C:windowssystem32imm32.dll» at 6C0C0000: builtin
180.298:0034:0038:trace:loaddll:build_module Loaded L»C:windowssystem32ntdll.dll» at 000000007BC00000: builtin
180.301:0034:0038:err:module:import_dll Loading library kernelbase.dll (which is needed by L»C:windowssystem32kernel32.dll») failed (error c0000020).
wine: could not load kernel32.dll, status c0000135
180.310:0020:0030:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
180.310:0020:0030:err:winediag:nodrv_CreateWindow The explorer process failed to start.
Setting breakpad minidump AppID = 739630
Steam_SetMinidumpSteamID: Caching Steam ID: 76561199087301916 [API loaded no]
180.559:0020:0024:err:steam:run_process Failed to create process L»»Z:mnt1D4F6F0309CE6C0Program Files (x86)SteamsteamappscommonPhasmophobiaPhasmophobia.exe» -vrmode none»: 1115
pid 3516 != 3515, skipping destruction (fork without exec?)

Same issue here. Can’t seem to get anything to run. Can still run everything in 5.0-9 no problem.

Same. Unable to launch anything. Proton 5.0-9 and 5.9-GE-ST-8 still work completely fine.

I’m in the same boat, nothing will run with Proton 5.13 on Fedora 33 on a Gnome/Wayland session.

Quake Champions (2017), Prey (2006), FarCry (2004), DOOM 3 (2004) or Quake IV (2005).

I tried restarting my client, verify Proton and all of my games, run an Xorg session, but they won’t launch.

Thankfully I can still manually fall back to proton 5.0-9 and the previous runtime.

Logfile: vyfuMCwE.log Full system specifications: 9MRtQFwe.log

GameAction [AppID 611500, ActionID 2] : LaunchApp changed task to ProcessingInstallScript with ""
/data/src/clientdll/installscript_posix.cpp (357) : Assertion Failed: strCommonRedistForeignInstallPath != ""
/data/src/clientdll/installscript_posix.cpp (357) : Assertion Failed: strCommonRedistForeignInstallPath != ""
_v2-entry-point[137291]: STEAM_COMPAT_APP_ID=611500
_v2-entry-point[137291]: STEAM_COMPAT_SESSION_ID=87f8e6d8eb860e11
_v2-entry-point[137291]: XDG_RUNTIME_DIR=/run/user/1000
_v2-entry-point[137319]: STEAM_COMPAT_APP_ID=611500
_v2-entry-point[137319]: STEAM_COMPAT_SESSION_ID=87f8e6d8eb860e11
_v2-entry-point[137319]: XDG_RUNTIME_DIR=/run/user/1000
bwrap: Can't mkdir /usr/lib64/gconv: Read-only file system
ln: misslyckades att skapa symbolisk länk '/run/user/1000/SteamLinuxRuntime.87f8e6d8eb860e11/socket' → '': Filen eller katalogen finns inte
/data/src/clientdll/installscript_posix.cpp (419) : Assertion Failed: Standalone evaluator returned error code for app 611500
/data/src/clientdll/installscript_posix.cpp (419) : Assertion Failed: Standalone evaluator returned error code for app 611500
GameAction [AppID 611500, ActionID 2] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 611500, ActionID 2] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 611500, ActionID 2] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 611500, ActionID 2] : LaunchApp continues with user response "CreatingProcess"
Game update: AppID 611500 "", ProcID 137405, IP 0.0.0.0:0
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Starting app 611500
>>> Adding process 137405 for game ID 611500
GameAction [AppID 611500, ActionID 2] : LaunchApp changed task to WaitingGameWindow with ""
>>> Adding process 137406 for game ID 611500
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
gamemodeauto: 
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
gamemodeauto: 
pid 137432 != 137406, skipping destruction (fork without exec?)
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 611500, ActionID 2] : LaunchApp changed task to Completed with ""
_v2-entry-point[137406]: STEAM_COMPAT_APP_ID=611500
_v2-entry-point[137406]: STEAM_COMPAT_SESSION_ID=87f8e6d8eb860e11
_v2-entry-point[137406]: XDG_RUNTIME_DIR=/run/user/1000
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 137424 for game ID 611500
>>> Adding process 137433 for game ID 611500
>>> Adding process 137436 for game ID 611500
>>> Adding process 137441 for game ID 611500
bwrap: Can't mkdir /usr/lib64/gconv: Read-only file system
ln: misslyckades att skapa symbolisk länk '/run/user/1000/SteamLinuxRuntime.87f8e6d8eb860e11/socket' → '': Filen eller katalogen finns inte
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 137475 for game ID 611500
bwrap: Can't mkdir /usr/lib64/gconv: Read-only file system
ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.87f8e6d8eb860e11/socket' -> '': No such file or directory
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kattpojken/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pressure-vessel-launch[137556]: Can't connect to peer socket: Could not connect: No such file or directory
>>> Adding process 137555 for game ID 611500
>>> Adding process 137556 for game ID 611500
Game removed: AppID 611500 "", ProcID 137405 
Uploaded AppInterfaceStats to Steam
Exiting app 611500

Yesterday Proton 5.13-1 worked for me, but today (after computer shutdown) I’ve got the same problem.

I had this problem too. Even when I changed my game (A Hat In Time and Doom 2016) back to an older version of proton, I still had the kernel32 issue. This fixed itself when I deleted the compatdata folder for each game and relaunched with the older Proton versions.

same issue none of games run, new version?

I also tried with a new proton prefix and the issue was the same :/

Ok, I just fixed it somehow. I reinstalled the steam and downloaded the proton 5.13 again.

I also have this:

ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.43a8a80b376a7b6d/socket' -> '': No such file or directory
pressure-vessel-launch[127686]: Can't connect to peer socket: Could not connect: No such file or directory

with the actual folder:

$ ls -lh /run/user/1000/SteamLinuxRuntime.43a8a80b376a7b6d/
prw-r--r-- 1 birdspider birdspider 0 16. Okt 18:17 fifo
$ file /run/user/1000/SteamLinuxRuntime.43a8a80b376a7b6d/fifo
/run/user/1000/SteamLinuxRuntime.43a8a80b376a7b6d/fifo: fifo (named pipe)

as in, is fifo supposed to be socket ?

I also was not able to run anything with new Proton-5.13-1 version, then I started debugging the issues using the
PRESSURE_VESSEL_VERBOSE=1 environment variable override, as I guessed that they all stemmed from the new runtime environment.

missing XDG_RUNTIME_DIR env variable

The first issue i found is that on my system (Slackware64 14.2) the XDG_RUNTIME_DIR env variable is not set (this is a system with no systemd, and IIUC this variable is tipically set by systemd at login time) and this breaks something in the SteamLinuxRuntime_soldier/_v2-entry-point script that gets called when launching a game with the new 5.13-1 Proton release:

/mnt/storage/Steam/SteamApps/common/SteamLinuxRuntime_soldier/_v2-entry-point: line 179: XDG_RUNTIME_DIR: unbound variable

This can be fixed by preparing a temp dir inside your user $HOME (seems like the script does not like world-readable paths) for that before launching steam:

mkdir -p ~/steam-tmp
export XDG_RUNTIME_DIR=~/steam-tmp
steam

This is a just stop-gap solution: I think it would be better for the _v2-entry-point script to provide a default location as a fallback.

libdconfsettings.so error

It seems like there’s an issue with this library, as this appears in the output using PRESSURE_VESSEL_VERBOSE=1:

pressure-vessel-wrap[28264]: Replacing self with bwrap...
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so

Does not seem to be fatal, though.

empty launch_args array is considered unbound variable

The launch_args array used in the _v2-entry-point script is not expanded at line 254 because it results as an unbound variable:

/mnt/storage/Steam/SteamApps/common/SteamLinuxRuntime_soldier/_v2-entry-point: line 254: launch_args[@]: unbound variable

This is new to me too, but an empty array is considered unbound when using set -u.
I solved this by deleting the entire line 254 of the file, assuming that a newly declared empty variable (a few lines prior) would’ve nothing to add there.

After the XDG_RUNTIME_DIR override and the launch_args array fix in the _v2-entry-point scripts, I was finally able to launch games with the new Proton version

Same problem, kernelbase.dll is a 0 byte file, so I replaced it with the one(it’s a 64,008 bytes file) from Proton 5.0-9 but now it fails with «error 4000000e»

What I’ve noticed is that the error code I have is because the symlinks are broken

Yesterday it was working. Now Ive tried with both 5.09 and 5.13-1 and both has the same issue.

[user@ws Proton 5.0]$ ./proton run ‘/home/user/.wine/drive_c/DOOME/DOOMEternalx64vk.exe’
esync: up and running.
wine: could not load kernel32.dll, status c0000135

huh, weird
I used 5.0-9 yesterday, worked fine. Will try again later.
However, did you create the prefix again? otherwise 5.0-9 -> 5,13-1 will break it, even if you try to use 5.0-9 because the symlinks are borken

huh, weird
I used 5.0-9 yesterday, worked fine. Will try again later.
However, did you create the prefix again? otherwise 5.0-9 -> 5,13-1 will break it, even if you try to use 5.0-9 because the symlinks are borken

[laza@lazacenter Proton 5.0]$ ./proton run ‘/home/laza/.wine/drive_c/DE/DOOMEternalx64vk.exe’
Proton: Upgrading prefix from None to 5.0-1 (/home/laza/proton/)
esync: up and running.
wine: could not load kernel32.dll, status c0000135

Yes I think it set the prefix automatically. Otherwise how to do it manually?

well that’s weird, I just install opensuse tumbleweed and it works for me…

I can’t run anything with Proton 5.13-1 or 5.13-2.
It says ‘launching’, but never launches.
It breaks the game’s compatdata/wineprefix, so I have to remove it for it to get rewritten.
Everything works fine with Proton 5.0.x.

Same issue here, error c0000135 on the launch of Metal Gear ground zero and red dead redemption 2.

symlinks copied to pfx directory were using wrong relative paths

         ./pfx/drive_c/windows/syswow64/kernel32.dll -> dist/lib/wine/fakedlls/kernel32.dll

fixed to use absolute path

After doing a clean install of Steam, I could install and run a couple of games with 5.13-2.
As soon as I’ve added my Steam Library from another partition, every game failed to launch. Even the games that ran before.

@clebercasali I had the same issue, but was able to get the games to work by removing the compdata directory of the mounted drive before adding it in steam (in addition to clean re-install).

This did require me to reinstall the games, but it’s fairly quick because steam will first check the destination for existing game files, so you won’t have to do a whole re-download.

In case if someone is also having a problem with this, I was able to solve this by reinstalling Proton 5.13. It was previously installed on NTFS partition, and I reinstalled it to ext4 root partition. Game seems to boot up well.

If your steam refuses to uninstall it due to unexpected error, It’s probably because some games are set to use Proton 5.13:

App ID 271590 depends on compatibility tool 1420170, cannot uninstall!GameAction [AppID 1420170, ActionID 2] : UninstallApps failed with AppError_17 with ""

Change them to use other versions like 5.0, and you will be able to uninstall it.
If that’s not the case and you have no idea what’s going on, try to run steam in a terminal. Steam should be completely terminated before doing it to see logs in the terminal.

EDIT: I am using Fedora 32, using Steam package provided from RPMfusion. The game I tested with was GTA V.
I wiped the prefix after doing this, not sure how it will work without doing so.

This is what I did to get it working again:

• Moved Proton 5.13 and Steam Linux Runtime — Soldier from my secondary library to the default library in the «home» partition (right click-properties-local files-move install folder);
• After moving finished, navigated to the default library with a file manager and deleted Proton 5.13 and Steam Linux Runtime directories;
• With file manager, went to my secondary library and removed all directories inside «compatdata»;
• Right click — properties — local files — verify integrity of tool files, for both Proton 5.13 and Steam Linux Runtime. Steam re-downloaded everything;
• After everything is downloaded and installed, launched a Proton game. It re-created the prefix/compatdata and worked.

I was getting this issue right after a system rebuild to include a reinstallation of Steam (but keeping all my old game files), and this fixed everything. Thank you!

Same issue with 2 different distro

@0xC0ncord how does one verify integrity of tool files?

Nevermind…had to do a search within steam for proton 5.13 and Steam Runtime Soldier after I followed the above steps
This fixed proton 5.13 and now cyberpunk 2077 works

I also have this problem with Proton 5.13-4. So how exactly do I fix it? To me it seems everyone above got it working in a different way and I am somewhat confused.

So is this something wrong with Proton or is it me not using Proton correctly?

One of the things that confuses me is that Proton seems to run fine when launched through Steam, but it no longer does from command line which worked fine in Proton 5.0.

I also have this problem with Proton 5.13-4. So how exactly do I fix it? To me it seems everyone above got it working in a different way and I am somewhat confused.

So is this something wrong with Proton or is it me not using Proton correctly?

One of the things that confuses me is that Proton seems to run fine when launched through Steam, but it no longer does from command line which worked fine in Proton 5.0.

#4409
Look at this, that should fix the issue, I think.

Getting this issue now.

Steam was running the whole time, no reboot — all of a sudden something that ran yesterday will now no longer run with the same error.

As previously mentioned, the issue seems to be with the wine prefix created by Proton 5.13 containing incorrect relative links that point to non-existent files in places like pfx/drive_c/windows/system32/, including the kernel32.dll which just happens to be loaded first.

#4409 fixes this issue and can be easily applied in a few minutes. I’ve left instructions on how to do that in a comment on that PR.

Hey @opl- , I saw #4409 and just did it on a completely fresh install and nothing changed for me. I’m tried it on Satisifactory and Rocket League, and then I reinstalled steam and did it again and I got a new error message. This was outputted after reinstalling steam:

$ pwd
/home/dan/.steam/debian-installation/steamapps/common/Proton 5.13
$ STEAM_COMPAT_DATA_PATH=~/.steam/debian-installation/steamapps/compatdata/526870 ./proton run ~/.steam/debian-installation/steamapps/common/Satisfactory/FactoryGame.exe
Proton: Upgrading prefix from None to 5.13-1 (/home/dan/.steam/debian-installation/steamapps/compatdata/526870/)
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
esync: up and running.
$ echo $?
0
$ screenfetch -n 
 dan@dan-MS-7641
 OS: Ubuntu 20.04 focal
 Kernel: x86_64 Linux 5.8.0-36-generic
 Uptime: 1h 59m
 Packages: 3820
 Shell: zsh 5.8
 Resolution: 5760x1080
 DE: GNOME 3.36.4
 WM: i3
 GTK Theme: Adwaita-dark [GTK2/3]
 Icon Theme: DMZ-Black
 Font: Cantarell 11
 Disk: 101G / 468G (23%)
 CPU: AMD FX-8350 Eight-Core @ 8x 4GHz
 GPU: GeForce RTX 2060
 RAM: 4363MiB / 16008MiB

Your PR comment changed something, but I don’t know what to do from here. Any thoughts?

new problem? where did the file go?

kernelbase.dll missing from
$USER/.steam/steam/steamapps/common/Proton 5.13/dist/lib/wine/fakedlls
$USER/.steam/steam/steamapps/common/Proton 5.13/dist/lib64/wine/fakedlls

broken empty link is created under $USER/.steam/steam/steamapps/compatdata/$APPID/pfx/drive_c/windows/system32

478.311:0028:002c:err:module:import_dll Loading library kernelbase.dll (which is needed by L"C:\windows\system32\kernel32.dll") failed (error c0000020).
wine: could not load kernel32.dll, status c0000135
478.312:0020:0024:err:environ:run_wineboot failed to start wineboot c0000135

validating proton5.13 files does not replace it.
uninstalling proton 5.13 and reinstalling does not replace it.

what happened?

ahhh…… i see
the files
kernelbase.dll at:
$USER/.steam/steam/steamapps/common/Proton 5.13/dist/lib/wine/
smaller file
$USER/.steam/steam/steamapps/common/Proton 5.13/dist/lib64/wine/
empty, 0 bytes. link wasnt broken its just empty!

https://dl.winehq.org/wine-builds/debian/dists/stable/main/
compared to the original files, which have data.
wine-staging-i386_5.13_buster_i386.deb
wine-staging-amd64_5.13_buster_amd64.deb

extracted — replaced missing kernelbase.dll

NEXT:

2163.481:009c:00a0:err:module:__wine_process_init failed to load L"C:\windows\system32\explorer.exe", error 4000000e
2163.484:0020:0098:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
2163.484:0020:0098:err:winediag:nodrv_CreateWindow The explorer process failed to start.

same thing, explorer.exe is 1kb file

well look at that
proton_dist.tar
the files are correct size in here

explains why verify files didnt work, proton extracts from that .tar file
i deleted Proton 5.13 folder and verified files
now the files exist properly

what happened????????

I was having this problem intermittently. Not sure why it was inconsistent. But I have solved it by realizing that my ntfs drive that my Steam library was on has been mounted with my username as the uid but root was the gid. So I just updated my fstab to include ‘gid=1000’ and the ‘permissions’ option then rebooted. Then for good measure I went ahead and completely removed all proton versions and reinstalled from steam. Works perfectly now. So the issue must have been with permissions.

My fstab entry: UUID=******** /mnt/games_ssd auto nosuid,nodev,nofail,x-gvfs-show,uid=1000,gid=1000,permissions 0 7

I saw this failure mode recently, and on investigating, I found that wine/fakedlls/kernelbase.dll was an empty file (0 bytes), similar to what @arrowgent and @PeterMX saw.

The dist/ directory isn’t managed by Steam’s normal CDN distribution mechanism (which is designed for a small number of large files, rather than Proton’s large number of small files), so verifying installed files in Steam cannot detect this. Instead, Proton unpacks proton_dist.tar to dist/ during startup. SteamLinuxRuntime_soldier does something similar, for the same reason.

I was able to this by deleting the dist/ directory and letting Proton re-unpack it the next time I ran a game.

I think the fact that multiple people have had this file become empty might suggest that something is semi-consistently going wrong with unpacking the archive. It would be useful if there was a way for Steam to signal to Proton that the user has asked to verify installed files, so that Proton could either validate the contents of the dist/ directory, or just delete it.

@D1G1T4L3CH0 wrote:

Then for good measure I went ahead and completely removed all proton versions and reinstalled from steam. Works perfectly now. So the issue must have been with permissions.

It could be the permissions, or it could be something that can be fixed by reinstalling Proton (like the empty file that I had) — after reinstalling, you can’t tell which any more.

For instance, if you had the same issue with an empty file that I did, then reinstalling Proton is likely to have fixed it.

okay so I’m on fedora 34 running wine 6.11.
I basically had the same problem with the kernel32.dll file

and I just literally had to do this simple step similar to the solve here…

This is what I did to get it working again:

• Moved Proton 5.13 and Steam Linux Runtime — Soldier from my secondary library to the default library in the «home» partition (right click-properties-local files-move install folder);
• After moving finished, navigated to the default library with a file manager and deleted Proton 5.13 and Steam Linux Runtime directories;
• With file manager, went to my secondary library and removed all directories inside «compatdata»;
• Right click — properties — local files — verify integrity of tool files, for both Proton 5.13 and Steam Linux Runtime. Steam re-downloaded everything;
• After everything is downloaded and installed, launched a Proton game. It re-created the prefix/compatdata and worked.

So, what I did was just copy the whole folder of «steam» from the location: $USER/.steam/
and then just pasted it the main $USER directory.
That’s literally all I had to do to fix the error.

There’s a temporary solution of adding wineprefix and setting a temporary location to run winecfg but it was inconsistent. Now, just typing winecfg in terminal works just fine.

I have been encountering this issue for a while now, and none of the mentioned fixes seem to do anything, and even more recent versions of Proton don’t seem to fix anything. Running on Debian 11.
Here’s the error I keep getting upon launch, with any proton version:
esync: up and running. 38273.770:0028:002c:trace:loaddll:build_module Loaded L"C:\windows\system32\wineboot.exe" at 0000000140000000: builtin 38273.771:0028:002c:err:module:import_dll Loading library kernelbase.dll (which is needed by L"C:\windows\system32\kernel32.dll") failed (error c0000020). wine: could not load kernel32.dll, status c0000135 38273.773:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\start.exe" at 0000000140000000: builtin 38273.774:0020:0024:err:module:import_dll Loading library kernelbase.dll (which is needed by L"C:\windows\system32\kernel32.dll") failed (error c0000020). wine: could not load kernel32.dll, status c0000135
Something about a certain kernelbase.dll, but I can’t seem to find what the error means nor how to fix it.

@Laporte12974 I had some weird problems some time ago like this one:
#4266

The solution for me was deleting steam runtime soldier from the NTFS partition and moving it to an ext4.
I hope this helps. Even though it seems unrelated I remember having that message as well at that point in time.

Received a similar issue when trying to download Wine on a Chromebook. Here’s what happened:
$ winecfg wine: could not load kernel32.dll, status c0000135
Also, in case this helps (my vain attempt to load notepad):
$ wine notepad wine: could not load kernel32.dll, status c0000135
If need be, here’s the result of «cat /etc/os-release»:
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"

winecfg
wine: could not load kernel32.dll, status c0000135
wine —version
wine-7.0 (Debian 7.0~repack-10)
running on kali linux
$ cat /etc/issue
Kali GNU/Linux Rolling n l

wine —version
wine-7.0 (Debian 7.0~repack-10)

This is the issue tracker for Proton, a Steam compatibility layer installed via Steam, which includes its own version of Wine. Valve does not maintain any other version of Wine that you might be using, so even if you get a similar error message, commenting on this issue will not result in a solution for you.

Received a similar issue when trying to download Wine on a Chromebook

The same applies here…

sudo apt install wine64

… and here.

This issue tracker is specifically for Proton, not for any other version of Wine you might have installed outside Steam.