The Hybrid Admin

Seeing the “Something went wrong [1001]” error when trying to sign into OneDrive or Outlook is incredibly frustrating. It completely blocks your access to Microsoft 365 apps.

This error typically happens when your local authentication data gets corrupted or stuck in a loop with Entra ID. Here are the most effective ways to fix it and get back online.

Fix 1: Clear your local authentication cache

When your login tokens get mixed up, the best first step is to delete the cached data.

1. Sign out of all Microsoft desktop apps including OneDrive, Outlook, and Teams.
2. Close any Microsoft programs that might still be running in the background.
3. Open File Explorer and paste the following path into the address bar:C:\Users\%username%\AppData\Local\Microsoft\
4. Find the folders named OneAuth and IdentityCache.
5. Delete both of these folders.
6. Restart your computer, launch OneDrive, and sign back in.

Fix 2: Clean the identity registry keys

If clearing the cache folders did not work, the old login state might be stuck in your Windows Registry.

1. Press the Windows key + R to open the Run dialog.
2. Type regedit and press Enter.
3. Navigate to this exact path:Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity
4. Right click and delete the entire Identity folder.
5. Next, navigate to Computer\HKEY_CURRENT_USER\Software\Microsoft\OneDrive and delete that folder as well.
6. Restart your computer and try signing in again.

Fix 3: Exclude folders in virtual environments

If you are running a virtualized setup with FSLogix profile containers, Error 1001 is a common known issue. It happens because security tokens are tied to the local hardware and break when they roam between different host sessions.

To fix this, you need to exclude the authentication folders from your roaming profile. Make sure both %localappdata%\Microsoft\IdentityCache and %localappdata%\Microsoft\OneAuth are added to your exclusions in the redirections file.