Hi EO,

In a small part of the user's computer, we found the eowp.exe file will be created in "c:\user name\AppData\Local\Temp\" folder, such as "eowp.17.0.64.0.exe" or "eowp.17.1.42.0.exe".

But we NEVER set EO.Base.Runtime.EnableEOWP to true, and those users also has "rundll32.exe" file in their computer.

It looked suspicious and we wanted to confirm why it was created? And we will be worried if our product will create a "*.exe" file on the customer computer.

I will be looking forward to your reply.



Thanks & Regards,
Qiang

Hi,

This behavior is by design. When you do not set EnableEOWP, our library will try use rundll32.exe first. However if for whatever reason that failed (usually due to the process being silently killed by a AntiVirus program), then the library will use eowp.exe.

The best way to avoid this kind of issue is to use this method to customize the name of eowp.exe:

https://www.essentialobjects.com/doc/eo.base.runtime.initworkerprocessexecutable.aspx

You can rename eowp.exe to a name that suggests it to be a part of your application and then ship that with your application. If you do not include the exe file in your distribution, InitWorkerProcessExecutable will automatically create it, however that may trigger false alarm again.

If you do rely on InitWorkerProcessExecutable to automatically create the file for you, make sure you download build .65 from our download page. In early build InitWorkerProcessExecutable may still try to re-create the file even if the file exists. In build .65 it will skip in that case.

Hope this helps. Please feel free to let us know if you still have any questions.

Thanks!

Hi,

This is because eowp.exe may change from version to version. So eowp.exe from one version may not work with the DLLs from another version.

Thanks!