title: Windows 10 powershell 'node' not recognized as the name of a cmdlet, function, script file, or operable program
body: <p><code>PS C:\Users\DELL&gt; node (OR) gcc --version (OR) g++ --version
  node: The term 'node' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
  the spelling of the name, or if a path was included, verify that the path is correct and try again.
  At line:1 char:1</p>
  <ul>
  <li>node</li>
  <li>
  <pre><code>  + CategoryInfo          : ObjectNotFound: (node:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
  </code></pre>
  </li>
  </ul>
  </code>
  I m having a problem with my Windows 10 Powershell, whenever I tried to get run code of (node/c++/c) via VS code I am getting an error in PowerShell, I have tried restarting my laptop also tried Restarting PowerShell and edited environment paths still <b>I am having the same error I think my Powershell Files got corrupted!</b> please help me I am new to Stackoverflow and A student of B.Sc.IT so my vs code editor for learning purposes is also dependent on Powershell I get totally stuck !! , Thanks in advance!
  <p><b>Due to Posting answer ban I m writing here hope it helps the community</b></p>
  <p>Actually, I have Tried the Following ways to solve this issue on windows 10~</p>
  <ul>
  <li>System Restore</li>
  <li>Powershell Restart</li>
  <li>Powershell Files Replace (with other window system's files in Program files..etc)</li>
  <li>Restart PC after troubleshooting</li>
  <li>Environment path change
  but didn't anything work...
  <b>But finally after windows 11 upgrade its automatically solved my issue</b></li>
  </ul>
  <blockquote>
  <p><i> I recommend you to install certain things(Apps, software, etc..)
  from the official Trusted website and do not tamper with system files
  unless necessary also avoid using Crack versions and multiple   .NET
  frameworks and installers on the same system unless necessary use only
  1 INSTALLER OF .NET VISUAL STUDIO latest in my case I think it was the
  problem...!! </i></p>
  </blockquote>