Skip to content

Est. 2011·Microsoft Partner ID 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

Free Fix 0x8004de80

OneDrive 0x8004de80 and 0x8004de86: OneDrive will not sign in or link the account

10 min read Updated October 5, 2026 Microsoft 365 & Entra ID

Fix it now

Microsoft publishes a fix for these two codes rather than a meaning: uninstall and reinstall the OneDrive app. Do the cheap, reversible things around it first – unlink, clear the stale account state, reset – because a reinstall on a machine that still holds the old identity usually lands in the same place.

Close OneDrive first, then run this from the Run dialog (Windows key and R)

%localappdata%\Microsoft\OneDrive\onedrive.exe /reset
  1. If nothing happens after a couple of minutes, try C:\Program Files\Microsoft OneDrive\onedrive.exe /reset and then the same path under Program Files (x86). Resetting does not lose files or data.
  2. In OneDrive settings, open the Account tab and choose Unlink this PC for every account listed, personal and work.
  3. Open Settings, Accounts, Access work or school, and disconnect tenant entries you no longer use.
  4. Start OneDrive again and sign in with the correct account, choosing the folder location deliberately rather than accepting an old path.
  5. If it still refuses, uninstall and reinstall the app, which is Microsoft’s published resolution for both codes.
  6. Before any of that, sign in to the OneDrive web app in a browser as the same account. If the browser also fails, this is not a client problem.

0x8004de96 is documented separately: it appears after you change your Microsoft account password, and Microsoft points to the guidance for syncing a different account.

If the client links and syncs, stop here. If the wrong account keeps returning after every reset, the next section explains where else Windows is holding it.

Why it happens

It is worth being straight about what is documented here. Microsoft’s OneDrive error code reference gives 0x8004de80 and 0x8004de86 a resolution – uninstall and reinstall the app – and no published meaning. So the honest position is that the sync app cannot complete sign-in or set the account up on this device, and the vendor’s answer is to replace the client. Anything more specific than that is inference, and inference is what sends people into registry hives they did not need to open.

The inference that is usually worth acting on, before the reinstall, is stale account state on the machine. OneDrive supports a personal account and one or more work accounts at once, and keeps a separate settings folder for each under the user profile. Alongside that, Office stores its own identity records, Windows stores tokens in Credential Manager, and the account broker keeps a record of every work or school account added to the machine. Four places to disagree, and a reinstall of the client clears only one of them.

They disagree after changes that looked harmless. A user is renamed, so their sign-in address changes but a cached record holds the old one. A device is handed to a new starter without a rebuild. A contractor’s tenant is removed but their entry under Access work or school is not. Someone signs in to Office with a personal account by accident. Microsoft documents the neighbouring 0x8004de96 as occurring after a Microsoft account password change, which is the same shape of problem: the machine is holding an account state that no longer matches reality.

The documented fix has not been tried properly

You have this one if 0x8004de80 or 0x8004de86 with no other symptom, on a machine that has been reset but not reinstalled.

  1. Reset the client using the documented path, then the two Program Files fallbacks if nothing happens.
  2. If reset does not clear it, uninstall and reinstall the app, which is what Microsoft publishes for both codes.
  3. Reinstall from a current installer rather than an old cached one, so you are not reinstalling the same defect.

A personal account is linked where a work account belongs

You have this one if The client shows a personal OneDrive folder, or the folder path carries a personal account name rather than your organisation’s.

  1. Unlink the personal account from the OneDrive Account tab.
  2. Sign out of the personal account in any Office app, under File then Account.
  3. Restart OneDrive and sign in with the work address only; if both are genuinely needed, link the work account first.

A personal account is not a fault in itself. It causes trouble when a policy or script assumes the first linked account is the work one.

Windows and Office still hold the previous account

You have this one if Signing in appears to succeed, then the client falls back to the previous account, or an old address is pre-filled and cannot be changed.

  1. Close every Office application and OneDrive.
  2. Clear the cached Windows credentials that refer to OneDrive and to the Office identity store, in Credential Manager under Windows Credentials.
  3. Remove the stale entry under Settings, Accounts, Access work or school.
  4. Sign in to one Office application with the correct account first, let it complete, then start OneDrive.

A leftover settings folder still claims the account

You have this one if The client reports the account is already being synchronised even though nothing appears to be linked.

  1. Unlink every account from the OneDrive Account tab and close the client.
  2. Look under %localappdata%\Microsoft\OneDrive\settings for business folders left over from a previous link.
  3. Rename rather than delete the folder for the account that will not link, so you can put it back.
  4. Start OneDrive and link the account again, choosing the folder location explicitly.

Never delete the synchronised data folder while files are still marked cloud-only. Unlink first, and confirm those files show as available online.

The device’s own work account registration is broken

