Windows 11 Search Web and Store Toggle Enters Insider Tests

Windows 11’s redesigned Search experience should not automatically become a user-controlled feature on managed PCs. IT teams should first decide whether web and Microsoft Store discovery supports their environment, then verify that existing Search, taskbar, and Settings restrictions produce a coherent experience before Microsoft moves the change beyond the Windows Insider Experimental channel.
Microsoft began the controlled feature rollout on July 13, 2026, according to the Windows Insider blog, and has not announced a general-availability date. That uncertainty is useful: administrators have time to test whether the cleaner interface complements their support model or exposes controls that users cannot meaningfully change.

The New Toggle Changes More Than Search’s Appearance​

The visible improvement is straightforward. Windows Search will label apps, settings, files, web results, and Microsoft Store suggestions more clearly, while prioritizing local apps, settings, and files when they are the stronger match.
Microsoft is also adding a control under Settings > Privacy & Security > Search that lets users decide whether web and Microsoft Store suggestions appear alongside local results. For unmanaged users, this promises a cleaner way to separate local discovery from online recommendations without abandoning Windows Search entirely.
For enterprise IT, however, the new control creates a policy question. A toggle that appears available, appears locked, disappears because Settings pages are restricted, or conflicts with an existing device policy can produce four different help-desk experiences—even if all four devices ultimately return similar local results.
That makes this more than the latest visual cleanup in Windows 11 Search. It is a new point where user preference, device policy, Windows edition, taskbar configuration, and support documentation can collide.
WindowsForum has tracked Microsoft’s broader effort to improve Windows Search usability, app discovery, and result ranking. The July 2026 change narrows that work into a concrete deployment choice: allow personal control over online suggestions, or standardize Search as a managed, local-first entry point.

---

Test the Intended Experience Before Testing the Interface​

The first pilot should not ask whether the new Search box looks better. It should ask what users are supposed to find, what they are permitted to change, and what support staff will tell them when Search behaves differently from a personal Windows PC.
A practical pre-rollout review can begin with these steps:

1. Enroll representative test devices in the Windows Insider Experimental channel and confirm whether the controlled rollout has reached them. Because Microsoft is staging the feature, two otherwise similar test devices may not receive it simultaneously.
2. Open Settings > Privacy & Security > Search and record whether the new web and Microsoft Store suggestions control is visible, editable, restricted, or absent.
3. Search for a locally installed app, a Windows setting, and a local file. Confirm that each result is clearly labeled and that the strongest local match appears ahead of web or Store suggestions.
4. Repeat the searches with web and Store suggestions enabled, then disabled. The test should establish what changes in the result set rather than relying on the toggle’s wording.
5. Apply the organization’s existing web-search policy to an eligible edition and repeat the same queries. Confirm that Windows does not perform web queries or display web results when DoNotUseWebResults is enforced.
6. Test every taskbar Search presentation used by the organization: hidden, icon only, icon and label, or the full search box. Users may perceive the same result behavior differently depending on how prominently Search is presented.
7. Repeat the test on devices where Settings pages are restricted. Verify that users can still understand the deployed Search behavior even if they cannot reach the page containing the new control.
8. Give the resulting matrix to service-desk staff before expanding the pilot. Support guidance should describe the managed experience, not merely repeat Microsoft’s instructions for an unmanaged PC.

The objective is not to validate every possible query. It is to identify contradictions: a visible control overridden by policy, a hidden control that support documentation tells users to change, or a full taskbar search box that advertises discovery features the organization intentionally blocks.

DoNotUseWebResults Draws an Important Edition Boundary​

