Microsoft pushed official ISO images for Windows 11 version 25H2 to the Insider download portal this week, giving enterprise imaging teams, OEMs, and security vendors the first clean-install media for the next feature update. The release caps a busy cycle: September Patch Tuesday restored the missing clock in the calendar flyout, the company’s three-phase VBScript deprecation plan gained new guidance for VBA developers, and the Phison SSD firmware scare—widely misattributed to Windows updates—was traced to preview engineering firmware. For IT managers and power users, the real work isn’t about flashy new features but about deployment readiness, legacy remediation, and hardening update pipelines.

25H2 Arrives via Enablement Package—ISOs Fill the Imaging Gap

Windows 11 25H2 follows the same enablement-package (eKB) model that Microsoft perfected with 22H2 and 23H2. Most of the build’s binaries have been sitting dormant in the 24H2 servicing stream, waiting for a tiny eKB to light them up. For devices already running current cumulative updates, the jump to 25H2 will be little more than a reboot. That’s good news for mass rollouts: fewer helpdesk tickets, minimal user disruption, and no multi-gigabyte download for patched machines.

But eKBs don’t help with clean installs, imaging, or first-boot/OOBE testing. Microsoft seeded the Release Preview channel with builds from the 26200 family and then, after a short delay, published ISO files for signed-in Windows Insiders. Community reports peg x64 ISO sizes between roughly 5.5 GB and 7.1 GB depending on edition and language. The media covers the consumer and business SKUs that integration teams need for validation labs, SCCM/MDT task sequences, Windows Update for Business offline provisioning, and Azure Marketplace image preparation.

The timeline matters: Microsoft’s initial plan called for ISOs “next week” after the Release Preview rollout, but a brief slip left enterprise teams waiting. With the files now live, those teams can pull reproducible, verifiable artifacts for certification testing, EDR performance baselining, and installer-telemetry checks. Visual changes in 25H2 are incremental—refined Start menu layouts, File Explorer tweaks, taskbar animation polish, and staged Copilot+ features gated to hardware with an NPU—but the enterprise story is about what’s being removed. PowerShell 2.0 and WMIC are vanishing from shipping images, and the EdgeHTML-era web stack is officially deprecated.

September Patch Tuesday Restores the Clock and Patches NDI Audio

The September 2025 cumulative updates landed with KB5065426 for Windows 11 24H2 and corresponding KBs for other servicing branches. The standout fix: the clock that disappeared from the calendar flyout in a previous build is back. Users had been clicking the taskbar clock only to see the date without the time; that regression is now resolved.

A more obscure but critical fix addresses audio stuttering in applications that use the Network Device Interface (NDI) while Display Capture is active. This issue crept in after earlier updates and caused dropped frames and crackling in streaming and production workflows. The LCU also bundles the usual security patches and installer compatibility fixes. As always, admins should test on representative hardware and watch for safeguard holds—Microsoft is still blocking updates on some Dirac Audio configurations until vendor-supplied drivers flow through Windows Update.

EdgeHTML and VBScript: Two Deprecation Timelines IT Must Track

Two legacy deprecation tracks demand immediate attention from IT architects and developers.

EdgeHTML Web Components
Microsoft is retiring the OS-integrated Legacy Web View (the COM/Win32 renderer for EdgeHTML), Hosted Web Applications from the Windows 8/8.1 era, legacy PWAs that relied on EdgeHTML packaging, and the old EdgeHTML DevTools. These components have been on life support since the Chromium-based Edge took over; the deprecation consolidates engineering effort on WebView2 and modern PWA packaging. Any line-of-business application still embedding or automating EdgeHTML will break on a future Windows release. The migration path is WebView2, which ships with the OS and is backed by the same Chromium rendering engine as Edge.

VBScript’s Three-Phase Farewell
VBScript deprecation is a longer, phased process, but it has concrete implications for organizations that still run .vbs logon scripts, call VBScript.RegExp from VBA macros, or invoke VBScript type libraries in COM automation. Phase 1, which runs through approximately 2026, keeps VBScript enabled by default as a Feature on Demand. Phase 2 (2026–2027) will disable the FOD by default; admins must explicitly enable it. Phase 3 will remove VBScript entirely, at which point any remaining .vbs calls or typelib references will fail.

Office 2508 and later builds already include native RegExp classes that can replace most uses of VBScript.RegExp without third-party dependencies. But the migration still demands code-level changes and regression testing. IT shops should start an inventory now: scan all logon scripts, Group Policy scripts, and VBA projects for VBScript dependencies, then prioritize a rewrite into PowerShell or JavaScript before Phase 2 arrives.

The Phison SSD Scare: Preview Firmware, Not a Windows Bug

Alarming reports of SSDs bricking after recent Windows updates triggered a wave of investigation. The common thread: Phison controllers. After analysis, Phison and Microsoft both concluded that the most severe failures occurred on drives running engineering or preview firmware—not on consumer production firmware. Reviewers and testers had inadvertently used pre-release firmware that wasn’t validated for public updates. Consumer SSDs with vendor-supplied firmware were not affected in the same way.

For fleet managers, the episode is a reminder to enforce firmware hygiene. Inventory SSDs, cross-reference firmware versions against vendor advisories, and apply updates only from official channels. Never run engineering/preview firmware on production hardware. After updating firmware, verify boot and recovery behavior before rolling out feature updates at scale.

Community Tools: Flyoobe and Nano11 Push the Envelope—at a Cost

Two community-driven projects drew attention this week, both illustrating the lengths enthusiasts will go to keep older hardware running or strip Windows to its bones.

