The following message occurs when clicking on any link in an email in Outlook 2010:
"This operation has been canceled due to restrictions in effect on this comptuer. Please contact your system administrator."
I am running a stand alone desktop computer in my home. Lenovo All-IN-One touchscreen C40-05, Windows 10, Home, MS Office 2010. I suppose I am the administrator because my wife refused the job and our children are grown and have all left home.
Removing Chrome and making Edge the default browser before reinstalling Chrome did not help the situation.
The Microsoft fix is at Hyperlinks are not working in Outlook
The reference to Outlook is a little misleading, as the description in the section Let me fix it myselfmakes clear. It is an error in IE that is causing the problem and the problem will appear with the app that you happen to be using when you click on a hyperlink. So you should be alright afterwards.
Denis
Hi Denis,The Microsoft fix is at Hyperlinks are not working in Outlook
The reference to Outlook is a little misleading, as the description in the section Let me fix it myselfmakes clear. It is an error in IE that is causing the problem and the problem will appear with the app that you happen to be using when you click on a hyperlink. So you should be alright afterwards.
Denis
Thanks for your reply. The reason I did not try the "Fix It Yourself" suggestions are two fold. 1. The instructions state that this fix is for:For Windows 7, Windows Vista, Windows XP, Windows Server 2008 and Windows Server 2003.
I'm running Windows 10 as stated in the original inquiry in this thread and it isn't listed. However, I tried it just now and a message opened saying "This download is not for your operating system. Well, I suppose that is because I am running Windows 10!
2. When working through the instructions for the "Do it yourself" editing of the registry, the registry for my Windows 10 computer did not have the same items as shown in the instructions so I was forced to quit.
What else can I try?
Thanks for your continued help.
Doug Wilkowske
Doug,
1 About "The reason I did not try the "Fix It Yourself" suggestions are two fold. 1. The instructions state that this fix is for:For Windows 7, Windows Vista, Windows XP, Windows Server 2008 and Windows Server 2003" You have misread the instructions. It is the automatic "easy fix" that is only available for those other operating systems.
2 About "When working through the instructions for the "Do it yourself" editing of the registry, the registry for my Windows 10 computer did not have the same items as shown in the instructions so I was forced to quit" Both the Registry keys referred to in Let me fix it myselfMethod 2exist in Windows 10. Do note that the procedure guides you through exporting the first key from a healthy computer so that implies that the key is either corrupt or missing from a computer that exhibits the fault symptoms.
3 You make no mention of Let me fix it myselfMethod 1
Denis
Hi Denis,Doug,
1 About "The reason I did not try the "Fix It Yourself" suggestions are two fold. 1. The instructions state that this fix is for:For Windows 7, Windows Vista, Windows XP, Windows Server 2008 and Windows Server 2003" You have misread the instructions. It is the automatic "easy fix" that is only available for those other operating systems.
2 About "When working through the instructions for the "Do it yourself" editing of the registry, the registry for my Windows 10 computer did not have the same items as shown in the instructions so I was forced to quit" Both the Registry keys referred to in Let me fix it myselfMethod 2exist in Windows 10. Do note that the procedure guides you through exporting the first key from a healthy computer so that implies that the key is either corrupt or missing from a computer that exhibits the fault symptoms.
3 You make no mention of Let me fix it myselfMethod 1
Denis
Yeah, I did mention Let me fix it myself Method 1. It's in number 1 above which is not for W10. The instructions clearly state W10 users should use method 2.
I chose the wrong sections in regedit the first time, so came to the erroneous conclusion the instructions were not for my current "updated" version of W10. When I read your comments and retried Method 2 for W10 users, it worked! Thanks for pointing me to that.
The tone of your comments reflects little patience with at home, non-expert users like me. I humbly suggest you adopt a more helpful, understanding approach. We are not all as well versed in "fixing" computer glitches as you. At first reading, I wanted to quit and try another more friendly forum person. After calming down and rereading, I tried it all again. I'm glad I did and I thank you once again.
Doug
