Windows 11 2025 Settings Refresh: AI Help, QMR Recovery, and Panel Migration

Microsoft’s 2025 refresh of the Windows 11 Settings app is more than a cosmetic tidy‑up — it’s a deliberate consolidation of legacy controls, new AI‑powered helpers, and a long list of practical features that close long‑standing gaps with Control Panel while adding modern, cloud‑assisted recovery and privacy controls aimed at both consumers and IT teams.

Background / Overview​

Microsoft delivered most of the Settings improvements across servicing updates for Windows 11 version 24H2 and then activated the broader, packaged experience as part of the 25H2 enablement model. That enablement approach means the same binaries can appear on both servicing branches and Microsoft can gate activation by hardware, region, or licensing — which explains why some 24H2 systems already show 25H2 features before a labeled 25H2 upgrade completes.
The changes landing in 2025 fall into three useful buckets: (1) interface and discoverability refinements that make Settings easier to navigate, (2) new user‑facing controls (passkeys, lock‑screen widgets, taskbar and clock toggles), and (3) functional platform additions like Quick Machine Recovery (QMR) and enhanced Recall privacy/export controls — plus an on‑device AI assistant that helps you find and apply settings. Community testing and early coverage have documented the staged rollout and gating strategy in detail.

---

What changed — the quick list​

• New Advanced page replaces the old For Developers area and consolidates advanced system controls.
• AI agent in Settings (Settings Mu) — natural‑language search and task automation on Copilot+ PCs.
• Quick Machine Recovery (QMR) — cloud‑assisted recovery in WinRE that can download targeted remediations.
• Windows Recall: reset and export options, and a shorter default retention window for snapshots on Copilot+ devices.
• Passkey integration with third‑party providers (e.g., 1Password) to use external managers with Windows Hello.
• Notification Center full clock — option to show a full clock including seconds in the Notification Center.
• Lock Screen widgets management, smaller taskbar buttons, Copilot key remapping, and a host of Control Panel → Settings migrations (mouse, time & language, default apps in EEA, HDR controls).

This catalogue reflects the features Microsoft staged in 24H2 and made broadly available (or gated) across 24H2/25H2 devices in 2025. Early previews and technical documentation produced by Microsoft and independent outlets confirm the items above.

---

Deep dive: the Settings redesign and Advanced page​

What Microsoft changed visually​

The Settings app has gotten a tidier, more centralized layout in several places. The search box moved from the left pane to the top center of the window, which better matches users’ expectations for a global search bar and supports the new AI agent’s conversational prompts. The “For Developers” page has been replaced by an “Advanced” page under Settings → System; the new page groups developer and advanced OS controls (including version control options for File Explorer) into sections that are easier to scan.

Why this matters​

Consolidation reduces cognitive switching. Rather than hunting across multiple legacy pages (Control Panel, scattered Settings subpages), Settings is moving toward a single discoverable surface where advanced options, search, and machine‑assisted help live together. That helps both regular users and IT pros pin down relevant switches quickly — especially when paired with the new agent.

---

The AI agent in Settings: what it is and how it works​

Settings Mu — the small, local model for configuration tasks​

Microsoft shipped an on‑device Settings agent — often referred to in early coverage as Settings Mu — that uses a lightweight model optimized for on‑device scenarios. The design intent is explicit: the agent helps you find and, with your explicit approval, apply settings using plain English (for example, “make my pointer larger” or “turn off location for Chrome”). The agent initially appears on Copilot+ certified machines and is subject to geography/language gating.

Capabilities and limits​

• The agent suggests settings and can perform changes only after confirmation. Users can also undo those changes if needed.
• On‑device operation means faster response times and better privacy because conversational processing does not require sending raw queries to the cloud by default.
• Availability is gated by hardware and policy: Copilot+ NPUs and specific builds are required today; Microsoft provides Intune/Group Policy controls to disable the agent in managed environments.

Practical example​

If you type “my screen is too bright when reading at night” the agent should show Night Light and adaptive brightness settings and offer one‑click toggles or a short guided flow to apply them.

---

Quick Machine Recovery (QMR): the most consequential platform change​

What QMR does​

Quick Machine Recovery extends the traditional Windows Recovery Environment (WinRE) with cloud‑assisted remediation. When a device repeatedly fails to boot, QMR can automatically:

• Boot to WinRE.
• Connect to a network.
• Upload diagnostic metadata and check Windows Update for targeted remediation packages.
• Download and apply fixes or remediation scripts and reboot to test success.