Flyoobe (formerly Flyby11) updated with new AI-related blocks and extensions, briefly disappeared from GitHub, then returned. It remains a potent hardware-requirement bypass and setup customization toolkit, but it’s unsupported and inherently risky. Using Flyoobe on a production endpoint can bypass telemetry, driver updates, or security features unintentionally. Enthusiasts should isolate it in test VMs.

Nano11 takes debloating to an extreme, producing images with a runtime footprint as low as 2.8–3.5 GB by stripping drivers, language packs, .NET precompiled assemblies, and more. The result is a non-serviceable franken-build that may be impossible to update or extend. Narrow use cases—VM testbeds or air-gapped experiments—are the only reasonable target; production endpoints must stick to supported images.

Copilot in Excel and Word: Productivity Helpers, Not Replacements

Microsoft’s Copilot features continue to trickle into Office apps. Excel’s new =COPILOT function lets users type natural-language prompts directly into cells to summarize, categorize, or transform ranges. It’s backed by a constrained model (likely an early rollout of GPT-4.1-mini) and subject to usage limits. Microsoft explicitly warns that the function is not suited for tasks requiring high accuracy or reproducibility—think regulated financial calculations or audit trails. Outputs must be validated.

Word Online gained one-click “Fix spelling and grammar,” which applies multiple corrections with an undo/review step. It’s convenient but still needs a human eye for tone and intent. For organizations subject to data governance policies, Copilot features must be evaluated against compliance posture before broad rollout. The rule of thumb: treat AI-generated content as a first draft, never as a final deliverable.

Microsoft Store Drops Developer Fee, Revises Policies

Microsoft removed the $19 one-time registration fee for individual developers in many markets, replacing it with a simpler ID-based verification flow. The change lowers the barrier for indie and global developers and is expected to boost submission volumes. At the same time, the Store team updated policies around child safety and generative-AI usage in apps. App managers should revisit distribution strategies—lower friction may open new markets but also demand more rigorous policy compliance checks.

Chrome’s Manifest V2 Sunset Pushes Users Toward MV3

Google’s multi-phase deprecation of Manifest V2 extensions is nearing the endpoint. Chrome 138/139 will remove enterprise exceptions, leaving many MV2-only extensions—including classic builds of uBlock Origin—disabled. Users who rely on MV2 ad blockers must migrate to MV3 versions, switch to browsers that still support MV2 (such as Firefox), or move to standalone app blockers. Developers with MV2 extensions should finish their MV3 migrations immediately; the clock is down to weeks, not months.

Gaming: Xbox Controller Gets Task View, GeForce NOW Goes Blackwell

An Insider build tweak gives the Xbox controller’s middle button a new role: short press opens Game Bar, long press opens Task View, press-and-hold still powers off the controller. The change is small but meaningful for handheld gaming PCs and controller-first workflows, putting Windows’ virtual desktops within thumb’s reach.

More significantly, NVIDIA rolled out Blackwell-powered RTX 5080-class servers to GeForce NOW, starting in September. The upgrade delivers DLSS 4 Multi-Frame Generation and claims of 5K/120 Hz streaming in Cinematic Mode. Early reviews put the cloud RTX 5080 experience on par with high-end local hardware under good network conditions. For gamers and enterprise streaming scenarios alike, the update materially raises the cloud-gaming performance ceiling. Meanwhile, the Epic Games Store gave away Ghostrunner, Monument Valley 2, and The Battle of Polytopia—claim-and-keep promotions that remain a low-friction perk for casual players.

Practical Guidance for IT Teams

– Imaging and deployment: Download the 25H2 ISO from the Insider portal, verify hashes, and test imaging pipelines. Audit scripts for PowerShell 2.0 and WMIC usage; replace legacy logic before fleet-wide deployment.
– Legacy script remediation: Inventory all VBScript and .vbs dependencies. Use Office 2508+ native RegExp classes, PowerShell rewrites, or JavaScript equivalents. Microsoft’s phased deprecation plan gives a runway, but each phase tightens the timeline.
– Firmware hygiene: Cross-reference SSD firmware against vendor advisories. Apply only production-certified firmware from official channels. Test boot and recovery after updates.
– Copilot governance: Gate Copilot features behind internal data policies. Require manual validation and audit trails for any AI-generated content used in regulated or high-stakes workflows.
– Store and browser readiness: Take advantage of the no-fee developer account if applicable, and revisit packaging for WebView2/PWA support. For browsers, plan MV3 migration or alternative ad blocking strategies before Chrome’s MV2 support ends.

Strengths and Risks

The enablement-package model continues to minimize user downtime and simplify deployment logistics. The availability of ISOs for 25H2 unblocks imaging and OOBE-centric testing. Clear, phased guidance for VBScript and EdgeHTML gives organizations lead time to migrate. On the flip side, rapid adoption of community bypass tools and extreme debloat scripts creates support and security risks on production hardware. Copilot features, while powerful, are non-deterministic and not yet ready for audited, reproducible workflows. Chrome’s MV2 deprecation and cloud-hardware transitions introduce temporary compatibility fragmentation that requires user education and contingency plans.

The Bottom Line

This week’s Windows news is a study in operational discipline. The 25H2 ISOs and Patch Tuesday fixes deliver needed stability, while the deprecation of EdgeHTML and VBScript signals that Microsoft is serious about retiring legacy components. The Phison firmware episode, community tooling risks, and browser extension phaseouts all reinforce the same lesson: change—even incremental change—demands disciplined testing, clear rollback plans, and prioritized remediation of legacy dependencies. Download the ISOs, inventory your scripts, update your firmware, and treat AI features as accelerators, not answers. The window for preparation is open now; it won’t stay open indefinitely.