The “PowerShell has stopped working” error is a common Windows crash message that can pop up randomly or every time you try to open PowerShell. It usually stems from corrupted system files, malware, conflicting third-party software, or a feature that’s been accidentally disabled — and most of the fixes are quick to try.
Why This Error Happens
This error generally indicates a crash within PowerShell caused by an underlying issue in the system or in a script that PowerShell can’t process correctly. A few causes come up repeatedly across reported cases:
- Malware infection — one of the most common reasons for this message is a hidden virus on the computer, which slows down the system and can interfere with other running processes.
- A specific malware family called Poweliks — your PC may be infected with Poweliks, a piece of malware known to interfere with PowerShell, typically running as dllhost.exe *32 or dllhst3g.exe *32, which can be stopped through Task Manager.
- Corrupted or conflicting system files — recent updates, file corruption, or third-party software conflicts are all frequently cited culprits.
Fix 1: Run a Malware Scan
Since malware is such a common cause, this is usually the first thing worth trying. It’s recommended to enter Safe Mode with networking before running the scan, then use antivirus software like Malwarebytes to scan your system files — if Poweliks or similar malware is found, the antivirus should remove it automatically.
Fix 2: Disable and Re-Enable the PowerShell Feature
Toggling PowerShell off and back on through Windows Features resolves the issue for many users:
- Open Control Panel and select Programs.
- Click Uninstall a program, then Turn Windows features on or off in the left panel.
- Find Windows PowerShell in the list and uncheck it, then click OK to save.
- Restart your PC, repeat the steps above, and re-check the box to re-enable the feature.
Following this process — disabling the feature, restarting, then re-enabling it — has fixed the error for a number of users.
Fix 3: Run an SFC Scan
If corrupted system files are behind the crash, Windows’ built-in repair tool can help. Running an SFC scan lets Windows automatically repair corrupted system files, after which you can check whether PowerShell launches normally.
Fix 4: Perform a Clean Boot
Third-party software conflicts are another frequent trigger. Performing a clean boot lets you check whether a conflicting piece of software is causing the crash — if the error stops occurring during a clean boot, you can narrow down and remove the specific conflicting app.
Fix 5: Check Your Antivirus Settings
Some antivirus tools actively block PowerShell rather than just failing to catch malware. Certain antivirus software, such as Smadav, has been known to block PowerShell from opening — temporarily disabling your antivirus can confirm whether it’s the cause, and if so, enabling an option like “Allow Windows Script” within the antivirus settings can resolve it.
Fix 6: Reset Group Policy Settings
If malware has altered system-level settings rather than just running in the background, this can also block PowerShell. Viruses can interfere with the Windows registry and Group Policy settings, so resetting Group Policy Settings back to default can fix the problem if that’s the underlying cause.
Fix 7: Try a System Restore
If the issue started after a recent change to your system, rolling back can help. Since the error may be caused by recent updates or file corruption, trying a System Restore to return to a previous, working configuration is worth attempting.
Fix 8: Create a New User Account
If none of the system-wide fixes work, the problem might be isolated to your specific user profile. Your account might be corrupted for various reasons, and creating a new user account often resolves the issue when other fixes don’t.
Fix 9: Review Startup Programs
Unsigned or unfamiliar startup programs can also interfere with PowerShell. Using a tool like Autoruns to review the list of programs running at startup — and removing any that aren’t digitally signed — can help identify and eliminate the culprit.
Common Mistakes to Avoid
- Skipping the malware scan because the error “feels” like a system settings issue — infections are one of the most frequently confirmed causes.
- Only toggling the PowerShell feature once instead of restarting between the disable and re-enable steps, which can prevent the fix from taking effect properly.
- Ignoring third-party antivirus software as a possible cause, since some security suites are known to actively interfere with PowerShell rather than just fail to detect a threat.
Join The Discussion
Have you run into the “PowerShell has stopped working” error, and which fix ended up solving it for you? Whether it turned out to be malware, a disabled feature, or a conflicting antivirus tool, share your experience and any troubleshooting steps you’d add to this list. If you’ve found a fix that isn’t mentioned here, it’d be great to hear what worked and how you tracked down the root cause.
