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)
Why does the "Restart Office to apply privacy settings" not go away even after i have closed all office products, restarted them i have even restarted PC and still every time i open an office priduct i have this same issue?
Restarted multiple times in different applications, rebooted PC still same error
Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
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 have been trying everything I can from Microsoft's support pages, and nothing fixes the issue.
No fix that I have found though by now there should have certainly been one. Seems like a quality assurance problem not unlike Boeing's. There is a connection between stored credentials for Microsoft 365 applications and OneDrive. Credentials Manager (accessible via Control Panel) can be used to delete authentication data for OneDrive and that sometimes seems provide a temporary solution.
This solution does not work!
I have the same issues with my desktop and Surface. My wife has the issues and she uses only 1 PC.
When I open an office app, I get the Restart Required message box. I can dismiss it, and then I try to go to Account Privacy .. Manage Settings.. but the restart Required window comes on again so I can't change the settings.
I can launch Word and Excel in save mode and make sure the setting are set to the same. but I still get the popup..
There must be a fix for this
Ron
It is a known issue microsoft engineering is working on a fix
The thread I am looking at started 27 June, and there are dozens of similar threads around. It's now 16th July. When will MS have a proper answer to this problem, instead of trying out solutions on users who think they are getting a proper answer?