Fix 0x80048054 and 0x80860010 in One Windows Profile

By Game Osborne · September 29, 2026 · Windows · Windows 11, Microsoft account, sign-in errors

Clear the damaged Microsoft sign-in cache for one Windows 11 user without resetting the PC or changing anyone else’s profile.

Before you repair anything

This guide assumes you can open the affected Windows 11 profile and that other profiles on the PC still work. It is especially relevant to Windows 11 24H2 and 25H2.

Errors 0x80048054 and 0x80860010 can appear when Windows’ saved Microsoft sign-in information becomes stuck. Microsoft apps may claim that there is no internet connection or that an application made too many requests, even while websites work normally.

The folders repaired below are inside LocalAppData, which is storage belonging only to the current Windows profile. Renaming them does not delete documents, reset the PC, or alter another user’s profile. It will sign this user out of Microsoft apps, so have the Microsoft account password available.

1. Sign in to the Windows profile that shows the error.
2. Connect the computer to a working Wi-Fi or Ethernet network.
3. Restart the computer while it remains connected to the internet.
4. Try signing in to one affected Microsoft app after Windows starts.

Install any available Windows fix

An online restart is Microsoft’s first workaround for the update-related version of this problem. If the error returns, check for a newer Windows update before clearing the profile cache.

1. Press Windows key+I to open Settings.
2. Select Windows Update in the left-hand column.
3. Select Check for updates.
4. Install any updates that Windows offers.
5. Restart the computer when Windows asks you to.

Reset the affected profile’s sign-in cache

A cache is temporary saved information. Windows rebuilds these sign-in caches automatically, so we will rename them instead of deleting them. That gives you an easy way back if necessary.

Close Word, Excel, Edge, Teams, OneDrive, Microsoft Store, Copilot, and any other Microsoft apps before continuing.

1. Press Windows key+R to open the small Run box.
2. Type %LOCALAPPDATA%\Microsoft into the Run box.
3. Press Enter to open that location in File Explorer.
4. Right-click the OneAuth folder if it is present.
5. Select Rename from the menu.
6. Rename the folder to OneAuth.old.
7. Right-click the IdentityCache folder if it is present.
8. Select Rename from the menu.
9. Rename the folder to IdentityCache.old.
10. Press Windows key+R again.
11. Type %LOCALAPPDATA%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC into the Run box.
12. Press Enter to open the AC folder.
13. Right-click the TokenBroker folder if it is present.
14. Select Rename from the menu.
15. Rename the folder to TokenBroker.old.
16. Restart the computer while connected to the internet.
17. Open the Microsoft app that previously showed the error.
18. Sign in with the affected Microsoft account again.

If Windows says a folder is in use

Do not force the folder or delete random files. Safe Mode starts Windows with only essential services, which can release a locked sign-in folder. You must use the account password in Safe Mode because a PIN, fingerprint, or face recognition will not work there.

1. Open Settings with Windows key+I.
2. Select System.
3. Select Recovery.
4. Select Restart now beside Advanced startup.
5. Select Troubleshoot on the blue recovery screen.
6. Select Advanced options.
7. Select Startup Settings.
8. Select Restart.
9. Press 4 when the numbered startup choices appear.
10. Sign in with the Windows account password.
11. Repeat the folder-renaming steps that previously failed.
12. Restart Windows normally after renaming the folder.

What to expect afterward

The first Microsoft sign-in may take longer because Windows is creating fresh cache folders. OneDrive, Office, Edge, Teams, and Store may each ask you to sign in again. Your locally stored files should remain in place.

Keep the folders ending in .old until sign-in works for a day or two. You can then delete those old folders. If several profiles begin failing at the same time, the cause is more likely a Windows update or service problem than damage inside one profile.

Bottom line

Start with an internet-connected restart and Windows Update. If only one profile remains affected, rebuilding that user’s OneAuth, IdentityCache, and TokenBroker caches can restore Microsoft sign-in without resetting the PC or disturbing anyone else.