running proton via CMD outputs wine: failed to open "c:\\windows\\system32\\steam.exe": c0000135

Steam for Linux

全部讨论艺术作品视频新闻指南

Steam for Linux > 综合讨论 > 主题详情

Picarica

2022 年 3 月 16 日上午 10:32

running proton via CMD outputs wine: failed to open "c:\\windows\\system32\\steam.exe": c0000135

i am trying to launch a program without acutally installing wine by myself, so i am trying out proton and everything i figured out except this, when i googled this error i got 1 result from chinese website, i dont know what is the issue

STEAM_COMPAT_CLIENT_INSTALL_PATH=/gamedisk/steamapps/compatdata/374320/pfx STEAM_COMPAT_DATA_PATH=/gamedisk/steamapps/compatdata/374320/pfx ./proton run ../../compatdata/374320/pfx/drive_c/windows/explorer.exe

and when i tried o launch it without STEAM_COMPAT_CLIENT_INSTALL_PATH i would get error

KeyError: 'STEAM_COMPAT_CLIENT_INSTALL_PATH'

so figured this out, but what this error ? when i tried launching wine, in the proton folder, it said wineserver not running, i saw wineserver there, but is it worth trying out with this rather than proton?

< >

正在显示第 1 - 6 条，共 6 条留言

Picarica

2022 年 3 月 16 日上午 11:37

引用自 catbox：
proton 5.13, 6.3, 7.0 and anything using pressure vessel requires a lot of extra steps.

you can run proton 3.7, 3.16, 4.2, 4.11, and 5.0 without steam open at all.

here is an example script:

#!/bin/sh export STEAM_LIBRARY="/home/picarica/.steam/steam/" export WINEARCH=win64 export PATH=/home/picarica/.steam/steam/steamapps/common/Proton\ 5.0/dist/bin:$PATH export WINEPATH=/home/picarica/.steam/steam/steamapps/common/Proton\ 5.0/dist/ export LD_LIBRARY_PATH=/home/picarica/.steam/steam/steamapps/common/Proton\ 5.0/dist/lib:/home/picarica/.steam/steam/steamapps/common/Proton\ 5.0/dist/lib64:$LD_LIBRARY_PATH export WINE=/home/picarica/.steam/steam/steamapps/common/Proton\ 5.0/dist/bin/wine export WINELOADER=/home/picarica/.steam/steam/steamapps/common/Proton\ 5.0/dist/bin/wine export WINESERVER=/home/picarica/.steam/steam/steamapps/common/Proton\ 5.0/dist/bin/wineserver export WINEDLLPATH=/home/picarica/.steam/steam/steamapps/common/Proton\ 5.0/dist/lib/wine export WINEPREFIX="/home/picarica/.steam/steam/steamapps/compatdata/374320/pfx" export DXVK_FRAME_RATE=60 export DXVK_HUD=scale=0.5,fps WINEPREFIX="/home/picarica/.steam/steam/steamapps/compatdata/374320/pfx" $STEAM_LIBRARY/steamapps/common/Proton\ 5.0/dist/bin/wine '/home/picarica/.steam/steam/steamapps/compatdata/374320/pfx/drive_c/windows/explorer.exe' #sh -c "env WINEPREFIX="/home/picarica/.steam/steam/steamapps/compatdata/374320/pfx" sh /home/picarica/.wine/winetricks --gui --verbose --optout"

thank you for this this seems like a fix enought for me but when i changed the paths in script and updated it a little i get this error

0024:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.

and i am not sure i am running it in shel normally, i am using linux mint, newest so i am not sure whats wrong i tried googling it, and other people were just running it via ssh or missing some dependencies
here is full log but it seems to be going pretty okay

