Microsoft's latest push to embed Copilot into every corner of Windows 11 has landed a new "Ask Copilot" option in File Explorer's context menu — but you don't have to live with it. Thousands of users have complained about the intrusive addition that appears whenever you right-click a file, cluttering a space many prefer to keep minimal. The good news? A simple, reversible registry edit hides the entry in minutes, and you don't even have to uninstall Copilot to do it.

PCWorld's recent how-to guide confirmed the fix, and independent community testing across forums and tech outlets has validated that it works on current Windows 11 builds. Here we dig deeper into why this menu item exists, exactly how the tweak works, alternative removal methods, and what pitfalls to watch for — compiling the most thorough guidance available.

Why 'Ask Copilot' Keeps Popping Up

Copilot's integration is part of Microsoft's strategy to make AI assistance a habitual part of everyday computing. The right-click shortcut lets you send a selected file directly to Copilot for summarization, explanation, or other AI-powered tasks. While the intent is to boost productivity, the placement rubs many users the wrong way. It joins a growing list of Copilot touchpoints: taskbar icon, Start menu recommendations, and side panels in Edge.

From a technical standpoint, the context-menu entry is a shell extension. Windows Explorer loads these extensions via COM (Component Object Model) components registered in the system registry. Modern packaged apps like Copilot can register a packaged COM server that exposes a Class ID (CLSID) Explorer uses to display the menu item. That CLSID — identified consistently by researchers and multiple guides — is {CB3B0003-8088-4EDE-8769-8B354AB2FF8C}. If you block or remove its registration, Explorer never loads the extension, and the "Ask Copilot" entry vanishes.

The Safest Route: Block the Shell Extension via Registry

This method hides the menu item without touching Copilot's other functionality. It's reversible, takes effect almost instantly, and leaves the Copilot app fully functional elsewhere.

Step-by-Step: Create a Blocked Key Entry

  1. Open Registry Editor: Press Win+R, type regedit, and hit Enter.
  2. Navigate to the Blocked key: Expand HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\. If Blocked doesn't exist under Shell Extensions, right-click Shell Extensions, choose New → Key, and name it Blocked.
  3. Add a new string value: Right-click the Blocked key, select New → String Value. Name it exactly {CB3B0003-8088-4EDE-8769-8B354AB2FF8C}.
  4. Set the value: Double-click the new string and enter Ask Copilot (the value is for labeling only; anything works).
  5. Apply and restart Explorer: Close Registry Editor. Open Task Manager (Ctrl+Shift+Esc), find Windows Explorer, right-click it, and select Restart. Alternatively, log out and back in or reboot.

After Explorer reloads, right-click any file — the "Ask Copilot" entry should be gone.

For Non-Admin Accounts: Use HKEY_CURRENT_USER

If you lack administrator privileges or prefer a per-user setting, repeat the same steps under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked. Create the key if absent, add the same string, and restart Explorer. Some users report needing a full reboot when using HKCU, so try that if it doesn't work immediately.

A .reg File for Faster Execution

You can automate the process by creating a registry patch file:

  • For system-wide (HKLM, admin required):
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked]
"{CB3B0003-8088-4EDE-8769-8B354AB2FF8C}"="Ask Copilot"
  • For current user (HKCU):
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked]
"{CB3B0003-8088-4EDE-8769-8B354AB2FF8C}"="Ask Copilot"

Save these as .reg files, double-click to merge, and confirm UAC if prompted.

What If the Blocked Key Doesn't Work?

In rare cases, the tweak might not stick after a simple Explorer restart. Try these troubleshooting steps:

  • Try the other registry hive: If you applied HKLM, test HKCU, and vice versa.
  • Perform a full reboot: Packaged COM registrations sometimes require a full system restart.
  • Check for updates: A Copilot update may have altered the CLSID or package path. Re-examine the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package for a Microsoft.Copilot key and verify the {CB3B...} class is still present. If the GUID changed, you'll need to identify the new one (community resources like AskVG often track these changes).

The Nuclear Option: Uninstall or Disable Copilot Entirely

If you'd rather remove Copilot from your system completely, Microsoft provides a straightforward uninstall option.

Through Settings

