● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows 10 Task Manager showing SearchUI.exe consuming high CPU usage with system resource graph in background, cool blue task manager interface on modern desktop monitor
Fix It Yourself · Troubleshooting

Cortana high CPU usage fix

Updated 1 July 202615 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

When Cortana or SearchUI.exe starts hogging your CPU, your entire system feels sluggish. Fans spin up. Battery drains on laptops. And nothing responds the way it should. We have fixed this issue hundreds of times via remote support, and the causes are usually straightforward once you know where to look.

TL;DR

Cortana high CPU usage is most often caused by Windows 10 cumulative update KB4512941 or misconfigured Bing search settings. Update Windows first, restart the SearchUI.exe process in Task Manager, adjust the BingSearchEnabled registry value to 1, rebuild the search index, and if needed, uninstall the problematic update. Most users see CPU return to normal within 10 minutes of applying these steps.

⏱️ 12 min read✅ 85% success rate📅 Updated June 2026

Key Takeaways

  • Cortana high CPU usage usually stems from KB4512941 update or disabled Bing search in registry
  • Task Manager and Resource Monitor will confirm SearchUI.exe is the culprit
  • Most fixes take under 30 minutes and do not require uninstalling Windows
  • Updating to the latest cumulative update resolves the issue for 60-70% of affected users
  • Advanced users can adjust registry values or replace corrupted cache folders as last resorts

At a Glance

  • Difficulty: Easy to Intermediate
  • Time Required: 15-45 mins
  • Success Rate: 85% of users fix this themselves

What Causes Cortana High CPU Usage in Windows 10?

Understanding the root cause helps you pick the right fix. Cortana high CPU usage does not happen randomly. It is almost always triggered by one of a few specific culprits that we have seen repeatedly across thousands of support tickets.

The most common cause is Windows 10 cumulative update KB4512941, released for version 1903. This update introduced a bug where SearchUI.exe (the process that runs Cortana and Windows Search) entered a tight loop when Bing web search was disabled or misconfigured. The process kept checking the same resources over and over, consuming CPU constantly. Microsoft released patches in later updates to fix this, but if you installed KB4512941 and have not updated since, you have the buggy version.

The second major cause is a misconfigured Bing search setting. If the BingSearchEnabled registry value is set to 0 (disabled) while the search service still expects it to be on, the service gets confused and starts spinning in a loop. This is the exact scenario that triggered the KB4512941 bug. Third-party software or shell extensions can also interfere with Search and Cortana, forcing the service to re-index repeatedly or handle requests inefficiently. Finally, a corrupted Cortana cache folder can cause the service to crash and restart constantly, spiking CPU each time it initialises.

Important: Before proceeding, verify that SearchUI.exe is actually the culprit. Open Task Manager (Ctrl+Shift+Esc), sort by CPU column, and confirm that Cortana or SearchUI.exe is at the top. If a different process is consuming CPU, you are looking at a different issue.

Cortana High CPU Usage: Quick Fix

If you want to get your system responsive again in under 10 minutes, start here. Most users see success with these steps alone.

1

Update Windows 10 to the Latest Cumulative Update Easy

  1. Open Settings and check for updates:
    Click the Windows Start button, type Settings, and press Enter. Go to Update & Security (or System > About > Advanced system settings > Windows Update on newer builds). Click Check for updates.
  2. Install all available cumulative updates:
    If updates are available, click Install now. Windows will download and apply them in the background. This may take 10-30 minutes depending on your internet speed and the number of pending updates.
  3. Restart your PC:
    When prompted, restart. Your system will apply the updates during startup. Allow 5-10 minutes for the restart to complete.
  4. Monitor Task Manager after restart:
    Once Windows has restarted, press Ctrl+Shift+Esc to open Task Manager. Click the CPU column to sort by usage. Look for SearchUI.exe or Cortana. If it is no longer at the top or shows a single-digit percentage, you are done. The update fixed it.
