I do not receive the update of windows 10 for Meltdown and I have updated it today my AVAST Free antivirus. It is normal? How can I update?
If you mean perform a Windows Update then you can download it manually (if it won’t happen automatically) by going here: http://www.catalog.update.microsoft.com/Search.aspx?q=KB4056892
Download the update for your system but please make sure you have the registry key first. Also, I’d create a restore point just in case you have issues so you can revert back before the update.
And how do I know if I have the registration key?
also be sure your W10 version is “1709”.
As far I’m concerned , no Meltdown anymore because I still have the version 1703 of W10
Go to start and search or press the windows key and R at the same time and enter “regedit” (without quotes) and then expand HKEY_LOCAL_MACHINE then SOFTWARE > Microsoft > Windows > CurrentVersion > QualityCompat, keep expanding through each of those until you get to the Quality Compat section and you should have a key with the Value and registry type within there (see below). Please don’t add the key manually as this can cause issues if done wrong. Avast is apparently ready for the update but I am not 100% yet on how to make sure.
Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD”
Yes and it happens to me in all the computers that I have avast and windows 10 1709
Well yes I have, but I do not get the update. I also have Malwarebyte but in its forum it says that yes it can.
It is possible that updates are delayed because of the amount of people downloading it.
There has been an update by Moroni, see below.
I don’t know why but I suspect it might be to do with the sheer amount of people trying to grab the update.
Ok then I’ll wait, since my friends who have Avast F…
Do your friends get the update or are they suffering from it too?
The same thing happens to me as those who have the same antivirus as me, do not receive the update.
In windows they tell me that if I have it updated against Meltdown and they say it is the update KB4054517 because it is stuck inside of it.
I’m missing the registry key despite using fully registered and functional copies of Win 10 64 (Home) 1709 and Avast Free Antivirus 17.9.2322. Any suggestions? Peter
CORRECTION: I do have the registry key (I looked in the wrong place in the registry) but MS update doesn’t provide the patch. Should I wait until Tuesday or take a chance on downloading and installing it manually?
I don’t think that’s correct. I’m pretty sure it should supersede KB4054517. I looked at their catalog and it tells you which ones it replaces.
Well then three people from the windows support have told me no, they have contacted several times to confirm and all have agreed that I have the update.
Same problem here missing the update and reg key:
Key="HKEY_LOCAL_MACHINE"Subkey=“SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat”
Value Name=“cadca5fe-87d3-4b96-b7fb-a231484277cc”
Type="REG_DWORD”
Data="0x00000000”
Avast free antivirus program version number: 17.9.2322 (build 17.9.3761.0), version of virus identifiers: 180105-0
Contents of AvastEmUpdate.ini →
[Config]
LastAppliedPatchId=371
How to get the patches?
I just discovered why some of us may not be getting the patch via MS Update even if we’ve verified that we have the required registry key. I downloaded from the Intel web site their SA-00086 chip tester that they developed specifically to determine if a user’s processor is vulnerable. I’ve attached the report for my Dell PC, which is approximately 5 yrs old. Surprise: I’m supposedly not vulnerable!! Perhaps there’s something my my registry that enables MS to detect that and determine that I don’t need a patch. You can download the tool directly from Intel at: https://downloadcenter.intel.com/download/27150?v=t The page that provides documentation is:
https://www.intel.com/content/www/us/en/support/articles/000025619/software.html Maybe you’ll be in luck also. Peter
You are vulnerable. Do not conflate the IME-bug with this issue.