HOW TO FIX €˜IS NOT RECOGNIZED AS AN INTERNAL OR EXTERNAL COMMAND€™ ERRORS

If you’re coming up against ứng dụng or commvà ‘is not recognized as an internal or external command’ errors when trying to lớn bởi something in the commvà line, update an phầm mềm or install something new, you’re not alone. It happens when Windows environmental variables are changed which prsự kiện the comm& being run.

Bạn đang xem: How to fix ‘is not recognized as an internal or external command’ errors

Fix ‘CMD commvà is not recognized’ errors

If you’re trying to lớn run a CMD commvà & are seeing ‘CMD is not recognized as an internal or external command’, that could be something different. Trying the above sầu fix may work but the issue may be being caused by a couple of registry entries that are interrupting the normal chain of commands.

Somehow, if you have AutoRun set in the registry, certain CMD commands such as ping or nslookup won’t always work. They return the error above. The .exe cộ is present & everything may look correct, but these two small entries are ruining your day.

Xem thêm: Cách Nhớ Dãy Hoạt Động Kim Loại, Dãy Hoạt Dộng Hóa Học Của Kim Loại Lớp 9

Those registry entries are:

HKEY_LOCAL_MACHINESoftwareMicrosoftCommand ProcessorAutoRun

HKEY_CURRENT_USERSoftwareMicrosoftCommand ProcessorAutoRun

This issue is at least a decade old. I have sầu a bookmark for an MSDoanh Nghiệp blog entry from 2007 that I have saved illustrating this very thing.

Navigate khổng lồ C:WindowsSystem32 and make sure the CMD executable is present.Perkhung the Environmental variables check as above. If that doesn’t fix it move on.Run the commvà ‘cmd /d’ which apparently stops autorun from running. If the message is the same, move sầu on.Find those two registry entries listed above & delete them.

This fix is old but gold. I used to lớn use this when I worked IT Admin at a well-known cable company. That is why I still have sầu it as a bookmark. The ‘comm& is not recognized as an internal or external command’ error has been around that long và as far as I know, the fix is still the same even five generations of Windows later. Nevertheless, if you bởi vì come across the error, at least you now know what lớn vì.

When was the last time you saw the ‘is not recognized as an internal or external command’ error in Windows? Did you use one of these solutions or something else?