Windows 11 Release Preview: Build 26100.6718 / 26200.6718 Fixes & 25H2 Enablement

Microsoft has quietly shipped small but important updates to the Windows 11 Release Preview channel — Build 26100.6718 for Windows 11 version 24H2 and Build 26200.6718 for 25H2 — rolling several stability fixes and clarifications into the pre-release stream while delaying one headline feature originally announced last week. (blogs.windows.com)

Background / Overview​

Microsoft publishes multiple preview channels for Windows 11 — Canary, Dev, Beta and Release Preview — with the Release Preview channel used to stage fixes and preview feature updates that are close to broad availability. The recent updates are delivered as a small cumulative package (KB5065789) to Release Preview Insiders and are explicitly targeted at both the 24H2 servicing baseline and the upcoming 25H2 enablement package. That means many machines already on 24H2 will receive a small enablement-style flip to 25H2 without a full reinstall; Microsoft has also staged ISO images for test and clean-install scenarios. (blogs.windows.com) (notebookcheck.net)
This cadence — servicing-channel patches plus an enablement package pathway — is how Microsoft intends to keep enterprise and consumer devices in sync across minor feature refreshes and quality improvements. Release Preview updates are therefore especially relevant to IT pilots and power users: they indicate what will likely ship broadly in the near term and which fixes Microsoft is prioritizing before general availability.

---

What shipped in Builds 26100.6718 / 26200.6718 (KB5065789)​

The official Windows Insider announcement for these builds lists a mix of gradual-rollout features and immediate fixes. The most operationally important items added on September 17 are the stability and servicing fixes; notable items include:

• Fixed an issue that could break playback of DRM‑protected content in some Blu‑ray, DVD and digital TV applications — a regression that could appear after installing KB5064081. (blogs.windows.com)
• Added support for Certificate Revocation List (CRL) partitioning in Windows Certificate Authorities to improve certificate infrastructure performance and scalability. (blogs.windows.com)
• Fixed a taskbar battery icon bug where the icon might not show a charging state despite the device actually charging. (blogs.windows.com)
• Resolved a Settings app crash when inspecting drive information under Settings > System > Storage (and the related File Explorer drive properties launch path). (blogs.windows.com)
• Fixed a Windows Update installation failure where some Insiders saw error 0x80070002 while attempting to install the build. (blogs.windows.com)

At the same time Microsoft quietly delayed the Click to Do table-detection feature first shown in earlier Release Preview notes; the blog post now confirms the feature will arrive in a future update rather than in this flight. This affects the “Convert to table with Excel” action that was demonstrated for Copilot+ devices. (blogs.windows.com)
Multiple independent outlets and testing communities reported the same changelog summary and rollout behavior, confirming the packages are circulating in the Release Preview channel and that Microsoft has made ISOs available to signed-in Insiders for clean-install testing. (notebookcheck.net)

---

Why the fixes matter (deep dive)​

0x80070002: Windows Update installation errors — what happened and why the patch matters​

The 0x80070002 Windows Update error is a historic and broad family of update failures; in practice it is a catch-all code Microsoft has historically returned when update components find missing files, corrupted metadata, or mismatch between update catalog metadata and local store. In recent Insider flights, some devices reported the error while attempting to download or apply cumulative updates — in certain cases downloads would stall or fail during the catalog/manifest phase and the update subsystem would abort. (blogs.windows.com)
Why this fix matters:

• It directly impacts the ability of preview devices to stay up to date with subsequent builds; for Insiders that can mean being unable to progress to newer builds or losing access to staged features. (blogs.windows.com)
• For IT pilots, an unresolved update failure in the Release Preview channel can stall compatibility testing and delay adoption plans.

Practical troubleshooting that remains useful if you still see 0x80070002 after installing the cumulative fix:

• Reset Windows Update components (stop wuauserv and BITS, rename SoftwareDistribution and catroot2).
• Run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow, using an ISO as a source if online restore fails.
• Attempt an in-place upgrade using a Release Preview ISO where permitted.

These steps are standard Windows Update remediation practices and remain relevant until your device confirms the build-install now completes. Community threads and Microsoft Q&A show many users had to fall back to ISOs or component resets before the fix landed, so organizations running Release Preview pilots should validate updates on a small cohort before broad rollout. (makeuseof.com)

---

DRM-protected playback regression (post-KB5064081)​

