List is not recognized as an internal or external command как исправить

I have encountered the same problem,when attempting to perform a download and extraction of audio.

The command and output used was

C:UsersXXDownloads>youtube-dl -v https://www.youtube.com/watch?v=yu18kV88OPk&list=PLIoba2FKuOvudx9uyzWt7cF07t8VuQUYi —extract-audio —ffmpeg-location C:UsersKevinDownloadsffmpeg-20171102-d5995c5-win64-staticbin
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [‘-v’, ‘https://www.youtube.com/watch?v=yu18kV88OPk’]
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.10.29
[debug] Python version 3.4.4 — Windows-10-10.0.15063
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] yu18kV88OPk: Downloading webpage
[youtube] yu18kV88OPk: Downloading video info webpage
[youtube] yu18kV88OPk: Extracting video information
[youtube] yu18kV88OPk: Downloading MPD manifest
[debug] Default format spec: best/bestvideo+bestaudio
[debug] Invoking downloader on ‘https://r3—sn-8vq5jvh15-2gte.googlevideo.com/videoplayback?key=yt6&mime=video%2Fwebm&gir=yes&itag=43&signature=6981458E7CD1C2995129E16C623C93502BD1EC69.6D4277B58AB738884FF9DE5EE9238C1F3CE08972&clen=4241409&dur=0.000&ipbits=0&expire=1509667382&ratebypass=yes&requiressl=yes&ip=41.0.165.119&ms=au&sparams=clen%2Cdur%2Cei%2Cgir%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Cratebypass%2Crequiressl%2Csource%2Cexpire&mv=m&mt=1509645691&pl=24&id=o-AElmf-KXSy1aKqFGEZ5F97NIc95uDEBZwYw9814sXtVg&mn=sn-8vq5jvh15-2gte&mm=31&lmt=1298878154002809&source=youtube&initcwndbps=301250&ei=1l37WcnYI4SSV7KUkPgC’
[download] Potatoheadz — Narcotic (Radio Edit)-yu18kV88OPk.webm has already been downloaded
[download] 100% of 4.04MiB
‘list’ is not recognized as an internal or external command,
operable program or batch file.

I was able to subsequently extract the audio using FFmpeg,output as follows

C:UsersXXDownloadsffmpeg-20171102-d5995c5-win64-staticbin>ffmpeg.exe -i ./»Potatoheadz — Narcotic (Radio Edit)-yu18kV88OPk.webm» -vn -acodec copy ./output.ogg
ffmpeg version N-88514-gd5995c531d Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 7.2.0 (GCC)
configuration: —enable-gpl —enable-version3 —enable-sdl2 —enable-bzlib —enable-fontconfig —enable-gnutls —enable-iconv —enable-libass —enable-libbluray —enable-libfreetype —enable-libmp3lame —enable-libopenjpeg —enable-libopus —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libtheora —enable-libtwolame —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx264 —enable-libx265 —enable-libxml2 —enable-libzimg —enable-lzma —enable-zlib —enable-gmp —enable-libvidstab —enable-libvorbis —enable-cuda —enable-cuvid —enable-d3d11va —enable-nvenc —enable-dxva2 —enable-avisynth —enable-libmfx
libavutil 56. 0.100 / 56. 0.100
libavcodec 58. 1.100 / 58. 1.100
libavformat 58. 0.102 / 58. 0.102
libavdevice 58. 0.100 / 58. 0.100
libavfilter 7. 0.101 / 7. 0.101
libswscale 5. 0.101 / 5. 0.101
libswresample 3. 0.101 / 3. 0.101
libpostproc 55. 0.100 / 55. 0.100
Input #0, matroska,webm, from ‘./Potatoheadz — Narcotic (Radio Edit)-yu18kV88OPk.webm’:
Metadata:
encoder : google
Duration: 00:03:43.84, start: 0.000000, bitrate: 151 kb/s
Stream #0:0: Video: vp8, yuv420p(progressive), 480×360, SAR 1:1 DAR 4:3, 25 fps, 25 tbr, 1k tbn, 1k tbc (default)
Stream #0:1: Audio: vorbis, 44100 Hz, stereo, fltp (default)
Output #0, ogg, to ‘./output.ogg’:
Metadata:
encoder : Lavf58.0.102
Stream #0:0: Audio: vorbis, 44100 Hz, stereo, fltp (default)
Metadata:
encoder : Lavf58.0.102
Stream mapping:
Stream #0:1 -> #0:0 (copy)
Press [q] to stop, [?] for help
size= 2650kB time=00:03:43.44 bitrate= 97.2kbits/s speed=2.79e+003x
video:0kB audio:2622kB subtitle:0kB other streams:0kB global headers:4kB muxing overhead: 1.065937%

