thanks for the file but unfortunately it does not work for RoboHelp2017.
Sorry for the delayed response but I have been working to deliver content to a client - without using RoboHelp.
I did get the RoboHelp issue resolved but I am not happy with the lack of any support from Adobe on this issue. Their tech support left the issue for me to try on another computer two months ago. No follow-up and no support or checks. They thought the problem was with user rights and wanted all users to be set as admins (which didn't work), something that many companies do not allow.
In the end I totally uninstalled TechComm Suite 2017 from my computer and cleaned up with Revo. I then reinstalled it to the default install location (C drive). This is the only option that worked. Problem is that my C drive is an SSD and I don't want the operating system clogged with program files. I should be able to install to any internal drive that I select. If not, then warn me on install and as conditions of the product. During install I was able to select any internal drive and there were no warnings that the product would not work with other programs.
I can now import from and export to Word 2016 (Office 365). I am not convinced that I should recommend RoboHelp to my client though, especially with this type of product support.
Thanks for you support on this Peter.
I have two machines with SSDs and I use a different logic. I put programs on the C Drive as that is going to be the fastest so my programs work quicker. I keep all my data on conventional hard disks or even USB drives so that I can access it on more than one PC. That works very well.
Turning to your scenario, I agree that if it is critical that TCS is installed on the C Drive, then either it should force that or at least issue a warning that it is critical. Please follow this link to create a bug report.
Post the link to that bug in this thread and others can vote for it.
Perhaps not surprisingly, I would disagree with you on not recommending the product. I have used it for some twenty years and I have looked at the competition. There is one major competitor and if you look at their forums, they have their issues the same as RoboHelp. Also normally Support do get to the bottom of issues like this. I have known them spend a couple of hours on fixing a really knotty licensing issue. On this one I think they should have found the cause as it is a rare but not unknown problem.
See www.grainge.org for RoboHelp and Authoring information