How to Fix “Background Task Host (backgroundTaskHost.exe) High CPU” Triggered by Windows Spotlight

Noticed my fan spinning up for no obvious reason a while back, checked Task Manager, and found backgroundTaskHost.exe sitting at a steady 15-20% CPU with the command line pointing at something called Global.DesktopSpotlight.App. Never heard of it before that moment. Turns out Windows Spotlight — the feature that rotates your lock screen and desktop background images — has its own background task, and it doesn’t always behave.

Quick Answer

• Check Task Manager’s Details tab and look at the command line of backgroundTaskHost.exe to confirm it’s actually Spotlight-related (Global.DesktopSpotlight) before assuming it is
• Disabling Windows Spotlight through Personalization settings is the direct fix, but it doesn’t always fully stop the background process
• Some users need to also change the “Let this system component run in the background” permission specifically for Spotlight to actually stop the task from relaunching
• A full restart (not just Explorer restart) tends to clear a genuinely stuck instance more reliably than ending the task alone
• Multiple duplicate Background Task Host entries piling up is a different, related symptom worth checking separately

Why It Fails

backgroundTaskHost.exe itself isn’t the problem — it’s a generic Windows process that hosts background tasks for UWP and Store apps, so blaming the process itself is a bit like blaming a moving truck for what’s inside it. When it’s tied to Windows Spotlight specifically, the actual task is Global.DesktopSpotlight.App, which runs periodically to check for and download new lock screen and desktop images, along with the occasional “fun fact” tips tied to those images.

A few specific things cause this in practice:

1. The Spotlight background task getting stuck rather than completing normally. It’s supposed to run briefly, fetch new content, and exit. When it doesn’t exit cleanly — often after a failed network request or an interrupted download — it can keep retrying or sit consuming CPU instead of shutting down.
2. Disabling Spotlight through Settings without touching the background permission separately. This is the one that catches people out constantly — turning off Windows Spotlight as your lock screen or desktop image source doesn’t necessarily stop its background task from still being allowed to run. Those are two separate toggles under the hood, even though they feel like they should be the same switch.
3. Sleep or hibernation interruptions. From what I’ve seen, this is a broader Background Task Host pattern, not just Spotlight-specific — background tasks that were mid-operation when the machine slept can come back in a stuck state after waking, retrying endlessly instead of resuming or exiting cleanly.
4. A buildup of duplicate task instances over time. Some users report dozens of Background Task Host entries accumulating in Task Manager, all technically “suspended” and using no active CPU individually, but collectively bogging down the system and occasionally one of them spikes. This tends to correlate with the “Power Optimized” background app permission setting rather than “Never.”
5. A slow or unreliable network connection during the image fetch. Since Spotlight pulls content from Microsoft’s servers, a flaky connection can leave the task retrying a failed download repeatedly instead of giving up after a reasonable number of attempts.

Common Scenarios

Step-by-Step Fixes

Step 1: Confirm It’s Actually Spotlight

Before changing settings, verify what you’re dealing with.

1. Open Task Manager (Ctrl+Shift+Esc)
2. Go to the Details tab
3. Right-click the column header → Select columns → check Command line
4. Find the high-CPU backgroundTaskHost.exe entry and check its command line — you’re looking for something referencing Global.DesktopSpotlight

If it references something else entirely (Mail, Phone Link, Widgets, Xbox), the fix path is different — this article is specifically about the Spotlight-triggered version.

Step 2: End the Stuck Task

Right-click the process in Task Manager → End task

This is a safe, temporary fix — Windows will relaunch background task hosting as needed, so you’re not breaking anything by ending it. It just doesn’t address the underlying cause.

Step 3: Disable Windows Spotlight as Your Background Source

1. Right-click the desktop → Personalize → Background
2. Change Personalize your background from “Windows Spotlight” to “Picture” or “Solid color”
3. Also check Lock screen settings and switch that away from Windows Spotlight if it’s set there too — these are separate settings in Windows 11 despite feeling related

Step 4: Adjust the Background App Permission Specifically

This is the step that actually stops the task from relaunching, not just changes what image source you see.

1. Go to Settings → Apps → Installed apps
2. Search for anything related to Spotlight, or check System → Background apps depending on your Windows 11 build
3. Find the relevant component’s background permission and set it to Never instead of Power Optimized

If you can’t find a dedicated Spotlight entry (it’s not always listed as a standalone app), this setting sometimes lives under Privacy & security → Background apps as a global toggle instead — worth checking there if the per-app route comes up empty.

Step 5: Restart Rather Than Just Ending the Task