wineserver: using server-side synchronization. 0068:err:module:map_image Could not map section .rsrc, file probably truncated 0068:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142 0034:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1114 0080:err:module:load_so_dll failed to load .so lib "/home/picarica/.steam/debian-installation/steamapps/common/Proton 5.0/dist/bin/../lib64/wine/winebus.sys.so": libudev.so.0: cannot open shared object file: No such file or directory 0080:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\winebus": c0000142 0034:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1114 wine: Call from 0x7bc8be3c to unimplemented function ntoskrnl.exe.RtlPcToFileHeader, aborting wine: Unimplemented function ntoskrnl.exe.RtlPcToFileHeader called at address 000000007BC8BE3C (thread 0050), starting debugger... 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 00b4:fixme:dbghelp:elf_search_auxv can't find symbol in module 0034:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0! 0034:fixme:service:scmdatabase_autostart_services Auto-start service L"nsiproxy" failed to start: 1053 0034:err:service:process_send_start_message pipe connect failed 0034:fixme:service:scmdatabase_autostart_services Auto-start service L"NDIS" failed to start: 1053 Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org 00c0:err:module:map_image Could not map section .rsrc, file probably truncated 0024:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0024:err:winediag:nodrv_CreateWindow Unknown error (193).

Marlock

2022 年 3 月 17 日上午 4:04

it's waaaaaaaaay easier to use Lutris and let it manage an instance of Proton for you than it is to manually solve all those tuning issues

That being said, you might get luckier with ProtonGE, because it's a 3rd-party developer doing it there is a slim chance it will play nicer outside Steam and pressure vessel

sodiboo

9 月 22 日上午 6:58

In my case, the error `failed to open "c:\\windows\\system32\\steam.exe": c0000135` is caused by a corrupted wine prefix. To anyone coming from Windows, the path it's trying to open sounds absurd; "what, that's not right. why is it looking in there". but no, that is genuinely supposed to exist, and if it doesn't, something is wrong with your installation. The wine prefix is stored under `steamapps/compatdata/<APPID>`. Deleting this folder fixed it for me, as Steam regenerated a valid one. Note that this is also usually where save data is stored (AppData, windows registry, etc), so exercise caution if you have any savefiles that matter.

(yes, i am leeching off this being the top search result. sorry about the revival of a three year old thread but i do genuinely believe this was likely the exact same issue as i was having just now)

I think it was corrupted in the first place because of my main drive for Steam being NTFS? (i inherited it from a dead Windows install and didn't bother repartitioning yet). When i installed/configured Steam initially, i was well aware that this could be an issue, and i made sure to install Proton and Steam Linux Runtime on my regular non-NTFS filesystem. But, i made the mistake of setting the default install directory to my NTFS drive. Steam wants the Proton stuff to be plug-and-play, you don't even have to think about it, meaning it will automatically install on-demand. But this caused new versions of Proton and Steam Linux Runtime to install on my NTFS drive. Simply moving those tools to my main drive (and also moving the game that was giving me trouble) did not fix the issue i was having; but i suspect that having them on an NTFS drive did somehow cause the problem in the first place. The file Proton can't open is `C:\Windows\System32\Steam.exe`, which is actually located at `~/.local/share/Steam/steamapps/compatdata/<APPID>/pfx/drive_c/windows/system32/steam.exe`, and that file was an invalid symlink for me. A bunch of other critical stuff in System32 was also broken, so instead of trying to fix any of those files, i deleted the entire thing up to and including the app's entire compatdata entry. As said, Steam regenerated it all in a non-corrupted state.

"Verify integrity of game files" does NOT catch this corruption, as that functionality only verifies the integrity of the game assets in `steamapps/common`. I don't think there's any button in Steam to press to magically fix issues in `steamapps/compatdata`, or even detect them (well, besides "Play", i guess). The game will simply fail to launch, throwing up cryptic errors that will have you scouring the internet for hours until it's too late and the other person you wanted to play with has already gone to bed, leaving you plenty of time to post your own answer in one of the top search results because whoever was here before did not really help you solve your issue or even point you in the right direction.

引用自 Marlock：
you might get luckier with ProtonGE

In my case, Valve's Proton simply didn't launch at all. Nothing on stderr. Not quite sure what's going wrong there, but at least ProtonGE gave me the error message that led me to this forum post. So, i guess yeah? I did get luckier with ProtonGE.