A family of Microsoft word processing software products for creating web, email, and print documents.
I'm experiencing the same issue. It's a bit surprising that the MS guys didn't provide solution.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
A family of Microsoft word processing software products for creating web, email, and print documents.
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.
I'm experiencing the same issue. It's a bit surprising that the MS guys didn't provide solution.
I had the same issue. Thought it was a larger software/environment issue and ended up doing a full reinstall of Windows 10 since I was having a few other issues (major Office 2016 crashes even after going through the Office Repair process). But, after reinstalling both Windows 10 and Office 2016 the error persisted.
Strangely, I have not seen the error in the last two days. I'm not sure what is different.
Only thing that I have done is that when the "sign in" window popped up, both in Word and in Excel, I "logged in" multiple times (probably like 3-5 times each). One time, the prompt stopped and I was able to close normally. Other times I got tired and just closed the window.
The only thing I can really figure is that the backend OneDrive issue is slowly being fixed on a gradual rollout.
My Version of Office is at 1707 Build 8326.2076
Same problem here in Win10 Pro. Tried reinstalling O365 and deleting credentials, but no luck.
Same problem.
Only started in the last week or so for me.
Office 2016, W10 Pro
Auto-updates ON
Any response from MS yet?
Having the same problem, not only in Word, but also in Excel and PowerPoint files of which stored in OneDrive. Even with the latest Insider build upgraded (1709, 8509.2001), the issue still existed.
Windows 10 build 1703.16251 fresh install, then O365 installed. This issue occurred in O365 slow and fast ring.
Today, it happens again.