This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When someone else in our OneDrive has downloaded files in the past, I used to be able to click on those same files and they would open without issue. Now, I get the above error code and have to continue to hit "try again." Does anyone have any idea as to why all of the sudden I'm having this problem? Thank you.
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.
Hi
hopefully this will help someone we were getting 0x80070185 for multiple users
it was our firewall decrypting HTTPS once i added exception for our onedrive site it seems to be working ok now.
Having the same issue - we are about to migrate from Dropbox to Onedrive, but this error 0x80070185 is blocking. If I restart onedrive, the problem goes away for a couple of hours, but we can't keep restarting Onedrive across the organization.
It happens on Mac and PC
Have tried reinstall, and new profile, still no joy.
i'm having this problem as of this week. tried resetting OneDrive as per the original instructions - still can't sync OneNote, still can't upload to OneDrive. why am i paying for this?
When someone else in our OneDrive has downloaded files in the past, I used to be able to click on those same files and they would open without issue. Now, I get the above error code and have to continue to hit "try again." Does anyone have any idea as to why all of the sudden I'm having this problem? Thank you.
correct error
This problem just disappeard for my client, no changes to their setup or in O365. I suspect it's some transient issue in SPO. I occasionally get the same issue in our own tenant but it's not consistent or reliably reproducable.