topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Wednesday April 17, 2024, 9:57 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Not Recognized as an Internal or External Command Error  (Read 2930 times)

deathknight47

  • Participant
  • Joined in 2014
  • *
  • default avatar
  • Posts: 2
    • View Profile
    • Donate to Member
Hii guyz...For few days I am getting a strange error while executing most of the commands via command prompt like ipconfig everytime i endup facing like ipconfig is not recognized as an internal or external command...I read about fixing the PATH in environment variables but i can't find a step by step procedure on how to fix the PATH in environment variable...If anyone can help i would really appreciate...Thanks

MilesAhead

  • Supporting Member
  • Joined in 2009
  • **
  • Posts: 7,736
    • View Profile
    • Donate to Member
Re: Not Recognized as an Internal or External Command Error
« Reply #1 on: July 08, 2014, 03:31 PM »
Right click on Computer,
click Properties,
click either Advanced Tab or Advanced System Settings (varies with Windows version)
Environment Variables should have a button near the bottom.

If it is blank you should be able to find example path,comspec and extended path strings on google.  My system path includes:

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static

I have a 64 bit system.  If yours is 32 bit you won't have C:\Program Files (x86)    it will just say C:\Program Files

Edit:  If you have W7 see this
http://www.sevenforu...iations-restore.html

deathknight47

  • Participant
  • Joined in 2014
  • *
  • default avatar
  • Posts: 2
    • View Profile
    • Donate to Member
Re: Not Recognized as an Internal or External Command Error
« Reply #2 on: July 18, 2014, 02:12 PM »
Hiii Thanks for your valuable information....The thing you have mentioned here is the same that I got from the below link that includes a step by step solution and it did worked for me :)...I think if there are some others users facing the same issue can go through the below article and fix such issue with simple trick...

http://www.rushinfor...ernal-command-fixed/

MilesAhead

  • Supporting Member
  • Joined in 2009
  • **
  • Posts: 7,736
    • View Profile
    • Donate to Member
Re: Not Recognized as an Internal or External Command Error
« Reply #3 on: July 18, 2014, 03:31 PM »
Thank you for posting the link.  :)