Microsoft shipped two Release Preview builds on September 12—with the fixes rolling out to Insiders on September 17—to address a pair of nasty regressions that have been tripping up Windows Insiders: the persistent 0x80070002 update installation failure and broken DRM-protected content playback in Blu-ray, DVD, and digital TV apps. The builds, 26100.6718 for version 24H2 and 26200.6718 for the upcoming 25H2, are delivered via the small cumulative update KB5065789. But while these critical fixes are now available for testing, one anticipated productivity feature—Click to Do's table-to-Excel conversion—has been pushed back to a future release.

What’s actually fixed in KB5065789

Microsoft packed several targeted repairs into this update, and they’re available immediately to anyone in the Release Preview channel. Here’s exactly what’s changed.

The 0x80070002 update failure is dead

The most disruptive bug was the infamous 0x80070002 error, which stopped some Insiders from installing newer preview builds altogether. This catch-all error typically signals missing files or a metadata mismatch between the update catalog and the local store, effectively jamming the update pipeline. With KB5065789, the manifest processing glitch that triggered the failure has been corrected, allowing previously stuck devices to resume normal flight progression.

DRM playback works again

A regression introduced by the August servicing update KB5064081 had silently broken protected content playback in many media applications. Blu-ray, DVD, and digital TV apps that rely on Windows’ DRM chain suddenly refused to play licensed streams. The fix restores the necessary interaction between OS DRM modules and third-party players, so your media center software should now function as expected. If you’ve been staring at a black screen instead of a movie, this is the patch you need.

Smaller but meaningful polish

  • Battery icon now shows charging state reliably. Some laptops had stopped displaying the charging indicator even when plugged in; that’s been corrected.
  • Storage settings and drive properties no longer crash. Opening Settings > System > Storage or right-clicking a drive in File Explorer could trigger an enumeration crash; the update resolves it.

Enterprise backend improvement: CRL partitioning

Certificate Revocation List (CRL) partitioning is now supported in Windows Certificate Authorities. This feature lets large organizations break their CRLs into smaller segments, reducing download sizes and speeding up revocation checks for deployments with hundreds of thousands of certificates. It’s a behind-the-scenes change that requires careful validation before turning on, but it’s a meaningful upgrade for complex PKI environments.

What didn’t make it: Click to Do and other delayed features

Microsoft originally teased a “Convert to table with Excel” feature for Click to Do, part of the AI-powered tools coming to Copilot+ devices. That flow would let you capture an on-screen table and instantly transform it into an editable spreadsheet. According to the official release notes, this feature has been held back and will arrive in a future update. It remains gated behind Copilot+ hardware and a Microsoft 365 subscription, so even when it lands, not everyone gets it. Other AI enhancements and accessibility improvements are also staging gradually via server-side rollouts, meaning your device may not see them immediately.

What this means for you right now

If you’re an Insider or enthusiast

  • Update now if you were blocked. If KB5065789 successfully installs, your 0x80070002 and DRM problems are resolved. Verify by checking Windows Update for further updates and testing your media apps.
  • Don’t panic if the install fails again. A minority of devices may still need manual intervention—follow the troubleshooting steps below.
  • Manage expectations about Click to Do. Do not plan workflows around the table conversion feature; it’s not in this build and its arrival date is unknown.

If you’re an IT admin or piloting 25H2

  • Test on a representative set of machines. Include devices that had 0x80070002 failures, machines with media playback software, and any endpoints running your PKI infrastructure.
  • Validate CRL partitioning in a lab first. Enable it on a non-production CA, confirm that revocation lookups work across partitions, and check your replication topology before wider rollout.
  • Prepare remediation scripts. Even with the fix, some machines might still choke on updates. Having automated DISM/SFC and component resets ready will save time.
  • Remember that the 25H2 enablement package is small but still a change. While it’s not a full OS upgrade, it flips on new features—treat it like any other pilot deployment and watch for compatibility gremlins.

How we got here: a timeline of regression and recovery

  • August 2025: Microsoft released servicing update KB5064081, which unwittingly broke DRM playback in many third-party media apps. Around the same time, the 0x80070002 update failure began surfacing more frequently in Insider flights, though its root cause was separate.
  • September 12, 2025: The KB5065789 Release Preview announcement was published, detailing the impending fixes and the Click to Do delay.
  • September 17, 2025: Builds 26100.6718 and 26200.6718 were pushed to the Release Preview channel as an optional update.
  • October 2025 (expected): These fixes are likely to reach all Windows 11 24H2 and 25H2 users via Patch Tuesday, along with the broader 25H2 enablement rollout.

What to do if you still hit the 0x80070002 error

If KB5065789 refuses to install or you encounter the error again, here’s a battle-tested recovery sequence. Start with the least destructive option and escalate if needed.

  1. Check basics
    • Make sure your system drive has at least 10 GB free.
    • Confirm Date & Time settings are set to automatic.
  2. Reboot and retry
    • A restart clears transient locks that can block the install.
  3. Reset Windows Update components
    • Open an elevated Command Prompt and run the following commands sequentially:
      net stop wuauserv net stop bits ren %systemroot%\SoftwareDistribution SoftwareDistribution.old ren %systemroot%\System32\catroot2 catroot2.old net start bits net start wuauserv
    • Reboot and attempt the update again.
  4. Run system health checks
    • Execute DISM /Online /Cleanup-Image /RestoreHealth
    • Then sfc /scannow
    • If DISM can’t find repair sources online, mount a Release Preview ISO and point it to the local sxs folder.
  5. In-place repair upgrade (last resort)
    • Use a signed Release Preview ISO to perform an in-place upgrade, keeping apps and files. This virtually always restores update functionality.

If all else fails, collect your WindowsUpdate.log and CBS logs and file a report via Feedback Hub.

One more thing: verify DRM playback carefully

Because the DRM regression affected different apps in different ways, don’t assume all your media software is fixed just because one player works. After installing KB5065789, run each of your Blu-ray players, TV tuner applications, and streaming apps that use DRM separately. This is especially important for home theater PC setups and digital signage kiosks that rely on protected content.

Outlook

These builds are a clear signal that Microsoft is focused on stability as it prepares the 25H2 feature update for broad release. The fixes are conservative, the feature delays are explicit, and the enablement package model remains in play—all of which points to a relatively smooth rollout in October. Keep an eye on the Release Preview channel for any follow-up patches, and don’t hold your breath for Click to Do table detection; Microsoft will announce it when it’s truly ready. In the meantime, Insiders and admins can now move forward with confidence that two of the most stubborn blockers have been excised.