#WINDOWS POWER SHELL STOPPED WORKING WINDOWS#

So the problem that the 90% of people are likely to encounter is that as soon as the script path has a space in it (either in the filename itself or in the directory path the file resides in), they will see the powershell console flash some red text at them for about 1/10th of a second before it closes, and they will be wondering why the script did not run or worse, they wonвЂ™t know that it didnвЂ™t run (see the вЂњKeep PowerShell Console OpenвЂќ section below). Error message when trying to run a script whose path contains spaces This is probably how 90% of people run their PowerShell scripts power uses might run their scripts directly from the PowerShell command prompt. If you donвЂ™t mind opening in an editor as the default action, then to run the script you can just right-click on the script and choose вЂњOpen withвЂќ вЂ“> вЂњWindows PowerShellвЂќ.

#WINDOWS POWER SHELL STOPPED WORKING WINDOWS#

ps1 filesвЂќ option is checked (this might be called вЂњAlways use the selected program to open this kind of fileвЂќ or something else depending on which version of Windows you are using). Just right-click on the script, go to вЂњOpen withвЂќ вЂ“> вЂњChoose default programвЂ¦вЂќ, and then select Windows PowerShell, making sure the вЂњUse this app for all. If this bugs you, itвЂ™s easy enough to fix. The default Windows action when you double click on a PowerShell script is to open it in an editor, rather than to actually run the script.

Make running (instead of editing) the default PowerShell script action Most of the other content in this post can be found elsewhere, but I provide it for context and completeness. Most people will likely find the вЂњRun script path with spaces from File ExplorerвЂќ (to be able to double click a PS script whose path contains spaces to run it) section below the most helpful. Fix Problem Where Windows PowerShell Cannot Run Script Whose Path Contains Spaces

Windows power shell stopped working