The AADSTS50196 error on Windows 10 means the server couldn’t issue a token because the client’s application identifier is missing or invalid. To fix it, clear the Windows credential cache, re-register the device with your work or school account, and check that the app or service you’re using hasn’t been uninstalled or altered.
What Is AADSTS50196?
AADSTS50196 is an Azure Active Directory (now Microsoft Entra ID) error code that appears when a device or app tries to authenticate but the token request is malformed. The full message usually reads: “AADSTS50196: The client application identifier is missing or invalid.” This means the authentication request didn’t include a valid client ID, or the client ID doesn’t match what the server expects.
On Windows 10, you’ll typically see this error in one of three places:
- When signing in to a work or school account in the Settings app
- When opening Office 365, Outlook, or Teams and getting a repeated login prompt
- When using the “Access work or school” settings to connect to an organizational domain
The error is almost always tied to a corrupted or stale token cache, a broken device registration, or a misconfigured application on the server side. It’s not a sign that your account is locked or compromised.
Why Does This Error Happen?
Windows 10 uses OAuth 2.0 and OpenID Connect to get tokens from Microsoft Entra ID. Every app that requests a token must present a client ID—a unique GUID that identifies the application. When the client ID is missing or doesn’t match a registered application in the tenant, the server rejects the request with AADSTS50196.
Common triggers include:
- An Office or Windows update that changed the app registration
- A third-party antivirus or cleanup tool that deleted registry entries
- Manually removing a work or school account incorrectly
- Using a local account that was later joined to Azure AD without proper re-registration
- Corrupted credentials in the Windows Credential Manager
In many cases, the issue is local to your device—the server is fine, but your device’s cached tokens or registration data are out of sync.
How to Fix AADSTS50196 on Windows 10
Work through these steps in order. Most users resolve the error at step 1 or 2.
Step 1: Clear the Windows Credential Manager
- Open Control Panel > User Accounts > Credential Manager.
- Click Windows Credentials.
- Look for any entry containing MicrosoftAAD, MicrosoftOffice16, or your organization’s domain.
- Click the entry and select Remove.
- Restart your PC and try signing in again.
If you see many entries, you can remove them all—Windows will recreate them on the next sign-in.
Step 2: Re-register the Device with Azure AD
- Go to Settings > Accounts > Access work or school.
- Select your work or school account, then click Disconnect.
- Restart your PC.
- Go back to Access work or school and click Connect.
- Enter your organizational email and password, then complete the registration.
This forces a fresh device registration and generates a new client ID for the local device.
Step 3: Repair Office or the Problem App
If the error appears in Office apps, repair the installation:
- Open Settings > Apps > Apps & features.
- Find Microsoft Office (or the specific app like Teams), click it, and select Modify.
- Choose Quick Repair first. If that doesn’t help, try Online Repair.
For other apps, uninstall and reinstall them. This restores the correct client ID registration.
Step 4: Run the Microsoft Support and Recovery Assistant
Microsoft’s free tool can diagnose and fix many Office and sign-in issues. Download it from Microsoft’s official site, run it, and select the scenario that matches your problem (e.g., “Office”). It will automatically check for corrupted tokens and re-register apps.
Step 5: Check the App Registration on the Server Side
If the error persists across multiple devices, the problem may be in the application registration in Microsoft Entra ID. Ask your IT administrator to:
- Verify the app’s client ID in App registrations under Microsoft Entra ID.
- Check that the app is enabled and that the redirect URIs match what the client uses.
- Confirm that the app has the required API permissions and that admin consent has been granted.
This is rare for standard Office apps, but common for custom line-of-business applications.
What If the Error Still Appears?
If you’ve cleared credentials, re-registered the device, and repaired the app, try these additional steps:
- Reset Windows Update components—some updates can corrupt the token cache. Use the built-in Windows Update troubleshooter from Settings > Update & Security > Troubleshoot.
- Create a new Windows user profile—a corrupted profile can cause authentication failures. Test by creating a local admin account and trying to sign in there.
- Check the system date and time—if your clock is off by more than a few minutes, token validation fails. Enable automatic time synchronization in Settings > Time & Language.
- Run the Azure AD Connect sync (if your organization uses it) to ensure your account is properly synchronized.
If none of these work, the issue may be a temporary outage on Microsoft’s side. Check the Microsoft 365 Service Health dashboard (if you have admin access) or wait a few hours.
How to Avoid This Error in the Future
Prevention is mostly about not breaking the token cache:
- Don’t use registry cleaners or “PC optimizers” that remove authentication entries.
- Always disconnect work or school accounts properly via Settings, not by deleting user profiles or registry keys.
- Keep Windows and Office updated—Microsoft frequently fixes authentication bugs in cumulative updates.
- If you use a VPN, ensure it doesn’t interfere with the authentication endpoints (login.microsoftonline.com).
For IT admins, enforce device registration policies and use Intune to manage devices so that re-registration can be done remotely if needed.
Frequently Asked Questions
Does AADSTS50196 mean my account is hacked?
No. This error is about the client application ID, not your password or account security. It simply means the app couldn’t present a valid identifier to the authentication server. Your account is not compromised.
Will I lose my files if I disconnect my work account?
Disconnecting a work or school account from Windows 10 does not delete your local files. It only removes the device from Azure AD and stops syncing settings and some data. Your documents and desktop files remain intact.
Can I fix this without admin rights?
Most steps—clearing credentials, repairing Office, and re-registering the device—require standard user rights. However, if the problem is on the server side (app registration or permissions), you’ll need an administrator to make changes in Microsoft Entra ID.
Why does this error only happen in Outlook but not in other apps?
Different apps use different client IDs and token caches. Outlook has its own registration and may be more sensitive to stale tokens. Clearing the Office credentials in Credential Manager and repairing Outlook usually resolves it.
Is there a command-line fix?
Yes, you can use dsregcmd /leave and then dsregcmd /join in an elevated Command Prompt to force a device re-registration. This is a more direct alternative to the Settings method, but you’ll need to sign in with your work account afterward.
Does this error affect Windows 11 too?
Yes, AADSTS50196 can appear on Windows 11 as well. The fixes are essentially the same, though the Settings menus are slightly different. The steps above work for both operating systems.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix msmpeg2vdec.dll Errors in Windows
- How to Update Sonos App and Speakers
- Unlock iPad Without Apple ID: Is It Possible?
- iOS 18 WhatsApp Notifications Not Working? Fix
- Fix Windows Cannot Locate Suitable Printer Driver
- Spotify Private Listening: Turn It On and Off