keepcalculator

06 Numbers and Powers

KB4515384 Bugs: What It Broke & How to Fix

Card No. 06·81248 · Updated · Standard formula, shown below

KB4515384 was a Windows 10 cumulative update (released September 2019 for versions 1903 and 1909) that broke several system features: it caused high CPU usage from the Cortana search process, broke the Start menu, and triggered audio and Bluetooth failures. This article explains the specific bugs, their causes, and the practical fixes you can apply.

What KB4515384 Actually Is

KB4515384 is a cumulative update for Windows 10, released on September 10, 2019. It applied to Windows 10 version 1903 (May 2019 Update) and later version 1909 (November 2019 Update). A cumulative update means it rolls up all previous fixes plus new ones into a single package. Microsoft releases these monthly on Patch Tuesday (the second Tuesday of each month).

The update’s official purpose was to improve security, fix bugs in the OS, and address issues with Windows Mixed Reality, Microsoft Office, and certain input devices. However, within days of release, users reported several serious regressions—new problems introduced by the update itself.

The Main Bugs Reported

The most widely reported bugs from KB4515384 were:

  • High CPU usage from SearchUI.exe (Cortana search): Even when idle, the search process consumed 30–50% of CPU, causing fans to spin loudly and laptops to drain battery quickly.
  • Start menu not opening or freezing: Clicking the Start button did nothing, or the menu opened but was unresponsive.
  • Audio problems: Some users lost sound entirely, or audio crackled and stuttered after the update.
  • Bluetooth failures: Bluetooth devices (headphones, mice, keyboards) would pair but then disconnect repeatedly.
  • Windows Sandbox and Antimalware Scan Interface (AMSI) issues: Windows Sandbox failed to start, and some applications using AMSI (like certain security tools) crashed.

These were not isolated incidents; Microsoft acknowledged the CPU bug in a support forum post and later released an out-of-band (emergency) update, KB4517211, on September 19, 2019, specifically to fix the search-related CPU issue.

Why Did These Bugs Happen?

The root cause of the CPU drain was traced to a bug in the search indexer. The update introduced a logic error that caused the indexer to repeatedly re-scan the same folders without ever completing, which spiked CPU usage. This is a classic example of an infinite loop in a background service.

The Start menu and audio issues were likely caused by conflicts with existing system files and drivers. Cumulative updates replace core OS files, and if a driver or third-party app relied on an older version, the new files could break that dependency. This is why some users only experienced issues after the update—their specific hardware or software combination triggered the conflict.

Microsoft’s official response for the audio and Bluetooth problems was to advise users to check for driver updates from their device manufacturers, as the update itself did not contain a fix for those.

How to Fix These Bugs

If you are still experiencing issues from KB4515384 (or a later update that inherited these bugs), here are the steps to resolve them:

  1. Install the out-of-band update KB4517211: This was the official fix for the CPU issue. Go to Settings > Update & Security > Windows Update and check for updates. If it does not appear, download it manually from the Microsoft Update Catalog.
  2. Run the Windows Update Troubleshooter: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. This can fix corrupted update files.
  3. Update your audio and Bluetooth drivers: Open Device Manager (right-click Start > Device Manager), find your audio device, right-click, and select “Update driver.” Do the same for Bluetooth adapters. If no update is found, check your PC manufacturer’s website.
  4. Restart the search service: Press Win+R, type services.msc, find “Windows Search,” right-click, and select “Restart.” This can temporarily stop the CPU drain.
  5. Uninstall the update (last resort): If nothing else works, go to Settings > Update & Security > Windows Update > View update history > Uninstall updates. Find KB4515384 and uninstall it. Your PC will revert to the previous version, but you will miss security fixes until the next cumulative update.

How to Avoid Future Update Bugs

You can reduce the chance of being hit by a bad update by delaying it. In Windows 10 Pro, you can set “Quality updates” to defer by up to 30 days. For Home edition, you can pause updates for up to 35 days. This gives Microsoft time to pull a buggy update and release a fix.

Always back up your important files before installing a major update. Windows creates a restore point automatically before a cumulative update, but having your own backup (e.g., to an external drive or cloud) is safer.

Also, check the Windows Update subreddit or Microsoft’s support forums before installing a new update. Users quickly report issues, and you can decide whether to wait.

Common Misconceptions

One common myth is that KB4515384 caused permanent hardware damage. It did not. The high CPU usage could overheat a laptop if left unchecked for days, but it did not brick devices. Another misconception is that uninstalling the update is always safe. It is not—uninstalling removes all security fixes from the previous month, leaving you vulnerable.

Also, many people blamed the update for issues that were actually caused by a separate bug in Windows 10 version 1903’s search indexer that existed before this update. The update made it worse for some, but not everyone with the CPU bug had installed KB4515384.

Frequently Asked Questions

Is KB4515384 still installed on my PC?

If you have kept Windows updated since September 2019, no. Later cumulative updates (like KB4522355 from October 2019) supersede it. You can check by going to Settings > Update & Security > Windows Update > View update history. If you see a later cumulative update, KB4515384 is no longer present.

Did Microsoft ever apologize for this update?

Microsoft did not issue a formal public apology, but they acknowledged the CPU bug and released a fix within nine days. They also updated their support document for the update to mention the known issue and the workaround.

Can I get KB4515384 bugs if I skipped it and installed a later update?

No. Later cumulative updates do not re-introduce bugs from an older update; they include all previous fixes plus new ones. However, some bugs can persist if they were never fixed in the codebase. The CPU issue was fixed in KB4517211, so any update after that includes the fix.

Why did the update break audio only for some users?

Because audio drivers are hardware-specific. The update replaced a shared Windows audio service, and if your specific sound card driver was incompatible with the new service, it failed. Users with generic drivers (like Realtek) were more affected than those with proprietary drivers from their laptop manufacturer.

Should I have uninstalled KB4515384 immediately?

Only if you were directly affected and could not wait for the fix. For most users, the issues were minor or non-existent. Uninstalling a cumulative update also removes all previous security fixes, so it is not a decision to take lightly. The safer option was to install the out-of-band fix.

Does this mean Windows updates are unsafe?

No. Bugs in updates are rare, and Microsoft tests them extensively. But no software is perfect, and cumulative updates touch core OS files, so occasional regressions are inevitable. The key is to back up, defer updates when possible, and know how to uninstall if needed.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →