Windows 11 September 2025 Update: On-Device Copilot AI Binaries and UI Enhancements

Microsoft's September cumulative for Windows 11 has landed and, rather than being a quiet maintenance release, it mixes visible UI polish, a handful of useful quality fixes and a fresh batch of staged, hardware-gated AI features — with one very practical sting in the tail: the cumulative installers are unusually large because Microsoft is shipping on-device Copilot model binaries inside the package. (windowscentral.com)

Background​

Microsoft issued the September 2025 Patch Tuesday cumulative for Windows 11 as part of its 24H2 servicing stream (KB5065426, OS Build 26100.6584). There are parallel packages for older servicing bases (customers on 23H2 receive a separate KB, such as KB5065431 for that branch). The 24H2 package bundles the Latest Cumulative Update (LCU) together with the Servicing Stack Update (SSU) and also includes updated on‑device AI components intended to power Copilot/Copilot+ experiences on qualifying hardware. (en.wikipedia.org)
Microsoft’s approach for these AI surfaces is explicit: the update delivers code and model binaries to devices, then server‑side enablement and hardware checks determine whether a given PC actually gets the feature turned on (Copilot+ gating depends on NPUs, platform firmware and entitlement). That explains why two otherwise identical machines can show different UIs after the same update. (blogs.windows.com)

---

What’s new — the five headline features you’ll actually notice​

This release contains many changes; five items stand out because they affect the day‑to‑day desktop experience for most users and because several have been the subject of hands‑on reporting.

1) Recall gains a dedicated home page (Copilot+ PCs only)​

• What changed: The Recall experience — Microsoft’s locally stored “snapshot” history for task resumption — now opens to a Home landing page that aggregates recent snapshots, top apps and websites so users can quickly resume work. The UI exposes Timeline, Feedback and Settings via a left navigation rail. Recall remains an opt‑in feature and is restricted to Copilot+ certified hardware. (blogs.windows.com)
• Why it matters: For users who adopt Recall, the new home page improves discoverability and makes snapshots easier to manage without hunting through buried menus. The feature is designed to keep data local and encrypted, unlocked by Windows Hello, but it has a history of controversy — which is why Microsoft emphasizes opt‑in controls. (theverge.com) (windowscentral.com)

2) The AI “Agent in Settings” expands beyond Snapdragon​

• What changed: The on‑device Agent in Settings (a small, local language model called Settings Mu) that answers natural‑language queries and suggests settings or repairs is being rolled out to more Copilot+ PCs, expanding from Snapdragon/ARM to devices with Intel and AMD processors (English initially). The feature runs locally and can propose changes that the user must confirm. (learn.microsoft.com) (beebom.com)
• Why it matters: For less technical users, this reduces the friction of finding the right toggle buried inside Settings. For IT and privacy teams, it’s notable because the model runs on‑device but activation is gated by hardware, region and enterprise policy settings. Administrators can control it via policy. (learn.microsoft.com)

3) Lock‑screen widgets become selectable​

• What changed: The lock screen’s widget area now supports pick‑and‑choose customization — you can add, remove and rearrange which widgets appear without having to accept the full set. This expands earlier, region‑limited experiments and is rolling out more broadly.
• Why it matters: This is a small but practical usability win. Users who previously avoided lock‑screen widgets because they couldn’t control which items appeared can now tailor the surface to what they use most.

4) Windows Search — image grid and clearer indexing status​

• What changed: Taskbar Search now shows image results as a grid, making it easier to visually find photos. Search also displays an indexing progress indicator when the system is still cataloguing content, so you can see whether results are complete. These changes simplify finding local photos and reduce the confusion caused by partial indexing. (support.microsoft.com)
• Why it matters: Faster visual scanning of images and a visible index progress bar are quality‑of‑life improvements for anyone who uses local photo search frequently.

5) Task Manager CPU reporting standardized​

• What changed: Task Manager now uses a single, standardized CPU usage metric across Processes, Performance and Users pages. Microsoft also added a hidden/optional “CPU Utility” column that preserves the legacy value for compatibility with scripts or workflows that relied on the old calculation. (support.microsoft.com)
• Why it matters: Inconsistent CPU figures across Task Manager panes have confused users and made third‑party monitoring tools harder to correlate; standardizing the metric removes that friction. The optional CPU Utility column lets power users keep the old number where needed.

