Installcore.O headache

I have the Same problem with my Macbook Pro! I was also told to go to the Mac area as well as everything else Rene was told. However, I was already in the Mac part as Rene was also. I got all the same answers to NO Avail. My AVG is also up to date and still have the same problem!

Hello Rene,
Please try to update your AVG program to to latest version and check whether it resolves the issue. Please feel free to contact us for further assistance.
Thank you.

Hello Sven,
We apologize for the inconvenience caused. I would like to keep you informed that it is a false detection by AVG program. Please uninstall(http://avgread.me/1LhhXRT) and reinstall (http://avgread.me/1ggvK09) your program, download the latest updates and then let us know the status. Thank you.

Hy guys, two days ago my up-to-date version of AVG started lighting up on my Macbook Air. It is complaining about Installcore.O, defining it as "potentially unwanted application" and recommending it to the quarantine. This is giving me a lot of headaches, as Installcore is pretty common, and removing it has rendered useless most of the applications where it was contained. Downloading and reinstalling the apps is futile, as their installer is sending off the alarm again. Applications affected in my case (up until now): Pixelmator, Intensify, PowerPhotos, iFax, Noiseless CK, Aurora HDR Pro, Diptic. From the web it seems that peolpe have problems with 1Password, too.
Does someone have any ideas on this? Unfortunately it's pretty urgent. Thanks a lot.

@ Rene W.
Rene, I'm not an AVG employee… I see you've posed your question to the dedicated AVG Mac OS support as per my previous posting.
AVG Guru

Hello Rene,
Please try to update your AVG program to to latest version and check whether it resolves the issue. Please feel free to contact us for further assistance.
Thank you.

…ah, OK. I didn't know that you're not an AVG employee - sorry. Yes, I selected the MacOS channel in the support chat, but it didn't feel like there was some Mac expert was talking to me as he or she was just asking to send these screenshots. Also this support person was not able to tell me if there's already a "master ticket" to this widely spread Installcore.O issue in their Mac AVG version.

So, as of now - there's only that workaround & no real solution for that problem. And moreover I don't know if the AVG engineering is working on a fix for this or not.

@ Rene W.
Rene, AVG Mac OS support… Please click on the following link (http://avgclick.me/AVGtechnical) and fill out your details, select as Mac OS then the name of AVG Program that you installed in your device and in description please completely explain about your issue and finally click on the 'Start Chat' option. You will start a live, online chat with one of the AVG agents.
AVG Guru

User Domonic Williamson has posted their own topic (https://support.avg.com/answers?id=906b0000000boc4AAA).
AVG Guru

Hello Sven,
We apologize for the inconvenience caused. I would like to keep you informed that it is a false detection by AVG program. Please uninstall(http://avgread.me/1LhhXRT) and reinstall (http://avgread.me/1ggvK09) your program, download the latest updates and then let us know the status. Thank you.

I've just got the info from the support team:


The update should be already released. You do not have to uninstall AVG Antivirus and then install it again. Just update your AVG Antivirus and the update will be downloaded.


I used the "Check for Updates…" function, removed the exceptions made and tested all the applications that were reported falsely yesterday. Everything works fine now - no false positives anymore. 

So thanks for the fix! I'm happy now…

A couple of minutes ago I've got the following info from the AVG support team:


The protection is not breached by any exception because the exception is created for exact file, therefore any modification of such file or any imitation of such file will be recognized as a thread.
Also we would like to inform you that we have fixed the detection of these false positives. The solution will by delivered by next update of AVG Antivirus.


So I hope that their next version update will fix this. At this point it would be helpful if the support team will respond to this thread here when the update is available - then I (and all the others with the same issue) would have the chance to update & check the behaviour of that new version…