Fix Driver Incompatible on Windows 10/11

You're updating Windows and it stops cold at 87% with a message about an incompatible driver. On Windows 10 the update might fail during CBS merge, while Windows 11 just refuses to proceed. This usually happens when a legacy or unsigned driver blocks the component store.

We've seen this pattern with KB5147675 (check CBS.log around the 87% mark). The core issue: driver incompatibility + policy enforcement + mismatched WinSxS mapping.

Try this first – DISM component repair

Instead of chasing five different fixes, start with the one that often clears the roadblock. Open Command Prompt as Administrator and run:

DISM /Online /Cleanup-Image /RestoreHealth

Wait for the operation to finish (it may take 10–15 minutes). After that, restart your PC and try the update again. In some cases this alone lets the update pass the 87% barrier.

What if DISM fails?
If you see an error or DISM can't complete, don't force the update. Jump straight to a Repair Install using an ISO – it's the safer fallback. That's the branch logic: DISM fail → Repair Install.

⚠️ Not fully verified on every system
This method worked on several Windows 10/11 builds (21H2 to 23H2), but some hardware configurations may need extra steps. The solution path is still DISM → SFC → Repair Install, but we're giving you the condensed version.

Why driver incompatibility shows up

When you install a cumulative update, Windows checks every driver against its compatibility list. An outdated or unsigned driver triggers a hard stop – especially on Windows 11. You might have noticed the update stuck at 87% then rolling back. That's the state signal: 87% failure.

Searching for "how to fix incompatible driver windows" or "windows 11 driver incompatibility error" brings up dozens of threads. Most suggest removing the driver via Device Manager, but we've found DISM is less intrusive and fixes the component store first.

Another common query is "driver not compatible after update fix" – people see this after a recent patch. The key is to avoid forcing incompatible drivers (that just delays the problem).

If you're looking for a working driver solution that doesn't require reinstalling Windows, try the DISM command above. It's a clean, Microsoft-supported repair that rebuilds system files without touching your personal data.

Don't skip these checks:
- After DISM succeeds, run sfc /scannow to verify driver file integrity.
- Make sure Windows Update services are running (wuauserv, bits, cryptsvc).
- If the error returns, re-register update components: net stop wuauserv & net start wuauserv.
- Still stuck? Use the "Repair Install" method (keep apps and data).

Validation: After the fix, the update should pass 87% without warnings, and the system won't roll back. No incompatible driver popups.

Avoid: Forcing an incompatible driver installation, skipping driver removal if asked, or permanently disabling Windows policy checks (that leaves you vulnerable).