Media playback of DRM‑protected content is a sensitive area because it touches licensing, app trust, and third‑party playback stacks. The September 17 update explicitly calls out a regression where certain Blu‑ray, DVD and TV apps could fail to play protected media after installing KB5064081 — the earlier servicing package — and the new small update addresses that problem. This is important for users who rely on dedicated playback applications or set‑top capture software. (blogs.windows.com)
Operational notes:

• The root cause appears tied to an interaction between the cumulative servicing payload and DRM modules used by third-party playback applications; Microsoft elected to ship a targeted servicing fix rather than a broad rollback. The fix’s presence in the Release Preview channel indicates Microsoft is reasonably confident but still staging the patch prior to general rollout. (blogs.windows.com)
• If you operate kiosks, media centers, or production environments that play DRM content, verify playback after installing KB5065789 and keep a rollback plan or offline ISO handy for remediation. Community reports show playback regressions can be app-specific, so test each playback path (Blu‑ray player, DVD app, tuner app) rather than just one. (blogs.windows.com)

---

Settings crash and battery icon: everyday polish with real user impact​

Two of the seemingly small fixes — the Settings app crash when viewing drive info and the battery icon not showing charging state — are “quality of life” fixes with high day‑to‑day visibility.

• A Settings crash while viewing storage or launching those panels from File Explorer can block routine maintenance and drive diagnostics. Insiders and device administrators use those pages frequently; a crash breaks workflows and increases support costs. The release notes confirm the crash has been fixed. (blogs.windows.com)
• Battery indicator problems (icon not reflecting charging state) are a classic user trust issue: when the UI disagrees with hardware behavior, users begin to doubt the system and may escalate support calls unnecessarily. Fixing the icon behavior reduces confusion and the volume of misleading support tickets. (blogs.windows.com)

Both are small fixes with outsized usefulness — they improve perception of stability and reduce friction for IT support teams.

---

CRL partitioning in Windows Certificate Authorities​

Adding CRL partitioning support in Windows Certificate Authorities is a backend improvement that matters most to enterprise PKI operators. CRL partitioning helps large-scale CA deployments manage revocation lists more efficiently by dividing CRL entries across partitions, which reduces the size of any single published CRL and improves revocation look-up performance.

• For organizations operating internal PKI at scale, this is a tangible manageability improvement. It may not affect end users directly but can reduce latency and bandwidth burden for devices checking certificate revocation status. Confirm your CA tooling and replication topology before enabling new CRL behaviors. (blogs.windows.com)

---

Click to Do table detection delayed — what changed and why it matters​

Microsoft previewed an expansion to Click to Do that would let the system detect simple on‑screen tables and offer a “Convert to table with Excel” action, including a shortcut workflow invoking Excel to paste the captured table. The promised feature was hardware and subscription gated — initially available on Snapdragon-based Copilot+ devices and requiring the latest Excel and a Microsoft 365 subscription. The September 17 update retracts the rollout and states the feature will arrive in a future update instead. (blogs.windows.com)
Why this delay is notable:

• The feature demonstrates deeper Microsoft 365 integration in Windows, blurring lines between OS-level capture tools and cloud-enabled productivity. The delay is a signal Microsoft prefers a gradual, controlled rollout — likely to limit early regressions and compatibility issues across device classes. (blogs.windows.com)
• The hardware and subscription gating (Copilot+ devices + Microsoft 365) affects who will see the feature first. Organizations must not assume universal availability at GA and should plan training and documentation accordingly. (blogs.windows.com)

Caution: Microsoft did not announce a new timeline for Click to Do’s table detection; plan for it arriving in a later build and avoid relying on it for immediate workflows. This timeline is not yet verifiable beyond Microsoft’s “future update” statement. (blogs.windows.com)

---

Deployment and IT implications​

25H2 via enablement package — what IT needs to test now​

Windows 11 25H2 is being staged as an enablement package for existing 24H2 devices in the Release Preview channel. An enablement package flips code already staged on 24H2 devices rather than shipping a whole new OS image. That’s convenient, but it places emphasis on:

• Compatibility testing for management tooling and scripts (notably, Microsoft has called out deprecation/removal of PowerShell 2.0 and WMIC in shipping images — validate any legacy automation).
• Validation of ISVs and drivers, especially for systems that touched preview flights earlier in the cycle. Even small UI or API changes can break older management agents. (blogs.windows.com)

Recommended pilot checklist (brief):

• Stage the enablement package on a small pilot group with representative hardware.
• Validate imaging, deployment tooling, and any custom post-install scripts.
• Test critical line‑of‑business apps and device drivers.
• Confirm any scheduled automation that depends on PowerShell 2.0/WMIC has been updated. (blogs.windows.com)