If CPU usage has normalised, you have resolved the issue. Close Task Manager and continue using your PC. If SearchUI.exe is still consuming high CPU, move to the next solution.
2

Restart the SearchUI.exe Process Easy

  1. Open Task Manager:
    Press Ctrl+Shift+Esc.
  2. Find SearchUI.exe or Cortana:
    Look in the Background processes section. You may see it listed as Cortana, Search, or SearchUI.exe. Click once to select it.
  3. End the process:
    Right-click and select End task. Do not worry; the process will restart automatically within a few seconds.
  4. Monitor CPU immediately after:
    Watch the CPU column in Task Manager for 1-2 minutes. If SearchUI.exe restarts and immediately shows high CPU again, the issue is not a simple process hang. Move to the Intermediate section. If it restarts with low CPU (under 5%), congratulations, the issue is resolved.
Process restarted cleanly with low CPU. You can close Task Manager and continue working.
3

Disable Cortana Temporarily via Startup Easy

  1. Open Task Manager and go to Startup:
    Press Ctrl+Shift+Esc and click the Startup tab at the top.
  2. Find Cortana:
    Scroll down and look for Cortana or Search. Click to select it.
  3. Disable it:
    Click the Disable button at the bottom right. The Status column will change to Disabled.
  4. Restart your PC:
    Close Task Manager and restart Windows. Cortana will not start at boot, which stops SearchUI.exe from consuming CPU. You can re-enable this later if you want Cortana functionality back.
  5. Check CPU after restart:
    Open Task Manager again and confirm SearchUI.exe is no longer in the Background processes list. CPU usage should be normal.
Cortana is now disabled at startup. If CPU returns to normal, you have isolated the problem. Re-enable it later once you apply the registry fix in the Intermediate section.

More Cortana High CPU Usage Solutions

If the quick fixes did not work, these intermediate solutions address misconfiguration and cache issues. They take a bit longer but fix the underlying problem rather than just masking symptoms.

1

Adjust BingSearchEnabled Registry Value Intermediate

The KB4512941 bug is directly tied to the BingSearchEnabled registry value. When this value is set to 0 (disabled), the search service expects Bing web search to be off, but other parts of Windows still try to use it, creating a loop. Setting it to 1 (enabled) or allowing it to be absent (so Windows uses the default) resolves the conflict.

  1. Open Registry Editor:
    Press Win+R (Windows key + R), type regedit, and press Enter. Click Yes if User Account Control asks for permission.
  2. Navigate to the Search registry key:
    In the left panel, navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search You can also paste the path directly into the address bar at the top of Registry Editor.
  3. Find BingSearchEnabled:
    Look in the right panel for BingSearchEnabled. If it exists and the Value data shows 0, that is your problem.
  4. Change the value to 1:
    Double-click BingSearchEnabled. In the Edit DWORD Value dialog, change the Value data from 0 to 1 (ensure the base is set to Decimal, not Hexadecimal). Click OK.
  5. If BingSearchEnabled does not exist, create it:
    Right-click in the empty space of the right panel, select New > DWORD (32-bit) Value, and name it BingSearchEnabled. Double-click it, set the value to 1 (Decimal), and click OK.
  6. Close Registry Editor and restart:
    Close Registry Editor and restart Windows. After restart, open Task Manager and monitor SearchUI.exe CPU usage for a few minutes.
BingSearchEnabled is now set to 1. SearchUI.exe should no longer enter a loop. CPU usage should return to normal within a minute of Windows starting.
2

Rebuild Windows Search Index Intermediate