The output from youtube-dl -U was

C:UsersXXDownloads>youtube-dl -U
youtube-dl is up-to-date (2017.10.29)

The Command Prompt lets you run a variety of executable files and get complex tasks done in a jiffy. Through it, anyone with an administrator’s account can access and change settings that otherwise wouldn’t be possible.

But this command interpreter has a specific language that one must know how to read and write. Even the smallest mistake can render the command useless and generate error messages. One of the most common ones being the “not recognized as an internal or external command…” error.

So, what exactly causes this “not recognized as an internal or external command” error and how can one fix it? We’ll explain.

Related: Common Windows 10 2004 issues and available fixes: Detailed list

What does the “is not recognized as an internal or external command” mean?

This error message could basically mean one of two things:

• The filename of the executable was entered without extension and without the whole path.
• Windows didn’t find the executable that matched the filename, including its extension, in any directory mentioned in Environment Variables “Path”. 

The error occurs, as the message itself suggests, when the Command Prompt program cannot recognize the file or program that you wanted to use or execute. But there can be other problems too.

1. Executable or script not installed

It is possible that the program that you want to execute via command prompt isn’t installed properly on your system. A corrupt installer is the most common cause for this. Either that or the installed executable file is not located in the directory where the command interface is looking for it. 

2. Filename and path not specified correctly

The most common cause of the error is a typing mistake while entering the command. Moreover, if you haven’t specified the path properly, the command prompt wouldn’t know where to look for the file and thus, render the error.

If you’re getting the error, it is important to check your command character by character to ensure it is specified correctly.

3. File Directory not found in Windows Environment Variables

Another possibility is that the directory of the file that you’re trying to execute doesn’t exist in Windows Environment Variables. The series of directories known as “Path” resides under System Variables in Windows Environment Variables, and is required for the commands to be executed. That is where your file directory must be as well, especially if you’re not specifying the complete path of your file in the command prompt. 

But some programs, viruses, and malware can change these environment variables.  If this happens, then the command Prompt wouldn’t be able to recognize the commands or execute them.

4. Executables in system32 not found on 64-bit Windows

For those using 64-bit Windows, there can be another potential cause of the error.

Windows 64-bit programs have “C:WindowsSystem32” as their directory, while 32-bit programs have “C:WindowsSysWOW64” as their directory.

Although most of the executables are found in both of these directories, there are some that exist only in System32, and only a handful in SysWOW64.

By default, the Windows Environment Variables “Path” contains the folder C:WindowsSystem32. That means when running in a 64-bit environment, the command prompt is looking for the path directory in C:WindowsSystem32. Therefore if you want to run 32-bit programs, you have to execute them in a 32-bit environment.

6 ways to fix the “is not recognized as an internal or external command” error

Fixing the “not recognized as an internal or external command” error mainly has to do with correcting the problems mentioned above. With that in mind, let us look at the fixes one at a time.

Method #01: Check if the Program is installed

First and foremost, ensure that the program that you’re trying to execute through Command Prompt is actually installed on your system and is at the appropriate location. You can check if the program is actually installed on your PC in a couple of different ways. 

One way is to check the list of “Apps & Features” from Windows Settings. Here is how you can do so:

Press Win+I to open Settings and select Apps.

With Apps & features selected in the left pane, you will see the list of programs in the right pane. 

If the program is not displayed here, open up File Explorer (Win+E) and navigate to the following folder:

C:WindowsSystem32 

This directory contains all your applications’ system files. Scroll through and check if the program you’re trying to run is available (with its executable file). If it’s not, the application is not installed in this folder and you most likely can’t execute the application by simply typing in its file name. This matter can be addressed by the following.

Method #02: Move the file to the System32 Folder

When you’re trying to run a program or an executable file from Command Prompt, the latter searches through the System32 folder and runs the file. But if the file is not there, as can be the case with some programs, you can move it to the System32 folder. Here’s how you can do so.

Note: You will need to be logged in to an administrative account for the following.

First up, go to your program’s location and copy all the files that are in the folder (select all the files and press Ctrl+C for this). In our example, we want to run Microsoft Edge (msedge.exe) through the command prompt and are copying all the files present in the application’s folder.

And pasting the files (Ctrl+V) in the C:WindowsSystem32 folder. 

Now, if you just enter the name of the executable file, your command will run without errors.

Method #03: Provide the full path of the file

Another important thing to keep in mind while typing the command is that the Command Prompt doesn’t know where the file is located. If you don’t want to copy the files to the System32 folder, you will have to specify the exact location of the executable that you want to run.

For instance, if you’re trying to execute PowerToys.exe located in the PowerToys folder in C drive, the command might look like this:

C:PowerToysPowerToys.exe

This method works only if there are no spaces in your command. But if there is a space somewhere in your file’s path, then you have to do the following.

Method #04: Insert the whole file path within double quotes

The “not recognized as an internal or external command” error can also be the result of improper use of the command lines, especially when inserting file paths.

In the command prompt, a “space” is read as the end of the command. Anything entered after a space entered through the “space” or “tab” key will be read as an argument. So, if there are spaces in your file path’s location, ensure that you enclose the path within double quotes. 

In our example below, we have to run the steamservice.exe file which is within the folder C:Program Files (x86)Common FilesSteam. So, to ensure that the space in the ‘Common Files’ folder is not read as the end of the command, we will insert the whole file path within double-quotes. Like this:

"C:Program Files (x86)Common FilesSteamsteamservice.exe"

Method #05: Change Environment Variables

Windows Environment Variables is the list of paths to common system applications that the Command Prompt uses to execute programs swiftly. If these environment variables are altered, the command interface won’t be able to find the location of the executable and render the error. 

A simple way to fix this is by editing the environment variables and adding the appropriate file path there. Doing so will also allow you to run the executable by entering just the name of the file. This is how you can do so:

Press Win+R to open the RUN box and search for “Control Panel”.

Click on System and Security.

Click on System.

In the left sidebar, click on Advanced system settings.

In the “System properties” window, click on Environment Variables at the bottom. 

This will open up the “Environment Variables” window. Here, under “System variables” click to select the Variable that says Path, and then click on Edit.

Now, to add a new variable value (file location), click on New.

Here, add the folder path to the program/application you want to run through Command Prompt.

You can either do this by simply going to where your application (chrome.exe in our example) is installed and copying the path…

… and pasting it in the environment variable window;

Or through the environment variable window itself. For this, click on Browse.

Then navigate to the folder, select it, and click on OK.

Once you have added this new environment variable for the Command Prompt to access, click OK on all open windows. If you now open Command Prompt and simply enter the name of the executable file, your application will open promptly.

Method #06: Change directory to SysWOW64

As mentioned earlier, there are some 32-bit programs that only work in a 32-bit environment. And since the directory for these is C:WindowsSysWOW64, you will have to tell the command prompt to look for it here, and not in the usual system32. 

To do so, simply type in the following command:

cd c:windowsSysWOW64

Doing this will change the directory in which the command prompt looks for your 32-bit executable. 

Fix: Python is not recognized as an internal or external command