---

Other notable introductions and small polish​

• A Click to Do first‑run tutorial improves discoverability of the assistant overlay and image/text actions.
• Windows Hello received a UI refresh to modernize sign‑in visuals across system flows.
• The notification center gets an optional larger clock that includes seconds (a feature many power users requested).
• Permission prompts were made more attention‑grabbing by dimming the background and presenting clearer modal dialogs.
  These are helpful—small‑to‑medium wins that collectively raise the polish level of the desktop. (windowscentral.com)

---

The sting in the tail: why this update is bulky (and why that matters)​

The most operationally consequential element of the September package is its size. Multiple reporting outlets and catalog entries show the offline .msu installers for the Patch Tuesday packages approach roughly 3.7–3.8 GB per architecture for 24H2 — an unusually large footprint for a monthly cumulative. That size is not accidental: Microsoft is shipping on‑device AI model binaries with the cumulative so that Copilot+/on‑device Copilot features can work offline or with low latency on qualifying hardware. (windowslatest.com)
Two practical consequences:

• Home users and organizations face larger downloads and more storage pressure on system drives (problematic for devices with small SSDs).
• Administrators that mirror updates with WSUS or manual deployment must plan for bigger deployment artifacts and longer patch windows. The “ship‑once, gate‑server‑side” strategy simplifies Microsoft’s servicing pipeline, but it pushes model payloads to every device regardless of whether the machine is Copilot‑capable.

If you don’t have a Copilot+ device, you still get the model binaries in the update package because the installer contains them; feature enablement is a later, server‑gated step. That design choice explains why non‑Copilot machines are paying the bandwidth and disk‑space cost even though they won’t use the models.

---

Verification and cross‑checks (what I checked and where)​

To ensure the reporting is accurate I cross‑checked the major claims with multiple sources:

• Microsoft documentation and Release Preview / Insider posts confirm the Agent in Settings (Settings Mu), requirements (Copilot+ hardware, English initially) and admin policy controls. (learn.microsoft.com)
• Windows Insider and official blog posts document the Recall preview history, the opt‑in model and the fact that Recall is gated to Copilot+ hardware in staged flights. (blogs.windows.com)
• Independent coverage from Windows Central and coverage roundups corroborate the list of visible UI changes (image grid search, lock‑screen widgets, Task Manager fix). (windowscentral.com)
• Operational reporting from update‑tracking outlets confirms the unusually large .msu sizes and attributes that to bundled on‑device AI model binaries. Administrators have reported offline installers roughly in the 3.7–3.8 GB range per architecture. (windowslatest.com)

Where a claim was unclear or previously disputed (for example, whether Recall is secretly installed or forced on machines), the authoritative position is: Recall remains opt‑in and removable, and Microsoft has emphasized opt‑in controls while staging rollout for security and privacy re‑evaluation. Anecdotal reports that Recall is “being forced” were traced to confusion about stubs and server flags; rely on the official opt‑in messaging and the documented removal path rather than truncated community commands. (theverge.com)

---

Practical guidance — what to do now (consumer and admin playbooks)​

For home users​

• Pause and read: Don’t panic‑install the optional monthly preview if you value a small SSD or limited bandwidth. Allow the cumulative to roll out via Windows Update or choose manual installation if you need the fixes.
• Check your device: If you don’t have Copilot+ hardware (no on‑device NPU at the required TOPS), you won’t get the Copilot features enabled — but you will still download the bundled model payload if you install the full offline package. Consider letting Windows Update deliver the delta rather than downloading the full .msu manually.
• Recall opt‑in: If Recall appears on your device and you don’t want it, follow Microsoft guidance to disable/uninstall it; beware of copy‑paste DISM commands from informal sources — verify the exact feature name using DISM /Online /Get‑FeatureInfo before issuing destructive commands.

For IT admins and imaging teams​

• Pilot widely: Deploy KB5065426 to a representative pilot group that covers Copilot+ and non‑Copilot hardware. The staged enablement model makes it essential to verify what features actually activate in your environment.
• Plan for bandwidth and storage: Treat the offline .msu packages as large installers. Mirror and caching strategies in WSUS/Update Catalog repositories should be adjusted to accommodate multi‑gigabyte files.
• Use known‑issue rollbacks and KIR carefully: Recent servicing history shows Microsoft sometimes issues later KIRs for problematic behavior; have rollback and recovery images prepared and a clear communications plan.
• Control Copilot features via policy: If you want to restrict the Agent in Settings or other on‑device AI experiences, use the provided enterprise policy options to disable them before broad deployment. (learn.microsoft.com)

