Home Support

AVG Support Community

Share tips and solutions on AVG Products

Have a question?

Community topics

AVG Gurus

These community experts are here to help

  • (AB) Alan Binch
  • (BA) Borislav Angelov
  • (VB) Vladimir Bartl
  • (SK) Subhadeep Kanungo
  • (MS) Miloslav Serba
James NobodyJames Nobody 

Windows 7 Meltdown & Spectre updates

Hi,

As I'm sure you are aware, there has been two serious security issues revealed that affects all Intel-based PCs:

https://spectreattack.com/

Microsoft has released a patch (ADV180002) for Windows 7 (and other OS) that fixes the most serious of the two vulnerabilities.

However, this patch is only made available to Antivirus "partners" that have confirmed that their software does not cause issues after the patch is installed.  Apparently, some Antivirus software are using unsupported kernel calls that can cause BSOD after the patch is installed.

I have checked a few of our Windows 7 PCs running AVG Antivirus and none have the ADV180002 installed or available from Windows Update.  This would imply that you are not one of the "partners" that have confirmed your software is compatible with the patch.

Can you tell me if and when you will be updating your software so this patch can be installed?

Thanks,

James
Best Answer chosen by Jan (Avast) 
Lukas RypacekLukas Rypacek
Hi, AVG 2017 is compatible with the security patch and is adding the required registry key since yesterday. Lukas.

All Answers