If you’re getting the same error when running Python through the command prompt, it is highly likely that Python’s executable file is missing from the environment variables. 

To fix this issue, all one needs to do is to find where Python is installed and add the path of the executable Python file to the “Path” variable in Environment Variables (as shown before). 

You will be able to run Python from the command prompt.

Fix: Python command opening Microsoft Store

On Windows 10, many have also found that sometimes, after adding Python’s path to the environment variables and running “python.exe” in the command prompt, a new problem comes up. Instead of opening python.exe directly, they are taken to the Microsoft Store. 

This is because Microsft embeds a couple of ‘fake’ executables in the folder and puts their app executable aliases in the On position. To fix this, simply search for and open “Manage app execution aliases” from the Start Menu.  Then turn Off python.exe and python3.exe.

You should be able to run python.exe from the command prompt now without being redirected to where you don’t want to go. 

Android Studio: is not recognized as an internal or external command

Android Studio has its own terminal command for executing commands. And the same error is encountered here when trying to run the ‘adb’ command.

The cause of the problem here tends to be the incorrect path to the adb folder. But it can be solved with ease if you know where the adb.exe file is located. 

By default, the adb is located in the following folder:

C:Users(username)AppDataLocalAndroidSdkplatform-tools

So, all one needs to do is to open Android Studio, click on File>Settings. In the next window, under Tools, click on Terminal. Then enter the complete location to adb in the Start Directory.

Restart Android Studio and your adb command should execute now.

Alternatively, you can change the directory in Android Studio’s terminal itself. Simply type in the following command:

cd C:Users(username)AppDataLocalAndroidSdkplatform-tools

Now, you should be able to run adb from Android Studio’s terminal command. 

CMD: Fastboot or ADB is not recognized as an internal or external command

Lastly, if you have downloaded Fastboot and are not able to execute the adb command from cmd, then it means you have to set the path to ADB in System Variables (in Environment Variables). 

Open Windows Environment Variables (as shown earlier), under “System Variables”, select Path and click “Edit”. Then add the full path to where the platform-tools folder is located (which contains adb.exe). Apply the changes.

Restart the command prompt, and you should be able to execute the adb command.

Entering the right commands in the interface and ensuring that the latter has access to the executable file is all that it takes for the command prompt to run the program/file/application that you have commanded it to. So make sure you follow the fixes mentioned herein and run your commands without any more errors.

RELATED

• How to solve Microsoft OneDrive “cannot connect to Windows” error on Windows 10 version 2004
• How to fix DISM ‘incorrectly reporting corruption’ error on Windows 10 version 2004
• How to fix the issue: This site can’t be reached. Server IP address could not be found.
• How to Fix “ERROR: x86_64 emulation currently requires hardware acceleration” on Windows

The Command Prompt is a handy way to perform specific tasks, but sometimes it doesn’t recognize what you want from it. Here’s how to fix that.

The Command Prompt in Windows is a handy utility. It allows you to perform many tasks quickly; however, the command processor may show the «not recognized as an internal or external command» error when you try to execute a command.

It is a common error and usually occurs due to incorrect command execution. This article explains the causes and a few troubleshooting steps to help you fix this error.

Why the Not Recognized as an Internal or External Command Error Occurs?

Windows OS keeps a list of paths known as Windows Environment Variables to launch and execute programs quickly. Any issues with it can cause the error.

Potential issues that cause this error include:

• Incorrect commands.
• Registry entries interrupting the functioning of commands and more.
• Executable programs or scripts not installed.
• An incorrectly specified path or filename.
• A missing file directory in Windows Environment Variables.

How to Fix the «Not Recognized as an Internal or External Command» Error

This error is often triggered when you run a program or CMD command, and something goes wrong. We have listed fixes for both versions of the error, so follow the relevant one to your case.

1. Verify if the Program Is Installed

Command Prompt can’t run a program that does not exist. If you are trying to execute a newly installed program, ensure it is correctly installed.