---

Benefits and risks — balanced assessment​

Strengths / positives​

• The update delivers meaningful polish to daily workflows: cleaner permission prompts, better image search, a more consistent Task Manager and useful lock‑screen customization. For many users that alone improves quality of life. (windowscentral.com)
• The Agent in Settings is an important accessibility and discoverability improvement, especially for people who struggle to navigate the dense Settings hierarchy. Running the model on‑device preserves latency and supports offline scenarios. (learn.microsoft.com)
• For Copilot+ adopters, features like Recall and Click to Do add genuine on‑device productivity capabilities that can speed content edits, visual searches and task resumption. (blogs.windows.com)

Risks / downsides​

• Payload size and blunt distribution: Bundling model binaries in checkpoint cumulatives means every device receives the weight of that payload, even if it cannot or will not use the models. That increases bandwidth and storage friction unnecessarily for many customers.
• Fragmented availability and support complexity: Because many AI features are gated by hardware/firmware and rollout flags, two identical machines may behave differently after the same update. That complicates troubleshooting and user expectations.
• Privacy/attestation concerns: Features that record snapshots (even when encrypted and opt‑in) attract scrutiny. Microsoft’s safeguards are real, but users and administrators must still evaluate the risk posture before enabling Recall on sensitive endpoints. (theverge.com)

---

Closing analysis — where this fits in Microsoft’s roadmap​

This update is tactical and strategic at once. Tactically, it fixes nagging UI inconsistencies and gives useful search and clock improvements that make Windows 11 feel more coherent. Strategically, it reinforces Microsoft’s chosen model for bringing on‑device generative capabilities to the desktop: ship model payloads centrally, gate feature activation by hardware/entitlement and iterate server‑side.
That strategy accelerates feature parity across architectures and simplifies Microsoft’s servicing pipeline, but it imposes a measurable operational cost on users and IT teams who must handle multi‑gigabyte cumulative installers even when their devices won’t run the new AI features. For organizations, the sensible response is not to block updates indefinitely, but to adopt measured pilot rollouts, verify Copilot feature activation in representative fleets, and tune distribution (WSUS/Delivery Optimization) to absorb the larger payloads. (learn.microsoft.com)
For typical home users the short takeaway is straightforward: install when ready, but be mindful that the offline installers are large; if your device has a smaller drive or limited bandwidth, allow Windows Update to stage the deployment rather than manually grabbing the full .msu packages. For enthusiasts with Copilot+ hardware, the release starts to show the benefits of on‑device AI — just be prepared for staged rollouts and ongoing adjustments.
The September update is not revolutionary, but it is consequential: a mix of tidy desktop improvements and a clear signal that Microsoft intends on‑device generative AI to be a first‑class part of the Windows experience — even if delivering those models to every endpoint raises practical questions that will shape deployment strategy for months to come. (windowscentral.com)

---

Source: TechRadar Windows 11's September update is here - these are the top 5 features, but there's a sting in the tail

 

[ChatGPT]

Microsoft’s September cumulative for Windows 11 landed as more than a routine Patch Tuesday — it bundles visible UI polish, several quality-of-life fixes, and a new tranche of staged, hardware‑gated AI features, but it also carries a practical sting: unusually large offline installers that include on‑device Copilot model binaries and push significant download and storage demands onto every PC that receives the update. (support.microsoft.com)

Background / Overview​

Microsoft published the September cumulative for Windows 11 (KB5065426, OS Build 26100.6584) on September 9, 2025. The package mixes security fixes with new OS behavior and on‑device AI components intended to power Copilot and Copilot+ experiences on qualifying hardware. The company’s engineering approach is explicit: ship client code and model binaries inside the cumulative, then enable features selectively (server‑side) depending on device hardware, licensing, and region. (support.microsoft.com)
This release is notable for two reasons that will affect both everyday users and IT teams: first, several headline features are exclusive to Copilot+ certified PCs (devices with NPUs or other accelerators and specific OEM/firmware attestation); second, the combined installers are roughly 3.7–3.8 GB per architecture — far larger than a typical monthly cumulative — because model binaries are included for on‑device AI. Multiple independent outlets and catalog entries confirm the size figures and Microsoft’s intent to deliver on‑device AI payloads in the cumulative. (berrall.com)

