Report Generation -- Excel works, Word doesn't (Error -41106) after O365 pushed out

[beng1972]

I have searched the last day and a half and haven't found a solution.  I apologize in advance if I overlooked the answer somewhere...   Throughout I am using the "Create Report VI" to open Excel and Word files.

Before IT pushed out O365, Excel and Word worked fine with Report Generation.  After that, I got Error -41106 for both Excel and Word. 

Following a solution found on this Board, I went in and modified the Registry for excel by deleting the last Excel registry entry.  Excel opens now in LV with no error.

Ignorance being what it is --  I am not an IT or Windows guru -- I located the Word entry in the registry and duplicated what I did for excel.  I still get Error -41106 for Word.  Word still started normally so I didn't break anything that is noticeable.

For what it is worth, there is a difference in the Word vs. Excel registry as Excel references a .exe and Word references a .olb file. 

As I said, I am not an IT or Windows person (I'm a hardware person who spends most days sniffing solder) so this may be a simple thing to fix but I have exhausted the LV discussion board and Google searches in finding a solution that works. 

Thanks in advance for any advice,

Ben

[OctavioS]

Good to hear that you were able to get Excel working. If the registry method did not work. I would recommend uninstalling and reinstalling Word as this is actually recommended to do before you start messing around with the registry. 

[rbj]

Hi Ben, and Everyone,

This was the most recent and relevant post I found on this error and I wanted to share this solution as it worked in my case.  I got a new Windows 10 PC from IT with O365 (32 bit) already installed, downloaded LV2019 (also 32bit).  Immediately got Error -41106 with word and excel, the registry looked correct and I didn't want to go through IT to reinstall word.  I opened "settings - apps and features" in Windows, found O365 and hit "Modify", followed the prompts to "fix" the program and, to my surprise, this solved the issue.  I would recommend trying this to anyone who gets this error!