Microsoft’s existing DoNotUseWebResults CSP remains the clearest control for organizations that want Windows Search to stay off the web. When enabled, it prevents Search from performing web queries and prevents web results from appearing.
The policy applies to Windows Enterprise, Education, and IoT Enterprise or IoT Enterprise LTSC. It does not apply to Windows Pro, which matters for organizations with mixed licensing, lightly managed branch devices, contractor systems, or PCs purchased outside the standard deployment process.
A configuration that works on Enterprise therefore cannot be assumed to establish the same experience on Pro. If users can control web and Store suggestions on one device but encounter an enforced local-only configuration on another, the discrepancy may be an edition limitation rather than failed policy processing.
The policy’s scope also clarifies the ownership decision. On supported editions, leaving DoNotUseWebResults unconfigured makes room for the user-facing choice. Enforcing it establishes a device-level posture in which online web discovery is not a personal preference.
Microsoft Store suggestions deserve separate attention during testing. The new Settings control groups web and Store suggestions into the user’s discovery decision, while DoNotUseWebResults is specifically documented as preventing web queries and web results. Administrators should not infer unverified Store behavior from the web policy’s name; they should observe the result categories presented by the pilot devices.
That distinction is especially important where the Microsoft Store is restricted through controls outside this Search change. A Store suggestion that points toward an app users cannot obtain is technically discoverable but operationally useless, and it can generate avoidable tickets.

Taskbar Policy Determines How Strongly Search Is Advertised​

ConfigureSearchOnTaskbarMode controls whether Windows 11 presents Search as hidden, an icon, an icon with a label, or a full search box. It is supported on Windows 11 24H2 and later, including Pro, Enterprise, Education, and IoT Enterprise editions.
Once the policy is configured, users cannot change that taskbar choice in Settings. This makes it a useful companion to a deliberate Search deployment, but it controls presentation rather than deciding whether web results should be available.
The combinations carry different expectations. A full search box suggests that Search is a primary route to apps, files, settings, and potentially online discovery. An icon-only configuration keeps the feature available without giving it the same visual prominence, while hiding Search reduces exposure but does not answer how Search should behave when invoked elsewhere.
IT should therefore test ConfigureSearchOnTaskbarMode and DoNotUseWebResults as separate policy dimensions:

• A full search box with user-controlled web and Store suggestions favors broad discovery.
• A full search box with web results blocked favors highly visible local navigation.
• An icon-only presentation can preserve access while reducing taskbar clutter.
• A hidden taskbar entry reduces visibility but should not be treated as a substitute for controlling web queries.

The new result labels may make all of these configurations easier to support because users can more readily distinguish a file from a Store or web result. Clearer labeling, however, cannot correct a policy design in which the interface offers choices that the organization does not intend users to exercise.

---

Locked Settings Can Turn a Useful Control Into a Support Trap​

Organizations that limit access to Settings need an additional test pass. If Privacy & Security > Search is unavailable, users may never see the control Microsoft expects them to use to manage web and Store suggestions.
That can be perfectly acceptable when policy defines the experience. It becomes a problem when support articles, onboarding material, or technicians instruct users to visit a page that their device configuration hides.
The safest approach is to document Search in terms of observable behavior. Tell users whether Search is expected to return local apps, settings, files, web results, and Store suggestions—not merely where a toggle would appear on an unrestricted PC.
This is also where pilot membership matters. A test group composed only of administrators will miss the locked-Settings experience faced by standard users. The validation pool should reflect the actual combinations of edition, taskbar mode, Settings access, and Search policy deployed across the fleet.

User Choice Fits Some Fleets Better Than Others​

Allowing users to control web and Store suggestions is reasonable where Windows PCs are individually assigned, Settings personalization is already permitted, and online discovery is considered useful. The cleaner labels and stronger prioritization of local matches may reduce the confusion that previously drove organizations toward stricter controls.
A managed local-first posture is more defensible where predictable results matter more than optional discovery. Shared devices, tightly standardized desktops, and support environments built around known local tools benefit from Search behaving consistently for every user.
Mixed environments may need both models, but the boundary should follow a deliberate device or user population rather than accidental policy coverage. In particular, the lack of DoNotUseWebResults support on Pro can make edition composition part of the Search architecture.
Microsoft has provided the beginnings of a better user experience, not a complete enterprise deployment model. The company has not announced when the change will reach general availability, and the Experimental rollout can still change before broader release.
The immediate task for administrators is to build a small Search acceptance test now: verify the new control, compare managed and unmanaged results, include Windows Pro where it exists, validate every enforced taskbar mode, and rewrite help-desk instructions around the experience users will actually receive. By the time Microsoft announces a wider rollout, the important decision should already be settled: whether Search is a personal discovery surface or a centrally defined route to local resources.

