On September 17, Microsoft released cumulative update KB5065789 to Windows 11 Insiders in the Release Preview channel. The small package delivers urgently needed fixes for the 0x80070002 Windows Update installation error, a DRM-protected media playback regression, and other stability issues. It also quietly sets the stage for the upcoming version 25H2 through an enablement package—meaning your 24H2 PC is just a small flip away from the next feature update.

What’s in the Patch: The Full Fix List

KB5065789 comes in two flavors: Build 26100.6718 for Windows 11 version 24H2 and Build 26200.6718 for devices already testing the 25H2 enablement package. Both include identical fixes. Here’s what’s new:

  • Windows Update error 0x80070002 resolved. This catch-all failure prevented many Insiders from installing builds, stalling both personal testing and enterprise evaluation.
  • DRM playback restored. A regression introduced by the earlier KB5064081 caused some Blu‑ray, DVD, and digital TV apps to fail when playing protected content. This update corrects that.
  • Settings crash fixed. Navigating to Settings > System > Storage (or launching drive properties from File Explorer) no longer crashes the Settings app.
  • Battery icon accuracy. The taskbar battery icon now correctly shows charging state when plugged in, fixing a misleading display bug.
  • CRL partitioning support. For enterprise certificate authorities, Windows can now partition Certificate Revocation Lists to improve performance and scalability.
  • Click to Do table detection delayed. Originally announced in earlier Release Preview notes, the “Convert to table with Excel” feature for Copilot+ devices has been pulled from this flight. Microsoft says it will come in a future update.

The update is a small, targeted release—no broad new features, just surgical fixes and behind‑the‑scenes improvements.

Why You Should Care: The Impact of These Fixes

If you’re a home user or power user

The 0x80070002 error is more than an annoyance; it can leave your PC stuck on an old build, missing security patches and feature updates. If you’ve been trying to get the latest Insider build only to see installation fail, this fix should clear the path.

DRM playback matters if you watch protected content on your PC—think Blu‑ray discs or subscription‑based TV apps. After KB5064081, some players simply stopped working. This update brings them back.

The Settings crash was a daily frustration for anyone who regularly checks disk usage or drive health. And the battery icon glitch? It undermined trust in basic system indicators. Both are now corrected, making Windows feel more polished.

If you’re an IT administrator

The update is a mixed bag of relief and homework. The Windows Update fix is critical for pilot groups testing cumulative updates; without it, test machines can fall behind, skewing compatibility assessments. Test it on a small cohort immediately.

DRM playback isn’t just a consumer concern—digital signage, kiosks, and training machines often rely on protected media. Verify playback in your environment post‑update, and have a rollback plan ready just in case.

The CRL partitioning support is a welcome back‑end improvement. If you operate an internal PKI, this can reduce bandwidth and latency for certificate checks, especially at scale. Consult your CA documentation before enabling new behaviors.

Then there’s the 25H2 enablement package. It’s not a full OS install; it’s a switch that activates code already on your 24H2 machines. That means deployment can be faster and less disruptive, but it also means you must validate that your management tools, scripts, and line‑of‑business apps are compatible. Microsoft has already warned about the removal of PowerShell 2.0 and WMIC from shipping images—if your automation relies on them, act now.

How We Got Here: The Bugs This Update Fixes

Let’s connect the dots.

KB5064081, an earlier servicing update, inadvertently broke DRM playback on some devices. The root cause is an interaction between the update’s components and third‑party media frameworks. Microsoft chose to ship a narrow fix in KB5065789 rather than a broader rollback, signaling confidence in the targeted patch.

The 0x80070002 error is a long‑standing Windows Update nuisance. On Insider builds, it often surfaces when the download process hits a metadata mismatch or corrupted files. Microsoft hasn’t detailed the exact cause in this instance, but the fix in KB5065789 suggests a servicing‑stack tweak or catalog correction.

