Windows 11’s latest Beta preview, delivered as
KB5074157 (Build 26220.7653), is a compact but meaningful update that blends UI modernization, practical format support, and a broad set of stability fixes — while keeping a handful of notable known issues active for testers and IT professionals to evaluate. The package surfaces
WinUI-based Account Settings dialogs,
.webp desktop wallpaper support, and
faster Copilot prompt suggestions in Click to Do for eligible devices, and also addresses taskbar, Start menu and Settings reliability problems exposed in recent Insider flights.
Background / Overview
Microsoft is shipping this preview as part of the Windows 11 25H2 preview stream (the 26220.* build family) and is using the enablement-package / Controlled Feature Rollout model: the cumulative binaries are broadly distributed, while visible features are gated and gradually turned on per device, account, or telemetry signals. That means installing KB5074157 applies the update to your device, but the new UI or Copilot behaviors may not appear until Microsoft enables them for your machine.
The flight is targeted at Insiders in the
Beta Channel and represents the usual trade-off for preview builds: closer-to-final polish for day‑to‑day flows along with a non-zero risk of preview regressions. Microsoft lists active known issues that make this unsuitable for production rollouts without prior validation.
What’s new in KB5074157 — Quick inventory
- Modernized Account Settings dialogs rebuilt with WinUI 3, including the Add account, Change account type and Account info flows; dialogs now respect Light/Dark theme modes.
- Click to Do (Copilot integration) prompt suggestions now load instantly for Copilot+ eligible devices, reducing latency in quick prompt workflows (regional and entitlement gating applies).
- Desktop background support for .webp raster images — users can set .webp files as wallpapers without third‑party converters.
- A set of reliability and usability fixes affecting the Taskbar, Start menu, Notification Center, Quick Settings, Settings app crashes, Bluetooth battery reporting, and a number of smaller UX regressions.
Each of these changes is modest on its own, but together they reflect a broader, incremental effort to unify Windows UI and evolve integrations with Copilot-era experiences.
Modern Account Settings UI: what changed and why it matters
The technical change
Microsoft has reimplemented several small but high-frequency dialog surfaces in Settings > Accounts > Other users using
WinUI 3. The updated dialogs use modern spacing, typography, and theme-aware controls, and present a system-modal sheet-style flow that matches other modern Settings pages. These updates explicitly aim to eliminate visual jank where legacy XAML or Win32 fragments previously produced inconsistent light/dark behavior.
Practical benefits
- Visual consistency: The dialogs now match the rest of Settings, reducing cognitive friction when admins or end users add accounts or change account types.
- Dark mode parity: No more bright legacy dialogs on a dark desktop; this reduces eye strain and improves the perceived polish of the OS.
- Accessibility improvements (potential): Modern WinUI controls typically expose more reliable semantic roles for screen readers and predictable keyboard focus behavior — although validation is still required.
Caveats and enterprise considerations
- Phased rollout and device gating: Not every Insider or device will see the new dialogs immediately; some are targeted based on device configuration, account type (work/school vs personal), or Microsoft’s rollout flags. This variability complicates helpdesk scripts and UI automation test reproducibility.
- UI automation and management tools: Scripts that rely on window class names, exact dialog titles, or legacy UI element hierarchies may fail and require updates. IT teams should validate RPA jobs, accessibility automation, and management tooling against the preview build.
- Localization risk: Early preview flights sometimes lag in localized strings; organizations using non-English language packs should spot‑check these dialogs.
Click to Do and Copilot prompt improvements: speed, gating, and privacy
What Microsoft changed
Click to Do’s Copilot prompt suggestions now render
instantly on eligible Copilot+ devices, trimming latency and making short, contextual actions feel immediate. This is implemented as a staged, entitlement‑gated experience that favors devices with on‑device inference capabilities and higher NPU performance. The rollout initially excludes certain regions (notably the EEA and China).
Why the improvement matters
Faster prompt suggestions convert Click to Do from a “nice to have” into a genuine productivity shortcut for tasks like summarization, translation, and small content extraction. When prompts are handled locally on a Copilot+ PC, latency drops and privacy posture improves because sensitive content can be processed on-device instead of immediately round-tripping to cloud services.
Important limits and cautions
- Regional and entitlement exclusions: Organizations in the EEA or China — and some global customers by virtue of entitlements — should not assume parity of behavior across their fleet. This has implications for training and demos.
- Hybrid on-device/cloud model: Non‑Copilot+ devices will still fall back to cloud processing for certain prompt types; this hybrid model means DLP, telemetry, and network policies should be reassessed. Admins must treat Copilot surfaces as data flow changes, not just UX tweaks.
- Privacy operationalization: Before enabling Copilot surfaces broadly, test Click to Do workflows with sanitized content and validate that telemetry, firewall rules, and endpoint DLP policies capture or block flows as intended.
.webp wallpaper support: small feature, measurable benefits
What changed
Windows 11 now accepts
.webp raster images as desktop backgrounds directly from Settings > Personalization > Desktop Background, eliminating the need for third‑party conversion for web-sourced wallpapers.
Why it matters
- Storage and distribution efficiency: WebP often delivers smaller file sizes at comparable visual quality to JPEG or PNG, which matters for large-scale deployments and for devices with limited storage or constrained update pipelines.
- User convenience: Users who download images from modern websites no longer need to convert them before setting a wallpaper.
Compatibility notes and enterprise impact
- Wallpaper automation: Organization scripts or MDM policies that set wallpaper images should be validated to ensure they accept .webp files; legacy tooling might assume JPG/PNG/BMP only.
- Third‑party wallpaper managers: Some managers and centralized imaging tools may need updates to treat WebP as a supported asset type. Test these before deploying at scale.
Reliability fixes and known issues — what’s been addressed, and what still needs work
Key fixes included in KB5074157
- Taskbar autohide: Resolved an issue where the taskbar could appear prematurely when set to autohide.
- Start menu: Memory leak mitigations and fixes for Start/Notification/Quick Settings not opening via click in some scenarios.
- Settings app crashes: Fixed crashes when interacting with audio devices.
- Bluetooth battery reporting: Restored battery level reporting for affected Bluetooth devices.
- Explorer/login: Fixes for explorer.exe hanging during first login in specific startup app configurations and a login password icon blanking issue.
These fixes address everyday reliability problems that had been eroding user confidence in recent Insider builds.
Known issues you should test for
Microsoft’s release notes (and community reports) highlight active problems that make this build unsuitable for certain production scenarios without validation:
- Secondary-monitor black-screen: An active investigation into black screens on some secondary displays remains open; multi‑monitor setups should be thoroughly tested.
- Taskbar/System Tray visibility: Some apps may not appear in the system tray as expected. This affects tray-dependent utilities and background apps.
- Xbox Full Screen Experience (FSE) quirks: Titles or utilities that expect fixed window sizes may behave unexpectedly in the new FSE shell. Validate gaming and controller-first scenarios carefully.
Risk analysis: strengths, operational risks, and mitigations
Strengths
- Targeted, low-risk UX polish: Moving frequently used dialogs to WinUI reduces fragmentation and is unlikely to introduce large attack surfaces; it’s a high-return polish for end users and admins.
- Performance & privacy benefits for Copilot: Localized Copilot inference on Copilot+ devices can shorten latency and reduce cloud exposure for sensitive prompts.
- Practical feature additions: WebP wallpaper support and multiple bug fixes improve day-to-day usability and reduce friction for common tasks.
Operational risks and trade-offs
- Fragmented experience across fleets: Controlled Feature Rollouts and entitlement gating mean identical images may behave differently across otherwise identical machines, complicating support and documentation. This remains the single largest operational headache for pilots and IT teams.
- Automation and accessibility regressions: UI migrations can break automation, RPA, and accessibility tooling that depend on legacy element IDs or window classes; these must be revalidated.
- Preview instability for multi‑monitor and tray scenarios: Known issues affecting secondary displays and tray app visibility make this preview unsuitable for production multi‑monitor setups until fixes land.
Mitigation checklist for IT and power users
- Create a dedicated Pilot ring with a mix of hardware and regional configurations.
- Capture full system backups or images before installing preview builds.
- Validate UI automation and RPA scripts against the build; update selectors and identifiers as needed.
- Test multi‑monitor setups, system tray apps, and any peripheral workflows that touch the taskbar or FSE.
- Sanitize data when testing Copilot/Click to Do workflows and review DLP telemetry to ensure no unintended exfiltration.
How to get KB5074157 and practical testing steps
- Enroll in the Windows Insider Beta Channel via Settings > Windows Update > Windows Insider Program.
- To increase the chance of receiving gated features quickly, enable “Get the latest updates as soon as they are available” in the Insider Program page. Remember that this only increases rollout probability — features are still controlled by server‑side flags and entitlements.
- After updating, confirm the build number in Settings > System > About or by running winver; the preview is associated with Build 26220.7653 (KB5074157). Validate visible behaviors (Account dialogs, wallpaper options, Click to Do latency) and run the checklist in the previous section.
Editorial assessment: incremental progress, not seismic change
KB5074157 is emblematic of Microsoft’s current cadence: iterative, pragmatic improvements delivered as preview updates while the company continues to gate broader experiences through enablement flags and entitlement checks. The
WinUI rework of Account Settings dialogs is a quiet but essential quality-of-life improvement that moves Windows toward a consistent, modern visual language. The
.webp wallpaper support is a welcome convenience for modern image workflows and enterprise imaging pipelines. Faster Copilot prompts on Copilot+ devices demonstrate tangible wins from the on‑device inference strategy — but those wins are constrained by regional exclusions and hardware entitlements.
From an IT management perspective, the preview’s most significant cost is operational: the fragmentation caused by phased rollouts and the lingering multi‑monitor/tray issues. For testers and enthusiasts, the build is worth installing on a dedicated test device; for production fleets the prudent approach remains: validate in a pilot ring, update automation and accessibility tests, and wait for the fixes that close the documented known issues before broader deployment.
Recommendations — a concise action plan for admins and power users
- If you are an Insider tester: install KB5074157 on a non‑production device, enable the Insider faster toggle if you want earlier gating, then exercise account flows, Click to Do prompts, wallpaper settings, and multi‑monitor scenarios. File structured feedback via the Feedback Hub for any regressions.
- If you are an IT admin evaluating 25H2: create a pilot ring representing typical endpoints, backup images, and sanity-check management tooling (Intune, Group Policy, RPA scripts) against WinUI dialog changes. Delay broad rollouts until the multi‑monitor and system tray issues are resolved.
- If you rely on Copilot interactions for regulated data: test Click to Do behavior in a controlled environment, confirm whether prompts are processed locally or in the cloud for your hardware and region, and update DLP policies accordingly.
KB5074157 is a compact preview with sensible, user-facing polish and a cluster of pragmatic fixes — the kind of iterative work that quietly improves day-to-day Windows use. The update’s real-world value will depend on rollout timing, device entitlements, and how quickly Microsoft addresses the remaining display and tray regressions. For Insiders and early adopters it’s a worthwhile preview to test; for production fleets it’s a reminder to validate UI-dependent tooling and multi-monitor behavior before adopting preview builds at scale.
Source: Windows Report
https://windowsreport.com/windows-1...count-settings-ui-and-webp-wallpaper-support/
Source: Windows Report
https://windowsreport.com/kb5074157-beta-preview-fixes-taskbar-start-menu-more-in-windows-11-25h2/