To verify the installation:

1. Press Win + R to open Run. Then, type control and click OK.
2. Then, in the Control Panel, go to Programs > Programs and Features.
3. Scroll through the list of installed apps and locate the app you want to run.

Alternatively, you can also view installed apps by accessing Apps and Features in Settings. To do this, press Windows key + I, click on Apps and locate the installed app.

By default, when you try to launch a program or a script from CMD, the command processor looks for the related files and paths in the System32 folder or environment variables. If the file is missing, it will return the not recognized as an internal or external command, operable program, or batch file error.

This is likely because Windows does not install most apps in the System32 folder, but C:Program Files instead.

You can resolve this issue in three ways:

1. First, use the full path of the executable file to launch the program.
2. Second, add the program path to Windows environment variables.
3. Finally, move the files to the System32 folder.

2. Use the Full File Path to Execute the Command

First, let’s try the full path method. Here, we will use the full file path instead of the app name to launch programs from Command Prompt. Here’s how to do it:

1. First, open the Command Prompt as administrator.
2. Next, type the full path of the application you want to launch. For example, if you want to open the ESBCalc Port located in the C: directory, then the command to open the app with the full path will look something like this:

    C:ESBCalcPort.exe 

3. That said, this will only work if the file path does not have any white spaces. If your file path has a space, type the file path inside double-quotes.

3. Use the Full File Path Within Double Quotes

Command Prompt reads the white spaces as the end of a command and treats anything after the space as a separate command.

Let’s say you want to launch the Internet Explorer app located in C:Program FilesInternet Exploreriexplore.exe via CMD. However, running this file path will return an error due to the space between Program Files and Internet Explorer.

To avoid this, you can insert the file path within a double quote. Here, the command to launch Internet Explorer will look like this:

 "C:Program FilesInternet Exploreriexplore.exe" 

4. Add the File Path to the Windows Environment Variables

You can edit the Environment Variables and add the file path of your application to its directory. This way, Command Prompt will identify the path for the entered command and execute it without the error.

Adding a full file path to the Windows Environment Variable can help you resolve the not recognized as an internal or external command error for the Flex, nmake, make, cobra, Is, terraform, gcc, code, Android Studio, Python, Fastboot, and ADB commands.

To edit Windows Environment Variable:

1. Press Win + R to open Run.
2. Next, type control and click OK to open the Control Panel.
3. In Windows 10, Go to System and Security > System. In the left pane, click on Advanced System Settings.
4. On newer versions of Windows 10 and Windows 11, go to Settings > System > About. Then, click on Advanced system settings under the Related settings section.
5. In the Advanced tab, click on the Environment Variables button.
   
6. In the new window, under System variables, select the Path variable.
7. Click the Edit button.
8. In the Edit window, click on New.
   
9. Here, you have to paste the program’s file path you want to run from CMD. For example, if you want to run the Chrome browser located in C:Program FilesGoogleChromeApplication, then the full file path will look like this:

    C:Program FilesGoogleChromeApplication 

10. Click OK to add it to the Environment Variables.
11. Then, click OK again.
12. Next click OK and Apply to save the changes.

Once you have added the new environment variable, restart your PC to apply the changes. After the PC restarts, open Command Prompt, enter the program’s name, and CMD will open it without any error.

If you experience issues with the commands like ipconfig, netsh, cipher, etc., then add the Windows system root folder file path in the Environment Variable dialog. Here’s how to do it.

1. Open the Environmental Variables dialog.
   
2. Next, select the Path variable under the System variables section and click on Edit.
3. Click New and paste the following:

    %SystemRoot%system32 

4. Click OK to save the changes.
5. Click OK, and then click OK and Apply to save the changes.

5. Move Files to System32 Folder

System32 is a protected system folder, and it is protected for a good reason. When you try to launch a program as an administrator, Command Prompt looks for the executable file in the System32 folder. However, since all the programs are not installed in the System32 folder, you may end up with an error.

