Microsoft rolled out optional September preview updates for Windows 11 that bundle a surprising mix of AI-powered conveniences, accessibility improvements, and a broad set of bug fixes — and while Microsoft patched several known regressions, a small number of playback and compatibility edge cases remain under investigation.
Microsoft published two non‑security, optional preview packages in late September: KB5065789 (targeting Windows 11 24H2 and 25H2 Release Preview builds) and KB5065790 (for Windows 11 23H2). These are preview (C‑release) packages intended for validation and staged rollout ahead of the regular October Patch Tuesday distribution; they do not install automatically unless users opt in or are enrolled in Release Preview / Insider rings. The updates deliver incremental feature enablement — notably AI actions in File Explorer and small Settings and accessibility refinements — while delivering fixes for several high‑impact regressions reported during August–September servicing.
These preview releases follow the familiar Microsoft pattern: ship the bits in the servicing payload, enable features via server gating for subsets of devices and tenants, and use Release Preview as the final validation ring for fixes and staged feature rollouts. That means some features will appear immediately for certain devices and accounts, while others remain server‑gated or require Copilot/Microsoft 365 entitlements and Copilot+ hardware.
Microsoft responded by staging a targeted fix into the Release Preview channel (packaged as KB5065789 builds in the 26100.67xx/26200.67xx series). The company’s release notes indicate the EVR/HDCP problem was partially resolved by the September preview and that some apps using DRM for digital audio may still experience playback issues; Microsoft is continuing investigation and will issue further fixes if necessary. In short: the worst of the regression was addressed for many apps, but not all scenarios are fully fixed yet.
Practical takeaway: if you rely on legacy Blu‑ray/DVD or capture/tuner workflows on Windows, avoid installing September rollups on mission‑critical machines until verifying playback with your specific apps and hardware. If you already installed the rollups and experienced playback failures, the Release Preview fix is intended to resolve many cases; patching via Release Preview or waiting for the wider October rollup is recommended. Community testing and vendor feedback have corroborated Microsoft’s timeline and mitigation approach.
Why it matters: even though SMBv1 is legacy and discouraged, many industrial devices, embedded systems, and older NAS units still rely on it. In environments where SMBv1 is unavoidable, the NetBT pathway remains in use and a regression like this can halt file access for entire workflows. The recommended interim workaround — where possible — was to allow SMB traffic on TCP port 445 so systems can fall back to direct TCP SMB instead of NetBT; the patch eliminates the need for this workaround in patched environments.
These previews are useful to early adopters and IT validation rings, but they are not a substitute for a conservative production patching strategy. Evaluate features and fixes in your environment, pay careful attention to SSU/LCU rollback mechanics, and keep an eye on Microsoft’s Release Health notes as the fixes make their way into the broader October cumulative rollup.
Source: pcworld.com Optional Windows 11 September update adds tons of new preview features
Microsoft published two non‑security, optional preview packages in late September: KB5065789 (targeting Windows 11 24H2 and 25H2 Release Preview builds) and KB5065790 (for Windows 11 23H2). These are preview (C‑release) packages intended for validation and staged rollout ahead of the regular October Patch Tuesday distribution; they do not install automatically unless users opt in or are enrolled in Release Preview / Insider rings. The updates deliver incremental feature enablement — notably AI actions in File Explorer and small Settings and accessibility refinements — while delivering fixes for several high‑impact regressions reported during August–September servicing. These preview releases follow the familiar Microsoft pattern: ship the bits in the servicing payload, enable features via server gating for subsets of devices and tenants, and use Release Preview as the final validation ring for fixes and staged feature rollouts. That means some features will appear immediately for certain devices and accounts, while others remain server‑gated or require Copilot/Microsoft 365 entitlements and Copilot+ hardware.
What’s new and notable in the September optional updates
AI actions in File Explorer — a practical first step
- Right‑clicking on supported images (.jpg, .jpeg, .png) now surfaces AI actions such as Visual Search, Blur Background, Erase Objects, and Remove Background. These edits are integrated with existing apps (Photos and Paint) for the heavy lifting. The actions are concise and oriented toward quick edits without launching full image editors.
- For documents stored in OneDrive or SharePoint, there’s now a Copilot‑powered Summarize option that can generate quick summaries without opening each file. This feature requires a valid Microsoft 365/Copilot license and is subject to server‑side gating.
Settings, keyboard shortcuts, and system polish
- The Advanced Settings page replaces the old “For Developers” area, consolidating developer and advanced system toggles in one place. Several time, language, and keyboard options migrated from Control Panel into Settings — a continuing push toward full Settings parity.
- Two small but handy keyboard shortcuts were added: Win + Minus inserts an en‑dash, and Win + Shift + Minus inserts an em‑dash. These tiny quality‑of‑life shortcuts are the sort of detail power users appreciate.
Accessibility and accessories updates
- Windows Narrator gains Braille Viewer support so refreshable braille displays can show on‑screen text natively (Windows key + Ctrl + Enter, then Narrator key + Alt + B). Voice Access expands natural language recognition on some Copilot+ devices. Controller behavior was refined for Xbox controllers: quick press opens Game Bar, long press opens Task View, and holding the button powers the controller down. These changes improve multi‑modal access and device ergonomics.
Other conspicuous fixes in the rollup
Microsoft documented a number of targeted reliability fixes in the preview updates; the list below summarizes the higher‑impact items that administrators and power users should know about:- File Explorer: removal of accented backgrounds in the “Open with” list, fix for overlapping icons and text at increased text scaling, and faster launch of cloud files.
- Hyper‑V: a fix for starting VMs with TPM on Arm64 devices. This relieves a painful edge case for Arm‑based virtualization users.
- Input / IME: corrected character rendering problems when using Chinese IME (and cases where characters previously appeared as empty boxes).
- Networking: an important fix for an SMB v1 over NetBT connectivity regression — addresses failures to connect to shared files and folders introduced by earlier September rollups.
DRM playback regression — partially resolved, still watchful
One of the largest headlines of September’s servicing cycle was a regression that could block playback of DRM‑protected content in some Blu‑ray/DVD and digital‑TV apps that rely on the legacy Enhanced Video Renderer (EVR) and OS‑level DRM/HDCP enforcement. The regression first appeared after an optional August preview (KB5064081) and then re‑emerged after the broader September cumulative rollup (KB5065426). Affected users reported black screens, copyright errors, and interrupted playback in legacy players — streaming apps such as Netflix were not impacted since they use newer app‑managed DRM flows.Microsoft responded by staging a targeted fix into the Release Preview channel (packaged as KB5065789 builds in the 26100.67xx/26200.67xx series). The company’s release notes indicate the EVR/HDCP problem was partially resolved by the September preview and that some apps using DRM for digital audio may still experience playback issues; Microsoft is continuing investigation and will issue further fixes if necessary. In short: the worst of the regression was addressed for many apps, but not all scenarios are fully fixed yet.
Practical takeaway: if you rely on legacy Blu‑ray/DVD or capture/tuner workflows on Windows, avoid installing September rollups on mission‑critical machines until verifying playback with your specific apps and hardware. If you already installed the rollups and experienced playback failures, the Release Preview fix is intended to resolve many cases; patching via Release Preview or waiting for the wider October rollup is recommended. Community testing and vendor feedback have corroborated Microsoft’s timeline and mitigation approach.
Deep dive: the SMB v1 over NetBT connectivity problem
A less glamorous but operationally serious regression surfaced after the September servicing stack: devices using SMB v1 over NetBIOS over TCP/IP (NetBT) could fail to connect to shared files and folders following the September security rollup (KB5065431). Microsoft documented the behavior and then included a remediation in the preview update KB5065790 for Windows 11 23H2. The fix restores connectivity in affected SMBv1/NetBT scenarios.Why it matters: even though SMBv1 is legacy and discouraged, many industrial devices, embedded systems, and older NAS units still rely on it. In environments where SMBv1 is unavoidable, the NetBT pathway remains in use and a regression like this can halt file access for entire workflows. The recommended interim workaround — where possible — was to allow SMB traffic on TCP port 445 so systems can fall back to direct TCP SMB instead of NetBT; the patch eliminates the need for this workaround in patched environments.
Enterprise and IT implications
Staged rollout and gating — test before broad deployment
These preview packages are explicitly non‑security and optional; Microsoft expects organizations to validate them in test rings and pilots. The combined Servicing Stack Update (SSU) and cumulative payload model used in these releases can complicate rollback scenarios — the SSU component persists once installed and may make complete uninstallation more involved. Patch managers should therefore:- Install in a Release Preview or validation ring first (not on production endpoints).
- Verify that mission‑critical apps (virtualization stacks, media playback pipelines, printers, and domain‑joined SMB shares) behave correctly after patching.
- Document rollback and recovery steps, including DISM/Remove‑Package procedures because using wusa.exe to uninstall the combined SSU+LCU package will not remove the SSU.
Hardware and licensing gating for AI features
Many AI features in File Explorer and Settings are hardware‑gated (Copilot+ NPUs) and license‑gated (Copilot/Microsoft 365 subscriptions). This means organizations should not assume immediate availability across the fleet: only Copilot+ devices with appropriate NPUs and tenants with Copilot entitlements will see the full set of AI experiences. IT procurement, imaging, and policy teams should include entitlement checks and hardware capability assessments before expecting these features to be usable at scale.Accessibility and compliance considerations
The Recall and Snapshot features, along with AI actions and Copilot integrations, involve telemetry and optionally stored snapshots. Organizations with strict retention, export, and privacy policies must validate opt‑in behaviors and confirm how captured data is stored and exported. Enterprise administrators should look for controls to limit snapshot collection and ensure compliance with retention policies. Microsoft’s rollout is opt‑in for snapshot collection, but auditing and governance are essential for regulated environments.What to expect next — rollout timeline and what to watch
- These preview updates are staged to Release Preview and may be rolled into the October Patch Tuesday mass deployment after validation. If you prefer stability, waiting for the October cumulative update (the scheduled monthly release that consolidates preview fixes) is prudent. WindowsForum community reporting and Microsoft’s own notes indicate a typical cadence where preview fixes are absorbed into the following month’s routine rollup.
- Microsoft will continue to address the remaining DRM audio edge cases; the company’s support doc explicitly states that while some EVR/HDCP problems were fixed in KB5065789, some apps that use DRM for digital audio still may fail, and a full long‑term fix is under investigation. Expect incremental hotfixes or October rollups to complete the remediation.
- Feature exposures for AI actions and Settings agent functionality will continue to be gradual and dependent on licensing and hardware. Users who do not see new functionality immediately should verify Copilot/Microsoft 365 licensing and hardware capability, and be patient — server gating often expands over weeks.
Step‑by‑step: how to evaluate and install the preview safely
- Identify test devices: choose systems that mirror production roles (media playback machines, Hyper‑V hosts, devices connected to legacy SMB shares).
- Enable Release Preview or manually download the optional package from Windows Update > Optional updates available (or use the Microsoft Update Catalog to fetch the .msu).
- Before installing: create a full system backup and record current Windows Update build numbers. Consider snapshots for VMs and image backups for critical endpoints.
- Apply the preview to test ring. Verify core functions: VM start/stop (Hyper‑V TPM on Arm64), File Explorer behavior (Open with list and text scaling), SMB connectivity for NetBT/legacy endpoints, and DRM playback on known affected apps.
- If issues appear, collect logs and open support cases as needed; if playback problems are present, consider rolling back or moving affected systems to a ring where the fix is validated. Microsoft’s guidance includes partial workarounds and explicit notes on SSU uninstallation mechanics — follow those carefully.
Strengths, limits, and risks — critical analysis
Strengths
- The updates deliver meaningful usability gains where they matter: File Explorer AI actions are pragmatic and reduce task friction, and the Settings consolidation closes long‑standing parity gaps with legacy Control Panel options. These are the kinds of incremental improvements that improve daily productivity.
- Microsoft’s staged response to the DRM regression was prompt: shipping a Release Preview targeted fix (KB5065789) to validate the resolution before broad rollout demonstrates responsible staging and helps prevent wider production disruption.
- The SMBv1/NetBT fix in KB5065790 addresses a real operational risk for sites that still rely on legacy SMB pathways, and the correction restores predictable connectivity without forcing administrators into risky long‑term workarounds.
Limits and remaining risks
- Feature fragmentation: on‑device vs cloud processing, Copilot license gating, and Copilot+ hardware requirements create inconsistent user experiences across the installed base. Corporations looking for consistent feature sets will need to plan hardware and licensing purchases carefully.
- Partial DRM fixes: Microsoft’s own documentation notes the EVR/HDCP playback problem is only partially resolved. Some apps that use DRM for digital audio remain affected. For media labs, broadcasting workflows, or legal playback environments, this is a non‑trivial continued risk until Microsoft issues a complete remediation.
- SSU coupling complicates rollback: because Microsoft bundles the Servicing Stack Update with the LCU in these preview packages, administrators should be prepared that simply uninstalling the LCU will not remove the SSU — there’s additional DISM work involved. That raises the stakes for testing and rollback planning.
Practical recommendations
- For home users: if you enjoy new features and are comfortable with preview updates, opt in to Release Preview and test the AI File Explorer actions and new Settings options. Back up important data before installing preview packages.
- For power users and enthusiasts: test AI actions but confirm that Copilot licensing and hardware gating are met if you want consistent behavior across devices. Try document summarization and image edits in a controlled environment and measure CPU/HDD/IO impact on real workloads.
- For IT and enterprise admins: treat KB5065789 and KB5065790 as validation flights. Prioritize testing of virtualization (Hyper‑V + TPM on Arm64), DRM playback on content‑critical systems, SMBv1/NetBT connectivity, print queue behavior, and any legacy IME or language stacks (Chinese IME rendering fixes were part of the rollups). Only promote to production after satisfactory validation.
Conclusion
September’s optional Windows 11 preview updates deliver a pragmatic blend of productivity features and reliability fixes: AI actions in File Explorer and Settings polishing are the most visible feature wins, while fixes for Hyper‑V TPM on Arm64, Chinese IME rendering, and SMB v1 over NetBT connectivity remedy real pain points. Microsoft’s staged fix for the EVR/HDCP DRM playback regression reduces immediate impact for many users, but a small set of audio‑DRM cases remain under investigation and should be monitored closely.These previews are useful to early adopters and IT validation rings, but they are not a substitute for a conservative production patching strategy. Evaluate features and fixes in your environment, pay careful attention to SSU/LCU rollback mechanics, and keep an eye on Microsoft’s Release Health notes as the fixes make their way into the broader October cumulative rollup.
Source: pcworld.com Optional Windows 11 September update adds tons of new preview features