Share via

What might be the issue if the error message 'exec: "powershell": executable file not found in %PATH%' appears when attempting to run PowerShell commands in a terminal on a Windows system?

Anonymous
2024-02-26T06:45:22+00:00

while using the PowerShell after the installation of IIS, I encountered the following error " exec: "powershell": executable file not found in %PATH% ", but the environmental variables are didn't change. can you please provide a solution without rebooting the server.

Windows for business | Windows Server | Windows cloud | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-02-27T06:17:09+00:00

    Hello Naveen Kumar Sakthivel,

    Thank you for posting on the Microsoft Community Forum.

    The error message "exec: "powershell": executable file not found in %PATH%" indicates that the PowerShell executable file is not found in the system's PATH environment variable.

    To troubleshoot this issue, you can try the following steps:

    1. Check if the PowerShell executable file is present in the system's PATH environment variable. You can do this by opening a command prompt and typing "echo %PATH%". If the PowerShell executable file path is not present in the output, you need to add it to the PATH environment variable.
    2. To add the PowerShell executable file path to the PATH environment variable, open the Control Panel, go to System and Security, and click on System. Click on the "Advanced system settings" link on the left-hand side, then click on the "Environment Variables" button. In the "System variables" section, scroll down and find the "Path" variable, then click on the "Edit" button. Add the path to the PowerShell executable file (usually C:\Windows\System32\WindowsPowerShell\v1.0) to the end of the "Variable value" field, separated by a semicolon (;).
    3. After adding the PowerShell executable file path to the PATH environment variable, open a new command prompt and try running PowerShell commands again. If the issue persists, you may need to repair or reinstall the PowerShell installation.

    Note: If you do not want to reboot the server, you can try restarting the "Windows Explorer" process from the Task Manager. To do this, open the Task Manager, find the "Windows Explorer" process, right-click on it, and select "Restart". This will refresh the system's environment variables without requiring a reboot.

    I hope you the information above is helpful.

    If you have any questions or concerns, please do not hesitate to let us know.

    Best Regards,

    Daisy Zhou

    0 comments