Windows 11 Insider Preview Build 26220.7859: CFR rollout, 365 Family prompt, reliability fixes

  • Thread Author
Microsoft has started rolling out Windows 11 Insider Preview Build 26220.7859 (KB5077223) to the Beta Channel, delivering a small but focused set of reliability fixes and a single new account-related suggestion that will be gradually enabled for Insiders who opt in to receive the fastest preview updates. This flight is distributed as an enablement package on top of Windows 11, version 25H2 (Build 26200.x), and continues Microsoft’s pattern of using controlled feature rollouts to surface new experiences to a subset of testers before widening the release. For Windows Insiders, the visible changes in this build are modest — improved system-tray icon behavior, File Explorer stability work, better Nearby Sharing for large files, a Settings reliability fix, and a Microsoft 365 Family subscription upgrade prompt on the Accounts page that can be turned off. What’s notable is the method and messaging: Microsoft is emphasizing incremental quality improvements and experimentation rather than sweeping new features in this Beta-channel flight.

Background / Overview​

Windows Insider Preview builds now frequently arrive as enablement packages that increment a base release’s major build number while keeping the underlying servicing baseline intact. In this case, the Beta Channel flight is distributed on top of Windows 11, version 25H2 using Build 26220.xxxx as the visible build family. That packaging model lets Microsoft toggle features on and off server-side for targeted groups, test compatibility, and deliver feature-enabled builds without the heavier process of a full feature-update install for every device.
Microsoft’s Insider posts for builds in the 26220 family routinely break changes into two buckets: (1) new features or experiences being gradually rolled out to Insiders who have turned on the “Get the latest updates as soon as they’re available” toggle in Settings > Windows Update, and (2) improvements and notable fixes that are rolling out to everyone in the channel. This dual-track disclosure is significant: it signals that some items you see in this blog post might land on your PC immediately only if you’ve opted into the faster preview toggle, while other fixes will appear broadly to Beta Insiders over time.
The Build 26220.7859 announcement follows that pattern. The new Microsoft 365 Family subscription prompt is being introduced as an opt-in server-side experiment for Insiders who have allowed the rapid rollout toggle; reliability fixes are being pushed to the whole Beta cohort in a staggered manner. The release messaging also reiterates that features may never ship beyond Insiders, and some previewed functionality may be incomplete or not fully localized.

What’s included in Build 26220.7859 (KB5077223)​

New (gradual) — Accounts: Microsoft 365 Family upgrade option​

  • Microsoft 365 Family subscribers who are part of the gradual rollout may see an option to upgrade to a different Microsoft 365 plan on the Accounts page in the Settings app.
  • The prompt is surfaced as suggested content inside Settings, and Microsoft has built an explicit opt-out: users can remove the upgrade suggestion by turning off suggested content in Settings.
  • This is a soft commercial nudge rather than a system-level change; it is opt-in via the Controlled Feature Rollout and can be disabled locally if you don’t want promotional suggestions shown in Settings.

Improvements & fixes (rolling out)​

  • Taskbar / System Tray: Improved reliability for showing app icons in the system tray when the taskbar is set to autohide. This resolves a flaky behavior where icons would sometimes not appear immediately after the taskbar was revealed.
  • File Explorer: Addressed an issue where all open File Explorer windows and tabs could unexpectedly jump to Desktop or Home. This fix targets the increasingly common annoyance of window focus or navigation state being lost.
  • Nearby Sharing: Improved the reliability of sending larger files using Nearby Sharing. This should reduce file transfer failures or stalls when moving big media or collections between nearby PCs.
  • Settings: Improved reliability configuring options in Settings > Bluetooth & Devices > Wheel, helping users who customize mouse-wheel behavior or wheel-based gestures avoid configuration errors.

How this is packaged and delivered​

