Fix Microsoft Account Too Many Requests Error in Windows 11

The “Too many requests” error in Windows 11 appears when you try to sign in to a Microsoft account or access Microsoft services, and the server temporarily blocks your IP or device due to excessive attempts. The fix is to wait a few minutes to an hour, clear cached credentials, and reduce sign-in frequency; if it persists, reset the Microsoft Store cache or adjust your network’s time settings.

What Causes the “Too Many Requests” Error

This error (often accompanied by code 0x80190001 or a message like “You have tried too many times. Please try again later”) is a rate-limiting response from Microsoft’s authentication servers. It happens when your device or network sends more sign-in requests than Microsoft’s threshold allows within a short period. Common triggers include:

• Repeatedly entering an incorrect password or PIN.
• Multiple apps or services trying to refresh your account token simultaneously.
• Background sync from OneDrive, Office, or the Microsoft Store.
• Using a VPN or proxy that shares an IP address with many other users.
• Incorrect system time or time zone, which breaks the authentication timestamp.

Microsoft implements these limits to prevent brute-force attacks and bot abuse, so the error is a protective measure, not a permanent ban.

Quick Fixes to Try First

Start with the simplest solutions, as they resolve the majority of cases:

1. Wait 15–60 minutes. The block is temporary; avoid retrying during this window.
2. Restart your PC. This clears temporary network and credential states.
3. Check your system time. Go to Settings > Time & Language > Date & time and enable “Set time automatically” and “Set time zone automatically.” If they are already on, toggle them off and on.
4. Sign out of all Microsoft apps (OneDrive, Store, Outlook) and then sign back in one at a time.

If the error appears when you first boot Windows, wait a few minutes before trying to sign in—background services are often still starting.

Clear Cached Credentials and Reset the Store

Stale or corrupted cached credentials can trigger repeated authentication attempts. To clear them:

1. Open Command Prompt as administrator (right-click Start > Terminal (Admin)).
2. Type wsreset.exe and press Enter. This resets the Microsoft Store cache and may take a minute.
3. Open Credential Manager (search in Start). Under Windows Credentials, look for entries starting with MicrosoftAccount: or OneDrive. Remove them, then restart.

If you use a work or school account, also remove entries under Generic Credentials that reference login.microsoftonline.com. After restarting, try signing in again.

Adjust Network and Proxy Settings

A shared IP (from a VPN, proxy, or strict NAT) can make Microsoft think many devices are hammering the server. To rule this out:

• Temporarily disable your VPN and try signing in on your regular connection.
• If you are behind a corporate proxy, check with your IT admin—they may have rate limits.
• Flush DNS: open Command Prompt as admin and run ipconfig /flushdns.
• Reset the network stack: run netsh winsock reset and netsh int ip reset, then restart.

On a home network, also power-cycle your router (unplug for 30 seconds) to get a fresh public IP if your ISP assigns dynamic addresses.

When the Error Persists: Advanced Steps

If the error continues after a few hours, try these deeper fixes:

1. Run the Windows Store Apps troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Store Apps.
2. Re-register the Store app via PowerShell (admin): Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
3. Check for Windows updates—a pending update can interfere with authentication components.
4. Create a new local administrator account (Settings > Accounts > Family & other users > Add account) and then link your Microsoft account from there. This isolates profile corruption.

If none of these work, you can temporarily use a local account to access your files. To switch: Settings > Accounts > Your info and choose “Sign in with a local account instead.” This does not delete your Microsoft account; you can switch back later.

How to Avoid Future Rate-Limiting

Preventing the error is largely about reducing unnecessary sign-in attempts:

• Use the Windows Hello PIN instead of typing your password repeatedly—it uses a local verifier and does not hit the server.
• Keep your password in a password manager to avoid typos that trigger retries.
• Do not rapidly switch between multiple Microsoft accounts on the same device.
• Close apps that continuously refresh tokens (like OneDrive) when not in use.
• If you use a shared PC, each user should have their own account rather than signing in/out repeatedly.

Also, ensure your system clock is always accurate—even a few minutes off can cause authentication failures that look like rate-limiting.

Frequently Asked Questions

How long does the Microsoft “too many requests” error last?

The block usually lasts between 15 minutes and 1 hour. In rare cases of aggressive retrying, it can last up to 24 hours. The timer resets each time you attempt a sign-in, so stop trying and wait.

Can I bypass the error by using a different network?

Yes, switching to a different network (e.g., mobile hotspot) often works because the rate limit is tied to your IP address. But if the block is based on your device ID, it may persist across networks.

Does this error affect my Microsoft account security?

No. It is a temporary throttle, not a security breach. Your account is not locked or compromised—just the sign-in process is temporarily restricted.

Why does it happen on a new PC?

New PCs often have many Microsoft services (Office, OneDrive, Store) trying to sign in simultaneously during setup. This burst of requests can trip the rate limiter. Wait an hour, then sign in once.

Will resetting my PC fix the error?

Usually not, because the issue is server-side. A reset only helps if the cause is corrupted local account settings. Try the credential and Store cache fixes first before resorting to a reset.

Can I use a local account permanently to avoid this?

Yes, you can use a local account for daily use. You will lose some features like OneDrive sync and Store purchases tied to your Microsoft account, but for basic Windows use it works fine. You can switch back anytime.

Related

• How to Record Discord Calls: PC & Mobile
• Excel Other Tips: Hidden Features That Save Time
• Scheduler Internal Error on Windows 10 Solved?