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)
Hyper links wont open and I get the error message.
Using Classic Outlook on Windows for personal email, calendar, and contact management
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.
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.
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.
I'm using build 16529.20182, do not have the Security update (KB5002427) and I'm seeing the same issue.
FQDN path doesn't work but the UNC path does with a pop-up.
im not to sure there is a temp solution with out breaking up your existing update solutions, i've removed the updates that caused the issues , but they will then re-install , and if your patching to a security level your then non-compliant , moving office back to a previous version isn't practical across 100's pc's within a company , and again you'll need to amend your update policies to not apply the latest release of office ,
MS really need to get a fix in place for this
the only particle way to work around is to copy the link to run ad open from there ,this works fine
Outlook online or reinstall office to an older version currently.