This flight is provided as an enablement package applied to Windows 11, version 25H2. Enablement packages are small updates that flip feature flags to move a device from one build label to another (for example from 26200 to 26220) without replacing the whole OS image. The enablement model allows Microsoft to:
  • Activate new features more quickly for targeted test groups.
  • Reduce install friction compared with a full feature upgrade.
  • Use server-side controls and Controlled Feature Rollout to expand or revoke features dynamically.
For Insiders, that means even tiny builds like 26220.7859 can change which set of previewed capabilities are available on a given device without requiring large downloads or major setup changes.

Controlled Feature Rollout — what it is and why it matters​

Microsoft continues to rely on Controlled Feature Rollout (CFR) technology to stage features. CFR is a deliberate, risk-managed process where features are enabled for a small subset of users initially, then ramped up as telemetry and feedback indicate stability and acceptance.
Key points about CFR for Insiders:
  • If you have the “Get the latest updates as soon as they’re available” toggle ON in Settings > Windows Update, you’ll be in the pool that receives features earlier.
  • Features rolled out via CFR may appear for only a fraction of Insiders at first, and there’s no guaranteed date for wider availability.
  • CFR allows Microsoft to disable a feature quickly if it causes regressions, minimizing exposure compared with a mass release.
This approach protects the broader Insider communities from large-scale regressions, but it also means that what one Insider sees may differ from another’s experience even when both are in the same channel. That inconsistency can be confusing but is an intentional trade-off to accelerate testing while managing risk.

Why these changes matter (and to whom)​

At first glance, Build 26220.7859 appears incremental: a small set of fixes and a non-invasive product-suggestion experiment. But the collection of changes reflects two broader priorities that matter to both end users and IT professionals:
  • Polishing reliability — The taskbar icon, File Explorer, and Settings fixes target everyday UX irritants that erode confidence in the OS. Small reliability wins translate into perceptible quality improvements for daily productivity workflows.
  • Monetization/engagement experiments inside Settings — Surfacing a Microsoft 365 upgrade prompt within the Settings Accounts page extends Microsoft’s ongoing experiment with contextual, product-driven suggestions inside system UI. The presence of a clear opt-out shows Microsoft is attempting to balance product engagement with user control.
Who should care:
  • Windows Insiders and enthusiasts who want to test small feature experiments and help surface regressions should install the build and use Feedback Hub to report issues.
  • IT professionals and admins should be aware of the enablement-package model and CFR behavior when advising Insider participation in managed environments — toggling the preview fast-rollout option could change what features appear on test devices.
  • Everyday users who do not opt into rapid preview rollouts are unlikely to see the Microsoft 365 prompt immediately; they’ll see the broader fixes as they roll out.

Practical guidance: should you install Build 26220.7859?​

If you are an Insider on the Beta Channel, consider these points before installing:
  • Turn the “Get the latest updates as soon as they’re available” toggle ON only if you want to be among the first to see server-side experiments. This toggle increases the chance of early feature exposure — and the chance of encountering early-stage bugs.
  • Back up important data before applying preview builds. Even minor reliability updates can trigger driver or app compatibility issues on certain hardware combinations.
  • If you use your PC for production work, wait until fixes land more broadly. The Beta Channel is more stable than Dev, but controlled rollouts still carry risk.
  • Use Feedback Hub (WIN + F) to report regressions, especially for the fixes listed in the announcement (taskbar behavior, File Explorer jumps, Nearby Sharing issues, Settings Wheel).
Recommended steps to prepare:
  • Create a system restore point and/or full backup.
  • Ensure critical drivers (graphics, storage) are updated to the vendor-recommended versions.
  • Verify you have adequate free disk space and that Windows Update is enabled.
  • If you are in a managed enterprise environment, consult IT policy before enabling rapid preview toggles.

Risks and potential downsides​