ISOs published to the insider ISO portal are useful for lab validation (clean installs and image captures) and Microsoft has staged ISO media for signed‑in Insiders to accelerate lab testing. Use those images to build test VM templates or capture updated golden images once the enablement package is accepted in your environment. (notebookcheck.net)

---

Practical guidance: If you're an Insider or IT admin​

• If you run the Release Preview channel and you saw the update show up, install the small package (KB5065789) and confirm the previously failing update path now completes; verify playback of DRM content if you rely on such apps; check battery reporting and storage pages in Settings. These are the high‑value regression areas fixed in this flight. (blogs.windows.com)
• For devices that previously exhibited 0x80070002 during install attempts, follow standard remediation in this order:
• Reboot and retry the update.
• Reset Windows Update components (stop services and rename SoftwareDistribution and catroot2).
• Run DISM /RestoreHealth then sfc /scannow (supply an ISO as source if required).
• If the problem persists, consider an in-place upgrade using a signed Release Preview ISO. Community and Microsoft Q&A threads document many such cases and the steps that helped users return to a healthy update state. (technewstoday.com)
• For enterprise pilots: include DRM playback test cases in your app compatibility matrix if your organization uses archived or protected media workflows. File a scoped test plan for storage/drive property pages and have support scripts ready for resetting Windows Update components if you publish the enablement package broadly. (blogs.windows.com)

---

Strengths in Microsoft’s approach — and areas to watch​

Strengths​

• Targeted, quick fixes: Microsoft’s 9/17 update delivered narrowly scoped remediation for high‑impact regressions (Windows Update, DRM playback, Settings crash) without bundling unrelated changes, which reduces risk during Release Preview pilots. (blogs.windows.com)
• Transparency on gating and timing: The Release Preview notes clearly state which features are gated by hardware, subscription, or region (e.g., Click to Do table detection initially on Snapdragon Copilot+ devices), which helps IT plan adoption and training. (blogs.windows.com)
• Enablement package model: Delivering 25H2 as a flip-type enablement package simplifies broad rollouts and reduces user disruption compared to full feature refreshes. ISOs for clean installs remain available for lab validation. (notebookcheck.net)

Risks and caveats​

• Timing uncertainty for delayed features: The Click to Do table-detection delay is a reminder that preview timelines can slip; organizations that expected to rely on newer productivity integrations should not schedule rollouts around preview-only functionality. Microsoft hasn’t provided a revised release date for the feature. (blogs.windows.com)
• Hidden ripple effects: Fixes to certificate, update, or media subsystems can interact unpredictably with third‑party drivers and security agents. IT pilots must include a broad set of functional tests (security posture, update-management workflows, imaging, and restore scenarios) before accepting the enablement package widely. (blogs.windows.com)
• Dependence on Microsoft 365 and Copilot+ hardware: New productivity add-ons are increasingly gated by cloud subscriptions and new silicon features. That can create an uneven feature experience across an organization and requires clear internal communication and license planning. (blogs.windows.com)

---

Conclusion — what to take away​

The 9/17 Release Preview update (Builds 26100.6718 and 26200.6718, packaged as KB5065789) is a classic quality-and-stability flight: it addresses practical, high-frequency user problems (Windows Update failures such as 0x80070002, media playback regressions tied to an earlier servicing package, Settings crashes, and a misleading battery icon) while pausing a headline productivity feature (Click to Do table detection) to ensure a cleaner rollout later. The inclusion of enterprise‑oriented improvements such as CRL partitioning further signals Microsoft’s emphasis on manageability and scale. (blogs.windows.com)
For Release Preview Insiders and IT pilots, the guidance is straightforward: apply the update in a controlled pilot, test the regression areas called out in the release notes (DRM playback, Windows Update, storage pages, battery UI), and use the published ISOs for clean installs and imaging validation where appropriate. For organizations planning adoption of 25H2, treat the enablement package as a pilotable change rather than a trivial toggle — confirm automation and legacy tooling compatibility (PowerShell 2.0 / WMIC deprecation in shipping images is specifically called out for validation). (blogs.windows.com)
If problems persist after applying KB5065789, continue to use the established Windows Update troubleshooting steps (reset components, DISM/SFC, ISO in-place upgrade) and engage Feedback Hub or Microsoft Q&A with logs — the Release Preview channel exists to surface exactly these kinds of real‑world incompatibilities before broad deployment. (makeuseof.com)

---

---

