One Drive Sign in Issue 0x8004e4be

We have been ripping our hair out over this issue on an end user's workstation for about a week now. The issue has now spread to my own system after OneDrive updated for me this morning.
I was able to fix it on my system, so just need to try these steps on the end user's system.

1. Delete cached credentials for OneDrive from Windows Credential Manager per the article below

• https://support.microsoft.com/en-us/office/unlink-and-re-link-onedrive-3c4680bf-cc36-4204-9ca5-e7b24cdd23ea

2. Perform a reset of OneDrive per the article below
   • https://support.microsoft.com/en-us/office/reset-onedrive-34701e00-bf7b-42db-b960-84905399050c
3. Backup and delete all registry keys associated with OneDrive at the following location
   • Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\OneDrive
4. Restart the computer

At this point, signing in to OneDrive results in a new error code: 0x8004e4cf and 3205.

One more restart of the PC seems to have solved that problem and OneDrive is again syncing on my PC (for now.)

Seems clear to me that there's an issue with the 23.054.0313.0001 update that Microsoft will hopefully address soon.

So far here is our solution..

Mind you, we are a fully VMware / VDI setup with 150+ users.

Running FSlogix 2210 HotFix 1 for our profile containers.

I rolled back to the differed ring: OneDrive Release Notes and then immediately disabled the automatic update scheduled task.

So far this has worked for our users. Without the scheduled task, OneDrive will stay on the release you install on the machines.

Because we manage golden images, I think we are going to continue to operate in this model and use differed ring releases going forward.

Hey, I am running this command on a daily basis now and having to reboot

if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) { Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.AAD.BrokerPlugin

Any idea if there is a permanent fix coming down?? Everyone at one of my customers is impacted.

We have the same problem

Windows 2019 server in AZURE

Onedrive.exe /allusers installation (installation on session host)

Latest build of Onedrive 23.054.0313.0001

Terminal server using FSLogix for all User Profile data

2 RD Session Host (RDSH1, RDSH2) in AZURE

2 RD Connection Broker in AZURE

Unpredictably we get the error both on users landing on RDSH1 and on users landing on RDSH2. Often forcing landing on SH other than the one giving the problem OneDrive logs in correctly.

After a lot of fighting with this... I went back to 23.020.125.0002 and installed it on one of our VDI pool machines.

Before the update could complete, I went in and linked an account. Sign-in worked fine.

Build 23.052.0313.0001 is not working for us.