Even small preview builds can surface non-obvious problems. Here are realistic risks to consider:
  • Installation failures or rollbacks. Some Insiders in past flights have reported update loops or failed installs. While not ubiquitous, these problems exist and are often hardware- or driver-specific.
  • Driver incompatibilities. Updates that touch underlying platform behavior or enable new flags can expose latent driver bugs, especially with older peripherals or third-party tooling.
  • Inconsistent experience across devices. Controlled rollouts mean features are unevenly distributed. That’s great for experimentation but frustrating if you want a consistent test baseline across multiple machines.
  • Privacy and suggestion UX. The Microsoft 365 upgrade prompt represents a soft commercialization of Settings. While an opt-out is available, some users and administrators object to promotional content appearing in system settings by default.
  • Localization and accessibility gaps. Microsoft specifically calls out that previewed features may be incompletely localized and that some accessibility features may not work across experimental features. For users who rely on localized strings or assistive technologies, that’s an important caveat.
When to avoid installing:
  • If your device runs critical workloads or is managed by enterprise policy, defer installation until the fixes are broadly released.
  • If you have mission-critical peripherals with limited driver support, wait for vendor-certified updates.

The Microsoft 365 prompt: nuance, UX, and controls​

The Microsoft 365 Family upgrade suggestion is worth a closer look because it illustrates how Microsoft is experimenting with commercial prompts within system surfaces.
What the announcement reveals:
  • The prompt will appear on the Accounts page in Settings for Microsoft 365 Family subscribers, offering an option to upgrade to a different 365 plan.
  • The experience is delivered as suggested content and can be disabled by turning off suggested content in Settings.
What this means for users:
  • The prompt is designed to be contextual: Microsoft assumes users with a Family subscription may want to move to a different plan (for example, to switch between Family and Personal or to trial Copilot-enabled tiers).
  • The presence of an opt-out respects user control, but the default state for Insiders in the experiment may be opt-in to suggested content — an important distinction for privacy-minded users.
Points to watch:
  • Whether Microsoft personalizes the suggestion beyond a generic upgrade offer (for example, showing feature differences or compatibility hints).
  • Whether the suggestion integrates billing flows or opens web-based portals when users accept — the in-app direction of those flows is important for user trust.
  • Whether similar suggestions expand into other Settings surfaces over time.

How to report problems and what to include in Feedback Hub​

If you install this build and encounter issues, Microsoft’s Feedback Hub is the primary channel for reporting. Helpful reports accelerate triage and increase the chance of a fix:
  • Reproduce the issue and collect exact steps to reproduce it.
  • Include system details: Windows build number (Settings > System > About), device model, and driver versions for relevant hardware (graphics, network).
  • Attach screenshots, logs, or a screen recording when possible.
  • For File Explorer or taskbar bugs, note whether the issue occurs with third-party shell extensions or after connecting specific peripherals.
  • Mark the feedback category accurately (e.g., Settings > Settings Homepage; File Explorer; Taskbar; Nearby Sharing).
Well-structured feedback improves Microsoft’s ability to correlate telemetry and accelerate rollouts or rollbacks during Controlled Feature Rollout.

Critical analysis: strengths, limitations, and communication​

Strengths
  • The build targets practical reliability issues that impact daily usability. Fixing taskbar icon visibility and File Explorer focus behavior are small wins that have disproportionate user impact.
  • Microsoft provides an opt-out for suggested content, which is an important privacy and UX control when introducing in-system product nudges.
  • Delivering this flight as an enablement package is efficient and minimizes installation overhead while enabling server-side control of features.
Limitations
  • The list of changes is narrow and largely incremental; Insiders seeking major new capabilities will find this build underwhelming.
  • Controlled rollouts create fragmentation: different Insiders will see different features, complicating coordinated testing across multiple machines.
  • Microsoft’s announcement text in the public blog has occasional redundancy and slightly awkward phrasing in the Reminders section; clearer, more concise communication would help Insiders understand exactly when and how features are applied.
