By namin


2008-11-20 04:19:35 8 Comments

As I sometimes have path problems, where one of my own cmd scripts is hidden (shadowed) by another program (earlier on the path), I would like to be able to find the full path to a program on the Windows command line, given just its name.

Is there an equivalent to the UNIX command 'which'?

On UNIX, which command prints the full path of the given command to easily find and repair these shadowing problems.

24 comments

@bobbogo 2019-10-08 11:37:56

Just have to post this Windows' one liner batch file:

C:>type wh.cmd
@for %%f in (%*) do for %%e in (%PATHEXT% .dll .lnk) do for %%b in (%%f%%e) do for %%d in (%PATH%) do if exist %%d\%%b echo %%d\%%b

A test:

C:>wh ssh
C:\cygwin64\bin\ssh.EXE
C:\Windows\System32\OpenSSH\\ssh.EXE

Not quite a one-liner if you wrap the code in setlocal enableextensions and endlocal.

@Gringo Suave 2019-10-31 17:49:47

Would prefer that in multiple lines so I could understand it. ;-)

@user11441889 2019-05-03 13:00:18

try this

set a=%~$dir:1
If "%for%"=="" (Echo %1 not found) else (echo %1 found at %a%)

@shalomb 2014-11-26 02:07:07

Under PowerShell, Get-Command will find executables anywhere in $Env:PATH.

Get-Command eventvwr

CommandType   Name          Definition
-----------   ----          ----------
Application   eventvwr.exe  c:\windows\system32\eventvwr.exe
Application   eventvwr.msc  c:\windows\system32\eventvwr.msc