---

References​

1. Primary source: learn.microsoft.com
   
   

   Policy-based in-box app removal | Microsoft Learn

   This article is most useful for IT administrators managing Windows Enterprise or Education devices who need to remove preinstalled Microsoft Store apps (in-box apps) at scale. It provides step-by-step guidance for enabling policy-based app removal via Intune or Group Policy, including...

   learn.microsoft.com
2. Independent coverage: windowscentral.com
   
   

   Microsoft announces major Windows 11 search overhaul that prioritizes clearer, local results, and removes ads: Huge effort to fix search on Windows is finally happening | Windows Central

   Windows 11's search user experience is getting a big update, with Microsoft moving to prioritize local results, remove promotional content, and much more.

   www.windowscentral.com
3. Independent coverage: pcgamer.com
   
   

   New changes to Windows 11 Start menu and search look genuinely exciting and thank the heavens that we'll be able to disable web results | PC Gamer

   Keep going in this direction, please, Microsoft.

   www.pcgamer.com
4. Independent coverage: techradar.com
   
   

   'We love this... except gradual rollouts': Windows 11 search is being improved in a big way, with users impatient to get these changes — and I don't blame them | TechRadar

   Less clutter, more relevance — and an option to ditch web results

   www.techradar.com
5. Independent coverage: blogs.windows.com
   
   

   Improving Windows Search Box, with less clutter and more control

   Hello Windows Insiders, You’ve been asking for search that is faster, more relevant, and easier to use—whether you’re opening an app, finding a file, or changing a setting. Because the Windows Search Box is where many people start, we focused

   blogs.windows.com
6. Primary source: WindowsForum
   
   

   Windows 11 Gets Unified Search Settings for Better Usability and Privacy Control | Windows Forum

   Microsoft’s ongoing evolution of Windows 11 has been characterized by a steady stream of quality-of-life improvements. While some changes are headline...

   windowsforum.com

 

[ChatGPT]

Windows 11 users who primarily launch apps, open Settings, and locate files should choose the local-first configuration by disabling web and Microsoft Store suggestions once the new Search control reaches their PCs. Home users who genuinely discover apps or look up information from the taskbar can keep a hybrid setup, while managed endpoints should generally treat web-first search as an exception that requires a defined business reason.
Microsoft began a controlled rollout of the revamped Windows Search Box to Windows Insiders in the Experimental channel on July 13, 2026. The change is modest on the surface—a cleaner result list, clearer labels, and a new control—but it turns Windows Search into something more important: a configurable launch-and-find surface rather than a fixed mixture of local and online results.
That matters because Search is often the first interface users encounter after opening the Start menu or pressing the Windows key. If the result list makes local files, administrative settings, and installed applications easier to recognize and reach, it can reduce friction without asking users to abandon familiar workflows. Microsoft’s decision to let users suppress web and Store suggestions also creates a new user-training baseline for help desks and desktop administrators.

The New Control Is Simple, but the Policy Choice Is Not​

The setting is located at Settings > Privacy & Security > Search. On eligible Insider systems receiving the controlled rollout, users can decide whether web and Microsoft Store suggestions appear beside local search results.
The immediate procedure is straightforward:

1. Open Settings in Windows 11.
2. Select Privacy & Security.
3. Open Search.
4. Find the new control for web and Microsoft Store suggestions.
5. Keep suggestions enabled for a hybrid search experience, or turn them off for a local-first result list.

Microsoft has not positioned the feature as a wholesale removal of search capabilities. Instead, it gives users a choice about whether external web and Store suggestions share the same result area as apps, settings, and files. That distinction is important for deployment planning: this is not a decision between “Search works” and “Search does not work.” It is a decision about what Search should prioritize as an interface.
Microsoft says apps, settings, and files are now prioritized when they are the better match. The company has also removed promotional content from web-result presentation, added clearer origin labels across app, settings, file, web, and Store results, improved typo matching for apps, and enabled two-character searches for local files.
For WindowsForum readers following the rollout, related coverage of the experimental update that removes promotions and adds the web toggle is useful context. The more consequential point is that administrators and power users can now set expectations around intent: are users searching their PC, searching a catalog, or searching the web?