If you still want to run the program from CMD and don’t want to type a full file path, you can move the program files to the System32 folder.

To move program files to the System32 folder:

1. Navigate to the installation directory for your program and copy all the files in the folder. Here, we will move Google Chrome files located in C:Program FilesGoogleChromeApplication to the System32 folder.
2. Next, navigate to the C:WindowsSystem32 folder and paste the copied files. Click Yes if a UAC prompt appears.
3. Next, open the Command Prompt as administrator, type chrome, and hit enter. CMD will instantly open the Google Chrome browser.

Fixing the CMD Not Recognized as an Internal or External Command Error

Command Prompt commands are not case-sensitive, but it does not forgive the use of extra spaces. To resolve this error, check if the commands are correct and use file paths with spaces within double-quotes. For the programs not installed in the System32 folder, add an environment variable with your application’s full file path to launch apps through CMD.

• MiniTool
  

• MiniTool News Center
  

• Fix “Not Recognized As an Internal or External Command” Win 10

By Alisa | Follow |
Last Updated September 01, 2022

If a command is not recognized as an internal or external command, it may be due to the messed up environment variables. Check how to fix this error in this post. To help you tackle data loss, manage hard drive partitions, backup and restore system, MiniTool software provides professional tools.

If you meet the error “command is not recognized as an internal or external command, operable program or batch file” problem in Command Prompt in Windows 10, the reason may be that the Windows Environment Variables are messed up. Check what Windows Environment Variables are and how to fix this error below.

Windows Environment Variables

Windows OS has a list of path to record the locations of most common system applications. When you use the Run prompt or CMD.exe to open a program, it can launch easily. This list is called Windows Environment Variables.

Your operating system uses the PATH system variable to locate needed executables from the Command Prompt or Terminal application.

If the Windows Environment Variables are messed up, it may cause some programs not working like Command Prompt not working.

You can learn how to fix not recognized as an internal or external command error in Windows 10 when you try to execute a command or open a system program in Command Prompt.

How to Fix Not Recognized As an Internal or External Command

Step 1. Go to C:WindowsSystem32 to check if the program actually exists. You can search and find the target exe file in System32 folder. If the program exists, then you can continue to modify the Windows Environment Variables to fix Command Prompt not recognizing commands errors.

Step 2. You can right-click This PC icon and select Properties. Click Advanced system settings to open System Properties window. After that, click Advanced tab and click Environment Variables.

Step 3. Then you can click Path under System variables, and click Edit button. Before you edit the PATH system variable, it’s advised you copy and paste the old environment variables to a text file to make a backup. In case something goes wrong, you can easily revert them.

Step 4. Check if there is a directory path of the executable file location, if not, enter the location of the executable file’s parent folder. After you edit the value, you can click OK.

Step 5. Then you can reboot your computer and execute the command again to see if the “not recognized as an internal or external command” problem is fixed in your Windows 10 computer.

How to Recover Deleted/Lost EXE Files in Windows 10

If some exe files are automatically or mistakenly deleted or unexpectedly lost in your Windows 10 computer, you can use MiniTool Power Data Recovery to easily recover exe files.

MiniTool Power Data Recovery is a professional easy-to-use data recovery program for Windows 10. You can use it to recover any deleted/lost files (incl. application exe files) from Windows 10 computer with ease. Still, this best data recovery software also allows you to recover deleted/lost files from external hard drive, USB flash drive, pen drive, thumb drive, SD card, and more. The free edition allows you to recover up to 1GB data totally for free. 100% clean and safe software, and extremely intuitive interface.

About The Author

Position: Columnist

Alisa is a professional English editor with 4-year experience. She loves writing and focuses on sharing detailed solutions and thoughts for computer problems, data recovery & backup, digital gadgets, tech news, etc. Through her articles, users can always easily get related problems solved and find what they want. In spare time, she likes basketball, badminton, tennis, cycling, running, and singing. She is very funny and energetic in life, and always brings friends lots of laughs.