You can simply put a shortcut to the program into C:WindowsSystem32 and that should make everything work fine. If those two path changes don’t work, there is a workaround.

If that is the case with your computer, just add %SystemRoot% again.Īnother way to fix program is not recognized as an internal or external command It is most likely removing a path that would cause issues. Adding a path should not affect your computer in any way. Just perform steps 1 to 4 and instead of Delete, select New and add the path you changed. If you find issues with other programs not executing, you can repeat the above steps and reverse your changes. There are applications out there that add registry entries that directly conflict with %SystemRoot% which is why removing it should work. Plus, %SystemRoot% is known to cause issues when used as a system path on some configurations. Otherwise, removing the %SystemRoot% entry should do the trick.Īs long as you have C:WindowsSystem32 present, you shouldn’t need %SystemRoot% as they point to the same place. In the vast majority of cases, adding, or re-adding C:WindowsSystem32 to the path will fix the ‘PROGRAM is not recognized as an internal or external command, operable program or batch file’ error.

If the retest fails, repeat this process and delete the %SystemRoot% entry.Confirm and close all windows and retest.Make sure C:WindowsSystem32 is present.Highlight Path in the bottom box and select Edit.Select the Environment Variables at the bottom of the Advanced tab.Select System and Advanced system settings.Type ‘control’ into the Cortana/Search Windows box and select Control Panel.

Wusa is not recognized