Communication critique
  • The blog post reiterates the same toggle instructions multiple times in slightly different wording, which may create confusion for less-technical Insiders. A single, crisp paragraph describing how CFR works and what the toggle controls — paired with a short FAQ on toggles, rollback, and reporting — would increase clarity.
  • Microsoft’s transparency about which features are telemetry-driven versus opt-in could be improved; Insiders benefit from precise details about whether a listed item will appear on a device or only if the server-side flag flips.

Recommended checklist for Insiders and admins​

For Insiders who want to participate:
  • Ensure you are on the Beta Channel and verify build number after the update (Settings > Windows Update > View update history).
  • Decide whether to enable the latest updates toggle — enabling it puts you in the CFR pool but increases variance across your machines.
  • Back up important files and optionally create a system restore point before installing.
  • Keep driver packages up to date from OEMs (graphics, storage, network), especially if you rely on older peripherals.
For administrators evaluating Insider participation:
  • Use test devices or virtual machines rather than production endpoints.
  • Turn off the fast rollout toggle on managed devices unless you have a specific test plan.
  • Track Flight Hub and official Insider posts to map which builds and features you want to validate.
  • Document and automate rollback and recovery steps in case a preview build affects developer tooling or imaging workflows.

What to expect next​

This build continues a broader pattern: Microsoft is iterating on Windows 11 through a sequence of targeted, small updates that focus on stability and experimentation. The presence of a Microsoft 365 suggestion inside Settings indicates an ongoing trend toward more context-aware product prompts, while the commit to fixing day-to-day UI reliability shows Microsoft is listening to pain points reported by Insiders.
Expect the following in the coming weeks:
  • Wider rollout of the listed fixes if telemetry and feedback are positive.
  • Further enablement-package updates in the 26220 family that enable or disable experimental features.
  • Additional tweaks to Guided rollout behavior where Microsoft refines which devices see new content based on telemetry and compatibility signals.

Conclusion​

Build 26220.7859 (KB5077223) is an example of the current Windows Insider cadence: modest, targeted updates that prioritize reliability and controlled experimentation over headline features. For Insiders, the build brings useful fixes to the taskbar, File Explorer, Nearby Sharing, and Settings that should improve daily stability — and an optionally surfaced Microsoft 365 upgrade prompt that underscores Microsoft’s increasing interest in contextual product suggestions inside system UI. If you’re running Beta-channel preview builds for testing and feedback, this update is worth installing and monitoring. If your PC is a production machine, the safer choice remains to wait for broader rollout and cumulative validation. Regardless, this release is a reminder of how Microsoft is balancing incremental polish with live experimentation as Windows 11 evolves.
Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26220.7859 (Beta Channel)
 
Click to expand...
Microsoft has shipped Windows 11 Insider Preview Build 26220.7859 (KB5077223) to the Beta Channel, a compact maintenance flight that does more housekeeping than feature-polishing — but it also quietly surfaces a new Microsoft 365 upgrade prompt inside the Settings app for some Microsoft 365 Family subscribers.

Background​

Microsoft continues to use the Windows Insider Program’s enablement-package model and Controlled Feature Rollout (CFR) to ship platform binaries broadly while gating new user-facing experiences to subsets of devices and accounts. That means installing the build does not guarantee you’ll immediately see every change; Microsoft turns features on server-side or via rollout flags and gradually ramps them out to Insiders who have the “get the latest updates as they become available” toggle enabled.
Build 26220.7859 is targeted at Windows 11, version 25H2 for Beta-channel Insiders and is primarily a reliability and fixes package. The new Microsoft 365 prompt is the only reported user-facing novelty in this flight; the rest of the update corrects flaky behaviors in the taskbar, File Explorer, Nearby Sharing and a particular Settings pane. Community trackers and forum threads picked up the same details within hours of the official announcement, confirming Microsoft’s public notes.

What’s new in Build 26220.7859 (KB5077223)​

