A Microsoft file hosting and synchronization service.
This didn't work for me. I even completely uninstalled then reinstalled it and still getting the error
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I get this error:
There was a problem signing you in
Please try again in a few minutes. (Error Code: 0x8004de69)
I waited one week. Then, I reinstalled Windows 10. The same error code. I didn't find the error code on Google. What does it mean?
Thanks!
A Microsoft file hosting and synchronization service.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This didn't work for me. I even completely uninstalled then reinstalled it and still getting the error
Reinstalling the local user profile resolved this issue for me. You may also need to recreate the user in AzureAD.
I encountered this, today, on a newly created MS 365 user. They are on a Mac running macOS Big Sur, with MS Office and One Drive with mainstream updates as of November 2021 installed.
I opened a case with MS but while waiting for them to call me I logged the user in to their MS 365 account, online and opened their One Drive Web app. I was then able to log them in to their One Drive desktop app immediately.
The user had been created a good couple of hours prior to attempting to log them in to their One Drive desktop app but my guess is the provisioning systems on Microsoft's back end had nodded off and the act of logging in to their One Drive Web app woke the beast to complete provisioning the user's SharePoint services.
Thanks!
This fixed the issue for my user.