Outlook error "Something unexpected went wrong with this url"

For the GPO to work correctly you need to use three forward slashes before the backslashes to establish the correct protocol.

This was in my example

i.e. for \myfileserver.internal you would use:

file:///\myfileserver.internal in the GPO

Ivan,

You can also apply this fix through the Registry Editor and it will leave the user with access to add/remove sites under the Trusted Sites or Sites in Local Intranet. I tried the fix through GPO first and didn't like that as well.

You'll want to head to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains in the Registry Editor and add your URL, UNC, or FQDN there. You will still see the Microsoft Security Notice pop up but I think that's a good thing as users should be paying attention to any links they receive and making sure it is a trusted link before opening.

Here is the link to Microsoft's page for IE security zones. Hope this helps.

https://learn.microsoft.com/en-us/troubleshoot/developer/browsers/security-privacy/ie-security-zones-registry-entries

We have the same issue. Removing the affected update and turning off the warning message via the registry aren't decent solutions regarding to security. Therefore, Microsoft MUST provide us with a fix/workaround without negleting the security.

I tried to add various patterns to the zone "Trusted Sites", but without success:

• file://domain.com
• file://domain
• file://*.domain.com
• \domain
• \domain.com

And still the warning message when trying to open an affected URL that consists of an UNC path:

Hi,

The problem with applying this "workaround" with GPO is that if we try to do it we take Administrative control of Trusted Sites or Sites in Local Intranet. This approach is removing any custom assigned by user sites.

This is very timeconsuming workaround as administrator should go computer by computer and document current sites.

It will be better Microsoft to provide real fix.

BR,

Ivan Cholakov

Hi Alex,

It would seem there will not be any "fix" the workarounds are the resolutions to be used with caution on verified trusted domains, IP Paths, URL's etc.