Microsoft documents QMR as a “best‑effort” system: it will try cloud remediation first, fall back to local Startup Repair if no fix exists, and retry according to configurable intervals. Test mode lets administrators simulate the flow safely.

Default behavior and manageability​

• On Windows Home, cloud remediation is enabled by default. On Pro, Enterprise and Education, the cloud and auto‑remediation options are disabled by default but can be managed via Intune and CSPs. Administrators can configure networks and retry intervals and even supply Wi‑Fi credentials for use in WinRE.
• QMR exposes a Settings page (System → Recovery → Quick machine recovery) where end users can review and change behavior. Documentation and guidance for organizations include test modes and centralized policy controls for large fleets.

Benefits and trade‑offs​

• Benefit: QMR dramatically reduces the need for physical or full‑image recovery in many widespread outages — an enormous win for home users and help desks.
• Trade‑offs: the feature uploads diagnostic data and connects to Microsoft’s services during recovery, which raises privacy and compliance questions for high‑regulation environments. Microsoft responds to this by offering configuration toggles and by disabling automatic cloud remediation by default on managed SKUs.

---

Windows Recall: reset, export, and retention policy​

What’s new​

Recall — Microsoft’s screenshot‑based task resumption tool — received two important additions in 2025:

• Reset Recall: a Settings option to delete all locally collected Recall data and reset the feature back to off.
• Export snapshots: for devices in the European Economic Area (EEA), Microsoft provides an export flow that encrypts exported snapshots and requires a one‑time export code the user must safeguard.

Retention and policy: the 90‑day detail​

Microsoft’s management policy for Recall snapshots exposes a configurable “maximum storage duration” (30/60/90/180 days or unlimited). Importantly, the administrative policy default value is set to 90 days, and on new Copilot+ PCs Microsoft is using 90 days as the default retention timeframe rather than unlimited. If administrators don’t configure the policy, the OS behavior can vary, but the policy default is explicitly 90 days in Microsoft’s CSP documentation. This means snapshots older than the configured period will be purged automatically.

Privacy and export mechanics​

• Exports are encrypted and require a one‑time export code; Microsoft does not hold the code and cannot help recover it. Exported snapshots are decrypted by third‑party apps using published documentation, and snapshots are output as .jpg (with metadata in .json).
• Microsoft’s enterprise guidance and policy CSPs allow admins to control Recall’s storage and retention — essential for regulated environments.

Caveat and verification​

There is a subtle deployment nuance: older previews behaved differently (unlimited retention until storage limits were reached). Microsoft’s CSP default of 90 days and the note that new Copilot+ machines surface 90 days as default explain the behaviour shift. When auditing or deploying Recall in production, verify the actual default on your target images and check the policy settings in your environment.

---

Authentication changes: passkeys that play nicer with password managers​

One of the more practical changes is third‑party passkey provider support in Settings → Accounts → Passkeys → Advanced options. That means Windows is building integration points so you can use external password managers (for example, 1Password) as a passkey provider alongside Windows Hello when authenticating to web sites and apps that support passkeys. The third‑party app must support passkeys on the device, and you’ll enable integration from an Advanced options page.
Why this matters: passkeys are becoming the dominant passwordless approach, and allowing a popular cross‑platform manager to work with Windows Hello reduces friction for users who want a single passkey store across phones, browsers, and PCs.

---

Usability and Control Panel migration highlights​

Microsoft continued migrating legacy Control Panel functionality into Settings. Notable examples:

• Mouse settings (pointer images, pointer trails, enhanced pointer precision) moved into Settings → Accessibility and Bluetooth & devices.
• Time & language now contains legacy controls like additional clocks in the system tray and time server selection under “Sync now”.
• Default apps behavior in Europe was expanded so the “Set default” flow can assign defaults for protocols and many file types (http, https, .html, .pdf) with optional Taskbar/Start pin during the change.
• HDR controls were made more granular (stream HDR video even when HDR is off, Dolby Vision toggles) and the setting language was refined (“Use HDR”).

These ports reduce the number of dialogs users must leave Settings to find and help IT teams create consistent, modern configuration baselines.

---

Smaller UI tweaks with real impact​

• Notification Center clock: a toggle to show a full clock (including seconds) inside the Notification Center was added to Settings → Time & language → Date & time. This appeared in preview channels and has been documented by multiple outlets and Microsoft docs.
• Taskbar — smaller icons: a new “Show smaller taskbar buttons” option allows users to make the taskbar icons smaller under certain conditions (Always / Never / When taskbar is full).
• Copilot key remapping: you can change the hardware Copilot key to trigger Copilot, Search, or even a custom Microsoft Store app.
• Lock screen widgets: Settings now has a Widgets control for the lock screen so you can add/remove or customize which widgets appear at lock.