Go to Settings → Apps → Installed apps. Locate Microsoft Copilot in the list, click the three-dot menu, and select Uninstall. This removes all Copilot UI surfaces, including the context-menu extension.

Group Policy for Pro and Enterprise

Managed environments can disable Copilot across the board via Group Policy:

  • Open gpedit.msc (available in Pro/Enterprise/Education editions).
  • Navigate to User Configuration → Administrative Templates → Windows Components → Windows Copilot.
  • Enable the policy "Turn off Windows Copilot".

For Windows 11 Home, the same effect can be achieved through a registry policy: under HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows, create a DWORD (32-bit) value named TurnOffWindowsCopilot and set it to 1. Note that policy locations can shift between builds, so verify this path on your version.

Advanced Tweak: Blanking the DllPath in PackagedCom

Power users who want to surgically disable only the context-menu extension without affecting other Copilot features can modify the PackagedCom registration directly. This is more fragile and version-dependent.

  1. Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package.
  2. Look for a subkey containing Microsoft.Copilot (the full name includes a version number, e.g., Microsoft.Copilot_1.0.0.0_x64__8wekyb3d8bbwe).
  3. Expand that key, go to its Class subkey, and find the entry {CB3B0003-8088-4EDE-8769-8B354AB2FF8C}.
  4. Under that class, locate the DllPath value (which points to CopilotNative.FileExplorerExtension.dll). Clear its data or delete the value entirely.

Why this is risky: Microsoft updates can change the package name or re-create the DllPath, silently restoring the context menu. If you go this route, export the entire Package key as a backup beforehand.

Community Consensus and Cross-Verification

The registry block method has been confirmed by multiple independent outlets. PCWorld's original guide, along with WindowsLatest, Ghacks, Beebom, and AskVG, all pinpoint the same CLSID and Blocked key approach. This convergence gives high confidence in its reliability for current Windows 11 builds (23H2 and newer).

Community forums add nuance: some users on insider builds report the entry reappearing after major OS updates, requiring reapplication of the registry tweak. Others note that Microsoft could change the CLSID in the future — a boilerplate caveat with any registry-based customization.

Safety First: Backups and Rollback

Before editing the registry, always create a safety net:

  • System Restore Point: Search "Create a restore point" in Start, click the System Protection tab, and hit Create.
  • Export Registry Keys: In Regedit, right-click the parent key you'll be editing (e.g., Shell Extensions) and choose Export.

To roll back the block:
- Navigate to the Blocked key and delete the string value you added.
- If you cleared a DllPath, merge the backup .reg you exported.

Enterprise and IT Administrator Considerations

For managed fleets, per-machine registry hacks are not scalable. Administrators should:

  • Use Group Policy to disable Copilot features centrally via ADMX templates.
  • Leverage MDM (e.g., Intune) for Windows Enterprise and Education.
  • Test updates in a staging environment to confirm that OS or Store updates don't revert customizations.

Additionally, organizations concerned about telemetry should validate how Copilot interactions — even context-menu prompts — might send signals outside the tenant. Microsoft's compliance documentation provides details on data handling.

Frequently Asked Questions

Does blocking the CLSID break Copilot?
No. Copilot remains fully operational via its taskbar icon, keyboard shortcut, and other entry points. Only the right-click menu item is hidden.

Which hive should I use: HKLM or HKCU?
HKLM applies system-wide and requires admin rights. HKCU works per-user without admin. If one fails, try the other.

Is there an official toggle to hide just the context-menu item?
Currently, no. Microsoft's official Copilot settings control visibility in the taskbar and overall enablement, but not the File Explorer context menu specifically. Registry is the only way to remove it without uninstalling.

Could a future update break this fix?
Yes. The CLSID or registration method may change. Monitor community forums after major updates and reapply if needed.

Conclusion: A Quick Fix with Lasting Relief

The "Ask Copilot" context menu entry is Microsoft's latest bid to weave AI into daily workflows — but it's clearly not for everyone. Hiding it via the Blocked registry key is a low-risk, reversible tweak that takes less than a minute. For those who want Copilot gone entirely, uninstall or group policy offer permanent solutions. Until Microsoft adds a user-facing toggle for context menu clutter, power users have a reliable workaround. Keep your backups handy and stay informed about build updates to keep your right-click menu clean and distraction-free.