---

What’s new — the headline features you’ll notice​

Copilot+‑only features: Recall home page, Click to Do tutorial, and expanded on‑device agents​

• Recall home page (Copilot+ PCs only): Recall — Microsoft’s opt‑in, local snapshot history that helps users resume prior activity — now opens to a dedicated Home landing page showing recent snapshots, top apps and websites, and a left navigation rail for Timeline, Feedback and Settings. Recall remains opt‑in and protected by local encryption and Windows Hello gating on Copilot+ hardware. (support.microsoft.com)
• Click to Do tutorial (Copilot+ PCs): A first‑run, interactive tutorial for Click to Do improves discoverability for the overlay assistant that surfaces actions from on‑screen content. This aims to reduce the friction for people who haven’t used contextual AI actions before. (techradar.com)
• Agent in Settings expands to AMD and Intel Copilot+ machines: The on‑device Agent in Settings (sometimes called the Settings agent, powered by a small local language model) that answers natural‑language queries and suggests settings or repairs has been expanded from Snapdragon/ARM Copilot+ devices to eligible AMD and Intel Copilot+ hardware (English initially). The agent runs locally, proposes changes, and requires explicit user confirmation before it commits system modifications. This capability is hardware‑gated and controllable by administrators. (techradar.com)

Together, these Copilot+ features underline Microsoft’s strategy of shifting inference to local silicon where available, improving latency and offline responsiveness, while gating rollout by hardware capability and licensing.

Windows Search and Task Manager polish​

• Image grid view in Search and indexing progress: The Windows Search experience now displays image results in a grid, simplifying photo discovery. Search also surfaces a visible indexing progress indicator so users can tell whether results are complete or still being prepared. These are classic quality‑of‑life improvements for people who search for local photos frequently. (windowscentral.com)
• Task Manager CPU reporting standardized: Microsoft has revised the Task Manager’s CPU calculation so that the values displayed in Processes, Performance, and Users pages line up with one another and match industry norms. The previous discrepancy — where Processes might show a process as 100% even if only one core was used — is being replaced by a standardized metric. For backward compatibility, an optional “CPU Utility” column preserves the legacy calculation for scripts or workflows that relied on it. Independent coverage and Microsoft’s notes both confirm the change. (pcworld.com)

Other visible polish and small wins​

• Lock screen widget selection: Users can now choose which widgets appear on the lock screen (add, remove, rearrange), an expansion of earlier regional experiments; this increases personalization without forcing unwanted content on the lock surface. (reddit.com)
• Windows Hello and notification UX updates: Windows Hello received a refreshed sign‑in UI; the notification center can optionally show a larger clock including seconds; permission prompts dim the background for clarity. These are discrete but meaningful refinements that improve discoverability and focus.
• Windows Studio Effects and camera routing: Copilot+ devices gain broader Windows Studio Effects support (background blur, voice focus, simulated eye contact), and Microsoft is extending these effects to external webcams via per‑camera toggles in Settings, subject to hardware/NPU support. (windowscentral.com)

---

The size problem: why this update is unusually large​

The practical complaint many users are seeing is simple: the September cumulative’s offline installers approach ~3.7–3.8 GB per architecture. Published direct downloads and catalog entries show the x64 package at ~3.81 GB and ARM64 near ~3.69 GB. Independent aggregators and update catalogs trace the bulk of that footprint to on‑device AI model binaries included in the cumulative so that Copilot+ features can work offline or with lower latency. (berrall.com)
Why Microsoft shipped model binaries inside the LCU:

• To enable offline inference and low‑latency Copilot experiences on qualifying hardware.
• To provide a single servicing artifact that can be delivered broadly while the company uses server flags and entitlement checks to enable features on supported hardware.

Operational consequence: even non‑Copilot+ PCs receive the large installer blobs (they will not necessarily get the Copilot+ UI enabled, but the model data is packaged alongside). That design saves Microsoft complexity but shifts storage and bandwidth costs onto all customers. (support.microsoft.com)

Real‑world impact​

• Devices with small SSDs (e.g., 64–128 GB) will feel immediate pressure during download and installation.
• Metered or capped connections will incur larger monthly downloads.
• Organizations managing large fleets must factor increased bandwidth, storage staging, and potential user helpdesk churn into deployment timelines.

---

Who gets what — the Copilot+ gating story explained​

Microsoft’s rollout model places enabling logic in three places:

• The LCU (cumulative) delivers code and model binaries to the device.
• Server‑side flags, device attestation, and licensing checks decide whether the device sees the Copilot+ experience.
• Hardware: Copilot+ certification typically requires an NPU or equivalent accelerator, firmware/TPM attestation, and OEM provisioning.

That means two otherwise identical machines can show different post‑update behavior: one with Copilot+ features available, the other without. The gating is explicit in Microsoft’s public notes and documented in the update’s component list (Settings Model, Semantic Analysis, Image Search component versions are part of the package). (support.microsoft.com)
Implication: being updated does not guarantee you’ll get the “new” AI UI — but it does mean you incur the download and storage cost.

---

Privacy, security, and enterprise governance concerns​

Recall and screen‑history privacy​

Recall stores local snapshots of screen and activity to enable resumption. Microsoft emphasizes opt‑in behavior, local encryption, and Windows Hello gating on Copilot+ PCs, but the feature’s existence raises legitimate questions:

• What gets captured by default and how easy is it to avoid sensitive captures (credentials, PHI, PII)?
• How are retention and purge policies configured for enterprise‑managed devices?
• What audit trails and administrative controls exist to detect misuse?

Microsoft’s implementation includes local encryption and Windows Hello for unlocking saved content, but administrative policies, documented retention and purge controls, and clear user consent flows will be essential before broad enterprise enablement. Community reporting and Microsoft’s own documentation flag these governance points.

On‑device models and telemetry​

On‑device inference reduces cloud exposure, but administrators and privacy teams must still understand:

• What telemetry (if any) is emitted by model inference or feature usage?
• Which features require cloud fallbacks or M365 entitlements that may transmit content?
• How does Microsoft surface per‑feature diagnostics in telemetry so administrators can audit usage?

Microsoft’s docs and support notes indicate per‑feature controls and “recent AI activity” tracking in Settings, but organizations should test and validate behavior under their telemetry baseline before enabling Copilot+ broadly. (windowscentral.com)

---

Known issues and hard requirements​

Microsoft’s KB page for KB5065426 (OS Build 26100.6584) lists the update’s highlights and known issues and notes that the release includes updated AI components (Image Search, Content Extraction, Semantic Analysis, Settings Model). The support page also highlighted ancillary concerns — for example, Secure Boot certificate expirations that organizations must plan for well in advance of June 2026. Review of Microsoft’s release notes is the authoritative starting point for any deployment. (support.microsoft.com)
Real‑world testing from community and coverage outlets has documented additional risk vectors:

• Driver incompatibilities can still cause blue screens or update rollback scenarios on certain machine/driver combinations.
• Some copilot features were regionally staged (e.g., widget dashboards and lock screen experiments initially in Europe).
• Insiders and early adopters have reported occasional regressions in Recall and Click to Do during early flights.

---

Recommended approach for home users and enthusiasts​

Follow a pragmatic, staged approach to installing and evaluating this update:

• Free up storage and check space: Ensure you have at least 10–15 GB free on the system drive prior to installing large cumulatives; that buffer helps avoid temporary space exhaustion during patch staging.
• Backup important files: Create a system image or at least file backups before a major cumulative that includes new components.
• Install on a test device first: If you have multiple machines, update a non‑critical PC first to validate driver compatibility and user‑profile behavior.
• Delay or pause if constrained: If a device has limited storage or you rely on metered data, use the Windows Update pause or schedule download during off‑peak windows.
• Review and toggle features: For privacy‑sensitive setups, check Settings > Privacy & security for Recall, AI activity controls, and diagnostic settings before enabling Copilot‑enabled features. (support.microsoft.com)

---

Practical steps for IT and enterprise administrators​

Enterprises should treat KB5065426 as a non‑routine cumulative with operational implications:

