Welcome Guest Search | Active Topics | Sign In | Register

The risk of creating the "eowp.exe" file automatically Options
Qiang
Posted: Thursday, May 25, 2017 5:32:36 AM
Rank: Advanced Member
Groups: Member

Joined: 10/10/2016
Posts: 35
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
Qiang
Posted: Friday, May 26, 2017 1:50:19 AM
Rank: Advanced Member
Groups: Member

Joined: 10/10/2016
Posts: 35
Hi EO,

Do you have any update?



Thanks & Regards,
Qiang
eo_support
Posted: Friday, May 26, 2017 10:23:48 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,067
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!
Qiang
Posted: Saturday, May 27, 2017 4:09:56 AM
Rank: Advanced Member
Groups: Member

Joined: 10/10/2016
Posts: 35
Hi EO,

Thanks for your response. The issue has been solved by build .65. And now we don't need to make sure the folder is writable. That's great! Thanks for your support.

I have one more question. Why does each version have a specific "eowp.exe" file?

Thanks & Regards,
Qiang
eo_support
Posted: Tuesday, May 30, 2017 8:58:14 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,067
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!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.