https://bugs.winehq.org/show_bug.cgi?id=51086
Giacomo Orlandi gia_@inwind.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gia_@inwind.it
--- Comment #4 from Giacomo Orlandi gia_@inwind.it --- I think I'm also affected by this issue. It might be a different bug, as I *think* it only started with wine 6.8 And the error message is slightly different: `wine: failed to load start.exe: c0000135` instead of `wine: could not load kernel32.dll, status c0000135`
Please let me know if I should create a new bug
I'm on Ubuntu 20.04.
### Vanilla Wine
`rm -rf ~/.wine && WINEARCH=win32 /opt/wine-devel/bin/wine notepad.exe` Failed with: `wine: failed to load start.exe: c0000135`
`rm -rf ~/.wine && WINEARCH=win64 /opt/wine-devel/bin/wine notepad.exe` Failed with: `wine: failed to load start.exe: c0000135`
`rm -rf ~/.wine && WINEARCH=win64 /opt/wine-devel/bin/wine64 notepad.exe` Works!
### Wine Staging
`rm -rf ~/.wine && WINEARCH=win32 /opt/wine-staging/bin/wine notepad.exe` Works!
`rm -rf ~/.wine && WINEARCH=win64 /opt/wine-staging/bin/wine notepad.exe` Works!
rm -rf ~/.wine && WINEARCH=win64 /opt/wine-staging/bin/wine64 notepad.exe works Works!
Battlenet on an existing prefix, probably created on wine-staging 6.5: `WINEPREFIX=~/'games/BattleNet-wine' WINARCH=win64 /opt/wine-staging/bin/wine64 ~/'games/BattleNet-wine/drive_c/Program Files (x86)/Battle.net/Battle.net Launcher.exe'` Works!
However (by mistake) I started Battlenet on that same prefix, using vanilla Wine64: `WINEPREFIX=~/'games/BattleNet-wine' WINARCH=win64 /opt/wine-devel/bin/wine64 ~/'games/BattleNet-wine/drive_c/Program Files (x86)/Battle.net/Battle.net Launcher.exe'` Works!
`WINEPREFIX=~/'games/BattleNet-wine' WINARCH=win64 /opt/wine-devel/bin/winecfg` Failed with: `wine: failed to load start.exe: c0000135`