5 Quick Ways to Fix Powershell Not Working

Identify issues in a clean boot environment

Reading time icon 4 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

Windows PowerShell has stopped working
XINSTALL BY CLICKING THE DOWNLOAD FILE
A message from our partner

For fixing Windows errors, we recommend Fortect:

Fortect will identify and deploy the correct fix for your Windows errors. Follow the 3 easy steps to get rid of Windows errors:

  • Download Fortect and install it on your PC
  • Launch the tool and Start scanning your PC for Windows errors
  • Right-click on Start Repair to deploy the right fix for each error encountered during the scan
Download Now Fortect has been downloaded by 0 readers this month, rated 4.6 on TrustPilot

Powershell not working is one of the most common issues with the command line tool. If you’re dealing with this problem, follow the steps below. We figured out a few ways to get rid of this error.

Just follow the easy steps below:

What can I do if PowerShell has stopped working?

1. Disable and re-enable Windows PowerShell

  1. Press Windows + R to open Run, enter appwiz.cpl in the text field, and click OK.appwiz.cpl
  2. From the left panel of the main window, click on Turn Windows features on or off.turn window features on or off to fix windows powershell stopped working
  3. Scroll down, locate the Windows PowerShell entry, uncheck the option and then click OK.disable to fix windows powershell stopped working
  4. Restart the computer for the changes to come into effect.
  5. Once the PC turns on, head back to the Windows Features window, tick the checkbox for Windows PowerShell, and click OK to re-enable it.re-enable
  6. Wait for it to install.install

After re-enabling the feature, check if the Windows Powershell stopped working issue is resolved.

2. Check your antivirus

2.1. Perform a full system scan

  1. Open Windows Defender or your third-party antivirus.
  2. Perform a full system scan.
  3. Locate and remove any suspicious files or apps.

Chances are you got infected with Poweliks, a malware that interferes with PowerShell. The file associated with this virus are dllhost.exe *32 or dllhst3g.exe *32 and can usually be stopped from Task Manager.

2.2. Temporarily disable your antivirus

It’s also possible that your antivirus is overzealous and tries to stop apps and processes that aren’t harmful.

That could be the case with Powershell. To test if this is true, disable your antivirus, and try opening Powershell again. If that’s the case, consider adjusting antivirus settings or upgrading to a better antivirus.

3. Perform a clean boot

  1. Press the Windows + R to open the Run command, type msconfig, and click OK.msconfig
  2. From System Configuration, go to the General tab, and uncheck the Load startup items field under Selective startup.uncheck to fix windows powershell stopped working
  3. Next, switch to the Services tab, check the Hide all Microsoft services checkbox and afterward click on Disable all.hide all microsoft serices
  4. Now, switch to the Startup tab and click on the Open Task Manager link.Open Task Manager to fix windows powershell stopped working
  5. Select the programs listed here individually and click on Disable at the bottom.disable startup programs to fix windows powershell stopped working
  6. Now, head back to the System Configuration window, and click on OK.click
  7. Click Restart in the prompt that appears.restart

By initiating a clean boot, you can see if a software conflict is causing Windows PowerShell malfunctions. In this way, you can start the Windows 10 system only with default features.

If the Windows PowerShell has stopped working error is not displayed after the clean boot is performed it means that there is a software conflict, so you need to remove the program responsible for this issue.

4. Create a new Microsoft account

Tip icon Tip
Remember to back up your data before completing this process. You might have to import your personal files and app under the new account.
  1. Press Windows + I to launch Settings, select Accounts from the navigation pane, and then click on Family & other users.family & other users
  2. Click the Add account button next to Add other user.add account to fix windows powershell stopped working
  3. Provide the required information and follow the on-screen instructions to complete the process.instructions

Your account might be corrupted (due to various reasons), and that’s why you still get the Windows PowerShell has stopped working error. So, try to create a new account, and the problem should be fixed.

5. Reset PowerShell to default

  1. Press Windows + E to launch File Explorer, paste the following path in the address bar while replacing Username with the one on your device, and hit Enter:C:\Users\Username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell
  2. Now, select the Windows PowerShell entry, and hit the Del key to delete it. Choose the appropriate response in case a confirmation prompt show up.delete
  3. Now, create a new user account on the same computer, head down the same path, and copy the PowerShell shortcut to a USB drive.
  4. Next, go back to the initial account, navigate to the Windows PowerShell folder, and paste the PowerShell shortcut here.

That’s it! PowerShell has now been reset to the factory settings, and any changes made will automatically be removed.

Why is Powershell not working?

Windows PowerShell may not open due to corrupted system files, conflicting third-party apps, or if it’s accidentally disabled. Many users find that clicking “Run as administrator” does nothing, often due to system corruption.

This can also affect Command Prompt, and you might see the “PowerShell is not recognized” error.

Wrapping up

Hopefully, the error message is gone now. If you have questions about the troubleshooting solutions from above, contact our team. You can get in touch with us by using the comments field below.

Also, if you come across other solutions to fix this error, list the troubleshooting steps in the comments, and we’ll update this guide accordingly.

More about the topics: PowerShell

User forum

0 messages