The Settings crash and battery icon bug are recent regressions, likely introduced in earlier 24H2/25H2 preview builds. They’re the kind of quality‑of‑life issues that erode user confidence, and Microsoft is rightly prioritizing them for Release Preview.

The 25H2 enablement scheme isn’t new—Microsoft used a similar approach for previous feature updates—but its inclusion in this flight confirms that the 25H2 codebase is stable enough for broad testing. Insiders who install Build 26200.6718 are essentially jumping ahead to 25H2, while those on 26100.6718 remain on 24H2 until they choose to upgrade.

As for Click to Do’s table detection, it was first teased as a Copilot+ exclusive, requiring Snapdragon hardware and a Microsoft 365 subscription. Its delay suggests the feature still needs polish, or that Microsoft wants to decouple it from the general‑availability timeline to avoid holding up the rest of the release.

What to Do Now: A Step‑by‑Step Guide

For every Release Preview user

  1. Install KB5065789. Check Windows Update; the update should download and install normally. If you’re on 24H2, you’ll get Build 26100.6718. If you already toggled the 25H2 enablement package, you’ll see Build 26200.6718.
  2. Verify the fixes.
    • Try a Windows Update check to confirm the 0x80070002 error is gone.
    • Launch a DRM‑protected video or Blu‑ray in your usual app to ensure playback works.
    • Open Settings > System > Storage and click on a drive; it shouldn’t crash.
    • Plug in your laptop and watch the battery icon—it should show charging immediately.
  3. Report any lingering issues via the Feedback Hub.

If you still see error 0x80070002

Even after applying KB5065789, some devices may still stumble during future updates. Try these steps in order:

  • Reboot and attempt the update again.
  • Reset Windows Update components:
    • Open an elevated Command Prompt.
    • Stop the services: net stop wuauserv, net stop bits.
    • Rename the folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
    • Restart the services: net start wuauserv, net start bits.
    • Reboot and check for updates.
  • Run DISM and SFC:
    • DISM /Online /Cleanup-Image /RestoreHealth
    • sfc /scannow
    • If DISM fails, mount a Release Preview ISO and use the /Source parameter.
  • Perform an in‑place upgrade using a Release Preview ISO. Download the ISO from the Microsoft Insider ISO portal, run setup.exe, and choose to keep apps and files. This often repairs stubborn update blocks.

For enterprise pilots

  • Apply KB5065789 to a representative test group.
  • Validate DRM apps across your portfolio, including custom media players.
  • Check storage and battery UI on various hardware—these small fixes can mask deeper driver issues, so a quick audit won’t hurt.
  • Test the 25H2 enablement package (if you plan to adopt it) on a few machines.
    • Deploy the enablement via Windows Update or a deployment tool.
    • Verify all management agents, security software, and automation scripts work.
    • Pay special attention to any legacy PowerShell 2.0 or WMIC dependencies—KB lists deprecation; they may be gone in 25H2.
  • ISO testing: Download ISOs for clean‑install validation or image building. Keep them on hand for recovery.

Looking Ahead: The Delayed Feature and the Road to 25H2

Microsoft didn’t give a new ship date for Click to Do’s table detection, only that it will arrive “in a future update.” Given the hardware and subscription gates, it’s likely to land with the general availability of 25H2, or possibly in a subsequent cumulative update for Copilot+ devices. For now, don’t plan workflows around it.

The 25H2 enablement package is already in final testing. For 24H2 users, the upgrade will be small and fast—likely a few hundred megabytes. When it goes live for everyone, it will appear as an optional update in Windows Update before eventually becoming a recommended one. Keep an eye on the Release Preview channel for the final build number and any last‑minute changes.

This flight is a textbook example of how the Windows Insider program works: ship critical fixes, hold back features that aren’t ready, and let the community validate stability. For Insiders and admins alike, the message is clear: install KB5065789, test the areas Microsoft highlighted, and prepare your environment for a low‑friction step into 25H2.