The headline: a Microsoft 365 upgrade prompt in Settings​

  • Microsoft 365 Family subscribers may see an upgrade to a different Microsoft 365 plan option on the Accounts page in Settings. The prompt appears as suggested content inside Settings for a subset of Insiders under CFR. Microsoft explicitly points to an opt-out: users can hide the suggestion by turning off Show me suggested content in the Settings app.

Reliability and bug fixes (rolling out)​

Microsoft lists a set of improvements being rolled out gradually:
  • Taskbar: improved reliability for showing app icons in the system tray when the taskbar is set to autohide.
  • File Explorer: addressed a bug where all open File Explorer windows and tabs might unexpectedly jump to Desktop or Home.
  • Nearby Sharing: improved reliability when sending larger files.
  • Settings: improved reliability for configuring options in Settings > Bluetooth & devices > Wheel.
These fixes are small individually but target high-frequency pain points that have been reported by Insiders in recent 26220-series flights. Community threads and independent trackers show these same fixes listed in changelogs and forum summaries.

Why the Microsoft 365 prompt matters​

At first glance the change is innocuous: a targeted prompt inside the Accounts page encouraging Microsoft 365 Family subscribers to change plans. But the prompt is significant for three overlapping reasons:
  • Commercialization inside core UX: Settings is a system-level experience users expect to contain system controls, not subscription marketing. Surfacing subscription upsells in Settings increases the presence of commercial prompts inside the OS’s control plane.
  • Rollout model and discoverability: Because the prompt is controlled server-side, not every Beta-channel Insider will see it even after installing KB5077223. This uneven visibility both soft-tests the behavior and complicates reproducibility for helpdesk staff, enterprises, and testers.
  • Privacy and data-signal implications: Microsoft’s recommendation systems for suggested content rely on account signals and device telemetry to determine what to surface. That raises questions about which account/device signals trigger this promotion and whether opt-out controls are respected consistently.
Those concerns are not theoretical — vendors have been extending commerce prompts into setup flows and settings for several releases now, and coverage from outlets and community discussions has tracked this trend over time. The new prompt fits a broader pattern of Microsoft leaning into subscription cross-sell opportunities inside Windows.

How the prompt appears and how to remove it​

The prompt shows up on the Accounts page in Settings as a suggested content tile for eligible Microsoft 365 Family subscribers. If you prefer not to see product suggestions in Settings, Microsoft provides an explicit toggle to remove suggested content.
To disable the suggested content tile (quick steps):
  • Open Settings (Win + I).
  • Go to Privacy & security → General.
  • Turn off Show me suggested content in the Settings app.
This setting is the authoritative in-OS control for suggested content in Settings; Microsoft documents it under privacy/general controls. For admins and power users, Group Policy and registry options exist to suppress many consumer experiences system-wide, but those are broader and have administrative implications.
If you manage multiple devices and want to block promotional suggestions across an organization, consider Group Policy paths such as Computer Configuration → Administrative Templates → Windows Components → Cloud Content → Turn off Microsoft consumer experiences, or equivalent MDM policies. Those policies are broader and will suppress other consumer-oriented features, so validate before wide deployment. Community guides and Windows 11 privacy writeups summarize these options and provide step-by-step instructions.

Controlled Feature Rollout: what it means for Insiders and admins​

The Controlled Feature Rollout model Microsoft uses for these 26220-series updates has three practical consequences:
  • Staged visibility: A device may have the latest servicing binaries but still not see a new UI or prompt until Microsoft enables it for that device/account cohort. This helps Microsoft test impact and telemetry signals at scale but complicates testing and helpdesk troubleshooting.
  • Opt-in rapid-update toggle: Insiders who enable “get the latest updates as they become available” will receive CFR-enabled experiences earlier. Microsoft calls this out in its blog post as the toggle to get early visibility of gated features.
  • Non-guarantee of permanence: Microsoft warns features may be changed, removed, or never shipped to general audiences. That uncertainty is part of the Insider preview remit — but it also means admins should treat CFR-visible behavior as transient until features are finalized.