---

Local-Only Should Be the Default for Managed PCs​

For managed PCs, disabling web and Microsoft Store suggestions is the clearest default when the endpoint’s primary role is business productivity, shared access, frontline work, or specialized operational software. Users in those environments normally search to launch a sanctioned application, reach a Windows setting, or retrieve a local document—not to browse an online result or discover a Store listing.
A local-first result list has practical training advantages. It is easier to explain that typing an application name opens the installed application, typing a setting leads to Windows configuration, and typing a filename surfaces local content. Clearer origin labels should reinforce that distinction, particularly for users who otherwise assume every result is equally local or equally authoritative.
This setting also gives IT teams a simpler support posture. If a user reports that “Search is showing the wrong thing,” help desk staff can first establish whether web and Store suggestions are enabled, rather than trying to explain why multiple result origins are competing in a single list. The new labels help, but a less mixed interface is still less likely to create confusion.
Local-first does come with a tradeoff. Users lose immediate suggestions that might point them to online information or Microsoft Store content, so teams should not frame the setting as a universal productivity improvement. It is a better fit where the device is a work tool with known applications and controlled workflows, not a general discovery device.
For organizations that do not yet have a policy mechanism for the new control, the near-term task is not to rush into broad changes. Document the desired user experience, test the Insider implementation on representative devices, and update service-desk guidance before broader availability. Microsoft has said further settings-ranking tuning is planned in the coming months, which means this is a moving target rather than a finished redesign.

Hybrid Search Is the Best Fit for Most Home Systems​

A hybrid configuration—keeping web and Microsoft Store suggestions visible—is the sensible middle ground for general home PCs. Many home users use Windows Search for more than launching Word, finding a photo, or opening a Control Panel replacement; they may also use it as a quick route to installable software or a related web lookup.
The new experience should be less disruptive than earlier versions because Microsoft says local apps, settings, and files receive priority when they are the better match. Promotional content is no longer part of web-result presentation, and explicit origin labels should make it easier to tell whether a result opens a local app, a Windows setting, a file, the web, or the Store.
That does not make every mixed result list equally useful. A household PC with several users, many installed applications, and a large local file collection may still benefit from disabling suggestions if people repeatedly complain that Search feels noisy. Conversely, a lightly configured laptop used for browsing, casual software discovery, and everyday tasks may find hybrid search convenient rather than distracting.
The key distinction is whether suggestions are complementary or competitive. If external results appear after Windows has already surfaced the intended app, setting, or file, hybrid search can be helpful. If users routinely have to visually sort through multiple origins to find an obvious local result, local-first is likely the better choice.
WindowsForum’s earlier look at hiding web and Store suggestions in Windows 11 Search captured the cleaner-interface appeal. The new training message should go further: users are no longer simply accepting Microsoft’s preferred search mix. They can align the interface with how they use the PC.

---

Web-First Is a Deliberate Exception, Not the Universal Setting​

A web-first approach—leaving web and Microsoft Store suggestions enabled and treating them as a central part of Search—fits a narrower set of users. It can make sense for people who intentionally use the taskbar or Start menu as a broad query box, frequently seek online answers, or regularly search for new applications.
Even then, web-first should not mean ignoring local results. Microsoft’s revised ranking behavior is explicitly designed to surface apps, settings, and files when those are the better match. The practical benefit of keeping suggestions enabled is not that web results should defeat local intent; it is that they remain available when local intent is weak, incomplete, or absent.
Power users deserve a separate consideration. Some will immediately disable every external suggestion because they want Search to behave like a strict local launcher. Others may keep the hybrid experience because app typo matching, short local-file searches, clear labels, and reduced promotion clutter make the result list more usable than before. The correct choice depends less on technical skill than on whether Windows Search is serving as an application launcher, a file finder, or a general query entry point.
The new two-character local-file search support is especially relevant here. Short searches are common when users know only an abbreviation, project code, or partial filename. That improvement strengthens the case for local-first use because Windows Search is gaining utility precisely in the local-search scenarios where people previously might have defaulted to broader suggestions.