It also finds PowerShell cmdlets, functions, aliases, files with custom executables extensions via $Env:PATHEXT, etc. defined for the current shell (quite akin to Bash's type -a foo) - making it a better go-to than other tools like where.exe, which.exe, etc which are unaware of these PowerShell commands.

Finding executables using only part of the name

gcm *disk*

CommandType     Name                             Version    Source
-----------     ----                             -------    ------
Alias           Disable-PhysicalDiskIndication   2.0.0.0    Storage
Alias           Enable-PhysicalDiskIndication    2.0.0.0    Storage
Function        Add-PhysicalDisk                 2.0.0.0    Storage
Function        Add-VirtualDiskToMaskingSet      2.0.0.0    Storage
Function        Clear-Disk                       2.0.0.0    Storage
Cmdlet          Get-PmemDisk                     1.0.0.0    PersistentMemory
Cmdlet          New-PmemDisk                     1.0.0.0    PersistentMemory
Cmdlet          Remove-PmemDisk                  1.0.0.0    PersistentMemory
Application     diskmgmt.msc                     0.0.0.0    C:\WINDOWS\system32\diskmgmt.msc
Application     diskpart.exe                     10.0.17... C:\WINDOWS\system32\diskpart.exe
Application     diskperf.exe                     10.0.17... C:\WINDOWS\system32\diskperf.exe
Application     diskraid.exe                     10.0.17... C:\WINDOWS\system32\diskraid.exe
...

Finding custom executables

To find other non-windows executables (python, ruby, perl, etc), file extensions for those executables need to be added to the PATHEXT environmental variable (defaults to .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.CPL) to identify files with these extensions in the PATH as executable. As Get-Command also honours this variable, it can be extended to list custom executables. e.g.

$Env:PATHEXT="$Env:PATHEXT;.dll;.ps1;.psm1;.py"     # temporary assignment, only for this shell's process

gcm user32,kernel32,*WASM*,*http*py

CommandType     Name                        Version    Source
-----------     ----                        -------    ------
ExternalScript  Invoke-WASMProfiler.ps1                C:\WINDOWS\System32\WindowsPowerShell\v1.0\Invoke-WASMProfiler.ps1
Application     http-server.py              0.0.0.0    C:\Users\ME\AppData\Local\Microsoft\WindowsApps\http-server.py
Application     kernel32.dll                10.0.17... C:\WINDOWS\system32\kernel32.dll
Application     user32.dll                  10.0.17... C:\WINDOWS\system32\user32.dll

You can quickly set up an alias with sal which gcm (short form of set-alias which get-command).

More information and examples can be found under the online help for Get-Command.

@TheIncorrigible1 2018-11-30 21:43:13

It finds much more than just executables. It also catches command files

@shalomb 2019-01-06 21:19:28

@TheIncorrigible1 - if you mean command files such as batch files (.BAT, .CMD, etc), they are considered executable because their extensions are named in the PATHEXT variable (which by default is PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MS‌​C;.CPL). Other executable types (e.g. .py, .rb, etc) can be added by adding the file extension in and creating an executable association with assoc/ftype - e.g. docs.python.org/3.3/using/…

@Prayson W. Daniel 2017-12-13 08:58:21

I am using GOW (GNU on Windows) which is a light version of Cygwin. You can grab it from GitHub here.

GOW (GNU on Windows) is the lightweight alternative to Cygwin. It uses a convenient Windows installer that installs about 130 extremely useful open source UNIX applications compiled as native win32 binaries. It is designed to be as small as possible, about 10 MB, as opposed to Cygwin which can run well over 100 MB depending upon options. - About Description(Brent R. Matzelle)

A screenshot of a list of commands included in GOW:

Enter image description here

@hamidreza samsami 2017-08-02 06:40:45

You can first install Git from Downloading Git, and then open Git Bash and type:

which app-name

@rogerdpack 2015-09-02 14:59:42

For you Windows XP users (who have no where command built-in), I have written a "where like" command as a rubygem called whichr.

To install it, install Ruby.

Then

gem install whichr

Run it like:

C:> whichr cmd_here

@rogerdpack 2018-03-23 14:56:26

downvoters leave comment please, cheers!

@sebastian-c 2018-06-11 15:35:26

I suspect that you're being downvoted because you're suggesting doing anything on Windows XP.

@Gringo Suave 2019-10-31 17:48:06

Didn't downvote but installing Ruby to implement a trivial command is a hard sell as well. There is a for loop above that could be put into a batch script.

@cmcginty 2012-11-30 23:00:43

In Windows PowerShell:

set-alias which where.exe

@palswim 2010-10-12 17:02:50

Cygwin is a solution. If you don't mind using a third-party solution, then Cygwin is the way to go.

Cygwin gives you the comfort of *nix in the Windows environment (and you can use it in your Windows command shell, or use a *nix shell of your choice). It gives you a whole host of *nix commands (like which) for Windows, and you can just include that directory in your PATH.

@Piotr Dobrogost 2011-08-29 09:15:08

GnuWin32 mentioned earlier by Ferruccio is much better in this case as you can have native where executable alone.

@Craig 2014-11-30 08:57:53

GnuWin32 is great, and I use it, but if you want this functionality without installing the GnuWin32 tools where.exe seems like the right call. Although, I do put the GnuWin32 tools in a \bin$ share on our network so that I can use them from workstations (and in batch files) that don't have them installed locally.

@mpasko256 2015-09-08 11:27:09

When we talk about Cygwin usage in Windows, I prefer: cygpath -w "`which <appname>`"

@Mawg 2010-03-26 00:50:50

If you can find a free Pascal compiler, you can compile this. At least it works and shows the algorithm necessary.

program Whence (input, output);
  Uses Dos, my_funk;
  Const program_version = '1.00';
        program_date    = '17 March 1994';
  VAR   path_str          : string;
        command_name      : NameStr;
        command_extension : ExtStr;
        command_directory : DirStr;
        search_dir        : DirStr;
        result            : DirStr;


  procedure Check_for (file_name : string);
    { Check existence of the passed parameter. If exists, then state so   }
    { and exit.                                                           }
  begin
    if Fsearch(file_name, '') <> '' then
    begin
      WriteLn('DOS command = ', Fexpand(file_name));
      Halt(0);    { structured ? whaddayamean structured ? }
    end;
  end;

  function Get_next_dir : DirStr;
    { Returns the next directory from the path variable, truncating the   }
    { variable every time. Implicit input (but not passed as parameter)   }
    { is, therefore, path_str                                             }
    var  semic_pos : Byte;

  begin
      semic_pos := Pos(';', path_str);
      if (semic_pos = 0) then
      begin
        Get_next_dir := '';
        Exit;
      end;

      result := Copy(Path_str, 1, (semic_pos - 1));  { return result   }
      { Hmm! although *I* never reference a Root drive (my directory tree) }
      { is 1/2 way structured), some network logon software which I run    }
      { does (it adds Z:\ to the path). This means that I have to allow    }
      { path entries with & without a terminating backslash. I'll delete   }
      { anysuch here since I always add one in the main program below.     }
      if (Copy(result, (Length(result)), 1) = '\') then
         Delete(result, Length(result), 1);

      path_str := Copy(path_str,(semic_pos + 1),
                       (length(path_str) - semic_pos));
      Get_next_dir := result;
  end;  { Of function get_next_dir }

begin
  { The following is a kludge which makes the function Get_next_dir easier  }
  { to implement. By appending a semi-colon to the end of the path         }
  { Get_next_dir doesn't need to handle the special case of the last entry }
  { which normally doesn't have a semic afterwards. It may be a kludge,    }
  { but it's a documented kludge (you might even call it a refinement).    }
  path_str := GetEnv('Path') + ';';

  if (paramCount = 0) then
  begin
    WriteLn('Whence: V', program_version, ' from ', program_date);
    Writeln;
    WriteLn('Usage: WHENCE command[.extension]');
    WriteLn;
    WriteLn('Whence is a ''find file''type utility witha difference');
    Writeln('There are are already more than enough of those :-)');
    Write  ('Use Whence when you''re not sure where a command which you ');
    WriteLn('want to invoke');
    WriteLn('actually resides.');
    Write  ('If you intend to invoke the command with an extension e.g ');
    Writeln('"my_cmd.exe param"');
    Write  ('then invoke Whence with the same extension e.g ');
    WriteLn('"Whence my_cmd.exe"');
    Write  ('otherwise a simple "Whence my_cmd" will suffice; Whence will ');
    Write  ('then search the current directory and each directory in the ');
    Write  ('for My_cmd.com, then My_cmd.exe and lastly for my_cmd.bat, ');
    Write  ('just as DOS does');
    Halt(0);
  end;

  Fsplit(paramStr(1), command_directory, command_name, command_extension);
  if (command_directory <> '') then
  begin
WriteLn('directory detected *', command_directory, '*');
    Halt(0);
  end;

  if (command_extension <> '') then
  begin
    path_str := Fsearch(paramstr(1), '');    { Current directory }
    if   (path_str <> '') then WriteLn('Dos command = "', Fexpand(path_str), '"')
    else
    begin
      path_str := Fsearch(paramstr(1), GetEnv('path'));
      if (path_str <> '') then WriteLn('Dos command = "', Fexpand(path_str), '"')
                          else Writeln('command not found in path.');
    end;
  end
  else
  begin
    { O.K, the way it works, DOS looks for a command firstly in the current  }
    { directory, then in each directory in the Path. If no extension is      }
    { given and several commands of the same name exist, then .COM has       }
    { priority over .EXE, has priority over .BAT                             }

    Check_for(paramstr(1) + '.com');     { won't return if file is found }
    Check_for(paramstr(1) + '.exe');
    Check_for(paramstr(1) + '.bat');

    { Not in current directory, search through path ... }

    search_dir := Get_next_dir;

    while (search_dir <> '') do
    begin
       Check_for(search_dir + '\' + paramstr(1) + '.com');
       Check_for(search_dir + '\' + paramstr(1) + '.exe');
       Check_for(search_dir + '\' + paramstr(1) + '.bat');
       search_dir := Get_next_dir;
    end;

    WriteLn('DOS command not found: ', paramstr(1));
  end;
end.

@paxdiablo 2010-03-26 01:30:23

Wow, there are people still using Pascal? :-)

@Mawg 2010-03-26 12:12:47

I imagine that there are. But not me. Did you see the line program_date = '17 March 1994';

@Janus Troelsen 2013-02-02 01:08:40

finding a free pascal compiler is no problem: freepascal.org

@yannis 2015-08-27 08:41:42

The unit my_funk; is unecessary. Thanks for posting a Pascal program, reminds me of my youth! It is such a pity that Pascal did not evolve.

@Mawg 2015-08-27 13:36:51

Oh, but it did. It is now object oriented, for instance. There is a great free, cross-platform, implementation and IDE at lazarus-ide.org And a direct descendant of Borland still lives in Delphi at embarcadero.com/products/delphi which is very expensive (imo) at $299 for the starter edition and $1k for the "usable" edition. However, it is cross platform - windows, iOs, Mac, Android. Get a trial edition or use Lazarus and feel 20 years younger ,-)

@piers7 2015-11-18 08:01:17

@yannis "such a pity that Pascal did not evolve" ... apart from 'Turbo Pascal' Anders going on to design C# you mean?

@Mawg 2015-11-18 08:09:10

Or Delphi, or Lazarus? A tiny thing like object orientation does not count as evolution?

@yannis 2015-11-19 05:44:12

@Mawg Delphi was the right way to go. After version 6 and when all the Borland guys fled to Microsoft it put a lot of people off, including myself.

@Mawg 2015-11-19 12:47:31

And now it costs a minimum $1k (!) unless you buy the $299 starter version, which is very limited (last starter I bought had no 64-bit code generation and, even worse for me, no database access). Lazarus is great, but a major plus for Delphi are the thousands of (free) VCL components.

@Mawg 2018-03-27 07:20:22

As of now (early 2018), they must have realized that they are losing custom, and the starter edition is now free (until you earn US $1k from it). It's only 32 bit, but there are free solutions to the restrictions. Either that, or Lazarus look good

@RexE 2008-11-20 05:16:34

If you have PowerShell installed (which I recommend), you can use the following command as a rough equivalent (substitute programName for your executable's name):

($Env:Path).Split(";") | Get-ChildItem -filter programName*

More is here: My Manwich! PowerShell Which

@scobi 2012-10-27 02:17:53

I was looking for this exact pithy powershell command. I had been using where.exe but having to mess around with the error code on top of parsing its output is far inferior to a native powershell solution. Thanks!

@jpmc26 2014-06-06 00:48:58

If you have PowerShell, you should using Get-Command.

@Craig 2014-11-30 08:56:05

But ($Env:Path).Split(";") | Get-ChildItem -filter programName* is so easy to type... ;-)

@piers7 2015-11-18 08:03:35

Downvoting in favour of Get-Command (sorry @RexE)

@dragon788 2017-04-13 15:18:24

This also fails if you have a variable in your path that is normally resolved by the system (aka %JAVA_HOME%).

@TheIncorrigible1 2018-11-30 21:44:59

Just use Get-Command. No need to parse directories.

@Giovanni Bassi 2018-06-01 02:02:25

I have used the which module from npm for quite a while, and it works very well: https://www.npmjs.com/package/which It is a great multi platform alternative.

Now I switched to the which that comes with Git. Just add to your path the /usr/bin path from Git, which is usually at C:\Program Files\Git\usr\bin\which.exe. The which binary will be at C:\Program Files\Git\usr\bin\which.exe. It is faster and also works as expected.

@David G 2017-02-09 23:31:11

TCC and TCC/LE from JPSoft are CMD.EXE replacements that add significant functionality. Relevant to the OP's question, which is a builtin command for TCC family command processors.

@user6017774 2016-09-25 01:45:38

This batch file uses CMD variable handling to find the command that would be executed in the path. Note: that the current directory is always done before the path) and depending on which API call is used other locations are searched before/after the path.

@echo off
echo. 
echo PathFind - Finds the first file in in a path
echo ======== = ===== === ===== ==== == == = ====
echo. 
echo Searching for %1 in %path%
echo. 
set a=%~$PATH:1
If "%a%"=="" (Echo %1 not found) else (echo %1 found at %a%)

See set /? for help.

@automatix 2016-04-01 12:02:00

In Windows CMD which calls where:

$ where php
C:\Program Files\PHP\php.exe

@Michael Ratanapintha 2008-11-20 05:52:50

Windows Server 2003 and later (i.e. anything after Windows XP 32 bit) provide the where.exe program which does some of what which does, though it matches all types of files, not just executable commands. (It does not match built-in shell commands like cd.) It will even accept wildcards, so where nt* finds all files in your %PATH% and current directory whose names start with nt.

Try where /? for help.

Note that Windows PowerShell defines where as an alias for the Where-Object cmdlet, so if you want where.exe, you need to type the full name instead of omitting the .exe extension.

@Michael Ratanapintha 2011-12-10 23:46:50

No, because grep examines the contents of its input, which you have to give explicitly. which and where.exe only look at the names of the files in a set of directories set in the PATH environment variables.

@Michael Ratanapintha 2012-09-25 05:40:45

@Ajedi32 - Correct, which is not in XP. As I said, "Windows Server 2003 and later".

@Ajedi32 2012-09-25 15:51:27

@MichaelRatanapintha Yeah, for some reason I was thinking that Windows Server 2003 was created before Windows XP. Man, XP is old...

@prusswan 2012-12-20 13:04:36

which means this works on XP64 (effectively WS2003)

@rob 2013-04-15 15:07:16

Works in Windows 8

@JonnyRaa 2014-01-28 14:46:59

watch out that this wont work in powershell unless you type where.exe

@Drealmer 2014-07-27 18:06:15

Warning: "where" won't work on quoted paths, be sure your %path% doesn't contain any.

@Tomasz Gandor 2015-07-08 09:00:25

Remember that where.exe is not a shell builtin, you need to have %windir%\system32 on your %PATH% - which may not be the case, as using where suggests that you may be working on problems with your path!

@Edward 2017-01-08 01:12:59

Didn't work in CMD on Server 2016 without typing where.exe

@tkokasih 2017-09-06 05:51:38

powershell Get-Command or gcm as mentioned in another answer is equivalent to where

@Emil Stenström 2018-02-08 14:50:17

Works in Windows 10 too.

@phantom-99w 2018-11-13 13:45:22

Just to be explicit: where.exe may return multiple values, in which case the first/top most one will be invoked. C:\Windows\System32> where.exe sqlcmd.exe c:\Program Files\Microsoft SQL Server\90\Tools\Binn\SQLCMD.EXE C:\Program Files\Microsoft SQL Server\100\Tools\Binn\SQLCMD.EXE C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\SQLCMD.EXE

@vulcan raven 2015-09-11 11:32:27

In PowerShell, it is gcm, which gives formatted information about other commands. If you want to retrieve only path to executable, use .Source.

For instance: gcm git or (gcm git).Source

Tidbits:

@Fez 2015-07-31 08:59:57

I have a function in my PowerShell profile named 'which'

function which {
    get-command $args[0]| format-list
}

Here's what the output looks like:

PS C:\Users\fez> which python


Name            : python.exe
CommandType     : Application
Definition      : C:\Python27\python.exe
Extension       : .exe
Path            : C:\Python27\python.exe
FileVersionInfo : File:             C:\Python27\python.exe
                  InternalName:
                  OriginalFilename:
                  FileVersion:
                  FileDescription:
                  Product:
                  ProductVersion:
                  Debug:            False
                  Patched:          False
                  PreRelease:       False
                  PrivateBuild:     False
                  SpecialBuild:     False
                  Language:

@Alexander McFarlane 2018-07-16 09:30:56

None of the other solutions worked for me but > get-command app.exe | format-list worked perfectly!

@Jean-François Larvoire 2014-12-18 13:29:59

None of the Win32 ports of Unix which that I could find on the Internet are satistactory, because they all have one or more of these shortcomings:

  • No support for Windows PATHEXT variable. (Which defines the list of extensions implicitely added to each command before scanning the path, and in which order.) (I use a lot of tcl scripts, and no publicly available which tool could find them.)
  • No support for cmd.exe code pages, which makes them display paths with non-ascii characters incorrectly. (I'm very sensitive to that, with the ç in my first name :-))
  • No support for the distinct search rules in cmd.exe and the PowerShell command line. (No publicly available tool will find .ps1 scripts in a PowerShell window, but not in a cmd window!)

So I eventually wrote my own which, that suports all the above correctly.

Available there: http://jf.larvoire.free.fr/progs/which.exe

@Jean-François Larvoire 2016-05-11 13:44:50

FYI I've open-sourced my which.exe tool mentioned above, and many others, on github.com/JFLarvoire/SysToolsLib. You may get the latest version there, report issues, etc.

@paxdiablo 2008-11-20 05:48:16

While later versions of Windows have a where command, you can also do this with Windows XP by using the environment variable modifiers, as follows:

c:\> for %i in (cmd.exe) do @echo.   %~$PATH:i
   C:\WINDOWS\system32\cmd.exe

c:\> for %i in (python.exe) do @echo.   %~$PATH:i
   C:\Python25\python.exe

You don't need any extra tools and it's not limited to PATH since you can substitute any environment variable (in the path format, of course) that you wish to use.


And, if you want one that can handle all the extensions in PATHEXT (as Windows itself does), this one does the trick:

@echo off
setlocal enableextensions enabledelayedexpansion

:: Needs an argument.

if "x%1"=="x" (
    echo Usage: which ^<progName^>
    goto :end
)

:: First try the unadorned filenmame.

set fullspec=
call :find_it %1

:: Then try all adorned filenames in order.

set mypathext=!pathext!
:loop1
    :: Stop if found or out of extensions.

    if "x!mypathext!"=="x" goto :loop1end

    :: Get the next extension and try it.

    for /f "delims=;" %%j in ("!mypathext!") do set myext=%%j
    call :find_it %1!myext!

:: Remove the extension (not overly efficient but it works).

:loop2
    if not "x!myext!"=="x" (
        set myext=!myext:~1!
        set mypathext=!mypathext:~1!
        goto :loop2
    )
    if not "x!mypathext!"=="x" set mypathext=!mypathext:~1!

    goto :loop1
:loop1end

:end
endlocal
goto :eof

:: Function to find and print a file in the path.

:find_it
    for %%i in (%1) do set fullspec=%%~$PATH:i
    if not "x!fullspec!"=="x" @echo.   !fullspec!
    goto :eof

It actually returns all possibilities but you can tweak it quite easily for specific search rules.

@Michael Ratanapintha 2009-01-01 03:27:10

Hey, I wish I had learned that! Too bad it doesn't work with MS-DOS or Win9x (that is, with command.com). (Raymond Chen has a more "elaborate" version you can turn into a batch file: blogs.msdn.com/oldnewthing/archive/2005/01/20/357225.aspx )

@paxdiablo 2009-04-09 05:41:33

@Michael, if you're still using DOS or Win95, finding executables on the path are the least of your problems :-)

@Mawg 2010-03-26 00:46:25

windows recognizes more than .exe as executable. Last time I coded a which back in W95/DOS days amdittedly, the search order was - current dir, then each path dir, for cmd.com, then cmd.exe, then cmd.bat So, even cmd.bat in current dir is executed befroe cmd.exe soemwhere in path

@paxdiablo 2010-03-26 01:34:03

@mawg, the original was for where you know the extension since it mirrors which under UNIX (where that extension-adding trickery doesn't occur). I've now added one which can do what you wish but it's no longer a simple command so much as a script. It first tries the unadorned command then each of the extension ones. Hope that helps. You can tweak it to your needs as you see fit (if you want the same search order as with Windows for example - this one shows all possibilities).

@Brad T. 2014-04-25 20:42:14

To turn this into a batch script, create a file called "which.bat": @echo off for %%i in (%1) do @echo. %%~$PATH:%i To add it to an alias.bat script that you load everytime you run cmd.exe (put the above script in a new directory called C:\usr\aliases): DOSKEY which=C:\usr\aliases\which.bat $* Then you can make a script to launch cmd.exe with the alias.bat file: cmd.exe /K E:\usr\aliases\alias.bat

@barlop 2014-06-13 10:40:59

worth noting, The example of for %i in (_____) do @echo. %~$PATH:i will find any extension not just exe. It works for file a.a or youtube-dl.py when that is in the path. But it is funny if you put a directory in there, it outputs it even if it's not in the path e.g. for %i in (%TEMP%) do @echo. %~$PATH:i

@Navaro 2019-02-20 20:12:00

Thank you I am working on a Windows 7 with no where command, and that does the the job

@Jon Court 2010-03-26 00:08:43

Go get unxutils from here: http://sourceforge.net/projects/unxutils/

gold on windows platforms, puts all the nice unix utilities on a standard windows DOS. Been using it for years.

It has a 'which' included. Note that it's case sensitive though.

NB: to install it explode the zip somewhere and add ...\UnxUtils\usr\local\wbin\ to your system path env variable.

@Kalpesh Soni 2013-05-22 19:46:56

it is not case sensitive, also i have to say which java.exe instead of which java - windows 7

@dash-tom-bang 2015-07-28 20:01:17

It has a couple of frustrations though having to do with newlines; grep for example won't match EOL without you putting in a . for the \r. It's a 99% solution though for sure!

@Michał Niklas 2008-11-20 09:39:21

I have created tool similar to Ned Batchelder:

Searching .dll and .exe files in PATH

While my tool is primarly for searching of various dll versions it shows more info (date, size, version) but it do not use PATHEXT (I hope to update my tool soon).

@Ferruccio 2008-11-20 06:44:18

The GnuWin32 tools have which, along with a whole slew of other Unix tools.

@Kalpesh Soni 2013-05-22 19:53:13

@Tim Lesher 2008-11-20 05:09:19

The best version of this I've found on Windows is Joseph Newcomer's "whereis" utility, which is available (with source) from his site.

The article about the development of "whereis" is worth reading.

@Axel Kemper 2016-01-16 19:50:45

Late comment: whereis has problems to find 64-bit executables under Win 7 64-bit.

@Robert Gamble 2008-11-20 04:28:14

Not in stock Windows but it is provided by Services for Unix and there are several simple batch scripts floating around that accomplish the same thing such this this one.

@Angel O'Sphere 2013-07-16 13:20:55

Except that the command you link only outputs the PATH variable and does not even check if the file is found there.

Related Questions

Sponsored Content

37 Answered Questions

[SOLVED] How do I install pip on Windows?

17 Answered Questions

[SOLVED] How do I run two commands in one line in Windows CMD?

46 Answered Questions

[SOLVED] How do I import an SQL file using the command line in MySQL?

29 Answered Questions

[SOLVED] How can you find out which process is listening on a port on Windows?

8 Answered Questions

[SOLVED] List all environment variables from the command line

31 Answered Questions

[SOLVED] How do I parse command line arguments in Bash?

14 Answered Questions

[SOLVED] How do I set a variable to the output of a command in Bash?

19 Answered Questions

[SOLVED] How to use unicode characters in Windows command line?

18 Answered Questions

[SOLVED] How to pass command line arguments to a rake task

10 Answered Questions

[SOLVED] How can I read command line parameters from an R script?

Sponsored Content