It was OK in the begining until AVG report malware on Imageburn about a year ago. I romove it from my Windows 7 system.
I try to download Imageburn again and AVG still complain Imageburn is infected with malware.
Any alternative to Imageburn ?
Thanks in advance.
+ Reply to Thread
Results 1 to 11 of 11
Try version 2.5.7Is he gone?
It's probably considering the installer's option to install 3rd-party bloatware (which is totally bypassable) as a positive. However, Imgburn (not Imageburn!), has not had ANY malware in any legit copies of it's core app. If AVG is still complaining after a bypassed-custom install, it is AVG's mistake.
Scott"When will the rhetorical questions end?!" - George Carlin
Yes, AVG is detecting OpenCandy:
You can simply choose not to install any of the "malware" when you install imgburn. Be careful, be sure to choose selective install at each step of the process. Even better block all access OpenCandy's web site in your hosts file. That will prevent OpenCandy from contacting their servers to download the other packages. You'll never have to worry about them again (unless they add more servers).
Even better than that: block many malware sites and lots of online ads with the hosts file from Winhelp2002 (all the above urls are included):
I scan this version with AVG and no malware found.
For the nth time, with the possible exception of certain Intel processors, I don't have/ever owned anything whose name starts with "i".
I have been using 22.214.171.124 since it came out with no problems and no malware detections.
ImgBurn, you only need the two updated .EXE files: the main one, and the Preview one. I just substituted them into an already-installed, previous version IB folder. (Should they go ahead and make these OpenCandy packages more devious, a procedure this simple might no longer be sufficient.)When in Las Vegas, don't miss the Pinball Hall of Fame Museum http://www.pinballmuseum.org/ -- over 150 tables from 6+ decades of this gradually disappearing American art form.
Malwarebytes will detect the OC component in the setup file and warn you (curiously enough my resident
A/V avast! Free, even though it is set to detect PUPs, does not warn about this).
The other thing is, if you run the setup executable from the CMD line with the /nocandy switch, it supposedly bypasses OC. I'm sure this has been mentioned around here recently.
The 126.96.36.199 version works OK for me. Thanks.