Windows 10: bat files not being run when double clicked in TC

[Dalai]

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

[jmwap]

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...

[jmwap]

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.

[Dalai]

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:

Code: Select all

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Command Processor
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor
HKEY_CURRENT_USER\Software\Microsoft\Command Processor

If there is such a value (especially in the first path), rename it, and try running the 32 bit CMD again.

Regards
Dalai

[Horst.Epp]

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:

Code: Select all

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Command Processor
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor
HKEY_CURRENT_USER\Software\Microsoft\Command Processor

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

[jmwap]

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:

Code: Select all

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Command Processor
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor
HKEY_CURRENT_USER\Software\Microsoft\Command Processor

If there is such a value (especially in the first path), rename it, and try running the 32 bit CMD again.

Regards
Dalai

you are the man! there was such a value, only in the third one. REnamed it and everything works now...

The value was
...conemu\ConEmu\clink\clink.bat" inject --autorun

I use conemu, with clink as well, but not sure when that value was added there and why is it making it not run fine...

[Dalai]

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

[jmwap]

for closure clink1.0a does not get injected fine, reverting to 0.4.9 works