Devcon is not an internal or external team. "Filename" is not an internal or external command, operable program, or batch file

Many users, when typing a series of commands in the console (or utility window), some of which are "adb", "javac", "telnet", "fastboot" may encounter a system failure to execute this command. And an accompanying message that the specified command is "Not an internal or external command, operable program, or batch file" . This is usually due to the fact that the path to the file serving the given command, and also with the fact that the required component is simply not installed in the system. In this article, I will tell you what the essence of the error “This is not an internal or external command of an executable program (adb, javac, telnet, fastboot)” is, and how to fix it.

The essence and causes of dysfunction (adb, javac, telnet, fastboot)

As I mentioned above, the reason for this message is that the system does not know the location of the files that are launched by these commands (usually the files have the same names as the commands, for example, the “fastboot” command is implemented through the fastboot.exe file).

The path to the desired file is usually specified in the variable "PATH" system settings (there must be a clear path to the directory in which specified files). If the required paths are not written there, then when you enter any of the described commands, the system gives an answer that (file name) is not an internal or external command of the executable program.

Also, the reason for the lack of support for such commands (in particular, "telnet") is the absence of this component in the system (you must install it yourself).

Not an internal or external team - how to fix

To get rid of the error “It is not an internal or external command”, you need to specify the path to the system (in English - “path”) to the directories where the files we need are located.

To do this, you need to know exactly where these files are located (for example, "javac" can be located along the path C:\Program Files\Java\jdk 1.8.0.45\bin (instead of "jdk 1.8.0.45" it can be "jdk" with another You need to copy the specified path to the clipboard (mark it with the cursor, and then press the key combination Ctrl + C).

1. Then go to the PC desktop, hover over "My Computer", click on the right mouse button, select "Properties" in the menu that appears.
2. In the window that opens, click on "Advanced system settings" on the left, and then on the "Environment Variables" button.
3. In "System Variables" look for the "Path" parameter, and add there after the semicolon the full path you copied earlier from the Program Files\Java directory.
4. Confirm the changes by clicking on "OK", then reopen the console, and type the desired command (you can also reboot the system for prevention), the error can be fixed.

An alternative would be to transfer non-executable files to directories known to the system (for example, to the common root directory of the Windows OS, or to C:\Windows\System32), usually the system works with them quite correctly.

https://youtu.be/awfBpttu-g4

Also, in the case of some components (for example, “telnet”), the problem with them arises due to their absence in the system, so they need to be reinstalled.

1. In the case of "telnet", this is done by going to "Control Panel" - "Programs and Features" - "Turn Windows features on or off".
2. We find "Telnet Client" there, put a tick to the left of it, and click on "OK".
3. The program will be installed and the "telnet" functionality should work correctly.

Conclusion

The error "Not an internal or external command (adb, javac, telnet, fastboot)" is usually caused by the system not having location information given file(the latter is usually placed in the "Path" variable), or the absence required component in system. To fix the error “is not an internal or external command”, I recommend that you specify the full path to the folder where the file is located in the “Path” parameter, as well as install the problematic components in the system (if there are none initially). This will stabilize the system and fix the error "This is not an internal or external command" on your PC.

Let's get back to my problem. To display all existing network devices in the system, enter the following:

C:\>devcon.exe find =net

The program displayed 7 devices! I only have 2 on my server network cards Intel® PRO /1000EB Network Connection. But then I remembered that the device manager does not display hidden devices. To see them, you need to select “View” -> “Show hidden devices” in the Device Manager window from the menu. Now everything is back to normal! :)

In order to disable all shown network devices, you must issue the following command (better not to do this remotely!):

C:\>devcon.exe disable=net

The device manager will honestly show us that all network devices are disabled. The network is completely disabled, which is what we needed.

In order to enable network devices, you must issue the command:

C:\>devcon.exe enable=net

Let's check the inclusion of all network devices in the device manager.

It remains for us to write two batch files with the above commands to enable and disable network devices and make tasks based on them so that they run at the right time.

It only remains for me to remind you, since with the help of the DevCon program you can disable almost any device on your computer, you must use it very carefully! Do not turn off devices by mask, do not turn off devices unknown to you, in this way you can make your operating system completely inoperable.

When you try to open any command through a utility window or console, you encounter an error - "Filename" is not an internal or external command, operable program, or batch file. The system stubbornly does not open the file for some reason and this fact is very annoying. The reason for this may be one of several options: the path to the file is incorrectly specified and the absence of the component in the system at all, i.e. it does not exist at the specified address.

The main reasons why the error "is not an internal or external command" appears

As already mentioned, one of the reasons is the incorrect path to the file being opened. Usually, the path to the file is registered in the "Path" variable in the system; a strict path to the directory in which the files are located must be specified. required files. If there are any errors in the settings when specifying the path in a variable, or when specifying the file name, then the system will generate just such an error - “file name” is not an internal or external command executed by the program.

The first step is to specify the exact path of the "Path" variable to the operating system so that there are no errors when opening the file. To do this, you need to know the location of the folder for sure. For example, let's turn to a program that will later work with an executable file in a specific folder.

The "Path" variable is an operating system variable that is used to find the specified executable objects through the command line or terminal. You can find it in the panel Windows controls. In new Windows versions and other operating systems, manually specifying is usually not required.

Specify the correct path in the path variable on Windows 7

To correctly specify the path, you need to know the exact location of the file. If the program file to be opened is located on the disk in C:\Program Files\Java\jdk 1.8.0.45\bin, then this path must be copied and specified in the system variable for subsequent opening.

In the event that the error appears again, try moving the program to the working directories of the disk with the installed operating system, for example /System32. Windows works with this directory more often.

Also, errors occur due to the lack of program components. You can eliminate them by adding the necessary ones. Let's take the Telnet component as an example. To enable it, go to:

Set "Path" variable in Windows 8/8.1/10

1. We go to the "Control Panel".
2. Click on the "Advanced system settings" link.
3. Find "Environment Variables". In this section, you need to select "Path". Then "Change", if not ready - create anew.
4. In the "Change system variable" item, specify the value you need and confirm with the "OK" button. Close all other windows by clicking OK.
5. Reopen your command prompt or terminal and try typing your prompt again. Now everything should work properly.