Closed CodingPeak closed 8 years ago
This is nothing to worry about.
The EXE is basically just a bat file wrapped in C. Which could often be a virus of some sort. But this isn't the case with this EXE. It's just very minimalistic code as I'm not that good in C to make it seem more secure for virusscanners.
If you still feel a bit uncertain here are the source files for the exe: https://github.com/jansmolders86/mediacenterjs-windows/blob/master/executable/main.c https://github.com/jansmolders86/mediacenterjs-windows/blob/master/executable/resource.rc.
I believe you, no problem. But you should get this fixed, as this will happen to more people. And I guess this is the reason why the installation "succeeded", but wasn't completely executed, because I was missing the installation of nodejs and environment variables weren't set properly...
Yep, AVG prevents me from opening mediacenterjs.exe
Thanks for letting me know guys. I'm going to dig on the web to find out how I can validate the EXE so vrisusscanners don't see it as a threat.
For the time being you can also use the BAT file version. It does exactly the same but without the nice icon :)
https://github.com/jansmolders86/mediacenterjs-windows/blob/master/mediacenterjs.bat
If someone has any experience in signing EXE files for windows I would love to pick their brain too solve this issue! Thanks!
@Rubenvanhoeyveld @rictorres, I just compiled a new setup file with a new executable. I'm curious if this one doesn't raise the virus warning. You'll need to reinstall though, from now on, the ffmpeg path variable is permanently written during setup so the exe doesn't have to mess with that.
should this come up, please read: https://github.com/jansmolders86/mediacenterjs/wiki/User-manual:-FAQ#im-getting-a-virus-or-unknown-publisher-warning-on-windows
Not sure if this is normal...