Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

OneDrive error 0x8004de40 or 0x8004de88: Can't sign in, the sync client can't reach the cloud

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A user sees "OneDrive Can't sign in. Error 0x8004de40" with the text "Login was either interrupted or unsuccessful. Please try logging in again. (Error Code: 0x8004de40)", or "We can't sign into your account, please try again later 0x8004de88". Microsoft's page says the code "indicates OneDrive is having trouble connecting to the cloud." The documented route is: confirm the device is online, make sure TLS 1.2 and the right cipher suites are available, restart or re-join the device to Microsoft Entra ID, and as a last step reset OneDrive.

One point needs care. Microsoft's OneDrive page is dated 2025-07-14 and tells you to tick TLS 1.0, 1.1 and 1.2. Microsoft's Azure Front Door page, dated 2026-10-19, says Front Door supports TLS 1.2 and 1.3 and has retired DHE cipher suites. Read the TLS part of the fix with both dates in mind.

What the error means

OneDrive for Business signs in over the network to Microsoft's cloud. The page lists two codes, 0x8004de40 and 0x8004de88, and says both point at trouble connecting to the cloud. The error does not say whether the fault is the network path, the encryption settings on the device, or the device's own identity.

The page splits its advice by operating system:

  • Windows 10: check cipher suites, check TLS protocols, then restart and, if needed, leave and re-join Microsoft Entra ID.
  • Windows 8, Windows 7 SP1, Windows Server 2012 and Windows Server 2008 R2 SP1: add the TLS 1.1 and 1.2 secure protocol registry keys (Microsoft's Easy Fix Tool does this), and for Windows 8 install KB 3140245 with a matching registry value.
  • All computers: if every earlier step is done, consider a reset of OneDrive.

The page says to confirm TLS deprecation changes as a possible cause: "Make sure that you carefully review information about TLS deprecation. That change might also cause this error."

Likely causes

Cause What you see How to confirm
The device has no working internet path Other Microsoft 365 sites and apps also fail on that device Open any Microsoft 365 site in a browser on the same device and network
TLS protocol settings on an older Windows version The error appears on Windows 8, Windows 7 SP1 or Windows Server 2012 / 2008 R2 SP1, the versions Microsoft's page lists for the Easy Fix Tool Check the Advanced tab of Internet Options (steps below)
The required cipher suites are missing or ranked low The error appears on a Windows 10 device that has had cipher or Group Policy changes Run Get-TlsCipherSuite and look for the four suites the page names
A Group Policy overrides the cipher order Changes made with PowerShell do not stick Compare Get-TlsCipherSuite after a restart; check the SSL Cipher Suite Order policy
The device's Microsoft Entra registration (your own check; the page lists the re-join as a step, not a cause) Sign-in still fails while the network and TLS checks pass Run dsregcmd /status and read the join state
Local OneDrive state (your own check; the page gives no cause for its last step) Every earlier check passes Microsoft's page ends by saying to consider a reset of OneDrive

Prove the cause before changing anything

Start with read-only checks and write down what you find.

  1. Confirm the device is connected to the internet. The page points to "Fix Wi-Fi connection issues in Windows" if it is not.
  2. On Windows 10, list the TLS cipher suites in priority order:
Get-TlsCipherSuite

Look for these four, which the page lists as supported by Azure Front Door for TLS 1.2:

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

You can query one suite by name:

Get-TlsCipherSuite -Name "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"
  1. Save the full list so you can restore the order later. Create C:\Temp first if it does not exist:
Get-TlsCipherSuite | Out-File C:\Temp\cipher-before.txt
  1. Check the device's identity state:
dsregcmd /status

Microsoft's dsregcmd page says to run it as a domain user account and lists AzureAdJoined, EnterpriseJoined and DomainJoined as the fields that show the join state. Save the output, because you will compare it after any re-join.

  1. Check whether a policy sets the cipher order. The page warns: "If the order doesn't reflect the change, check if the SSL Cipher Suite Order Group Policy setting configures the default TLS cipher suite order." Ask whoever owns Group Policy before you change a cipher list on a managed device.

Example (illustrative): a 14-person office on contoso.com.au has one Windows 10 laptop, lt-014, showing 0x8004de40 after a security policy was tightened. The two ECDHE suites above are the target. Get-TlsCipherSuite on lt-014 shows one of the two missing and the other far down the list. The fix is to add the missing suite and put both ECDHE suites in the first two places of the order.

Fix

Work down this list and stop when OneDrive signs in.

Fix the cipher suites (Windows 10)

The page's first solution is to make the four suites the highest priority in the list. Note that the two DHE suites among the four are no longer supported by Azure Front Door: its page dated 2026-10-19 says "Support for DHE cipher suites retired on April 1, 2026" and its TLS 1.2 list names ECDHE suites only. Treat the two ECDHE suites as the ones that matter. The page gives two routes: a group policy (or local group policy), or PowerShell.

Risk: the PowerShell command below changes the TLS cipher order for the whole computer, not just OneDrive. Other applications use the same list. A service that relied on the old order can fail to connect. Save first: complete the save-first step above (cipher-before.txt) and take a full backup or, on a virtual machine, a checkpoint. Back-out: if the suite was not in the saved list, run Disable-TlsCipherSuite -Name "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384". If it was in the saved list, Microsoft's cmdlet page does not say how to move a suite that is already listed, so the dependable back-out is the backup (or, for a virtual machine, the checkpoint) taken before the first command, together with cipher-before.txt to compare against; for a Group Policy change, restore the policy from its recorded value. After any back-out, compare Get-TlsCipherSuite with the saved file. No restart is required, according to Microsoft's cmdlet page.

The command:

Enable-TlsCipherSuite -Name "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384" -Position 0

Run Get-TlsCipherSuite again. The page says: "After you run Enable-TlsCipherSuite, you can verify the order of the cipher suites by running Get-TlsCipherSuite." Read the list after every command, then repeat for the second ECDHE suite at position 1.

Save first: record the policy's current value and the scope before editing.

Risk: a policy change applies to every computer in its scope.

If a Group Policy sets the order, change the policy rather than the local list, or the policy will overwrite your change.

To undo it, use that record.

Check the TLS protocols (Windows 10)

Risk: ticking TLS 1.0 and 1.1 allows older, weaker protocols for programs that use these Internet Options settings on that computer. Save first: before you change anything, open the settings and note which boxes are ticked. Back-out: open inetcpl.cpl again, return the boxes to the noted state, then Apply and OK. The Front Door page dated 2026-10-19 says "TLS 1.0 and 1.1 aren't supported", and it lists TLS 1.2 and 1.3. Confirm TLS 1.2 is ticked and test OneDrive; tick TLS 1.0 and 1.1 only if the device owner accepts the lower setting, although the OneDrive page says to tick all three.

Steps: press Windows logo key+R, type inetcpl.cpl, and press Enter. On the Advanced tab, enable the boxes, then select Apply and OK.

Older Windows

For Windows 8, Windows 7 SP1, Windows Server 2012 and Windows Server 2008 R2 SP1, the page points to the Easy Fix Tool, which "can add TLS 1.1 and TLS 1.2 Secure Protocol registry keys automatically". For Windows 8 it also lists KB 3140245 and a matching registry value.

Risk: the Easy Fix Tool edits the registry. Microsoft's error page does not name the keys it changes, so there is no single key to export. Before you run it, take a full backup of the device or, on a virtual machine, a checkpoint. Back-out: restore from that backup or checkpoint.

Restart, then leave and re-join Microsoft Entra ID

The page says to restart the device while it is connected to your Microsoft Entra domain. If that does not work, it gives a sequence of two commands, to be run from an elevated Command Prompt, given after the restriction and the mark below. The page then says to close the window, restart the computer and sign in to OneDrive. It adds: "You must be connected to your organization’s network when you do these steps."

Restriction: run the sequence only on the one device where the network, TLS and cipher checks above have passed, the restart did not help, and the saved dsregcmd /status output shows DomainJoined YES and AzureAdJoined YES, which is a hybrid joined device. Do not run it on any other join state.

Disruptive step: dsregcmd /leave removes the device from Microsoft Entra ID until dsregcmd /join succeeds. Impact: until the join completes, cloud sign-in and any policy that depends on the device identity can fail for that user. Save first: record dsregcmd /status and have a local administrator account available. Back-out: Microsoft documents no way to restore the earlier registration other than the device registering again, and dsregcmd /join is the command its page gives for that, to be run while on the organisation's network. After it, compare dsregcmd /status with the saved output.

The two commands:

dsregcmd /leave
dsregcmd /join

Reset OneDrive

Microsoft's error page ends with "If you have completed all the previous steps, consider doing a reset of OneDrive." The words "a reset of OneDrive" link to Microsoft's Reset OneDrive support page (date not shown).

Disruptive step: a reset of OneDrive. Impact: the page says a reset disconnects all sync connections on the device, personal and work or school, and OneDrive then runs a full sync; folders chosen for selective sync must be chosen again. Microsoft says you will not lose files or data. Save first: open the OneDrive status and confirm nothing is waiting to sync, note which folders are chosen for sync, and copy the local OneDrive folder to a different drive or folder. Back-out: there is no way to undo a reset; after it, start OneDrive by hand (Microsoft's page says to go to Start, type OneDrive and select the OneDrive desktop app), sign in again, choose the noted folders, and compare the sync folder with the copy.

For the OneDrive sync app on Windows, the reset page first runs wsreset.exe (its step 2 says "If OneDrive is still not syncing, let's continue with resetting the OneDrive sync app"), so the reset below is the later step. Run wsreset.exe first, or note that you skipped it. The reset page says to select Win+R, paste %localappdata%\Microsoft\OneDrive\onedrive.exe /reset and select OK. If Windows reports it cannot find the file, it gives C:\Program Files\Microsoft OneDrive\onedrive.exe /reset and then C:\Program Files (x86)\Microsoft OneDrive\onedrive.exe /reset.

Confirm the fix

  • The user can sign in and the OneDrive cloud icon in the notification area stops showing an error.
  • Get-TlsCipherSuite lists the suites you added at the front, in the order you set.
  • dsregcmd /status shows the same join state as before you started, unless the re-join was the fix.
  • A file saved in the OneDrive folder syncs, and appears at the web site.

What to watch afterwards

  • Whether the error comes back after the next Group Policy refresh. That points at a policy that overwrites the cipher list.
  • Changes in what the cloud accepts. The Front Door page dated 2026-10-19 says "Support for DHE cipher suites retired on April 1, 2026". The OneDrive page dated 2025-07-14 still lists two DHE suites among the four. If your list relies on the DHE entries alone for a client, check that the ECDHE entries are present and high in the order.

Risks and limits

These commands have not been run or lab-tested.

  • The OneDrive page covers Windows 10 and the older systems it names. It does not name Windows 11 or newer Windows Server releases, so for those the steps are a starting point only.
  • The two Microsoft pages do not agree on protocols. The OneDrive page tells you to tick TLS 1.0 and 1.1; the Front Door page lists only TLS 1.2 and 1.3. Microsoft's pages do not say which of the two OneDrive sign-in depends on, so do not treat the older instruction as current.
  • The reset steps come from Microsoft's separate Reset OneDrive page, which covers Windows, Mac, Android and iOS; follow its Windows steps only.
  • Changing cipher suites or TLS settings on a server that hosts other services can break those services. Test on one device first.
  • Microsoft's pages change over time; check the current pages before acting on a date or cipher list.

Sources