Copilot WAM Broker Error in Windows 11: Step-by-Step Fix

When you launch Copilot on Windows 11, you may see an error message about the Web Account Manager Broker. This error prevents Copilot from signing in or responding to your queries. The root cause is a corrupted or misconfigured WAM component that handles authentication between Windows and Microsoft services. This article explains why the WAM Broker fails and provides a clear, step-by-step fix to restore Copilot functionality.

Why the WAM Broker Error Appears in Copilot

The Web Account Manager Broker is a Windows 11 component that manages authentication tokens for Microsoft services. When you sign into Copilot, Windows uses the WAM Broker to obtain an access token from your Microsoft account. If the Broker’s stored tokens become corrupted, or if a work or school account is partially disconnected, the authentication process fails. Copilot then shows an error message such as “Something went wrong. Please sign in again” or a generic WAM failure code.

Common triggers include:

Corrupted Microsoft Account Credentials

Windows stores your Microsoft account credentials in a secure cache managed by the WAM Broker. If this cache gets out of sync — for example, after a password change or a failed update — the Broker cannot issue a valid token.

Mixed Work and Personal Accounts

Many users sign into Windows 11 with a work or school account and then add a personal Microsoft account for Copilot. When the WAM Broker tries to serve both accounts, it can confuse the token issuance, especially if the work account uses Conditional Access policies that block personal token requests.

Outdated or Corrupt Web Account Manager Service

The WAM Broker runs as part of the Windows “Web Account Manager” service. If this service is stopped, disabled, or its internal database is damaged, Copilot cannot authenticate.

Steps to Fix the Copilot WAM Broker Error

The following steps remove corrupted account data and reset the WAM Broker. Perform them in the order listed. If one step does not resolve the error, proceed to the next.

Step 1: Remove and Re-add Your Microsoft Account in Windows

1. Open Windows Settings
   Press Windows + I to open Settings. Go to Accounts > Email & accounts.
2. Remove your Microsoft account
   Under “Accounts used by other apps,” find your Microsoft account (the one you use for Copilot). Click it, then select Remove. Confirm the removal when prompted.
3. Restart your PC
   Restart Windows 11 to clear any cached tokens from memory.
4. Add the account again
   Go back to Settings > Accounts > Email & accounts. Click Add a Microsoft account and sign in with the same credentials.

Step 2: Disconnect Work or School Accounts

1. Open Access work or school
   In Settings, go to Accounts > Access work or school.
2. Disconnect any work account
   If you see a work or school account listed, click it and select Disconnect. Confirm the action. This removes the account’s cached tokens from the WAM Broker.
3. Restart your PC
   Restart to ensure the WAM Broker resets its token store.
4. Reconnect only if needed
   After testing Copilot, you can reconnect the work account. If the error returns, keep the work account disconnected while using Copilot.

Step 3: Reset the Microsoft Store Cache

1. Open Command Prompt as Admin
   Press Windows + X and select Terminal (Admin) or Command Prompt (Admin).
2. Run wsreset.exe
   Type wsreset.exe and press Enter. A blank Command Prompt window appears. Wait for the Microsoft Store to open automatically. This process clears the Store’s cache, which also resets the WAM Broker’s internal database.
3. Close the Store
   After the Store opens, close it. Restart your PC.

Step 4: Repair or Reset the Web Account Manager Service

1. Open Services
   Press Windows + R, type services.msc, and press Enter.
2. Find Web Account Manager
   Scroll to Web Account Manager. Right-click it and select Properties.
3. Set startup type to Automatic
   In the Properties window, ensure the Startup type is set to Automatic. If it is not, change it and click Apply.
4. Restart the service
   Click Stop, then click Start to restart the service. Close the Services window.

Step 5: Use the Microsoft Account Troubleshooter

1. Open Get Help
   Press Windows + Q, type Get Help, and open the app.
2. Run the account troubleshooter
   Type Microsoft account sign-in and follow the prompts. The troubleshooter will detect and fix common WAM Broker issues automatically.

If Copilot Still Has Issues After the Main Fix

If the error persists, check for these related problems.

Copilot Shows “Sign in required” Even After Re-adding Account

This usually means the WAM Broker cache still holds a corrupted token. Repeat Step 1 and Step 3. Then, in Copilot, click your profile icon and select Sign out. Close Copilot completely, reopen it, and sign in again.

Copilot Works in Microsoft Edge but Not in Windows

This indicates the Windows-side WAM Broker is broken while the Edge browser uses its own token store. Run the wsreset.exe command from Step 3. If that does not help, run the SFC /scannow command in an admin Command Prompt to repair system files.

Error Code 0x800706ba or 0x80004005

These error codes point to a broken Web Account Manager service. Open Services, locate Web Account Manager, right-click it, and select Restart. Then run wsreset.exe again. If the error returns, perform an in-place repair of Windows 11 using the Windows Update Assistant.

Copilot WAM Broker Error vs General Copilot Sign-in Error

Item	WAM Broker Error	General Sign-in Error
Root cause	Corrupted WAM token cache or service	Network issues, expired password, or server outage
Error message	“Something went wrong. Please sign in again” or WAM-specific code	“Can’t sign in” or “Check your network connection”
Primary fix	Remove and re-add account, reset WAM cache	Check internet, update password, wait for Microsoft server status
Service involved	Web Account Manager (WAM)	Azure Active Directory, Microsoft 365 sign-in service
Scope	Affects only Copilot and apps using WAM	Affects all Microsoft 365 apps and services

After completing the steps above, open Copilot and sign in again. Click your profile icon, select Sign out, then close and reopen Copilot. Enter your credentials. If the error is gone, the WAM Broker is functioning correctly. As a proactive measure, keep the Web Account Manager service set to Automatic and avoid using multiple Microsoft accounts on the same Windows profile for Copilot.