Alok KumarAlok Kumar (Avast)
Hello James,
Thank you for bringing this to our notice. We are aware of the new windows update and checking it with our developers.
Once we receive an update, will post it here.
Best regards,
Alok.
Rob MelvinRob Melvin
How do you not have an official response to a major flaw that effects all of your users?  Customers have to search and search to find this obscure post about it?  All your comptitors have a released a staement or an update.  I guess I need to fill out the support request form to get any information sicne IM a paying business customer?   You would think AVG would be all over this?  This is the speardsheet from MS devolper about AV programs updating to comply with new patch. This issue came to light two days ago. AVG still has no official statement about it.....    https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?sle=true#gid=0
Rob MelvinRob Melvin
How do you not have an official response to a major flaw that effects all of your users?  Customers have to search and search to find this obscure post about it?  All your comptitors have a released a staement or an update.  I guess I need to fill out the support request form to get any information sicne IM a paying business customer?   You would think AVG would be all over this?  This is the speardsheet from MS devolper about AV programs updating to comply with new patch. This issue came to light two days ago. AVG still has no official statement about it.....    https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?sle=true#gid=0
Alan BinchAlan Binch
@ Rob Melvin
Rob, From the Alok Kumar (AVG Technologies) posting you'll see that the situ is presently being checked out by the AVG developers.
AVG Guru
Lukas RypacekLukas Rypacek
Hi, AVG 2017 is compatible with the security patch and is adding the required registry key since yesterday. Lukas.
This was selected as the best answer
m ferrarom ferraro
Hi Kukas - what about AVG business edition?
Currently at 16.161.8039
Alan BinchAlan Binch
@ m ferraro
M, General topic info.. "Business products" support.. For assistance have a look @ this AVG webpage (https://support.avg.com/business_contact_form?l=en_US). Please be informed that this Community forum basically deals with 'home' version of AVG products. Furthermore the "Business products" area has now been removed from the 'Community topics' list @ the top LHS of this page. Finally please be informed that the support for "Business products" is not now available in this Community.
AVG Guru
Alok KumarAlok Kumar (Avast)
Hello,
Yes, AVG 2017 is compatible with the Windows patch and we protect against the malware.
Best regards,
Alok.
King PodKing Pod
I have AVG IS 2017 latest version and still haven't received the meltdown patch from Windows update
Robert SkwirskRobert Skwirsk
How can you determine if you are using
Internet Security 2017 or 2018?

I purchased Internet Security 2018 Unlimited.
Where can I find this in the program?

My ABOUT, within AVG, says
Software Version 17.9.3040
I downloaded it from MyAvg Online Account
Alan BinchAlan Binch
@ King Pod
King, Please see your other posting (https://support.avg.com/answers?id=9060N000000TrmmQAC). AVG 2017 is compatible and adding the registry key since the 3rd January 2018.
AVG Guru
Mika JuntunenMika Juntunen
So AVG AntiVirus Free subscription doesn't have support for said threat?
Version 17.9.3040 and no said registry key "Qualitycompat" in place.
Guy WellsGuy Wells
@Mika Juntunen same here, no registry key for "Qualitycompat" or MS update.

AVG AV Free      v17.9.3040(x64) (Build 17.9.3761.0)
AVG Zen             v1.231.3.19448
AVG Setup          v1.226.3.18174
AVG Framework   v1.226.3.17610
Windows 10         v1709 (OS Build 16299.125)

Manual update request reports "Already up to date".
Any info about when (and what version) AVG AV Free will get the compatibility update?
Black BadgerBlack Badger

@ Alan Binch | AVG Guru

AVG - Business Support's solution is to direct us this forum.   They state that this forum is for business customers.   

I am a business customer, and was directed to this forum by the business support.   It appears no one knows what is going on.  Or if they do, there is no place to post information about the business products.

Since the AVAST has bought out AVG has AVG business been abandoned ?  If not, where are we able to discuss the business products ?  Or get support for them ?

If they want us business customers to be quiet and go away.  They should say so.   I guess the removal of the bsuiness forum and lack of communication speaks a 1000 words... 

Bill SchreiberBill Schreiber
So, to anyone from AVG on this board.... why doesn't someone from AVG get its compatability status on the only known source tracking this issue, and let all your customers breathe a little easier? AVG's response has been a classic case of what NOT to do when such a potentially damaging situation develops.

Researcher Kevin Beaumont has created a constantly updated online spreadsheet listing AV software compatibilities with the Windows patches. This is where EVERYONE is checking: https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?sle=true#gid=0

Come on AVG, show you care about your customers facing the biggest vulnerability in memory! Malwarebytes (which, BTW, is on the list as compatible) is but a click away...  
Alan BinchAlan Binch
@ Black Badger
Black, "Business products" support.. Have a look @ this AVG webpage (https://support.avg.com/business?l=en).
AVG Guru
Melissa CloudMelissa Cloud
I have AVG Ultimate. My AVG Internet Security version is v17.9.3040 (Build 17.9.3761.0) released 12/21/2017. Manual attempts to update state that it is already up to date. No registry key is present.

When will a version be available to me which does support this patch? Because the answer "AVG 2017 is compatible with the security patch and is adding the required registry key since yesterday" does not seem accurate.

I'm becoming very frustrated with all the digging around I'm having to do to find a clear and reliable answer to this. Every other anti-virus provider I've ever heard of has updated their status with the tracker for this issue and provided an easily visible public statement. I really cannot understand why AVG has not done the same.
Chris WoodChris Wood
How about AVG Free. My engine was last updated on December 21st Build 17.9.3761.0.
I just tried to update and it said it was current. How and when should I get a version downloaded that will create the regkey?

Thanks

Chris
Alan BinchAlan Binch
@ Chris Wood
Chris, Have a look @ the user Jean P. posting in this topic (https://support.avg.com/answers?id=9060N000000TrmmQAC).
AVG Guru
Chris WoodChris Wood
Sure seems a funny way to get the regkey. Tried uninstall from Windows 10 and use the AVG Repair  option. Once it completes the regkey has been created.

Think AVG need to putout a new version of the engine rather than make customers get it by the uninstall/repair method.

Chris
Byron KelleyByron Kelley
AVG has not been installing the registry key. I had to install it myself after discovering it still was not installed as of the morning of 7 Jan 18. This may be the last time I use AVG if this kind of thing continues. Don't get me wrong, I really like the product but to be the one of the last internet security companies to get on the bandwagon over something like this is simply not good for business.
Guy WellsGuy Wells
Just to confirm that going through the uninstall/repair installation worked for me.

However, I like to say to the AVG support personnel that they should listen to what the user community are saying about requesting AVG program update using the normal method, as per https://support.avg.com/SupportArticleView?l=en&urlName=AVG-Meltdown-Spectre-vulnerabilities&supportType=home, to get the registry entry does not always (if at all?) work. Rather than reiterating "AVG 2017 is compatible with the security patch and is adding the required registry key since 2017-01-03", which can be quite infuriating from a user's perspective.

I'd also suggest that you feed this back to the developers in order to investigate why this registry entry is not added via a normal update and requires a run through the installer to do so. There must be an awful lot of users out there who won't be receiving the MS update due to this (granted I'm speculating here).
AvinashAvinash (Avast) 
Guy,
I apologize for the delay in responding to you. Could you check the registry location now to verify the key is created or not? If it is not, please let us know the path where did you search for the key.
Guy WellsGuy Wells
I think my post implied the key had been created after going through the uninstall/repair process.

Here's the registry key export to confirm:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat]
"cadca5fe-87d3-4b96-b7fb-a231484277cc"=dword:00000000
 
Ask a question
Struggling with non-AVG technology? We can fix that, too!