Windows Update Error 0x80070015 Fix: Device Not Ready SOLVED 2026

I'll be honest with you—when Windows Update hit 42% and then threw error 0x80070015 at me, I was ready to pull my hair out. The message just said something about a "device not ready," which told me absolutely nothing useful. Three hours of searching forums, two failed automatic retries, and one very frustrated evening later, I finally cracked the code. If you're stuck at that same 42% wall, let me save you the headache and share exactly what worked for me.

The Fix That Actually Worked (After 3 Failed Attempts)

I tried the obvious stuff first—restarting my PC, running Windows Update troubleshooter, even disabling my antivirus. Nothing worked. Then I found a solution path that finally addressed the root cause: Pending.xml → CBS Reset → Manual Install. Here's what I did, step by step.

Step 1: Reset CBS Transaction State (The Game Changer)

This was the moment everything clicked. I opened File Explorer and navigated to C:WindowsWinSxS. Inside, I found a file called pending.xml. From what I learned, this file tracks pending CBS (Component-Based Servicing) transactions that Windows never finished. I right-clicked, renamed it to pending.xml.old, and held my breath. Warning: If pending.xml deletion fails for you (access denied errors), you'll need to take ownership of the file or boot into Safe Mode first.

After renaming, I restarted my PC. This single step reset the entire CBS transaction state and cleared whatever was blocking the update pipeline. I checked CBS.log afterward (that's the unique signal to watch) and saw the read failures were gone.

What Didn't Work First (My Error Path)

Before figuring out the pending.xml trick, I tried clearing the update cache and restarting services—Method 1 failed completely. That's when I learned that when pending.xml reset fails, you have to move to Method 2 (CBS reset). In my case, renaming the file worked on the second try after I took ownership of the WinSxS folder.

Step 2: Check Disk Integrity (Don't Skip This!)

Even after resetting CBS, I wanted to make sure my drive wasn't actually having issues. I opened Command Prompt as Administrator and ran:

The scan took about 20 minutes but found and fixed some minor file system errors. If disk check fails for you, that's a red flag—it might mean actual drive problems. But in my case, it came back clean, which confirmed the issue was purely software-related.

Step 3: Clear Update Cache & Restart Services

With CBS reset and disk verified, I cleaned out the temporary update files. In an elevated Command Prompt, I ran:

This cleared out any corrupted download fragments that might have been causing the "device not ready" error.

Step 4: Manual Install from Catalog (The Final Push)

After all that prep work, Windows Update still showed the update as pending. So I went to the Microsoft Update Catalog, searched for KB5147310, and downloaded the version matching my system (Windows 11 x64). I double-clicked the .msu file, and this time—finally—the installation sailed past 42% and completed without errors.

How to Validate It's Really Fixed

After applying this fix, here's how I confirmed everything was working:

• Update progressed beyond 42% — The installation completed fully without getting stuck
• CBS.log showed no read failures — I checked the log at C:WindowsLogsCBSCBS.log and searched for "0x80070015" — nothing found
• Update completed successfully — Windows Update history showed "Success" status with no error codes

What NOT To Do (Learn From My Mistakes)

Quick Troubleshooting Branch

Based on what worked for me and what didn't, here's the decision tree I wish I had from the start:

• If pending.xml deletion fails → Reset CBS using DISM (run DISM /Online /Cleanup-Image /RestoreHealth)
• If CBS reset fails → Check disk with CHKDSK — disk errors might be the root cause
• If disk check fails or shows errors → Manual install from catalog — bypass Windows Update entirely

Final Thoughts: Error 0x80070015 looks scary, but it's almost always a software pipeline issue, not a hardware failure. The pending.xml rename trick is what finally unblocked my system, and I've used it to help three friends fix the same error. Watch for KB5147310 in your update history, check CBS.log for clues, and don't give up at 42%—the fix is closer than you think. You've got this!