Google is testing a new guided setup experience in Chrome that visually escorts users through the final Windows Settings step required to make it the default browser on Windows 11. First spotted by Windows Report on July 6, 2026, the feature is an unsubtle but welcome addition for anyone who has groaned at the multiple clicks needed to ditch Edge.

What Google Actually Changed

Chrome's standard first-run flow on Windows already offers a standalone "Set as default" button, but clicking it merely opens the Default apps screen in Settings—and that's often where the hand-holding ends. Casual users frequently land there, see a list of file and protocol associations, and close the window without actually completing the switch.

According to the early build captured by Windows Report, the new guided page appears to intercept that moment. Instead of dumping you into a generic settings panel, Chrome now overlays a series of instructional callouts that point directly to the "Set default" button for Chrome—or, depending on the interface variant, walks you step-by-step through the entire protocol-association process. The change is reminiscent of onboarding wizards that other applications (like Adobe's PDF reader) have used to help users navigate Windows' multi-step defaults.

Crucially, Google is not altering the system mechanism. The feature strictly directs the user to the appropriate Settings page; it does not set defaults automatically, which would breach Windows security policies. The test appears limited to Chrome Canary, and it's unclear when—or if—the feature will graduate to stable. Google has not published a support article or commented officially.

What It Means for You

For everyday users

The guided overlay demystifies a process that has remained stubbornly confusing since Windows 11 launched. If the feature ships, swapping to Chrome could become a single guided flow: launch the browser, say yes to the prompt, and follow on-screen arrows straight to the correct toggle. No longer will people accidentally leave Edge as the default simply because they couldn't find the buried setting. That said, the visual walkthrough also functions as a persistent nudge—some may find it overloads an already chatty first-run experience.

For power users and enthusiasts

If you already know your way around Settings, the additional screens might feel like hand-holding you could skip. There's a strong chance Google will include a dismiss option ("Don't show again") that lets you bypass the tutorial. Power users on Canary builds can already test it by enabling the related flag (if available) or triggering a fresh installation. Those managing multiple profiles should note that the walkthrough may appear per-profile until the default is confirmed system-wide.

For IT administrators

Organizations that deploy Chrome via policy will be unaffected on managed devices—the feature won't override Group Policy or MDM-configured default associations. Nevertheless, admins should watch for the behavior when users install Chrome manually outside of managed deployments, as the extra step could confuse staff who expect the process to be automatic. As always, the cleanest path remains pushing the DefaultAssociationsConfiguration policy to enforce browser defaults across the fleet.

How We Got Here

The default-browser brouhaha is neither new nor subtle. Microsoft's own history provides the necessary context:

  • Windows 10 era (2015–2020): Changing defaults required navigating Control Panel or Settings with moderate friction. Third-party browsers could prompt users, but the experience was inconsistent.
  • Windows 11 launch (October 2021): Microsoft introduced per-protocol defaults, breaking the simple one-click switch for browsers. Instead, users had to manually associate HTTP, HTTPS, HTML, and more—a move widely criticized as a walled garden defense for Edge.
  • Backlash and compliance (2022): The EU raised concerns, and competitors like Firefox and Opera cried foul. Microsoft partially walked back the change, adding a single "Set default" button for known browsers in the March 2022 update (KB5011563). But the damage was done: millions of users had already surrendered to Edge out of confusion.
  • Google's earlier attempts: Chrome has long included a "Make default" toast or infobar, especially on Windows. However, these prompts rarely bridged the gap between clicking the button and actually finishing the switch. This new guided walkthrough is a direct response to that leaky funnel.
  • Industry trend: Apple and Android have faced similar scrutiny over default apps. Google's move mirrors a broader push to give users clearer control, even as platforms continue to subtly favor their own services.

What to Do Now

If you want Chrome as your default right now (without waiting for the new feature)

  1. Open Settings > Apps > Default apps.
  2. Search for Google Chrome in the list.
  3. Click the Set default button at the top of the page. This will associate all relevant protocols and file types with Chrome.
  4. Alternatively, scroll through the list and manually set associations for .htm, .html, HTTP, HTTPS, and other web-related items if you prefer a partial switch.

If you see the new guided flow (Canary builds)

When the page appears during first run or after an update, follow the numbered callouts. It typically involves:
- Accepting the prompt to change your browser.
- Waiting for the Settings app to open.
- Clicking the highlighted Set default button pointed out by an overlay arrow or border.
- Confirming the change and closing Settings.

Should the overlay not appear, check whether the #default-browser-guided-onboarding flag (or similar) is enabled in chrome://flags. Keep in mind that experimental features can break, so do this only on a non-critical device.

If you want nothing to do with it

  • During onboarding: Click the skip or close button on the guided screen. Chrome should remember your choice.
  • After onboarding: You can still navigate to Settings manually, but the tutorial will not launch again unless you reset Chrome.
  • Admins: Block the behavior entirely by pre-configuring default associations through Group Policy or Intune.

Outlook

The guided setup is likely to roll out gradually through Chrome's experimental channels over the coming months. Microsoft will almost certainly not attempt to block it—that would invite antitrust scrutiny and break its own guidelines for app-to-settings deep linking. However, expect subtle jousting. Microsoft could tweak the Settings UI to reduce the impact of visual callouts, or Edge might debut its own, even more streamlined, default prompt. For users, the immediate benefit is clarity; for the industry, it's another round in the never-ending default-apps boxing match. As always, keep your Chrome installation updated and your configuration backups handy—because in the battle for your browser bar, the only constant is change.