When clicking (or CTRL+clicking) a link in Microsoft Word 2010 (likely affecting other versions) that requires prior authorization, I'll frequently end up being pointed to an invalid URL. Theoretically, this is an issue with both Word and the service provider's own redirect, but I believe the issue is fundamentally with Word.

I've noticed that there is a delay of 1s-2s after clicking. It appears that Word is validating the link prior to opening my default browser. This is a problem because it also appears to be following the 301/302 redirect internally prior to opening the browser and instead opens the redirected URL instead of opening the browser using the originally specified URL.


  • Lag when clicking (or CTRL+clicking) links in Microsoft word.
  • Website links which require authorization and redirect will result in opening default browser on the redirected page URL instead of the originally intended URL. If the site doesn't cleanly/transparently incorporate the return URL in the login page URL, it will effectively result in you not visiting to the intended page.
  • Servers which return a 500 or 403 error may be completely denied access, when all I want is for it to open in Chrome/Firefox/etc. This happens by presenting an error alert/dialog without ever leaving Word itself.

Example 1:

This particularly affects links which require authorization. For example, I found a URL on superuser.com that requires authorization and redirects if not authorized. The end result is you never get to the intended URL. While this is an error in superuser's redirect, the fundamental issue lives within Word.

  1. Link pasted into Word: https://superuser.com/users/preferences/
  2. In the background, processes this URL and, naturally because it or Internet Explorer is not logged in, it receives a response to visit: https://superuser.com/users/login?ssrc=user_prefs&returnurl=http%3a%2f%2fsuperuser.com%2fusers%2fpreferences%2f0
  3. Finally, since thankfully superuser.com knows I'm already logged in, it follows returnurl which unfortunately is still not valid: https://superuser.com/users/preferences/0

Example 2:

Another authorization example which demonstrates unclean redirect behavior is JIRA. This happens even if you're already authorized/logged in.

  1. Link pasted into word: https://INSTANCE.atlassian.net/browse/ISSUE-1234
  2. Word opens this URL: https://INSTANCE.atlassian.net/login?dest-url=%2Fbrowse%2ISSUE-1234&permission-violation=true
  3. Even though you're logged into JIRA, you will not be redirected to the originally intended URL so your journey ends here.


How do I disable this or is it even possible to workaround at all?

  • Hah, it is. Copy/paste error. I was in a hurry (work). I'll update that now, thanks @Arjan Jan 8, 2016 at 23:35

1 Answer 1


It seems you're not using Internet Explorer as your default browser? Then you're probably running into "Microsoft Office Protocol Discovery". A few more details in my answer at Clicking hyperlinks in Email messages becomes painfully slow, here at Super User.

A registry workaround is described in You are redirected to a logon page or an error page, or you are prompted for authentication information when you click a hyperlink to a SSO Web site in an Office document:

Hyperlinks from Office to Internet Explorer or to another Web browser

If this issue occurs when you click hyperlinks in Office documents that either directly open HTML Web content or are redirected to HTML content, client users can avoid the problem by enabling a registry key to send the hyperlink navigation to the browser instead of directly binding to the hyperlink from Office. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

218153 Error message: "Cannot locate the Internet server or proxy server" when clicking hyperlink

Note Regardless of the version of Office that you have installed, add the registry key in the exact location that is specified in Microsoft Knowledge Base article 218153.

When you use this registry setting, the HLINK component that is used by Office opens the hyperlink in the default Web browser. This registry setting affects all HLINK clients, not just Office. Therefore, use this registry key carefully. For more information about issues that may occur if you use this workaround, click the following article number to view the article in the Microsoft Knowledge Base:

280680 Cannot follow hyperlink to Office document

The above-mentioned KB218153 describes when this occurs:

The ForceShellExecute registry key is not present in the following location or is not set to 1:

For 32 bit Office Versions installed on 64 bit OperatingSystems


For 32 Bit Office Versions installed on 32 bit Operating Systems or 64 Bit Office Versions installed on 64 bit Operating Systems

HKEY_LOCAL_MACHINE \Software\Microsoft\Office\9.0\Common\Internet

So, adding ForceShellExecute with value 1 should stop this behaviour.

For recent versions (say, Office 365), one may want to read some feedback on the above, claiming;

Active Office Version: 16.0.13127.20296


Note step 3 in the fix:

In Registry Editor, browse to one of the following subkeys (create the keys if they do not exist):

I read up on this problem on several forums and I made the same mistake many people made with this, this must be setup as 9.0, not the current version of office. Also I wish these all had something faster to run like what I've pasted below, just needs to be ran in an admin command prompt

For 32-Bit Office on a 64-Bit machine
REG add "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\9.0\Common\Internet" /v "ForceShellExecute" /t REG_DWORD /d "1" /f

For 32-Bit machine or 64-Bit office
REG add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\Common\Internet" /v "ForceShellExecute" /t REG_DWORD /d "1" /f

  • Outstanding Google-fu on you, good sir! This works for me. It's still a little slow, however, it doesn't redirect me to the login page -- it actually goes where the link points which is the least I can ask for. Thank you very much for finding this! Jan 8, 2016 at 23:34
  • 1
    Future reference, this is the aforementioned KB article which includes a link to a quick/dirty downloadable fixer MSI (for the lazy): support.microsoft.com/en-us/kb/218153 Jan 8, 2016 at 23:37
  • Any ideas if there's an equivalent for Office 365? The solution didn't work adding the reg-key under Office\16.0 Nov 25, 2020 at 11:19
  • 1
    @Luke, the KB article was updated in July 2020, and says "Applies to: Word for Office 365, ..." So, I'd say the solution has not changed. That's all I can say; I'm not using Windows. But github.com/MicrosoftDocs/OfficeDocs-Support/issues/795 may help?
    – Arjan
    Nov 26, 2020 at 16:24
  • 1
    (@Luke, I've quoted the relevant parts in my answer above.)
    – Arjan
    Nov 26, 2020 at 16:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.