Each small UX tweak responds to frequent user requests and helps power users tailor the interface.

---

Risks, governance, and IT operational considerations​

Microsoft’s 2025 Settings updates bring clear benefits — but they also add complexity for IT teams and raise a few risks to consider:

• Feature gating and fragmentation: Many features are hardware, region, or license gated (Copilot+ NPUs, Microsoft 365 Copilot entitlements, EEA-specific Recall exports). That means a mixed‑fleet deployment can show inconsistent behavior, complicating helpdesk troubleshooting and training.
• Data and recovery privacy: QMR uploads diagnostics and may download remediation packages during recovery; Recall collects snapshots and can export encrypted records. IT should plan policy settings for data retention and confirm whether QMR is acceptable under organizational privacy regimes before enabling cloud remediation on managed devices.
• Legacy automation fallout: Microsoft removed legacy components (PowerShell 2.0 runtime and WMIC in recent servicing updates). Organizations with scripts or monitoring that rely on those tools must audit and migrate to modern PowerShell or CIM approaches before broad deployment.
• Operational surprises with enablement packages: Because 25H2 largely flips staged features on top of 24H2 with a small enablement package, administrators must treat the update as a configuration change that may change support lifecycles and require re‑validation of imaging processes.

---

Practical checks and quick how‑tos for users and admins​

• How to verify you have the agent in Settings:
• Open Settings and look for a centered search box that accepts plain language. On Copilot+ machines the agent will be available; Intune admins can control the experience with the Windows AI policy.
• How to check and configure Quick Machine Recovery:
• Go to Settings → System → Recovery → Quick machine recovery. For admin management use the RemoteRemediation CSP or the Intune Settings catalog. You can also enter test mode with reagentc.exe /SetRecoveryTestmode.
• How to export or reset Recall (EEA export workflow):
• Settings → Privacy & security → Recall & snapshots → Advanced settings to export past snapshots or to reset Recall. The export flow generates an export code that you must keep safe — Microsoft cannot recover it for you.
• How to enable the Notification Center clock:
• Settings → Time & language → Date & time → “Show time in Notification Center”. If the toggle isn’t present in preview builds, some outlets documented using ViveTool to toggle experimental flags, but production systems should rely on official updates.

---

Final assessment — strengths and the notable unknowns​

Strengths

• Thoughtful consolidation: Migrating Control Panel features into Settings and cleaning up discoverability is long overdue and makes everyday configuration easier for most users.
• Operational resiliency: QMR is a major step forward for endpoint self‑healing and will reduce recovery effort in many scenarios.
• Privacy mechanics for Recall: export encryption, user‑initiated exports, and reset options give users explicit control — a necessary response to earlier security scrutiny.

Potential risks and unknowns

• Gating fragmentation means features will appear unevenly across fleets and users; expect varying user experiences depending on hardware and licensing.
• Telemetry and recovery data flows: QMR and parts of the AI experience upload diagnostic or usage data; organizations must assess compliance impact.
• Migration load for legacy automation: removal of PSv2 and WMIC requires proactive auditing for enterprises.

The Settings refresh is an incremental but meaningful step: Microsoft has prioritized practical polish, improved recoverability, and added guarded AI assistive features without forcing a radical UX change. For consumers, the improvements are mostly quality‑of‑life; for IT teams, the changes are operational and require careful validation.

---

Conclusion​

Windows 11’s 2025 Settings updates deliver a more coherent configuration experience and introduce platform changes that matter in real deployments — Quick Machine Recovery for resilience, Recall controls for privacy and portability, and a local Settings AI to shorten the path from want to change. The rollout strategy — shipping binaries in servicing updates and flipping features on by policy or entitlement — reduces upgrade friction but increases the importance of testing and governance.
Administrators should validate QMR and Recall policies in lab rings, audit for legacy script dependencies (PowerShell 2.0, WMIC), and document how feature gates and licensing will affect support. Regular users will see tangible wins: clearer Settings navigation, better lock‑screen widgets, a full Notification Center clock, and the ability to keep passkeys in third‑party managers while continuing to use Windows Hello.
These are not experimental gimmicks — they are practical changes aimed at smoothing Windows for everyday tasks while preparing the platform for broader, responsible AI integration.

---

Source: Windows Central Windows 11 update brings smarter, cleaner Settings app