The Labels Matter More Than the Visual Cleanup​

Clear origin labels may sound cosmetic, but they are a meaningful usability and support improvement. Search results have historically compressed several different actions into one visual surface: open an installed app, alter a Windows setting, open a document, visit a web result, or view a Store recommendation.
When those origins are plainly identified, users can make a more informed choice before clicking. That reduces the chance that a search for a setting becomes a web detour, or that an attempt to locate software becomes an unexpected Store experience. It also gives administrators a more concrete vocabulary when explaining what users should expect.
This is why the feature should not be assessed solely by whether promotional content has disappeared. Removing promotions improves the presentation, but origin clarity and result control change the operating model. Windows Search becomes easier to tune around user intent rather than forcing everyone into one result blend.
There is still a limit to how far the current rollout goes. Microsoft says it plans additional settings-ranking tuning in the coming months. Administrators should therefore avoid turning this experimental behavior into a rigid long-term standard before seeing how later ranking changes affect real queries, especially common searches for Settings pages and internal application names.

Frequently Asked Questions​

Does disabling web and Store suggestions disable Windows Search?​

No. Apps, settings, and files remain the core local result categories. The new control determines whether web and Microsoft Store suggestions appear alongside them.

Which users should choose local-first search?​

Managed-device users, shared-PC users, and people who mainly launch installed applications or find local files should generally choose local-first. It is also a good choice for anyone who wants a less mixed result list.

Is this redesign available to all Windows 11 PCs now?​

No. Microsoft began a controlled rollout to Windows Insiders in the Experimental channel on July 13, 2026. Availability beyond that group has not been established in the current information.

Should IT teams change their search guidance immediately?​

They should start testing and preparing guidance, but avoid assuming the current ranking behavior is final. Microsoft has said more settings-ranking adjustments are planned over the coming months.
The immediate takeaway is not that every Windows 11 PC should hide web results. It is that Windows Search now has the beginnings of a real operating choice: local-only for focused work, hybrid for general use, and web-first only where web and Store discovery are genuinely part of the job.

---

References​

1. Primary source: support.microsoft.com
   
   

   Windows Search and Privacy | Microsoft Support

   Learn how to connect Windows Search with your accounts in the cloud, manage your Windows Search and SafeSearch settings, clear search history, and more.

   support.microsoft.com
2. Independent coverage: windowscentral.com
   
   

   Microsoft announces major Windows 11 search overhaul that prioritizes clearer, local results, and removes ads: Huge effort to fix search on Windows is finally happening | Windows Central

   Windows 11's search user experience is getting a big update, with Microsoft moving to prioritize local results, remove promotional content, and much more.

   www.windowscentral.com
3. Independent coverage: techradar.com
   
   

   'We love this... except gradual rollouts': Windows 11 search is being improved in a big way, with users impatient to get these changes — and I don't blame them | TechRadar

   Less clutter, more relevance — and an option to ditch web results

   www.techradar.com
4. Independent coverage: blogs.windows.com
   
   

   Improving Windows Search Box, with less clutter and more control

   Hello Windows Insiders, You’ve been asking for search that is faster, more relevant, and easier to use—whether you’re opening an app, finding a file, or changing a setting. Because the Windows Search Box is where many people start, we focused

   blogs.windows.com
5. Independent coverage: eweek.com
   
   

   Windows Search Update: New Setting Gives Users Control Over Web Results | eWeek

   Microsoft is testing a cleaner Windows Search experience that removes web promotions, prioritizes local results, and adds more control over suggestions.

   www.eweek.com
6. Primary source: WindowsForum
   
   

   Windows Search Experimental Update Removes Promotions, Adds Web Toggle | Windows Forum

   Microsoft is testing a cleaner Windows Search experience that removes promotional content from web results and gives users more control over whether web and...

   windowsforum.com