epg123 exe file quarantined by Symantec

An evolving, supported alternative to Rovi
Important Information
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf

epg123 exe file quarantined by Symantec

Post#1 » Sat Aug 19, 2017 10:19 pm

Symantec Endpoint Protection Cloud quarantined epg123utility.exe on a Windows 3 PC today when I installed the latest release v1.1.15).

Symantec's Virus/Malware/firewall/etc. security system complained specifically that WS.Reputation.1 was detected by Download Insight.

Is this utility necessary for "normal" new installations onto Win7 PCs?

Has anyone else had this issue?

Thanks,

Jim
JShort
 
Posts: 6
Joined: 8 July 2017

Post#2 » Sat Aug 19, 2017 10:33 pm

The utility file is not needed... it is only there to make it easier to upgrade from v1.0.2 and below to the current version. It's interesting that Symantec now has a problem with it even though it is the exact same file since almost February. :roll:

Basically, EPG123 doesn't have enough of a reputation, and I haven't payed for a code signing certificate, which makes it suspicious.
User avatar
garyan2
 
Posts: 2298
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#3 » Sun Aug 20, 2017 12:45 pm

I have had a problem with both V1.1.14 and 1.1.15 EPG123.exe being rejected by AVG Free virus checker when I run them. I tried to restore V1.1.13 to the epg123 directory, but it would no longer complete the WMC schedule write.
So I am currently restoring a C image - I happen to have one that is only a week or so old!
Steve
sjr56stn
 
Posts: 23
Joined: 3 March 2015
HTPC Specs: Show details

Post#4 » Sun Aug 20, 2017 2:05 pm

So I restored my C partition thus reverting to EPG123 V1.1.13, but it still doesn't complete the WMC schedule. After the 'blood line' progress bars have finished there is an error message that flashes up which I think says EPG123_v1.1.4_w7.exe has stopped working (It think - the message disappears again very quickly). I do not see a progress bar for updating the WMC schedules. Now when I try and run it again I do not get that error message, but the update of the WMC schedules doesn't run.
The trace log doesn't have any new entries since the 18th.
This stopped working when AVG Free objected to EPG123 V1.1.14 running, but I cannot understand what can be stopping it from working after I have restored a C image.
Any ideas?
Steve
sjr56stn
 
Posts: 23
Joined: 3 March 2015
HTPC Specs: Show details

Post#5 » Sun Aug 20, 2017 2:14 pm

OK I think the reason I didn't see the error message was because WMC had started to make a recording. Now that I have halted the recording a see the error message relates to EPG123Client_w7, and the error message comes as the updating WMC schedules progress bar gets to 100%.
Steve
sjr56stn
 
Posts: 23
Joined: 3 March 2015
HTPC Specs: Show details

Post#6 » Sun Aug 20, 2017 4:04 pm

Can you open EPG123 Client? If your AV software is blocking a file, sounds like it is this one.
User avatar
garyan2
 
Posts: 2298
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#7 » Sun Aug 20, 2017 4:37 pm

Gary,
I thought about file blocking and checked all the files in the EPG123 directory. A number were in fact marked as "Might be blocked" and so I unblocked them.
EPG123_Client does open and the GUI seems to work, but if I perform the EPG123 Save and Update I get the error message right at the end.
However, I have realised that the transfer of the data to the WMC schedules is mostly working, and I have two weeks of schedules for most of my channels. (One channel that I have added to the line up is empty though.) The problem may have therefore been around for some time, and I was unaware of it until I ran the EPG123 GUI and noticed the error message right at the end. This would certainly explain why my restore to a recent C Image didn't solve the problem. The issue might therefore have nothing to do with the AVG Free problem with V1.1.14 and V1.1.15.
Steve
sjr56stn
 
Posts: 23
Joined: 3 March 2015
HTPC Specs: Show details

Post#8 » Sun Aug 20, 2017 5:11 pm

.. and I am afraid I misled you over the trace.log file, which is being updated. Here are the last few lines of the most recent attempt:

[20/08/2017 16:44:02] Beginning epg123 client execution.
[20/08/2017 16:44:02] ===============================================================================
[20/08/2017 16:44:02] [ INFO] Beginning epg123 client execution. 2017-08-20 15:44:02Z
[20/08/2017 16:44:02] [ INFO] Import: True , Match: True , NoLogo: False , Force: False
[20/08/2017 16:44:02] [ INFO] epg123 client version: 1.1.13 for Win7
[20/08/2017 16:44:02] Entering importMxfFile() for file "C:\epg123\epg123.mxf"
[20/08/2017 16:44:21] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[20/08/2017 16:44:21] Exiting importMxfFile(). SUCCESS.
[20/08/2017 16:44:21] [ INFO] Matching CBBCHD to channel 204

Steve
sjr56stn
 
Posts: 23
Joined: 3 March 2015
HTPC Specs: Show details

Post#9 » Sun Aug 20, 2017 5:47 pm

sjr56stn wrote:.. and I am afraid I misled you over the trace.log file, which is being updated. Here are the last few lines of the most recent attempt:

Code: Select all
[20/08/2017 16:44:02]  Beginning epg123 client execution.
[20/08/2017 16:44:02] ===============================================================================
[20/08/2017 16:44:02] [ INFO] Beginning epg123 client execution. 2017-08-20 15:44:02Z
[20/08/2017 16:44:02] [ INFO] Import: True , Match: True , NoLogo: False , Force: False
[20/08/2017 16:44:02] [ INFO] epg123 client version: 1.1.13 for Win7
[20/08/2017 16:44:02] Entering importMxfFile() for file "C:\epg123\epg123.mxf"
[20/08/2017 16:44:21] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[20/08/2017 16:44:21] Exiting importMxfFile(). SUCCESS.
[20/08/2017 16:44:21] [ INFO] Matching CBBCHD to channel 204

Steve

Was there anything after that last entry? Something similar to the below?

Code: Select all
[8/19/2017 8:26:39 AM] [ INFO] Completed EPG123 client execution.
[8/19/2017 8:26:39 AM] [ INFO] EPG123 client execution time was 00:00:05.8301791.

If it stops abruptly, then like you said, the client has stopped working with the error message. It may be having a problem with the automatch, so I would suggest turning that off and trying again. You will have to manually match the new channel you added.
User avatar
garyan2
 
Posts: 2298
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#10 » Sun Aug 20, 2017 8:14 pm

Yes, it was shopping abruptly during the matching. I have turned off automatic matching and manually matched the new channel and its schedule is now showing in WMC. I will check tomorrow whether the overnight scheduled task worked correctly with auto-matching switched off.
Any idea why my virus checker will not permit your new V1.1.15 to run?
Steve
sjr56stn
 
Posts: 23
Joined: 3 March 2015
HTPC Specs: Show details

Post#11 » Mon Aug 21, 2017 10:27 am

Gary,
The overnight scheduled update worked without any errors (with the auto-matching feature switched off). So it looks like something in my line-ups and WMC channels was breaking your auto-matching code. Is there anything I can send you to help you to nail down the problem? (I am going to be away for a couple of weeks after tomorrow.)
Steve
sjr56stn
 
Posts: 23
Joined: 3 March 2015
HTPC Specs: Show details

Post#12 » Tue Aug 22, 2017 11:51 am

Completely remove all AV software and use the free and robust Microsoft Security Essentials. Everything else is bloatware, IMHO.
Sammy2
 
Posts: 1365
Joined: 24 August 2012
HTPC Specs: Show details


Return to EPG123



Who is online

Users browsing this forum: No registered users and 1 guest

cron