Discussion:
Cygwin corrupted taskkill in windows commandline
Hazel
2012-09-20 14:06:39 UTC
Permalink
Hi, I just installed cygwin and now I can not use the native taskkill command
from windows command line, it will only reply with:

'taskkill' is not recognized as an internal or external command, operable
program or batch file.


This installation of Windows XP Pro 32Bit SP3 has been working with no
issues since it was installed a year ago.

I really need to solve this issue as ALOT of tools i have for windows uses
"taskkill" for aborting DOS programs i use for special equipment such as a
dot-matrix printer.



--
View this message in context: http://cygwin.1069669.n5.nabble.com/Cygwin-corrupted-taskkill-in-windows-commandline-tp92938.html
Sent from the Cygwin list mailing list archive at Nabble.com.
j***@rivierenland.xs4all.nl
2012-09-21 08:26:59 UTC
Permalink
From: Hazel <***@inbox.com>
Date: Thu, Sep 20, 2012 at 07:06:39AM -0700
Post by Hazel
Hi, I just installed cygwin and now I can not use the native taskkill command
'taskkill' is not recognized as an internal or external command, operable
program or batch file.
I think that's more probably related to the command taskkill being found
than to the file taskkill.exe being corrupted by Cygwin. Did something
change your PATH ?

Kind regards,
Jurriaan
--
And money rides while people crawl
And another quiet night goes by
Oysterband - Another quiet night in England
Voris, Ben
2012-09-21 15:59:36 UTC
Permalink
On my system, taskkill is /cygdrive/c/Windows/system32/taskkill. That is, it is not part of Cygwin but is part of Windows. I suspect either that your PATH no longer includes /cygdrive/c/Windows/system32 or that taskkill.exe has been removed from that Windows directory.

-----Original Message-----
From: Hazel

Hi, I just installed cygwin and now I can not use the native taskkill command
from windows command line, it will only reply with:

'taskkill' is not recognized as an internal or external command, operable
program or batch file.


This installation of Windows XP Pro 32Bit SP3 has been working with no
issues since it was installed a year ago.

I really need to solve this issue as ALOT of tools i have for windows uses
"taskkill" for aborting DOS programs i use for special equipment such as a
dot-matrix printer.



--
View this message in context: http://cygwin.1069669.n5.nabble.com/Cygwin-corrupted-taskkill-in-windows-commandline-tp92938.html
Sent from the Cygwin list mailing list archive at Nabble.com.
Earnie Boyd
2012-09-21 18:28:55 UTC
Permalink
Post by Voris, Ben
On my system, taskkill is /cygdrive/c/Windows/system32/taskkill. That is,
it is not part of Cygwin but is part of Windows. I suspect either that your
PATH no longer includes /cygdrive/c/Windows/system32 or that taskkill.exe
has been removed from that Windows directory.
If it is 64 bit system then it will not be available in a 32 bit
process such as Cygwin's bash in that directory. You'll need to look
at /cygdrive/c/Windows/sysnative/taskkill instead.
--
Earnie
-- https://sites.google.com/site/earnieboyd
Voris, Ben
2012-09-24 16:18:10 UTC
Permalink
From: Earnie Boyd
Sent: Friday, September 21, 2012 11:29 AM
To: cygwinAtcygwinDOTcom
Subject: Re: Cygwin corrupted taskkill in windows commandline
Post by Voris, Ben
On my system, taskkill is /cygdrive/c/Windows/system32/taskkill. That is,
it is not part of Cygwin but is part of Windows. I suspect either that your
PATH no longer includes /cygdrive/c/Windows/system32 or that taskkill.exe
has been removed from that Windows directory.
If it is 64 bit system then it will not be available in a 32 bit
process such as Cygwin's bash in that directory. You'll need to look
at /cygdrive/c/Windows/sysnative/taskkill instead.
--
Earnie
-- https://sites.google.com/site/earnieboyd
As I read it, http://msdn.microsoft.com/en-us/library/windows/desktop/aa384187(v=vs.85).aspx says that use of sysnative is optional for WOW64 applications. However, http://support.microsoft.com/kb/942589 reports a problem with directly using system32 on 64-bit version of Server 2003 and Windows XP. Perhaps the version of Microsoft Windows is the issue?

On my Windows-7 64-bit system, sysnative is not in the path but system32 is. On that system, taskkill seems to work from Cygwin.

: file $(type -p taskkill.exe)
/cygdrive/c/Windows/system32/taskkill.exe: PE32 executable (console) Intel 80386, for MS Windows

: $taskkill /?

TASKKILL [/S system [/U username [/P [password]]]]
{ [/FI filter] [/PID processid | /IM imagename] } [/T] [/F]

Description:
This tool is used to terminate tasks by process id (PID) or image name.

...

C:\> dir %SYSTEMROOT%\taskkill.exe /s
...

Directory of C:\Windows\System32

2009-07-13 18:39 112,640 taskkill.exe
1 File(s) 112,640 bytes

Directory of C:\Windows\SysWOW64

2009-07-13 18:14 77,824 taskkill.exe
Hazel
2012-09-25 18:32:20 UTC
Permalink
What is it that's so hard to understand?.

C:\Windows\system32\cmd.exe Can not execute native functions.

This is on *XP Pro 32bit* as already stated.



--
View this message in context: http://cygwin.1069669.n5.nabble.com/Cygwin-corrupted-windows-commandline-tp92938p93051.html
Sent from the Cygwin list mailing list archive at Nabble.com.
Earnie Boyd
2012-09-25 19:46:10 UTC
Permalink
Post by Hazel
What is it that's so hard to understand?.
C:\Windows\system32\cmd.exe Can not execute native functions.
This is on *XP Pro 32bit* as already stated.
Then you have an issue that is not related to Cygwin even though the
issue may have begun coincidental to you installing Cygwin.
--
Earnie
-- https://sites.google.com/site/earnieboyd
Hazel
2012-09-27 13:49:35 UTC
Permalink
What do I have to do in order to fix this?.

My XP Cd does not offer a repair option.



--
View this message in context: http://cygwin.1069669.n5.nabble.com/Cygwin-corrupted-windows-commandline-tp92938p93113.html
Sent from the Cygwin list mailing list archive at Nabble.com.
Christopher Faylor
2012-09-27 14:54:26 UTC
Permalink
Post by Hazel
What do I have to do in order to fix this?.
My XP Cd does not offer a repair option.
Fix *what*? There were suggestions in this thread. If you tried them and
they didn't work then make it clear precisely what isn't working.

Also, if this isn't an actual Cygwin problem then please look elsewhere
for help.

Loading...