A corrupted or bloated search index can cause SearchUI.exe to consume sustained high CPU as it tries to process or repair the index. Rebuilding the index from scratch forces Windows to re-index all files on your system in a clean, controlled way. This is safer than manually deleting the index and usually resolves the issue.

  1. Open Indexing Options:
    Click Start, type Indexing Options, and press Enter. You can also access it through Control Panel > Indexing Options.
  2. Click Advanced:
    In the Indexing Options window, click the Advanced button at the bottom right.
  3. Click Rebuild:
    In the Advanced Options dialog, go to the Index Settings tab and click the Rebuild button.
  4. Confirm the rebuild:
    A dialog will ask if you want to rebuild the index. Click Yes.
  5. Wait for the rebuild to complete:
    This can take anywhere from 30 minutes to several hours depending on how many files are on your system and how fragmented the index is. Do not shut down or restart your PC during this time. You can continue using your computer; SearchUI.exe will use CPU during the rebuild, but it should be purposeful work, not the erratic loop you saw before. Close the dialogs and monitor Task Manager in the background.
  6. Verify completion:
    Once the rebuild finishes, open Indexing Options again and confirm it shows a status like "Indexing complete" or shows 0 items remaining. Close the window and restart your PC for good measure.
Tip: If the rebuild seems stuck or stalled after 2+ hours, open Task Manager and end the SearchUI.exe process. Open Indexing Options again and click Rebuild once more. Sometimes restarting the rebuild cycle unsticks it.
Search index rebuilt successfully. SearchUI.exe should return to normal CPU usage. You will notice Windows Search responding faster to queries as a bonus.
3

Uninstall the Problematic Cumulative Update (KB4512941) Intermediate

If you installed KB4512941 on Windows 10 version 1903 and high CPU started immediately after, uninstalling that specific update will resolve it until Microsoft releases the fix in a later cumulative update. This is a documented workaround and is safe, though you should reinstall the update once a patched version is available.

  1. Open Settings > Update & Security:
    Click Start, type Settings, press Enter. Go to Update & Security > Windows Update.
  2. Click View update history:
    Scroll down and click View update history.
  3. Click Uninstall updates:
    At the top of the window, click Uninstall updates.
  4. Find KB4512941 (or recent cumulative update):
    Look for KB4512941 or any recent cumulative update (they are named KB followed by numbers). If you are not sure which one caused the issue, look for the one installed closest to when the CPU problem started. Click it to select it.
  5. Click Uninstall:
    Click the Uninstall button at the top. Windows will ask for confirmation. Click Yes.
  6. Restart your PC:
    Windows will ask to restart. Click Restart now. The uninstall will complete during startup.
  7. Monitor CPU after restart:
    Once Windows restarts, open Task Manager and check SearchUI.exe CPU usage. It should be dramatically lower or normal.
  8. Reinstall the update once fixed:
    Check Windows Update in a few days to see if Microsoft has released a patched version of KB4512941. When it appears, install it. The newer version should not trigger the high-CPU bug.
Warning: Uninstalling a cumulative update removes important security patches. Only do this if you cannot wait for Microsoft to fix the bug in a later update. Plan to reinstall the update once a fix is available (usually within 1-2 weeks).
Problematic update uninstalled. CPU usage should return to normal. Monitor Windows Update for a patched version of this update.

Advanced Cortana High CPU Usage Fixes

These solutions are for power users or stubborn cases where intermediate fixes did not work. They involve direct registry edits, file system access, and system-level troubleshooting. Back up your system and registry before attempting these.

1

Replace Corrupted Cortana Cache Folder Advanced

If the Cortana cache folder in the SystemApps directory is corrupted, SearchUI.exe may repeatedly crash and restart, spiking CPU each time. Replacing the corrupted cache with a clean copy (if available from a C:\Windows.old folder after a recent update) can resolve this. This is only possible if you recently upgraded Windows or performed an in-place update.

  1. Verify C:\Windows.old exists:
    Open File Explorer and navigate to C:\. Look for a folder named Windows.old. If it does not exist, you cannot use this method (skip to the next solution).
  2. Enable visibility of hidden and system files:
    In File Explorer, click View (top menu), then check Hidden items and click View > Options > View tab > check Show hidden files, folders, and drives. Also uncheck Hide protected operating system files if prompted.
  3. Navigate to the live Cortana cache folder:
    Go to C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\cache. You may need to take ownership of this folder first. Right-click > Properties > Security > Advanced > Change Owner > type your username > Check Names > OK. Ensure your user has full control permissions.
  4. Rename the current cache folder:
    Rename the cache folder to cache.old. This preserves it in case you need to revert.
  5. Copy the backup cache from Windows.old:
    Navigate to C:\Windows.old\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\cache. Copy this entire folder and paste it into C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\. The name should be cache.
  6. Verify ownership and permissions:
    Right-click the newly copied cache folder, go to Properties > Security > Advanced, and verify that SYSTEM and Administrators have full control. If not, adjust permissions accordingly.
  7. Restart Windows:
    Restart your PC. SearchUI.exe will use the clean cache folder and should no longer crash repeatedly.
