Windows 11 Bloatware Suppression — Copilot, Widgets, and Forced Edge/Bing Defaults via GPO, Registry, and Intune
Windows 11 ships Copilot, the Widgets panel, and hard-coded Edge/Bing Start menu search integration as default-on features with no complete GUI removal path. In enterprise environments these components consume resources, redirect searches away from the user's default browser, and re-enable themselves after feature updates if not persistently suppressed. Remediation combines Group Policy (or Intune configuration profiles), targeted registry values, and AppX package removal to suppress all three components. GPO/MDM enforcement is required to survive feature updates; local registry edits alone are overwritten.
Indicators
- Copilot button visible on taskbar and cannot be removed through Settings > Personalization > Taskbar
- Widgets panel appears on taskbar and opens on hover/click, consuming resources
- Start menu web searches open Bing in Microsoft Edge regardless of the user's configured default browser
- Edge is launched for microsoft-edge:// protocol links even when another browser is set as the system default
Likely causes
- Microsoft ships Copilot, Widgets, and Edge/Bing integration as default-on features in Windows 11 with no single GUI toggle covering all components
- Start menu search routes web results through Bing and Edge at the OS level, bypassing the user's default browser setting entirely
- Feature updates re-enable or reinstall these components, overriding previous manual registry removals that lack GPO/MDM backing
- Enterprise Group Policy objects required to suppress these features are absent from standard Windows 11 installs and must be explicitly configured
Diagnostic steps
-
Identify which unwanted components are active: check taskbar for Copilot and Widgets buttons; open Settings > Personalization > Taskbar and record toggle states; perform a Start menu web search and observe which browser and search engine open.Establishes exactly which of the three feature areas (Copilot, Widgets, Edge/Bing override) require remediation, since steps differ per component.
-
Run: gpresult /h gpreport.html — open the report and search for policies referencing 'Copilot', 'Widgets', 'Dsh', and 'WindowsCopilot'.Determines whether any suppression policies are already applied, missing, or conflicting before making changes.
-
Open Settings > Apps > Default apps, confirm the desired browser is set as default, then perform a Start menu web search to verify whether Edge/Bing is still overriding the default browser setting.Distinguishes between a missing default-browser setting (simple fix) and an active Edge/Bing OS-level override (requires MSEdgeRedirect or protocol handler lockdown).
-
Run in PowerShell: Get-AppxPackage *WebExperience* — note whether the Widgets (WebExperienceHost) package is installed for the current user.Confirms whether the Widgets app package is present and subject to removal, or already stripped, before deciding on GPO-only vs package-removal approach.
Resolution path
- Disable Copilot via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows Copilot > 'Turn off Windows Copilot' — set to Enabled. On builds without this ADMX policy, create HKCU:\Software\Policies\Microsoft\Windows\WindowsCopilot and set DWORD value 'TurnOffWindowsCopilot' = 1.
- Disable the Widgets panel via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Widgets > 'Disable Widgets' — set to Enabled. Alternatively set HKLM:\SOFTWARE\Policies\Microsoft\Dsh, value 'AllowNewsAndInterests' = DWORD 0. For per-user taskbar button suppression also set HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced, value 'TaskbarDa' = DWORD 0.
- Redirect forced Edge/Bing Start menu searches to the user's default browser: install MSEdgeRedirect (https://github.com/rcmaehl/MSEdgeRedirect) — this intercepts microsoft-edge:// protocol calls and routes them to the configured default browser. Note: EdgeDeflector is non-functional on Windows 11 22H2 and later; use MSEdgeRedirect only.
- If policy-based Widgets disabling is insufficient, remove the Widgets app package entirely: run 'Get-AppxPackage *WebExperience* | Remove-AppxPackage' in an elevated PowerShell session.
- Ensure all suppression settings are enforced at the domain (GPO) or cloud (Intune configuration profile) level — not via local registry edits alone — so they survive Windows feature updates that reset local-only changes.
Prevention
- Apply Copilot and Widgets Group Policy settings (or equivalent Intune configuration profiles) as part of the baseline Windows 11 image or Autopilot provisioning script so features are suppressed from first login and never visible to end users.
- Include AppX package removal for WebExperienceHost/Widgets in the Windows imaging or Autopilot provisioning script (Remove-AppxPackage *WebExperience*) so bloatware is stripped at deployment time rather than reactively after user complaints.
- Pin browser default association XML via DISM or Intune to lock down protocol handler defaults and prevent Windows updates from resetting Edge as the handler for microsoft-edge:// links.
- Implement a periodic compliance check — Intune compliance policy or a scheduled PowerShell script — that validates Copilot, Widgets, and Edge-default policy states remain in their intended configurations after cumulative or feature updates.
Tools
- gpresult (Group Policy results reporting — gpresult /h gpreport.html)
- Get-AppxPackage / Remove-AppxPackage (PowerShell AppX package management)
- Group Policy Management Console — GPMC (domain-level policy enforcement)
- MSEdgeRedirect — GitHub (third-party tool to redirect forced Edge/Bing protocol calls to default browser; works on 22H2+)
- Registry Editor — regedit.exe (manual registry value changes)
- Microsoft Intune / MDM (cloud-managed configuration profile enforcement)