You have this one if Several Microsoft 365 applications ask for credentials repeatedly on the same device, not only OneDrive.

  1. Run dsregcmd /status and read the device state section.
  2. On an Entra joined device, confirm it shows as joined and that a primary refresh token is present.
  3. Remove and re-add the work account under Settings, Accounts, Access work or school, then sign out of Windows and back in.
  4. If the device state is genuinely broken, treat it as a device registration problem rather than a OneDrive one.

Full reference

What the vendor publishes for each code here

Code What Microsoft publishes
0x8004de80 A resolution – uninstall and reinstall the app – and no stated meaning
0x8004de86 Documented together with 0x8004de80, same resolution, no stated meaning
0x8004de96 Occurs after you change your Microsoft account password; see the guidance on syncing a different account
0x8004dec5 Not listed on Microsoft’s OneDrive error code page at all
You’re already syncing this account No vendor page publishing this string was found; treat it as an existing link already present on the machine

That table is the reason this article is ordered the way it is. Where the vendor publishes a fix, do the fix. Where it publishes nothing, work the machine state methodically rather than reaching for whichever explanation makes the story tidy.

The four places account state lives

  1. The OneDrive settings folders under the user profile, one per linked account.
  2. Windows Credential Manager, which holds tokens for OneDrive and the Office identity store.
  3. The work or school account list under Settings, Accounts, which the account broker reads.
  4. Office’s own identity records, which is why signing in to an Office app first often fixes the client.

A reset clears the first of those. A reinstall clears the first and some of the fourth. Neither touches Credential Manager or the account broker, which is precisely why the wrong account comes back after a reset and people conclude the reset did not work.

Doing it across a fleet

  • The same sequence scripts perfectly well through your management tool: unlink, clear the cached credentials, remove the stale work account entry, reset, then reinstall if needed.
  • Test on a handful of machines first, because credential entry names vary between builds.
  • Check what is marked cloud-only before any script touches the sync folder; placeholders are not files.
  • Capture the OneDrive version before and after, so you can tell a genuine reinstall from a failed one.
  • Where a whole group fails at once, look for a change to the tenant or the account rather than to the machines.

When the browser fails too

One check reorders the whole investigation: sign in to the OneDrive web app in a browser on the same machine, as the same account. If that also fails, nothing on this page applies and the problem is the account or the service, not the client. It takes a minute and it is the difference between fixing the right thing and reinstalling a working application.

Every code this article covers

Code What it points at Source
0x8004de80 Microsoft publishes a resolution for this code – uninstall and reinstall the OneDrive app – but no meaning. Treat it as the client being unable to complete sign-in on this device Microsoft Support
0x8004de86 Documented together with 0x8004de80 and with the same published resolution and no stated meaning Microsoft Support
You're already syncing this account No vendor page publishing this string was found. Functionally, an existing link for that account was found on the machine and a second one is refused not published by the vendor
0x8004dec5 Not listed on Microsoft’s OneDrive error code page. Work it as a sign-in failure: unlink, clear the account state, reset, then reinstall not published by the vendor
0x8004de96 Occurs after you change your Microsoft account password; Microsoft points to the guidance for the ‘you’re syncing a different account’ condition Microsoft Support

Confirm the fix worked

  1. The OneDrive Account tab lists only the intended accounts, with the folder paths you expect.
  2. A file created in the synchronised folder appears in the web app under the correct account.
  3. Signing out of Windows and back in leaves sync running without a prompt.
  4. An Office application shows the expected account under File, Account.

Questions people ask about this

Will any of this cost money?

No. This is device-side state and it costs nothing to fix. If the underlying account has no OneDrive, you get a different error and that is a separate question about the subscription rather than the client.

Does unlinking or resetting delete my files?

No. Microsoft states plainly that you will not lose files or data by resetting OneDrive, and unlinking leaves the local folder in place. The care needed is with files marked cloud-only, which are placeholders rather than content: download them first if you need them offline.

Why does the wrong account keep coming back after a reset?

Because a reset clears the client’s own configuration and not the Windows and Office account state around it. If the broker still hands out a token for the old identity, the client uses it again on the next start.

Is there a documented meaning for 0x8004de80?

No. Microsoft’s error code page gives a resolution for it – uninstall and reinstall the app – without stating what the code means. Anyone telling you it specifically means a cached identity is inferring, and this article says so rather than repeating it.

Can I do this across a fleet?

Yes. The steps script well through a management tool. Test on a handful of machines first, because the names of cached credential entries vary between builds.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix AADSTS80001 and AADSTS80002: pass-through auth and password sync are failing License Error Authorization_RequestDenied: the admin centre refuses your change Free Fix 8344 and Event ID 6801: Entra Connect cannot authenticate to your directory Free Fix LargeObject and ExceededAllowedLength: Entra ID rejects an oversized object
← Back to Knowledge Base