For IT pros and helpdesk teams, the CFR model increases the importance of baselining: confirm which devices have the binary installed, which devices have CFR features enabled, and whether account entitlements (e.g., Microsoft 365 Family membership) are contributing to any behavior. In practice this often requires coordinating with users, checking the OS build, and reproducing the account state on a test device.

Privacy, user choice, and interface hygiene — The trade-offs​

Microsoft’s ability to surface a subscription prompt inside Settings stems from two sources: account entitlements and the presence of the suggested-content system. From a product perspective, the rationale is straightforward — help users discover relevant Microsoft services they already have or could benefit from. From a user and privacy perspective, the change raises reasonable pushback.
Key trade-offs:
  • Convenience vs. clutter: A small minority of users appreciate seeing helpful subscription-related suggestions where account management happens. But many users view Settings as a control surface and object to commercial content there.
  • Targeted signals vs. transparency: Microsoft can target the prompt to Microsoft 365 Family subscribers, which is sensible, but transparency about what signals triggered the prompt and how to opt out should be straightforward, consistent and discoverable.
  • System integrity vs. monetization: As commercial prompts appear deeper in the OS, the line between system guidance and marketing blurs. Enterprise customers and privacy-conscious consumers will push back if prompt behavior is inconsistent or difficult to disable.
Industry reporting and community commentary have tracked Microsoft’s increasing integration of subscription prompts inside setup and core UI. That broader trend supports why this single prompt, though small, invites scrutiny.

The reliability fixes — practical impact and testing notes​

Although the build is light on new features, the reliability fixes address recurring, user-visible problems:
  • System tray icons when autohide is on: The fix aims to make icons reliably appear when the taskbar is revealed. For users who rely on system tray apps (VPN clients, backup agents, communication apps), this reduces the chance of missing status indicators. Test: toggle taskbar autohide on/off and confirm icons reappear immediately when the taskbar is revealed.
  • File Explorer windows jumping to Desktop/Home: Reported by Insiders in prior flights, this bug could be disruptive for multitasking users with many Explorer windows and tabs. The patch aims to prevent mass focus shifts. Test: open multiple Explorer windows and tabs, perform common navigation, and verify that windows remain on expected folders.
  • Nearby Sharing large-file reliability: Improvements should reduce failed transfers and timeouts for larger payloads. Test: try PC-to-PC sharing of multi-hundred‑MB files over Wi‑Fi and check transfer resilience.
  • Settings > Bluetooth & devices > Wheel: Fixes address configuring hardware-specific wheel options (e.g., mice with scroll wheels). Test hardware-specific config flows and validate persisted settings.
These fixes are targeted and pragmatic — they reduce friction more than they add capabilities. Admins and power users should validate behavior on representative hardware, especially where the File Explorer and taskbar are scripted or integrated into management workflows.

What Insiders and admins should do now​

For everyday Insiders who want minimal fuss:
  • If the Microsoft 365 prompt shows and you don’t want suggestions in Settings: turn off Show me suggested content in Settings → Privacy & security → General. That will remove the tile for settings-sourced suggestions.
  • If you rely on the Beta Channel but want to avoid early CFR changes: keep the “get the latest updates as they become available” toggle off. CFR-gated experiences are more likely to appear for devices with that toggle enabled.
For IT admins and support teams:
  • Baseline builds and features: track devices’ installed KB numbers and whether they have CFR-enabled features. Use a test device to reproduce account-specific prompts.
  • Policy options: if you want to suppress consumer experiences at scale, validate Group Policy and MDM settings (for example, tools that turn off Microsoft consumer experiences) in a pilot deployment before rolling out broadly.
  • Update escalation paths: because CFR can create inconsistent experiences, prepare helpdesk scripts that include checking the Settings toggle, account membership, and whether the Insider toggle is enabled.

