Stop requesting save changes to document template

C:\Program Files (x86)\Microsoft Office\Office14\STARTUP

called clicktocall.dot 

Any .dot file in this location will be loaded as an Add-in.  It will be so loaded, regardless of its name.

Turns out that this problem is with document templates coming with Word add-ins.

Turning off Bluetooth may solve the problem but it may not. The true root cause of this problem is the fact that some add-ins load new document templates which have not been adequately tested with Bluetooth. 

In my case, our IT departments installs Cisco Unified Communicator which requires that a dot document template file from 

C:\Program Files (x86)\Microsoft Office\Office14\STARTUP

called clicktocall.dot 

is loaded automatically as part of the Cisco add-in initialization every time you start Word.

Since I do not use this add-in, I renamed the file to be called clicktocall.__dot and the problem went away. I also tried re-enabling Bluetooth afterwards and the problem did not reappear.

Hope this helps.

Also, check out this link:

https://supportforums.cisco.com/discussion/11026551/click-call-and-microsoft-word

And how I got to realizing that it was clicktocall.dot causing the problem:

In Word 2010, click on

File > Options > Add-Ins > Manage Word Add-Ins (dropdown), Go...

Under the Templates and Add-ins window, you'll see Global templates and add-ins in the list an entry called 'clicktocall.dot'. 

The Remove button was greyed out and unclicking this clicktocall.dot did not solve the problem.

So, long story short: you have to keep removing / renaming file names for these offending add-ins until the problem goes away. Word seems to load all files that have a *.dot extension, so changing the .dot extension to *.__dot solves the problem.

Alternatively and/or additionally, you can also disable the add-in completely:

File > Options > Add-Ins > Manage COM Add-ins (dropdown), Go...

Uncheck Cisco.ClickToCall.Word, then click OK.

The restart Word to be on the safe side.

FWIW: this is Windows 7 Enterprise and Word 2010.

PS: When a fire alarm goes off all the time unnecessarily, people find a way to disable it permanently regardless whether their house will burn down eventually or not. Maybe fire alarm manufacturers should think about manufacturing fire alarms that 1) have sensible defaults and 2) can be tested, calibrated and configured intelligently by customers without having to navigate into 5 deep menus (help files are completely useless, you have to scour the internet for true answers), and 3) do not have any places for untested add-ins that will cause the fire alarm to go off all the time unnecessarily. This whole debugging process took 2 hours of my time and I fail to understand why I would ever use Cisco Click To Call Word Add-in *ever*. Apple is absolutely right about taking away and controlling as much customization as possible.

This problem is 100% attributable to poorly written Add-Ins.

Add-Ins in Microsoft Word

***

Cool. So I've calmed down, removed the bluetooth add-in and this time restarted Word and it worked. I am curious as to how a badly written add-in was in there in the first place. Who wrote it badly and placed it there? It certainly wasn't me.

Thanks everyone for your patience and help.

You are welcome...

Some computers come with them already installed. Others are installed when you install a different program that wants make it easier for you to use that program to work with Word. Generally, they do what the author wanted it to do but have unintended side effects (bugs). Generally this seems to happen when the program tries to change the interface by adding buttons/menus to Word. It does not have to be done the way they do it, but they use the way they know, and unless they are very meticulous, it will cause problems to some users.

Microsoft wants people / developers to be able to make changes to the interface and make programs work together. MS trusts that people will do this responsibly.

It is easy to make such changes by actually making the change to a distribution template rather than using code to make the change. You can find samples of such Add-Ins on my download page as well as those of a number of the MVPs on this forum. Graham Mayor, Greg Maxey, Doug Robbins, and Jay Freedman come to mind as people who have posted free Add-Ins that are very well-behaved.

This problem is 100% attributable to poorly written Add-Ins.

Add-Ins in Microsoft Word

One other similar problem is in corporate networks with a login that overwrites the normal template from a dictated standard template. That does not block the saving, but it does erase any changes at the next login to the network.

The error message is confusing, perhaps unnecessarily.

You can get a query about saving changes to the actual document template if you have made a style change or something similar and told Word you wanted it for all documents from the template.

Cool. So I've calmed down, removed the bluetooth add-in and this time restarted Word and it worked. I am curious as to how a badly written add-in was in there in the first place. Who wrote it badly and placed it there? It certainly wasn't me.

Thanks everyone for your patience and help.

This problem is 100% attributable to poorly written Add-Ins.

Add-Ins in Microsoft Word

One other similar problem is in corporate networks with a login that overwrites the normal template from a dictated standard template. That does not block the saving, but it does erase any changes at the next login to the network.

The error message is confusing, perhaps unnecessarily.

You can get a query about saving changes to the actual document template if you have made a style change or something similar and told Word you wanted it for all documents from the template.