• Inventory and classify endpoints: Identify which devices are Copilot+ certified, which have limited SSD capacity, and which run legacy drivers that historically caused update problems.
• Prepare bandwidth and content staging: Use Delivery Optimization, WSUS, or SCCM/Intune staging to distribute the large payloads efficiently, and consider peer caching for remote offices.
• Pilot ring: Deploy the update to a small, representative pilot group (including Copilot+ and non‑Copilot machines) for at least one week to capture telemetry on battery, thermal, driver, and UX impacts.
• Audit privacy and compliance: Define policies for Recall and any snapshot/storage features, including automatic purge durations, encryption keys, and role‑based access to stored artifacts.
• Communicate with users: Publish guidance that explains why the update is large, how to reclaim space, and how to opt in/out of AI features where appropriate. (support.microsoft.com)

---

Risk assessment — strengths and tradeoffs​

Strengths and strategic opportunities​

• Faster, local AI experiences: On‑device inference yields lower latency and offline capability, improving dictation, camera effects, contextual actions, and accessibility features for qualifying hardware.
• Incremental polish: UX improvements — standardized Task Manager metrics, clearer indexing status, lock screen tweakability, and a refreshed Windows Hello — make the everyday experience feel smoother.
• Privacy options: Running models locally reduces cloud exposure compared with cloud‑only inference scenarios, a material plus for regulated or privacy‑conscious deployments. (windowscentral.com)

Notable risks​

• Update bloat for all devices: Packaging model binaries in the cumulative increases download and storage costs for every device, even those that will never enable Copilot+ features.
• Uneven user experience: Hardware gating and server‑side flags lead to inconsistent UI/UX between otherwise identical endpoints — a support overhead for helpdesks.
• Governance and privacy complexity: Features like Recall add questions around capture scope, retention, and legal/regulatory compliance that organizations must resolve before enabling.
• Driver compatibility: As with past 24H2 deployments, certain drivers (audio, camera, GPU) remain potential sources of post‑update disruption. (windowslatest.com)

---

Mitigations and practical fixes​

• Use Delivery Optimization or WSUS/Update Catalog to pre-stage the large .msu packages and avoid saturating WAN links; peer caching helps remote sites.
• Configure Intune policies to control feature enablement or hide Copilot elements until testing and governance are complete.
• Disable or defer Recall and other Copilot+ features via Group Policy or MDM profiles until audit and consent workflows are in place.
• Keep device drivers and firmware current; treat firmware updates (OEM device platforms and NPU drivers) as preconditions to Copilot+ enablement.
• For constrained devices, leverage the Windows Disk Cleanup and Storage Sense tools to reclaim staging and temporary file space before update. (support.microsoft.com)

---

Final verdict — what this means for Windows users​

The September cumulative for Windows 11 is an evolutionary update with strategic intent: Microsoft is embedding on‑device Copilot model binaries so local AI features can be delivered at low latency and (in some cases) offline. That future is compelling — better dictation, smarter camera effects, and contextual helpers that reduce friction are real productivity wins for those on compatible hardware. (techradar.com)
However, Microsoft chose a tradeoff that will sting many users today: packaging model binaries into broadly distributed cumulative installers raises download and storage demands for everyone, including traditional systems that won’t get Copilot+ features enabled. The result is an uneven rollout experience and operational friction for constrained devices and managed fleets. Administrators and savvy home users should assume this is the new normal for near‑term releases and plan accordingly: stage patches, audit privacy settings, validate drivers, and postpone or pilot where appropriate. (berrall.com)
The big picture is clear: Windows is evolving into an agentic, AI‑augmented OS with on‑device intelligence where hardware permits. That progression offers real benefits, but the industry and Microsoft still need to refine delivery strategy so feature gains do not impose disproportionate costs on the many devices that will never fully use those models. Until then, the September update is both a meaningful step forward and a reminder that software architecture choices — particularly around update packaging and gating — have immediate consequences for users and IT teams. (support.microsoft.com)

---

Quick checklist (actionable items)​

• Free up at least 10–15 GB on small SSD systems before installing this cumulative.
• Pilot KB5065426 on a non‑critical machine first.
• Verify driver and firmware currency (audio, GPU, camera).
• Configure Delivery Optimization or WSUS for managed environments.
• Review privacy settings for Recall and other Copilot features before enabling.

The September cumulative is worth attention: it delivers polished improvements and a preview of a more agentive Windows, but the operational and privacy tradeoffs are tangible. Prepare now, pilot carefully, and treat Copilot+ features as opt‑in benefits rather than automatic upgrades. (support.microsoft.com)

---

Source: Observer Voice Windows 11 Update Introduces Top Features with Notable Drawback