Risks and unanswered questions​

  • Server-side enforcement and opt-out durability: While Microsoft documents the suggested-content toggle, some users have reported intermittent disappearance of settings or inconsistent opt-out behavior in older builds. If you see unexpected suggestions reappear, re-check the toggle and test on a clean account to determine whether the behavior is account- or device-scoped. Community posts indicate this can be an area of friction.
  • Telemetry signals driving prompts: Microsoft hasn’t published the full decision tree that determines which accounts see what prompt. That lack of transparency complicates reproducibility for IT admins and privacy-focused users.
  • Business and enterprise impact: While the current prompt targets Microsoft 365 Family subscribers (consumer accounts), similar approaches could be extended to other subscription types, which could raise questions in corporate environments if prompts appear for managed or hybrid accounts.
Flagged claim: the exact account/device signals used to select which Microsoft 365 Family subscribers see the prompt are not published in the build notes. If that level of detail matters for your environment, treat the deployment as a test and demand reproducible steps in your lab before rolling any guidance to end users.

Verdict — incremental update with outsized policy implications​

Windows 11 Insider Preview Build 26220.7859 is, technically, a lightweight maintenance release. The reliability fixes are welcome for users who’ve seen the File Explorer focus jump or flaky system tray icon behavior. At the same time, the Microsoft 365 upgrade prompt — small, targeted and easily disabled — is an example of a broader trend: the operating system is increasingly a channel for Microsoft’s subscription offerings.
From a product perspective, this may improve discoverability for users who genuinely benefit from plan changes. From a policy and privacy standpoint, it underscores the importance of clear opt-out controls, transparent signal usage, and administrative tools to manage consumer experiences at scale. Microsoft has provided an in-OS toggle and standard admin controls exist for more aggressive suppression, but the rollout model (CFR) and limited transparency around targeting raise valid questions for enterprises and privacy-conscious users.
Insiders who test this build should validate the reliability fixes on representative hardware and confirm whether the Microsoft 365 tile appears for their account. Administrators should update helpdesk guidance, consider policy-level suppression if they don’t want these prompts, and treat the feature as a staged test rather than a fully baked platform change until Microsoft lifts the CFR gates.

Practical checklist — quick actions you can take now​

  • Check your build: confirm your device shows Build 26220.7859 (KB5077223) in Settings → System → About.
  • If the Microsoft 365 prompt appears and you want it gone: Settings → Privacy & security → General → turn off Show me suggested content in the Settings app.
  • Test taskbar system tray and File Explorer behavior after the update to validate the fixes in your workflow.
  • For admins: pilot Group Policy or MDM controls to suppress consumer experiences before rolling them to the organization.
Windows 11’s 26220.7859 build is a small step forward in reliability and a reminder that Microsoft’s product strategy for Windows increasingly weaves subscription prompts into core UI surfaces. The engineering fixes are useful; the subscription tile is a policy conversation worth having — and, importantly, it’s easily reversible for users who prefer a Settings app free of promotional suggestions.
Source: Neowin Windows 11 Beta build 26220.7859 arrives with a new Microsoft 365 upgrade prompt in Settings
 
You must log in or register to reply here.

Similar threads

  • Article Article
Windows 11 Insider Preview Build 26220.7752 Adds Built-in Sysmon and CFR Rollouts
Replies
0
Views
42
ChatGPT
  • Article Article
Windows 11 26220.7262 Insider Preview: HD Voices, AI Tools, CFR Rollout
Replies
1
Views
42
ChatGPT
  • Article Article
Windows 11 Beta Build 26220.7670 Brings Fixes and CFR Rollouts (KB5074169)
Replies
0
Views
34
ChatGPT
  • Article Article
Windows 11 Insider Preview 26220.7670 Beta Channel CFR Fixes (KB5074169)
Replies
0
Views
28
ChatGPT
  • Article Article
Windows 11 in 2025: Navigating Chaos, CFR Rollouts, and the AI Push
Replies
0
Views
26
ChatGPT