If the spike keeps coming back after ending the task once, do a full restart rather than repeatedly killing the process. Background tasks stuck from a sleep/wake cycle tend to clear more reliably with an actual restart — Fast Startup can preserve part of the previous session on a simple shutdown/power-on, so use Restart specifically, not Shut Down followed by powering back on.

Step 6: Check for a Broader Background Task Host Buildup

If Task Manager shows many Background Task Host entries beyond just the Spotlight one:

1. Go to Settings → Apps → Installed apps
2. For any app with a “more options” or “advanced options” section, check Background component permissions
3. Set the ones you don’t need actively updating in the background to Never

What Actually Worked For Me

Ending the task the first time did nothing — it was back within a couple minutes, sitting at roughly the same CPU usage. So I went to Personalization and switched my background away from Windows Spotlight entirely, assuming that would be the end of it.

It mostly was, but not completely — the spike came back, just less frequently, maybe once every hour or two instead of constantly. That’s when I found the background permission setting buried separately from the personalization option. Changing Spotlight-related background permissions to Never, on top of already switching away from it as the background source, is what actually stopped it for good. If I’d only done one of those two things, I’d probably still be dealing with the occasional spike and wondering why the “fix” wasn’t sticking.

Not 100% sure why Microsoft splits these into two separate controls instead of one obvious toggle, but that’s Windows for you sometimes — the setting that looks like it should be the whole fix is often only half of it.

Advanced Fixes and Edge Cases

Checking the file’s digital signature if you’re not sure it’s legitimate. Right-click backgroundTaskHost.exe in File Explorer (it should be in C:\Windows\System32) → Properties → Digital Signatures tab, and confirm it’s signed by Microsoft. If it’s running from a different location or has no valid signature, that’s not this issue — treat it as a possible malware masquerade and run a scan instead of following Spotlight-specific steps.

Event Viewer correlation. If you want to confirm the pattern rather than guess, check Event Viewer for BackgroundTaskInfrastructure events around the times CPU spikes happen — several users have found these logs line up closely with Task Manager’s process list, giving a clearer picture of which specific background task triggered each spike.

SFC and DISM if the issue persists after all Spotlight-specific fixes. Occasionally the underlying cause isn’t Spotlight’s task logic itself but corrupted system files affecting how background tasks get managed generally:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Run these if you’ve done everything Spotlight-specific and the general Background Task Host pattern (not just Spotlight) is still showing up elsewhere.

Group Policy route for more permanent control. On Pro and Enterprise editions, Windows Spotlight can be disabled more thoroughly through Group Policy (Computer Configuration → Administrative Templates → Windows Components → Cloud Content), which some users report sticks better across updates than the Settings app toggle alone.

What Rarely Works

Just disabling Spotlight through the Personalization Background dropdown alone, without also touching the background app permission, is the fix most people try first and the one most likely to leave the problem half-solved — exactly what happened in my case initially. Similarly, repeatedly ending the task every time it spikes technically “works” in the moment but doesn’t address why it keeps coming back, so you end up doing it indefinitely instead of fixing it once.

Prevention Tips

• If you don’t actively use Windows Spotlight, disable both the personalization source and its background permission together, not just one
• Keep Windows updated — some of the stuck-task behavior tied to sleep/wake cycles has been quietly improved across cumulative updates over time
• Periodically glance at Task Manager’s Background Processes section if your fan seems to run more than expected — catching a buildup early is easier than untangling a dozen stuck entries later
• Avoid installing multiple system optimizer tools claiming to fix this automatically — several of the search results pushing this fix are thinly disguised ads for paid “PC cleaner” software that doesn’t do anything Task Manager and Settings can’t already do for free

FAQ

Is backgroundTaskHost.exe itself a virus? No, it’s a legitimate Windows process, as long as it’s running from C:\Windows\System32 and carries a valid Microsoft signature. If not, that’s a different problem worth scanning for separately.

Will disabling Windows Spotlight break anything else? No, it only affects the rotating background/lock screen images and their occasional tips. Nothing else depends on it.

Why does ending the task keep bringing it back? Windows relaunches background task hosting on demand — ending the process is a temporary relief, not a permanent fix, unless you also address the underlying permission or stuck-task cause.

Does this happen on Windows 10 too? Yes, Windows Spotlight and its background task behavior predate Windows 11, though the exact Settings menu paths differ slightly between versions.

Editor’s Opinion

the annoying part here is that turning off spotlight in personalization feels like it should be enough and it just isnt always. check the background permission too, dont assume one toggle covers it. also if your fan spikes randomly its worth a quick look at task manager’s command line column before blaming something more dramatic, more often than not its something this mundane