I use the web browser control in a .NET Windows Form application (not background scraping, just to display web pages to the end user); everything has been working great until recently.

I have a few clients that are having problems with the browser opening. After checking virus scanning (failure), I decided to play with the EO Worker Process executable to see if that would work.

I made a test build of my software after upgrading to 18.3.46 (no code changes, since it just activates by copying the file into the folder with the other EO*.* files).

My application works without issue with eowp.exe in the folder. I’m pretty sure these are Windows 10 machines, and I saw on this forum an issue existed with a (poor) Microsoft patch (that has since been rectified).

Here is my question: what is the downside to just always have eowp.exe installed along with my product?

I assume a negligible amount of memory. When do you recommend using eowp.exe and when not to use it? I thought maybe if the application had no interface (i.e., scraping data) it might be better to not include it. In fact, if I read the documentation correctly, eowp.exe allows the Chromium engine to access double the memory space (without any special compile switches)--seems potentially advantageous.

I’m leaning towards including it, so I do not need to deal with one off issues, but I’d like to know the negatives.