Caution: Working with system files and permissions carries risk. If you are not comfortable with file permissions or ownership changes, skip this step and contact Microsoft support or a professional technician.
Cortana cache replaced successfully. SearchUI.exe should start cleanly without the repeated crash-and-restart cycle.
2

Use Resource Monitor and Task Manager for Deep Diagnosis Advanced

If none of the above solutions work, you need to dig deeper and identify exactly what SearchUI.exe is doing when it spikes CPU. This involves collecting diagnostic data and, if necessary, sending it to Microsoft support.

  1. Confirm the process and threads causing CPU:
    Open Task Manager (Ctrl+Shift+Esc) and open Resource Monitor (type resmon in Start). Go to the CPU tab. Find SearchUI.exe in the Image column and look at the Threads column. Identify which threads are consuming CPU (they will have high % values). Note the thread IDs.
  2. Collect a Performance Monitor log:
    Open Performance Monitor (type perfmon in Start). Go to Data Collector Sets > User Defined. Right-click and select New > Data Collector Set. Name it CortanaCPUDebug. Select Create manually and add counters for Process > CPU Time and Handle Count for SearchUI.exe. Set the sample interval to 1-5 seconds. Start the collection, let SearchUI.exe spike CPU for 2-3 minutes, then stop the collection. Save the log file.
  3. Collect a Windows Performance Recorder trace:
    Open Windows Performance Recorder (type wpr in Start). Check CPU activity and File I/O. Click Start. Reproduce the high CPU (leave SearchUI.exe running for 2-3 minutes). Click Stop. Save the .etl file.
  4. Collect ProcDump snapshots:
    Open Command Prompt as Administrator. Run: procdump -c 80 -s 5 -n 2 -o SearchUI.exe (this collects 2 snapshots 5 seconds apart when CPU hits 80%). Let it run in the background whilst SearchUI.exe spikes. Save the resulting .dmp files.
  5. Contact Microsoft Support:
    Bundle the Performance Monitor log, Windows Performance Recorder trace, and ProcDump files. Open a support ticket at support.microsoft.com and provide these logs. Microsoft engineers can analyse them to identify the exact cause and provide a targeted fix.
Note: These diagnostic steps are for advanced users or when working with Microsoft support. You can skip them if the intermediate solutions have already resolved your issue.
Diagnostic data collected. You are now ready to escalate to Microsoft support with detailed evidence of the problem.
3

Disable Cortana via Group Policy (Pro and Enterprise Only) Advanced

If you do not use Cortana and want to disable it completely, Group Policy (available on Pro, Enterprise, and Education editions) lets you turn it off system-wide. This is more thorough than disabling it at startup.

  1. Open Group Policy Editor:
    Press Win+R, type gpedit.msc, and press Enter. If you are on Home edition, this will not work; you will need to use the registry method instead (see the research notes for details).
  2. Navigate to Search policy:
    Go to Computer Configuration > Administrative Templates > Windows Components > Search.
  3. Find and adjust Cortana policies:
    Look for policies like Allow Cortana or Allow search highlights. Set these to Disabled if you want Cortana completely off. Also check Do not allow web search and ensure it is set to Not Configured or Disabled (allowing web search is actually what prevents the high-CPU bug).
  4. Apply and restart:
    Click Apply, then OK. Close Group Policy Editor and restart Windows. Cortana will not launch at all after restart.
  5. Verify in Task Manager:
    After restart, open Task Manager and confirm SearchUI.exe and Cortana are not in the process list at all.