Source: Neowin Microsoft fixes Windows Update error 0x80070002 and other issues in new Windows 11 builds

 

[ChatGPT]

Microsoft has quietly shipped two companion Release Preview builds — Build 26100.6718 (24H2) and Build 26200.6718 (25H2) — as part of the small cumulative package KB5065789, addressing a set of high‑impact regressions (notably the persistent 0x80070002 update failure and DRM playback breakage introduced by an earlier servicing update) while delaying one of the headline productivity features until a later flight. (blogs.windows.com)

---

Background​

Microsoft delivers Windows 11 preview builds through multiple Insider channels; the Release Preview stream is the near‑final staging ground for fixes and enablement-style flips that will reach mainstream users. The KB5065789 package is explicitly targeted at both the current servicing baseline (24H2) and the upcoming enablement package for 25H2, meaning many existing devices receive only a small activation change rather than a full OS reinstallation. This delivery model reduces upgrade downtime for broad rollouts but raises validation needs for IT pilots and power users. (notebookcheck.net)
Why this flight matters now:

• It fixes a Windows Update failure that left some Insiders unable to complete preview installs (error 0x80070002), a class of problem that can block adoption and testing. (blogs.windows.com)
• It patches a DRM playback regression (Blu‑ray/DVD/digital TV apps) introduced after the August KB5064081 servicing update, restoring protected content playback in affected apps. (blogs.windows.com)
• It includes smaller but user‑visible polish (battery icon charging state, Settings/Storage stability) and a backend enterprise improvement (CRL partitioning for Windows Certificate Authorities). (blogs.windows.com)

These focused fixes — rather than a broad feature rollup — are a classic quality‑and‑stability flight intended to keep pilot groups moving forward while minimizing regression risk.

---

What Microsoft shipped in Builds 26100.6718 / 26200.6718 (KB5065789)​

The Release Preview update bundles both gradual rollout features (gated, server‑side or hardware/license‑restricted) and immediate fixes. Below is a precise breakdown of the most operationally relevant items in this flight.

Immediate fixes and behavior restores​

• Fixed Windows Update installation failure where some Insiders encountered error 0x80070002 while attempting to install preview builds. This was a blocking failure for a subset of devices that stalled installs during manifest/catalog processing. (blogs.windows.com)
• Resolved a regression from KB5064081 that could break playback of DRM‑protected content in some Blu‑ray, DVD and digital TV applications; the patch lets affected media apps play protected streams again. (blogs.windows.com)
• Fixed a taskbar battery icon bug where the icon sometimes failed to show charging status even when the device was plugged in, restoring accurate battery UI feedback. (blogs.windows.com)
• Corrected a crash when opening Settings > System > Storage or the File Explorer drive properties page that occurred while the system was enumerating and checking drive information. (blogs.windows.com)

Enterprise and platform changes​

• Certificate Revocation List (CRL) partitioning support was added to Windows Certificate Authorities. This backend enhancement helps large PKI deployments by breaking CRLs into smaller partitions to reduce the size of any single published CRL and improve revocation lookup performance in high‑scale environments. Administrators should validate replication and tooling before toggling partitioning on production CAs. (blogs.windows.com)

Delayed or gated features​

• Microsoft delayed the broadly publicized Click to Do table detection feature that can convert on‑screen tables to Excel spreadsheets. The blog now confirms the “Convert to table with Excel” flow will arrive in a future update rather than in this build; the feature remains hardware‑ and subscription‑gated (initial Copilot+ device previews and Microsoft 365 subscription for full flow). Organizations should not expect immediate availability. (blogs.windows.com)
• Other Click to Do / AI enhancements and accessibility improvements were staged to roll out gradually and remain subject to server-side gating.

---

Why these fixes matter (technical context and impact)​

0x80070002: more than a numeric annoyance​

The error code 0x80070002 is a long‑running catch‑all that Windows Update historically throws when required update files are missing or metadata between the update catalog and the local store is inconsistent. In the Insider previews, the symptom often manifested as a download stall or a manifest mismatch that caused the update subsystem to abort, leaving devices unable to progress to newer builds. For Release Preview Insiders, this is particularly disruptive because it blocks validation of later builds and can leave test devices stuck on older baselines. The KB5065789 fix restores the normal update path for those devices. (blogs.windows.com)
Practical impact:

• Individual Insiders who previously could not finish preview installs can now complete the pipeline without the workaround detours.
• Enterprise pilots that depend on a continuous Release Preview image for application and driver validation will see fewer blocked upgrades — a direct reduction in test friction.

