sodcalculator

10 Tech How-To

Fix Windows PowerShell High CPU Usage in Windows 11

Guide 10-54776 · Updated · Step by step

If PowerShell is constantly using high CPU in Windows 11, the issue usually stems from a stuck script, a corrupted profile, or a misbehaving scheduled task. This guide walks you through the most effective fixes, from quick checks to deeper system repairs, so you can restore normal performance.

Why PowerShell Uses High CPU in Windows 11

PowerShell is a legitimate system component that runs background scripts, scheduled tasks, and system maintenance. Occasional spikes are normal, but sustained high CPU (above 30% for minutes) indicates a problem. Common causes include:

  • Infinite loops or hung scripts – a script that never exits can peg a CPU core.
  • Corrupted PowerShell profile – a profile with errors loads on every session, causing repeated failures.
  • Scheduled tasks gone rogue – tasks that run PowerShell with high frequency or without proper completion.
  • Malware or unwanted software – some threats disguise themselves as PowerShell processes.
  • Windows Update or system file corruption – broken system components can trigger repeated PowerShell repair attempts.

Quick Checks Before Deep Fixes

Start with these simple steps to rule out temporary issues:

  1. Restart your computer – clears stuck processes and resets the PowerShell runtime.
  2. Check Task Manager – press Ctrl+Shift+Esc, go to the Processes tab, and look for Windows PowerShell or pwsh. Note the CPU column and whether it fluctuates.
  3. End the problematic process – right-click the PowerShell entry and select End task. If it restarts and still consumes CPU, continue with the fixes below.

Fix 1: Clear or Repair Your PowerShell Profile

A corrupted profile is one of the most common culprits. To test, temporarily rename the profile file:

  1. Open File Explorer and navigate to %UserProfile%\Documents\WindowsPowerShell (or %UserProfile%\Documents\PowerShell for PowerShell 7).
  2. Find the file named Microsoft.PowerShell_profile.ps1 (or profile.ps1).
  3. Rename it to profile.ps1.bak.
  4. Restart PowerShell and monitor CPU usage. If it drops, the profile had a problematic script. You can open the .bak file in Notepad to review and edit it, then restore it after fixing the issue.

If you don’t see a profile file, it’s not the cause—skip to the next fix.

Fix 2: Scan for Malware and Unwanted Software

Malware often hides under legitimate process names. Run a full system scan with Windows Security:

  1. Open Windows Security (search in Start menu).
  2. Go to Virus & threat protection > Scan options.
  3. Select Full scan and click Scan now. This can take over an hour, so plan accordingly.

If you have a third-party antivirus, run its full scan as well. Also check for recently installed apps you don’t recognize in Settings > Apps > Installed apps—uninstall anything suspicious.

Fix 3: Disable or Repair Problematic Scheduled Tasks

Windows runs many PowerShell-based tasks. A task that fails repeatedly can cause high CPU. To find and fix:

  1. Open Task Scheduler (search “Task Scheduler” in Start).
  2. Navigate to Task Scheduler Library and look for tasks that trigger PowerShell (you can sort by the “Actions” column or check the task’s Properties).
  3. For any task you suspect, right-click and select Disable to test. If CPU drops, re-enable and edit the task to fix the script or schedule.
  4. You can also check the task’s History tab for errors.

Be cautious: don’t disable system-critical tasks like Windows Update or Defender. Only disable tasks you recognize as non-essential.

Fix 4: Run System File Checker and DISM

Corrupted system files can make PowerShell behave erratically. Run these built-in tools:

  1. Open Command Prompt as Administrator (right-click Start > Terminal (Admin)).
  2. Type sfc /scannow and press Enter. Wait for the scan to complete (may take 15-20 minutes).
  3. If SFC finds issues, run DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This can take longer.
  4. Restart your PC after both commands finish.

These tools repair system files without affecting your personal data.

Fix 5: Update Windows and PowerShell

An outdated system or PowerShell version may have bugs that cause CPU spikes. Check for updates:

  1. Go to Settings > Windows Update and click Check for updates. Install all pending updates, then restart.
  2. For PowerShell 7 (if installed), update it via the Microsoft Store or by running winget upgrade Microsoft.PowerShell in a terminal.

Windows 11 updates often include fixes for PowerShell-related issues.

Fix 6: Create a New User Account (Last Resort)

If nothing else works, your user profile may be corrupted. Create a new local account and see if the problem persists:

  1. Go to Settings > Accounts > Family & other users.
  2. Click Add account and choose I don’t have this person’s sign-in information > Add a user without a Microsoft account.
  3. Create a new username and password.
  4. Log into the new account and check if PowerShell CPU usage is normal. If it is, migrate your files and settings to the new account.

This is a disruptive step, so try it only after exhausting other options.

Frequently Asked Questions

Is it safe to end the PowerShell process in Task Manager?

Generally yes. PowerShell is not a critical system process; ending it will stop any running scripts. Unsaved work in a PowerShell window will be lost, but your system will remain stable. If it restarts automatically, that’s normal.

Why does PowerShell start at boot and use CPU?

It often runs scheduled tasks or startup scripts. Check Task Scheduler for tasks with triggers at logon. Also check the Startup tab in Task Manager—disable any PowerShell entries you don’t recognize.

Can a PowerShell profile cause high CPU even if it’s empty?

An empty profile is unlikely to cause issues. The problem is usually a profile that loads modules or runs commands that hang. If your profile is empty, skip that fix and look at scheduled tasks or malware.

Will resetting Windows 11 fix PowerShell high CPU?

Yes, a full reset (keeping or removing files) will eliminate any system-level corruption or malware. However, it’s a drastic step—try all other fixes first. Back up your data before resetting.

How do I know if PowerShell high CPU is caused by malware?

Run a full antivirus scan. Also check the process’s path: in Task Manager, right-click PowerShell and select “Open file location.” If it’s not in C:\Windows\System32\WindowsPowerShell\v1.0 or C:\Program Files\PowerShell, it’s likely malicious.

Preventing Future High CPU Issues

To avoid recurrence, keep Windows and PowerShell updated, avoid installing scripts from untrusted sources, and periodically review scheduled tasks. If you use PowerShell frequently, consider using PowerShell 7 (pwsh) which has better performance and is updated separately. Also, enable execution policy restrictions: run Set-ExecutionPolicy RemoteSigned in an admin PowerShell to block unsigned scripts.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →