I have the same problem:
I am having the same problem, every restare require that I repair, uninstall/reinstall AVAST to get past the lockout. The processor is plainly busy running several copies of the warning, and I have tried creating an exception to the file iqvw64e.sys without success. Is there a known fix for this issue?
I'm having the same issue, what was the answer? I'm trying to post my own question but your website keeps saying its having issues.
Hello Paul.
Thank you for contacting AVG Community Support.
We will certainly check and help you.
To proceed further, please create a separate AVG community post by clicking the link below and post your questions in your own post, so we will check with your AVG account and help you accordingly.
https://support.avg.com/support_ask
Thank you for your understanding.
Hello Noel,
Thank you for contacting AVG Community Support.
We are really sorry to know this. We'll certainly check and help you out.
It would be very beneficial if you can send me a screenshot of the blocked driver vulnerable warning so I can have a clearer picture of the issue.
You can post the screenshot here in your topic. Click on Answer & then click on the Image [mountain symbol] & follow the instructions.
Awaiting your response.
Every morning i get a message: AVG Security has blocked iqvw64e.sys due to vulnerabilities that could cause your PC's systems instability or put at risk of a hacker attack.
I have an option to make an exception but not sure if that's a good idea.
My PC is Windows 7.
How do I fix this so I don't get this message and keep my PC safe.
Hello Jon,
Thank you for contacting AVG Community Support.
I apologize for the inconvenience caused.
We will certainly check and help you.
To proceed further, please create a separate AVG community post by clicking the link below and post your questions in your own post, so we will check with your AVG account and help you accordingly.
https://support.avg.com/support_ask
Thank you for your understanding.
Hi Paul,
Thank you for contacting AVG Community.
We're glad to look into this & help you.
Please write back to us in your own post to proceed further.
Thank you in advance!
I am having the same problem, every restare require that I repair, uninstall/reinstall AVAST to get past the lockout. The processor is plainly busy running several copies of the warning, and I have tried creating an exception to the file iqvw64e.sys without success. Is there a known fix for this issue?
How is this issue fixed. Having the same problem. These posts are a year old and the issue still persists?!
Hello John,
Thank you for contacting AVG Community Support.
We will certainly check and help you with this issue.
To proceed further, please 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 accordingly.
https://support.avg.com/support_ask
Thank you and keep us updated.
Dinesh,
I think the problem is clear from the screenshot above.
I'm using Windows 10 with all the latest updates.
Please investigate.
Paul
Hello Noel,
Thank you for contacting AVG Community Support.
We are really sorry to know this. We'll certainly check and help you out.
It would be very beneficial if you can send me a screenshot of the blocked driver vulnerable warning so I can have a clearer picture of the issue.
You can post the screenshot here in your topic. Click on Answer & then click on the Image [mountain symbol] & follow the instructions.
Awaiting your response.
Hello Noel,
Thank you for reaching AVG Community Support.
We regret the inconvenience you had with getting pop ups regarding a Vulnerable driver. We will certainly help you with the issue. We've sent you an email to your registered email address. Please check for the email and revert to us.
Thank you for your understanding.
I have the same problem:
I'm having the same issue, what was the answer? I'm trying to post my own question but your website keeps saying its having issues.
How is this issue fixed. Having the same problem. These posts are a year old and the issue still persists?!