DRM playback regressions — why they break workflows​

DRM‑protected playback depends on a chain of trust between application players, OS DRM modules, and the media content provider’s license server. The regression introduced by KB5064081 apparently altered an interaction within the cumulative servicing payload that affected those DRM modules, causing playback of protected content to fail in third‑party Blu‑ray, DVD or digital TV apps. The targeted patch in KB5065789 restores those interactions and prevents media‑center and kiosk workflows from breaking. This is an example where a relatively low‑level servicing change can have outsize impact on specialized workloads. (notebookcheck.net)

CRL partitioning — the enterprise angle​

For large internal PKI deployments, CRL partitioning is a meaningful manageability feature: partitioned CRLs are smaller, reducing bandwidth and lookup latency for certificate revocation checks. While end users won’t notice this change, organizations that operate hundreds of thousands of certificates will likely see measurable operational improvement — but only if their CA topology and replication tooling are validated first. Misconfiguration could lead to revocation lookup failures. (blogs.windows.com)

---

Verification: what we checked and cross‑references​

To confirm the contents and scope of the release, the official Windows Insider blog post for KB5065789 was consulted and used as the authoritative changelog and release note for the builds in question. Independent coverage from outlets that track Insider flights (NotebookCheck, Neowin, and other community tracking) corroborated the key fixes, added context on enablement/rollout behavior, and noted the delayed Click to Do deployment. This cross‑reference approach confirms the claims made in the Release Preview announcement and flags the delayed timelines as Microsoft‑stated rather than speculative. (blogs.windows.com) (notebookcheck.net) (neowin.net)
Cautionary note: Microsoft’s announcement describes some features as gradual or gated, so visibility and behavior can differ by device, region, and subscription entitlement. The timeline for the delayed Click to Do table detection remains unspecified beyond Microsoft’s “future update” note; treat that item as deferred until Microsoft publishes a new rollout date. (blogs.windows.com)

---

Actionable guidance for users and IT admins​

These builds are in the Release Preview channel — a near‑final testing surface intended for pilots and enthusiasts who want to validate bits before broad availability. The following checklist prioritizes safety and operational confidence.

For individual Insiders and enthusiasts​

• Install KB5065789 if you encountered 0x80070002 or DRM playback failures; the patch addresses those specific regressions. After installing, verify:
• Windows Update no longer fails with 0x80070002.
• Blu‑ray/DVD/digital TV apps that previously failed can now play protected content.
• Battery icon properly shows charging status.
• Settings > System > Storage and File Explorer drive property inspections no longer crash.
• If the update still fails, follow the standard remediation ordering:
• Reboot and try the update again.
• Reset Windows Update components (stop relevant services, rename SoftwareDistribution and catroot2). (learn.microsoft.com)
• Run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow; if online repair fails, supply an ISO as the source. (makeuseof.com)
• As a last resort in preview environments, perform an in‑place upgrade with a Release Preview ISO to restore update plumbing. (blogs.windows.com)
• Verify DRM playback in every app you rely on — the regression could vary between playback stacks; test Blu‑ray players, tuner software, and store apps individually.

For IT pilots and enterprise adopters​

• Treat the 25H2 enablement package as a pilotable change, not a trivial toggle. Stage KB5065789 on a representative pilot cohort that includes:
• Imaging and deployment automation workflows.
• Line‑of‑business apps and legacy drivers.
• Security agents and endpoint protection software.
• Any media center or DRM playback endpoints.
• Validate your CA tooling and replication topology before enabling CRL partitioning; perform staged testing in a lab CA environment to confirm revocation lookups succeed across partitions.
• Confirm any automation that relies on deprecated tooling (PowerShell 2.0, WMIC) has been updated; Microsoft explicitly called out legacy tooling as an adoption risk for updated images.
• If devices in your fleet previously failed updates with 0x80070002, include remediation scripts in the deployment plan to reset Windows Update components and automate DISM/SFC operations as pre‑validation checks. Community reports show the component reset sequence restored update health in many cases prior to the fix shipping. (learn.microsoft.com)

---

Troubleshooting steps (concise, reproducible sequence)​

Below is a compact, action‑oriented runbook for admins or power users to follow when encountering 0x80070002 or failed cumulative installs in these preview channels.

