ghisler(Author) wrote: ↑2018-11-29, 11:49 UTC
Apparently cmd.exe is missing in windows\SysWOW64\cmd.exe. Try copying it there from windows\Sysnative\cmd.exe
This neither fits the error description nor is it a good idea. If the file was missing, Windows would show an error message when trying to launch that EXE. I don't read of such behavior in jmwap's description.
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
ghisler(Author) wrote: ↑2018-11-29, 11:49 UTC
Apparently cmd.exe is missing in windows\SysWOW64\cmd.exe. Try copying it there from windows\Sysnative\cmd.exe
it is not missing, there is a cmd.exe there, a 32b exe. The one in windows\Sysnative\cmd.exe is a 64b exe...
Dalai wrote: ↑2018-11-28, 20:25 UTC
Please do the following: Win+R, enter "cmd.exe", ENTER. In the open CMD window type "%SystemRoot%\SysWOW64\cmd.exe" (without the quotes), ENTER. Please post the full CMD window output here.
Regards
Dalai
This is the output:
C:\Users\xxx>%SystemRoot%\SysWOW64\cmd.exe
Microsoft Windows [Version 10.0.17763.134]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\xxx>
At the end, I think I am in the original cmd, cause if I type exit, the window closes.
Mmh, that's weird. The 32 bit CMD seems to be (almost) completely broken. Wouldn't surprise me if a Windows update or upgrade broke it (on your system, because Horst.Epp reported it's working fine on his system). But maybe not. Please check the following registry paths for a value named AutoRun:
Dalai wrote: ↑2018-11-29, 14:58 UTC
Mmh, that's weird. The 32 bit CMD seems to be (almost) completely broken. Wouldn't surprise me if a Windows update or upgrade broke it (on your system, because Horst.Epp reported it's working fine on his system). But maybe not. Please check the following registry paths for a value named AutoRun:
If there is such a value (especially in the first path), rename it, and try running the 32 bit CMD again.
Regards
Dalai
Here the 2 versions of cmd.exe on my system:
The one in syswow64 is 231 KB (236.544 bytes) from Samstag, 15. September 2018, 09:29:07
The one under System32 is 272 KB (278.528 bytes) from 15. September 2018, 09:28:38
Windows 11 Home x64 Version 23H2 (OS Build 22631.3672) TC 11.03 x64 / x86
Everything 1.5.0.1378a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.78
QAP 11.6.3.3 x64
Dalai wrote: ↑2018-11-29, 14:58 UTC
Mmh, that's weird. The 32 bit CMD seems to be (almost) completely broken. Wouldn't surprise me if a Windows update or upgrade broke it (on your system, because Horst.Epp reported it's working fine on his system). But maybe not. Please check the following registry paths for a value named AutoRun:
Interesting. It seems that the injection done by ConEmu doesn't work in a 32 bit CMD. Maybe an error in clink.bat? Trying to inject a DLL of the wrong architecture?
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64