Hello Noel, and Cindy. My name is Jovana and I'm with AVG senior support. Firstly please accept my sincere apologies for the delay.
This is certainly not the usual response time, and we're doing our best to improve it.
Please note that this was a false positive detection, and I'm truly sorry for any inconvenience it may have caused you. I know how discomforting this situation appears, but I assure you this was never our intention. It often happens that after certain services and applications are updated, our antivirus blocks it until it gets double-checked.
For this specific case, all that needs to be done is to make sure virus definitions are updated. To do so, open the AVG application and click the Refresh icon next to the Virus definition in the bottom-right corner of the main application screen. Then just wait while AVG checks for virus definition updates.
In general, note that you can report false positive files, for our specialists to check them in more detail and remove the detection, at the following link: False Positive File Form
Similarly, you'll see that you can also submit a malicious sample.
Laslty, as Noel mentioned, AVG and Avast are sister companies, and the fix was implemented on both ends, once it was brought up to our attention.
I hope this clarifies and helps. Feel free to write back if you have any further issues.
Thank you both so much for your understanding and patience.
Jovana
Hello Noel,
We apologize for the inconvenience caused to you.
We will check and help you with this issue.
If possible, could you please share us the screenshot of threat detected pop-up in order to check and help you further?
For taking a screenshot, please refer to this article: https://bit.ly/3DB328d
You can post the screenshot here in your topic. Click on Answer & then click on the Image [mountain symbol] & follow the instructions.
Thank you and keep us updated.
In the past few days this was reported and rundll32.exe was secured. Now when quicken is started it reports
System.Exception: Failed to start image manager
at EO.Internal.vpsi.wxpi.hiva()
at EO.Internal.vpsi.wxpi.mccq()
This problem is being reported many times on the quicken community forums the last couple of days.
Is win32:malwatre-gen a false positive. If it is how do I reverse the protection applied to this file? Quarantine is reported empty BTW.
The last problem was fixed after an update. Now the problem just reoccurred starting on October 23.
Hello Russ,
We are sorry for the inconvenience caused. We will check and help you to resolve it. We request you to create a separate AVG community post by clicking the link below and post your questions in your own post, so that we will check with your AVG account and help you with additional support.
https://support.avg.com/support_ask
Thank you for your understanding.
Hello Noel, and Cindy. My name is Jovana and I'm with AVG senior support. Firstly please accept my sincere apologies for the delay.
This is certainly not the usual response time, and we're doing our best to improve it.
Please note that this was a false positive detection, and I'm truly sorry for any inconvenience it may have caused you. I know how discomforting this situation appears, but I assure you this was never our intention. It often happens that after certain services and applications are updated, our antivirus blocks it until it gets double-checked.
For this specific case, all that needs to be done is to make sure virus definitions are updated. To do so, open the AVG application and click the Refresh icon next to the Virus definition in the bottom-right corner of the main application screen. Then just wait while AVG checks for virus definition updates.
In general, note that you can report false positive files, for our specialists to check them in more detail and remove the detection, at the following link: False Positive File Form
Similarly, you'll see that you can also submit a malicious sample.
Laslty, as Noel mentioned, AVG and Avast are sister companies, and the fix was implemented on both ends, once it was brought up to our attention.
I hope this clarifies and helps. Feel free to write back if you have any further issues.
Thank you both so much for your understanding and patience.
Jovana
Thank you for sharing the screenshot, Noel.
It seems to be a false detection by AVG.
We have escalated this issue to our AVG senior level team and they will check and help you further.
Request your patience and understanding!
I see now that AVAST and AVG merged. If AVAST has a solution why doesn't AVG share the same solution with its users?
is there an update? Another antivirus, AVAST, has the same problem that AVG has, Are these two products related? They provided a soution by updating their database. Is this something AVG can do too?
The last problem was fixed after an update. Now the problem just reoccurred starting on October 23.