Outlook error "Something unexpected went wrong with this url"

Anonymous
2023-03-15T14:14:05+00:00

Hyper links wont open and I get the error message.

Outlook | Windows | Classic Outlook for Windows | For home

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.

0 comments

92 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-08-21T09:30:49+00:00

    I hope permanent fix is come Soon

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-08-21T10:04:58+00:00

    I hope permanent fix is come Soon

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-08-21T16:04:22+00:00

    This change is a permanant change due to a security update. The mitigation is to add the affected URLs to Internet Options, Trusted Sites, per guidance here, Outlook blocks opening FQDN and IP address hyperlinks after installing protections for Microsoft Outlook Security Feature Bypass Vulnerability released July 11, 2023 - Microsoft Support.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2023-08-21T20:51:43+00:00

    This change is a permanant change due to a security update. The mitigation is to add the affected URLs to Internet Options, Trusted Sites, per guidance here, Outlook blocks opening FQDN and IP address hyperlinks after installing protections for Microsoft Outlook Security Feature Bypass Vulnerability released July 11, 2023 - Microsoft Support.

    So Microsoft's solution to security issues is to block links to every file on a mapped drive? And why FQDN but not UNC? This is just **** programming, and I expect better from Microsoft.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  5. Anonymous
    2023-08-25T06:40:05+00:00

    I agree. This is not a *** decent solution.

    And the steps mentioned in the documentation above didn't fix our issue either.

    How embarassing from Microsoft...

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments