Modern Setup Host Causing High CPU Usage on Windows 11

Hey everyone, I’ve noticed Modern Setup Host is suddenly using a lot of CPU on my Windows 11 system, especially during idle time. My fans ramp up and performance drops while it runs in the background. I’m not currently installing any updates manually, so this seems odd. I’ve tried restarting and pausing updates but it keeps coming back. Is this normal behavior or something stuck in the update process, and what’s the safest way to fix it without breaking Windows Update?

Tagged: Windows 11

Windows

All Replies

Viewing 3 replies - 1 through 3 (of 3 total)

Mira Lennox Lennox

Participant

March 17, 2026 at 10:02 am

Good question, this kind of issue usually doesn’t touch your personal files since Windows Update works in a separate system area. At worst you might see temporary glitches or a failed update, not actual data loss. That said, if something does go missing, stop using the system right away to avoid overwriting files, check the Recycle Bin and previous versions first, then use a trusted recovery tool like Stellar Data Recovery to scan and restore anything important.

This reply was modified 2 days ago by mark willium.

George

Participant

March 17, 2026 at 9:57 am

Thanks, that helped with the CPU issue. One more thing I’m worried about, if this was caused by a stuck or failed update, is there any chance it could affect or corrupt my personal files? And if something did get lost during the process, what’s the safest way to recover that data without making things worse?

mark willium

Keymaster

March 17, 2026 at 9:49 am

This usually happens when a Windows update is stuck or still processing in the background. First, let it run for a bit if an update is in progress. If it keeps spiking CPU, restart your PC, then go to Windows Update and click “Check for updates” to force it to complete. If that doesn’t help, run the Windows Update troubleshooter and clear the SoftwareDistribution folder by stopping the Windows Update service, deleting its contents, and restarting the service. Also make sure you have enough free disk space since low storage can trigger this issue.

Viewing 3 replies - 1 through 3 (of 3 total)