Outlook error "Something unexpected went wrong with this url"

You're right Matt. It's on file path URL's that are having an issue. I suspected that problem was came from recent updates by Windows Update - Security Updates for Microsoft Outlook (KB5002427)

Tried to uninstall the patch and hyperlinks works again. But today the patched (KB5002427) came back and the problem occurred again.

For what it's worth, this KB doesn't seem to be present on one of our machines that's been having the issue, so I don't think this is it.

Also, it's not just 2305 and 2306. We switched the affected user to the Semi-annual Enterprise channel which bumped him down to 2302, and the problem persisted there.

Admittedly, our situation is a little different, as we're using an IP address, not a friendly name, so it's hard to say for sure, but it was working with no issues up until this morning when we had two users report the problem.

What we found was that when we right-click 'Copy Hyperlink', and paste the link anywhere, the URL shows \(IPADDRESS)****path\to\file.csv. It seems to be adding a '' to the path. When we paste it into a web browser, the web browser is smart enough to interpret it and get us to where we need to go. The file browser is not. Notably, this '' is not present in the error itself, and doesn't show as part of the link until you copy and paste it. I'm not sure if it's related, but that seems to be why the link is so picky about where you use it after you copy it.

We have the same issue. FQDN does not work, if I remove .net from the link it works.

Please Microsoft test your updates before you send them out to everybody or at least provide a fix.

Hi, getting the exact same behaviour as this.

On messages with a file path that has been done with an FQDN because the user is working remote through a VPN, we get the error.

On messages with a file path that is only on a host name or drive letter, the message gives the security warning but otherwise works.

Thanks

We have the same problem. Hopefully will be fixed soon.

We have two clients with the same issue, and the only thing in common I can see is the latest version of Microsoft 365 and these two patches:

KB5028851

KB5028185

At the moment we are copying and pasting links and changing them from FQDN to UNC.