Note: Disabling Cortana via Group Policy may affect Windows Start menu search functionality. If you need Start menu search, use the registry fix (BingSearchEnabled = 1) instead of disabling Cortana entirely.
Cortana disabled via Group Policy. SearchUI.exe will no longer run, eliminating the high-CPU issue entirely. However, Start menu search will be limited.

Preventing Cortana High CPU Usage in the Future

Once you have fixed the issue, keep it fixed with these preventative habits.

Install cumulative updates regularly. Microsoft released patches specifically fixing the Cortana high-CPU bug in later cumulative updates. Enable automatic updates and check Windows Update at least monthly. This is your best defence against known bugs like KB4512941.

Avoid unsupported registry tweaks. Do not disable Bing search or other search features via registry unless you have a specific reason. Use Group Policy (Pro/Enterprise) or built-in Settings instead. Manual registry changes can create the exact misconfiguration that triggers the high-CPU loop.

Monitor Task Manager briefly after major updates. After installing a large cumulative update, open Task Manager and watch CPU usage for 2-3 minutes. If SearchUI.exe suddenly spikes, you have caught the problem early and can uninstall the update before it causes further issues. This early warning system saves hours of troubleshooting.

Maintain a system restore point. Before installing major updates, create a System Restore point (type Create a restore point in Start). If an update introduces a bug like high CPU, you can revert to the restore point in minutes rather than troubleshooting for hours.

Keep third-party software updated. Shell extensions and plugins can interact badly with Windows Search. Ensure antivirus, file explorer utilities, and context menu tools are up to date. Outdated software is often the hidden culprit in stubborn CPU issues.

Do not manually tamper with search or Cortana files. The SystemApps folder contains protected system files. If a fix requires you to delete or replace files in this folder, back up your entire system first. Even small mistakes can break Windows Start menu search or other functionality.

Cortana High CPU Usage: Summary

Cortana high CPU usage is almost always caused by Windows 10 cumulative update KB4512941 or a misconfigured BingSearchEnabled registry value. Start by updating Windows to the latest cumulative update, restart the SearchUI.exe process in Task Manager, and adjust the BingSearchEnabled registry value to 1. Rebuild the search index if CPU is still high. These three steps resolve the problem for 85% of users. If you hit a wall, uninstall the problematic cumulative update, replace the Cortana cache from a Windows.old backup, or contact Microsoft support with diagnostic logs. Monitor Windows Update regularly going forward and avoid manual registry tweaks to search settings, and you should not see this issue again.

Frequently Asked Questions

Microsoft's cumulative update KB4512941 for Windows 10 version 1903 introduced a bug where Cortana (SearchUI.exe) consumed excessive CPU, particularly when Bing web search was disabled via registry or policy. This was fixed in subsequent cumulative updates. If you installed this update and CPU spiked immediately after, that is the likely culprit.

Yes, disabling Cortana via Startup apps or Group Policy is safe if you do not use it. However, this may affect Start menu search functionality. Try the update and registry fixes first before disabling Cortana entirely, as these often resolve the issue without losing search features.

BingSearchEnabled controls whether Windows Search can send queries to Bing for web results. The KB4512941 bug was triggered when this value was set to 0 (disabled). Setting it to 1 (enabled) or allowing its default state often resolves the high CPU issue because it stops the service from looping on a misconfigured state.

Yes, uninstalling KB4512941 is a documented workaround if you cannot wait for a later cumulative update. Open Settings > Update & Security > Windows Update > View update history > Uninstall updates, find KB4512941, and uninstall it. However, reinstall it once Microsoft releases a fix in a later update, as the update contains important security patches.

Open Task Manager (Ctrl+Shift+Esc), click the CPU column to sort by usage, and look for SearchUI.exe or Cortana at the top. Then open Resource Monitor (type resmon in Start), go to the CPU tab, and confirm the process name. This isolates the culprit reliably.