In most cases, this error stems from faulty system files or corrupted third-party apps. As such, let’s check out how you can easily fix PowerShell if it goes unresponsive often.
1. Enable the Windows PowerShell
This error might pop up simply because the Windows PowerShell is disabled. So, you can tackle the issue by tweaking a few settings as follows:
Type Turn Windows Features on or off in the Start Menu search bar and select the Best match. Locate the Windows PowerShell option and click its drop-down menu. Check all the Windows PowerShell boxes, press OK, and then close the Windows Features screen. Finally, restart your device to apply these changes.
2. Run the Windows PowerShell With Administrative Privileges
Opening the Windows PowerShell with administrative privileges might help. So, let’s check out how you can do this:
Type Task Manager in the Start Menu search bar and select the Best match. Click the File tab in the top-left corner and select the Run new task option. Type Powershell and check the Create this task with administrative privileges box. Finally, click OK to open an elevated PowerShell window.
3. Try Using a Different Microsoft Account
In some instances, this issue might only be affecting the account you’re currently using. So, the best way to tackle the issue is to use a different Microsoft account. If you don’t have a Microsoft account, you might just consider creating it to check if this resolves the issue.
Now, here’s how you can create or sign in to a Microsoft account on Windows:
Click the Windows key and select the Settings option. Select Accounts and then click Email & accounts on the left-hand side. Click Add a Microsoft account on the right-hand side and fill in your details.
Follow the on-screen instructions and then try open the PowerShell tool.
If the issue persists, then you’re likely dealing with system issues. In this case, we’ll show you how you can resolve the problem.
4. Get Rid of Suspicious Third-Party Programs
Some faulty third-party apps might be the ones responsible for this error. However, you might find it difficult to locate the corrupted app that’s causing this issue. In this case, performing a clean boot will help you out.
Once you find the faulty app, you could either update it or completely get rid of it. And if you decide to delete the problematic app, use a reliable third-party uninstaller. This will help get rid of the residual files that might remain and cause other issues.
5. Try the Built-In Troubleshooters
There are a couple of built-in troubleshooters that you can use in various situations. If we assume that this error is caused by system maintenance issues, then the System Maintenance troubleshooter could help.
So, let’s check out how you can run this troubleshooter to tackle the issue at hand:
Type Control Panel in the Start Menu search bar and select the Best match. Click the View by drop-down menu and select Small icons. Click Troubleshooting from the menu items. Next, scroll down and select the System and Security option. Click the System Maintenance option. Next, click Advanced and then check the Apply repairs automatically box. Finally, press Next and follow the on-screen steps.
If the issue persists, then we should take a different approach. Since this might be a hardware-related problem, let’s see how the Hardware and Devices troubleshooter could help:
Press Win + I to open the System Settings. Select Update & Security and then click Troubleshoot on the left-hand side. Locate and click on the Hardware and Devices troubleshooter. Finally, press the Run the troubleshooter button and follow the on-screen steps.
6. Perform a System Scan
This error could be caused by faulty system files. In this case, you’d need to perform a system scan and repair those problematic files.
And when it comes to scanning and repairing system files, you can always rely on the Check Disk, DISM, and SFC tools.
Now, let’s get started and check how you can run a Check Disk scan:
Open the Start Menu search bar and type Command Prompt. Right-click on the Command Prompt option and select Run as administrator. Type the following command and press Enter to run a Check Disk scan:
Replace the C: command with the correct drive letter if your Windows OS is installed on a different drive.
After running this scan, follow these steps to run the DISM tool:
Open an elevated Command Prompt by following the previous steps. Type the following command and press Enter:
From there, type the command below and press Enter:
Restart your device once the scan is complete. Now, run an SFC scan through these steps:
Open an elevated Command Prompt as per the previous steps. Type the following command and press Enter:
Wait for the SFC scan to complete and then restart your device.
7. Restore Your Windows Device
Restoring your device with the System Restore tool could also help. The System Restore feature helps undo any recent changes that might be causing system errors. So, this might also get rid of the bugs that are interfering with PowerShell.
Now, here’s how you can use the System Restore tool to tackle this issue:
Type Control Panel in the Start Menu search bar and select the Best match. Click the View by drop-down menu and select Small icons. Scroll down and select the Recovery option. Now, click the Open System Restore option and click Next to continue. Select a restore point from the options, press Next, and then follow the on-screen steps.
8. Reset the Device to Its Factory Settings
As a last resort, resetting Windows to its factory settings could help. But before you proceed, keep your data safe by backing up your device.
Now, here’s how you can reset your Windows device:
Press Win + I to open the System Settings. Click Update & Security and then select Recovery on the left. Finally, press the Get started button on the right and follow the on-screen instructions.
Automate Your Favorite Tasks With the Windows PowerShell
The “PowerShell has stopped working” error can be quite annoying—especially if you don’t know what’s causing it. Fortunately, the methods we’ve covered should help you easily get rid of this error.
