Nitro Pro Add-In

[ID4Nitro]

Hi there, just installed Nitro Pro 13.13.2.242 the other day and still get "An error occurred. Access to the path C:\users........\NitroWordAddin.ini is denied".

This happens to all office items except to outlook. I have Windows 10 Pro latest, and office 2019 latest updates.

I can disable these addins but why do I still get them pesky error messages. Kind of annoying.

Thanks for some pointers to fix this. I have Googled with all sorts of keywords, but no helping solutions.

[Allain Umailin]

Hello @ID4Nitro,

Thank you for reaching out to us through our Community Forums and our sincere apologies for this inconvenience.

This issue appears to be an issue with the Rights of your user profile. Either you don't have read/write access to the folder, or there is something restricting access within your profile.

To further troubleshoot, kindly uninstall/install your Nitro Pro plug-in for MS Office applications by referring to these steps:

1. Close your Nitro Pro and MS Office applications if they're open.
2. Right-click on the Nitro Pro desktop icon and select Run as Administrator.
3. Go to Help tab > Support Tools > PDF Creation tab and untick the boxes for MS Word, Excel and PowerPoint under Microsoft Office Add-ins. 
4. Click Update Add-ins button. Installation will be done in the background. Once it's done, you should receive a message 'Update of add-ins was successful. To activate your changes, please restart Microsoft Office applications'.
5. Go back to PDF Creation tab and tick the boxes for MS Word, Excel and PowerPoint. Click Update Add-ins button. Installation will be done in the background.
6. Click OK > Close and test again the affected MS Office application.

Thank you for choosing Nitro and I hope this helps!

[ID4Nitro]

Thanks AllainU for replying.

I am afraid following the steps noted did not help.

What I did was disabled addins by removing tick marks since I am not using them anyway.

This is a single user home PC and I am the only user with full admin rights so I am not sure why this could be a user permission issue.