• Check free disk space on C: and confirm Date & Time settings are automatic; both can block updates. (makeuseof.com)
• Reboot the device and attempt the update again — sometimes transient locks are cleared by a restart.
• Reset Windows Update components:
• Open an elevated Command Prompt and run:
• 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 retry. (learn.microsoft.com)
• Run health checks:
• DISM /Online /Cleanup-Image /RestoreHealth
• sfc /scannow
• If DISM needs a source, mount a Release Preview ISO and point DISM to the local SxS folder. (makeuseof.com)
• If the device is still blocked, perform an in‑place repair upgrade using the signed Release Preview ISO (keeps apps and data). This restores update components and usually resolves persistent manifest or component corruption. (blogs.windows.com)

Note: All of the above are standard, proven Windows Update remediation techniques; if logs continue to show failures after these steps, collect WindowsUpdate and CBS logs and open a Feedback Hub/Support case with Microsoft including logs for targeted assistance. (learn.microsoft.com)

---

Strengths and notable positives​

• Targeted, low‑risk fixes: The KB5065789 package focuses on real user pain points (update failures, DRM regressions, UI misreports) without adding heavy new features that increase regression surface. This reduces rollout risk while still restoring critical functionality.
• Enablement package model continuity: Delivering 25H2 as an enablement flip is operationally efficient for large fleets and consumer devices alike — smaller downloads, faster restarts, and easier rollback through standard servicing controls. The release confirms Microsoft’s continued reliance on this model.
• Enterprise‑oriented improvements: CRL partitioning is a practical, non‑glamorous improvement that will help very large PKI operators reduce revocation lookup cost and manage CRL sizes more predictably.

---

Risks, caveats, and things to watch​

• Ripple effects of low‑level fixes: Fixes to update, certificate, or DRM subsystems can interact unpredictably with third‑party drivers and security agents. Comprehensive functional tests (imaging, application compatibility, security posture) are required before broadly accepting the enablement package.
• Feature gating and fragmentation: Microsoft’s gradual rollout and hardware/subscription gating (Copilot+ hardware, Microsoft 365 entitlements) mean adoption and user experience can vary across a fleet. Don’t schedule rollouts around features still marked as gated or “coming soon.” The Click to Do table detection delay is the clearest example; its availability remains unspecified. (notebookcheck.net)
• Unresolved edge cases: While the 0x80070002 fix will resolve many update failures, not every instance of that code has the same root cause; organizations should adopt the recommended remediation runbook and be prepared to use in‑place repair ISOs when required. Community threads show a minority of devices still needed manual intervention before the fix was applied. (learn.microsoft.com)

---

Timeline and rollout expectations​

• Microsoft published the KB5065789 Release Preview announcement (initial post on September 12, 2025), and subsequently updated the post to note the 9/17 release of Builds 26100.6718 and 26200.6718 as the small servicing package carrying the fixes. Insiders in the Release Preview channel should see the optional preview appear under Windows Update. (blogs.windows.com)
• Independent reporting and community tracking indicate the broader stable GA of the 25H2 enablement package is expected in the normal October servicing window for Windows feature refreshes, though Microsoft often staggers availability by regions and device families. Treat the Release Preview as the last chance to surface compatibility issues before that general availability. (notebookcheck.net)

---

Bottom line and recommended next steps​

This Release Preview flight is a quality‑focused, conservative update that restores core user experiences and gives enterprises a safer pathway to the 25H2 enablement package. The headline fixes — the 0x80070002 update error remediation and the Blu‑ray/DVD/TV DRM playback repair — remove two real blockers that were harming both individual Insiders and production‑adjacent media workflows. For admins and power users the priority actions are:

• Pilot KB5065789 on a representative cohort, validating update health, DRM playback, battery reporting, and storage page stability.
• Prepare remediation scripts for updates (reset components, DISM/SFC) and keep Release Preview ISOs handy for in‑place repairs where needed. (learn.microsoft.com)
• Delay any dependency on the Click to Do table detection feature until Microsoft provides definitive rollout dates and hardware/service gating details.

These builds are an incremental but meaningful step toward a smoother 25H2 rollout; the cautious, surgical approach to fixes is exactly what pilot programs and IT validation windows are for — accept change deliberately, test broadly, and keep rollback paths ready.

---

Microsoft’s Release Preview cadence exists to catch exactly these kinds of regressions before wide public release; the KB5065789 update is evidence that rapid, narrowly targeted servicing still plays a central role in reducing friction for both enthusiasts and enterprise adopters. (blogs.windows.com)

---

Source: Windows Report Windows 11's latest Insider build 26100.6718 (24H2) & 26200.6718 (25H2) fixes update error 0x80070002, Blue-ray playback issues & more