Outlook error "Something unexpected went wrong with this url"

Enable or disable hyperlink warning messages in Office programs - Office 365 | Microsoft Learn

Enable or disable hyperlink warning messages in Office programs - Office 365

Describes how to enable or to disable hyperlink warning messages in Microsoft Office programs.

HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\common\security

DisableHyperlinkWarning = 1

@Ivan,

I found there is an Office bug logged for the issue where closing Word or Excel causes SfB to crash. The issue is being investigated. The support engineer found a short-term mitigation, but I am not sure if it will cause other issues, so test it if you think it might help.

He found setting DefaultIMApp to Teams stopped the SfB crash. If you check Event Viewer you will likely see Event 1000/1001 Lync.exe for each time you close those apps and SfB crashed.

Outlook uses that DefaultIMApp for presence and other integration so there might be tradeoffs if it is used e.g. Instant messaging client features not available - Outlook | Microsoft Learn.

Computer\HKEY_CURRENT_USER\SOFTWARE\IM Providers

Reg Key:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\IM Providers]

"DefaultIMApp"="Teams"

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

Trying to figure out the proper "trusted site" to add to GPO so users are able to open the following link:

\Companyname.sharepoint.com@ssl\DavWWWRoot\Sites\XYZ.Doc

Users are right clicking and dragging files from mapped SharePoint sites into the body of an Outlook msg and selecting "create hyperlink". This used to work until the latest update. I'm not sure if adding anything into the trusted site will even work for this scenerio. Anybody know? If so what is the actual site I need to put into the GPO. I have tried: file:///\companyname.sharepoint.com and that didn't work.

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 all,

I know this is a very late reply, but I wanted to make sure you saw that we posted a Known Issue article, Outlook blocks opening FQDN and IP address hyperlinks after installing protections for Microsoft Outlook Security Feature Bypass Vulnerability released July 11, 2023 - Microsoft Support.

The Security Update CVE articles (in the link above) are also updated with a FAQ item explaining the changes further and that these are expected. These changes should have been communicated with the security updates. I apologize for the disruption.

This issue is also being published in the M365 Service Health Dashboard as EX649739.

Hi Gabrielle,

That is great news. Any idea on a timeline for a fix? I really don't want to poke holes in our internal security if I can avoid it.