Forum Discussion
Authentication prompts when opening a document
After weeks of digging I believe I found the source of the prompt issue:
On an affected machine open up Registry Editor and navigate to:
"HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\ServicesManagerCache\ServicesCatalog"
In our case I found these entries to be the culprit:
TP_BOX_BETA
TP_BOX_2
TP_EGNYTE_PLUS
I've simply deleted these entries and the prompts immediately stopped on my own machine.
In my instance most of the users were affected, so I created a GPO that would modify(delete) these entries upon user login - not had a report of the prompts since. As a safety measure I've also disabled the "Optional Connected Services" for Office users in the Trust Centre\Privacy settings.
Our environment is a mix of W10/W11, Citrix (Server 2012 R2) users.
How I found the solution:
After days of digging around in the Office suite settings, our network settings and not getting anywhere with our network support guys I thought I'd check the registry to see if anything pops up relating to
storage.googleapis.com & cdn01.boxcdn.net, that's how I stumbled upon those entries.
Hope this helps as I've been lurking this thread for weeks now hoping for an answer.
V.
- Thank you for your advice.
I tried deleting only the "thumbnails" registry key under TP_EGNYTE_PLUS and it seems to work.
The problem is that after a few days the key recreates itself....
It remains to be understood what egnyte.com is for and why it has to download icons from storage.googleapis.com....- Egnyte seems to be an optional Office integration, however no idea why it keeps popping up as we never even looked at using it. I keep a group policy on that mods the registry files - that seems to have worked rather well so far, I believe only had 1 or 2 users that reported the proxy prompts since implementing, both of which were result by a simple gpupdate.
- Thank you I will investigate this and report back.
- Please do - curious to know if this works for others as well.
- Unfortunately I dont see any of those reg keys.
Think this was caused by multiple reasons, one being defender blocks. We excluded some key files that were being reported as blocked in defender. Outdated web proxy system on the devices.
Seems to all be resolved now.
