No, it’s one of the SVG we use internally that requires it. We’ll remove this dependency in next update. It doesn’t affect apps, only ExeOutput itself.
Ok. I know you guys must be busy because no one is helping me. I get one response - then nothing - then I get an email which says “Hey! If you aren’t going to post anything I’m going to close this posting!” With a great big happy face.
The truth is - ExeOutput still will not even come up and run. I am going to try to uninstall it and then reinstall it to see if maybe that will fix it.
By going back in time via the downloads - I have arrived at version2.0.0 from 2017. This installs and runs without a problem. Now to install a later version and see what happens.
Ok. I upgraded from 2.0.0 to 2.1.0 and - program will not launch. Gives the same error at that point. Removed the entire program again, now cleaning the registry.