Windows Update Could Not Be Installed Because of Error 2149842967: Corrupted Cache Reset Fix in 3 Steps

Windows update could not be installed because of error 2149842967 after a botched driver update last week, and the fix was shockingly simple—just a corrupted cache. ⚡ I spent hours digging through logs, only to realize the real issue wasn’t the update itself.

The solution? A three-step reset that clears the junk without reinstalling Windows.

This error crops up when Windows Update gets stuck on partially downloaded files or service conflicts. The official troubleshooter often fails because it doesn’t always reset the cache properly.

My method skips the guesswork: stop the update service, delete the corrupted files, and restart the service. It’s foolproof and takes under 10 minutes.

You’ll walk away with a clean update service, no more error codes, and updates installing smoothly. The best part? No registry edits or command-line risks—just safe, Microsoft-approved cleanup. If you’ve been stuck on this error for days, this is your reset button.

Works for Windows 10 and 11, whether the error appears after a failed update, driver conflict, or system restore. Let’s get your updates flowing again—without the headaches.

Root Causes Of Update Failures

When Windows encounters error 2149842967 during updates, it’s rarely a random glitch—there’s usually a specific technical trigger. Below, we break down the most common causes, explained in plain terms with the science behind them.

🔍 Corrupted update components

Windows Update relies on a system of temporary files (stored in %windir%\SoftwareDistribution\) to download and install patches. If these files become corrupted—whether due to a failed download, abrupt shutdown, or malware interference—the update process stalls.

The error code often surfaces when Windows detects a mismatch between the expected and actual file integrity.

Why it happens:

• Partial downloads: If an update file downloads incompletely (e.g., due to network interruptions), Windows may mark it as "valid" but fail during installation.
• Disk errors: Bad sectors on your hard drive can scramble file data, making components unusable.
• Antivirus interference: Overzealous security software may quarantine or modify update files, triggering corruption flags.

🔗 System file system (NTFS) issues

Windows Update depends on the NTFS file system to manage permissions, timestamps, and file attributes. If NTFS metadata (like Alternate Data Streams or Hard Links) gets corrupted—or if file permissions are misconfigured—the system may reject updates with cryptic errors like 2149842967.

Key triggers:

• Improper shutdowns: A forced restart (e.g., power loss) can leave file handles open, corrupting NTFS structures.
• Third-party tools: Disk utilities (e.g., chkdsk or sfc /scannow) may not always repair NTFS errors fully.
• User permission changes: Modifying C:\Windows\ folder permissions via Group Policy or manual edits can break update access.

🛡️ Windows modules installer service (TiWorker) conflicts

The TiWorker.exe process (Windows Modules Installer) is the backbone of updates, but it can fail if:

• It’s stuck in a loop: A previous update left TiWorker in a "pending" state, causing it to freeze or crash.
• Resource exhaustion: High CPU/memory usage (e.g., from background apps or malware) starves TiWorker of resources.
• Service dependencies fail: TiWorker relies on services like wuauserv and msiserver. If these are disabled or misconfigured, updates fail silently.

Fun fact: This error often appears when TiWorker’s manifest.xml files (used for update metadata) are damaged.

🔄 Group policy or registry misconfigurations

Windows Update behavior is controlled by Group Policy (for enterprises) and registry keys (for all users). If these settings are altered—whether manually, by malware, or via third-party tools—the system may reject updates with errors like 2149842967.

Common culprits:

• Disabled update services: Keys like HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU may be set to Disabled.
• Corrupted proxy settings: Incorrect proxy configurations in the registry can block update servers.
• Third-party "optimizers": Tools like TuneUp Utilities or Advanced SystemCare sometimes over-optimize Windows Update settings.

Pro tip: Always back up your registry before making changes (Export via regedit). A single wrong edit can break your system!

Fix Windows Update Errors in 3 Steps

Encountering error 2149842967 during Windows updates can feel like a dead end—but it’s often just a sign your system needs a little TLC. Below, we’ve mapped the most common causes to straightforward fixes, so you can get back to smooth updates in no time. 🚀

🔥 Corrupted Windows Update Cache: Quick Reset

When your update cache gets cluttered or corrupted, Windows can’t install new updates properly. A simple reset usually clears the issue.

🍳 Step 1: Stop Windows Update Service

Before resetting, pause the update process to avoid conflicts.

1. Press Win + R, type services.msc, and hit Enter.
2. Find Windows Update in the list, right-click, and select Stop.
3. Also, stop the Cryptographic Services (right-click → Stop).

👨‍🍳 Step 2: Delete the Update Cache

Navigate to the folder storing corrupted update files and clear it out.

1. Open File Explorer and go to: C:\Windows\SoftwareDistribution\Download
2. Select all files (Ctrl + A), then Delete them.
3. If prompted, confirm deletion.

🥘 Step 3: Restart Services & Try Again

With the cache cleared, restart the services to let Windows fetch fresh updates.

1. Go back to services.msc and restart both:
   • Windows Update
   • Cryptographic Services
2. Restart your PC and attempt the update again.

> 💡 Pro Tip: If the issue persists, try running the Windows Update Troubleshooter (search for it in the Start menu) before proceeding to the next fix.

🔪 Faulty System Files: Repair with DISM & SFC

If corrupted system files are blocking updates, Windows’ built-in tools can restore them.

⏰ Step 1: Run Deployment Image Servicing and Management (DISM)

DISM repairs Windows image files that might be causing conflicts.

1. Open Command Prompt as Administrator (Win + X → Terminal (Admin)).
2. Paste this command and press Enter: DISM /Online /Cleanup-Image /RestoreHealth
3. Wait for the process to complete (may take 10–20 minutes).

⏰ Step 2: Run System File Checker (SFC)

SFC scans for and repairs missing or corrupted system files.

1. In the same Admin Command Prompt, run: sfc /scannow
2. Wait for the scan to finish (another 10–15 minutes).
3. Restart your PC and check for updates again.

> 🔥 Warning: If DISM fails with an error (e.g., "source files could not be found"), your Windows installation media may be needed. Insert your Windows USB and run: > DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\Repair > (Replace C: with your USB drive letter.)

🎯 Third-Party Interference: Safe Mode Update

Antivirus, firewall, or driver conflicts can sometimes trigger update errors. Booting into Safe Mode isolates the issue.

⏰ Step 1: Boot into Safe Mode

1. Press Win + R, type msconfig, and hit Enter.
2. Go to the Boot tab, check Safe boot, and select Network (if you need internet).
3. Click OK, then Restart.

⏰ Step 2: Install Updates in Safe Mode

Once in Safe Mode, open Settings → Windows Update and attempt the installation again.

⏰ Step 3: Return to Normal Mode

1. After updates install, repeat the steps above to uncheck Safe boot.
2. Restart normally and verify the fix.

> 🌡️ Pro Tip: If Safe Mode works but normal mode fails, temporarily disable third-party antivirus (like McAfee or Norton) or update drivers via Device Manager.

✨ Prevention Tips: Keep Updates Smooth

Once you’ve resolved the error, follow these steps to avoid future hiccups:

• 📊 Schedule regular updates: Go to Settings → Windows Update → Advanced options and set active hours to avoid interruptions.
• 💪 Clean up disk space: Use Disk Cleanup to free up space (especially in C:\Windows\SoftwareDistribution).
• 🔄 Reset Windows Update components monthly: Run these commands in Admin Command Prompt to refresh components: net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
• 🛡️ Keep security software updated: Ensure your antivirus and firewall are compatible with the latest Windows version.

Frequently asked questions