Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: moroni on January 05, 2018, 12:21:21 PM
-
UPDATE [Jan 9] Microsoft has pushed the update to Win 8.1 as well. Users of Avast should receive the updates automatically for all the supported versions of Windows.
--------------------------------------------------
UPDATE [Jan 8] Microsoft is the pushing security updates in stages. As of now, Avast users of Win 7, Win 10 RS2 and Win 10 RS3 are getting security updates automatically, other versions will follow soon.
--------------------------------------------------
Hi everyone,
Please be aware that AVAST is compatible with the MS Security Update for the Intel Vulnerability called "Meltdown" since December 2017, and is also storing the required registry key (since January 3rd 2018). Users of AVAST should not have any issues receiving the patch via Windows Update.
More info at https://support.avast.com/en-ww/article/253/
-
Maybe I shouldn't be having trouble, but I am. I'm using Win 10 Home, 1709 (build 16299.125), Avast Free Antivirus 17.9.2322 (Build 17.9.3761.0) with virus definition 180105-0. My firewall is the Windows 10 built-in firewall left at the MS default settings. Forcing a Windows update indicates that I'm up to date. However, my last update was installed in mid-December. Similarly, forcing updates to the Avast program and virus definitions also indicates that I'm up to date. However, no sign of the MS patch for Meltdown. Suggestions please!
Peter
-
Further information, I checked my registry and do not have the key I'm supposed to have. Please advise. Peter
CORRECTION: I was looking in the wrong place in the registry. I do have the required key. However, MS update isn't providing the patch. Should I wait until Tuesday or manually download and install the patch now?
-
It looks like Microsoft is pushing the patch quite slowly (it was not offered on my computer either).
If you want to install it manually without waiting, you can get the cumulative update for Win10 from https://support.microsoft.com/en-us/help/4056892/windows-10-update-kb4056892 (https://support.microsoft.com/en-us/help/4056892/windows-10-update-kb4056892) - there is a link to Microsoft Update Catalog website.
-
Hello, I expect this fix at patch tuesday (second tuesday in month).
-
Hello, I expect this fix at patch tuesday (second tuesday in month).
This is more what I would expect of MS, whilst this is a vulnerability, in the past MS still waited until patch Tuesday and on occasion even longer before patching. As has been mentioned the actual patch for this is within a KB that includes other stuff also. So I'm not so sure how much urgency MS are putting into this.
Not to mention this isn't an immediate issue, first your computer would also have to be infected to take advantage of the vulnerability.
-
The point is the vulnerability can be exploited using JavaScripts embedded in malicious sites. The patch from MS also contains fixes to IE and Edge, meaning MS should be interested in releasing it to all end users ASAP.
Mozilla have released a hotfix with adjustments for browser config to minimize the exploitation possibilities, and Google have published their settings recommendations. IE and Edge can't be updated separately though, given how MS now handles patching.
-
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
-
Got tired of waiting.
Downloaded and Installed Cumulative Update for Win 10 64Bit from MS.
All went smoothly. :)
-
@ pdkent2002
It isn't so much what you have in registry to determine your need for the patch, but that your AV would support the patch if issued.
The Intel tool is checking your CPU to see if it is vulnerable and it is in more 'modern' CPUs with the vulnerability/flaw. I suspect your CPU, like mine (Core2Duo E8300) predates this determination of a modern CPU.
-
Surprise: I'm supposedly not vulnerable!!
Yes you are!
This tool checks for a vulnerability in the Intel Management Engine. That is a completely separate problem from both Meltdown and Spectre.
-
Still not getting the Win10 patches for this security issue - on every PC I have Avast installed on. Avast is up to date on all of them. I have rebooted them multiple times. So, I take issue with your confidence that Avast is compatible!
I removed Avast from one of them and guess what - after rebooting the system (required to complete the uninstall of Avast) - UPDATES began immediately.
And for those with Malwarebytes installed as well (I have it on all my PC's), the computer I mention here has Malwarebytes installed and running before, during and after deleting Avast. No issues with that software preventing the update.
MS has no vested interest in putting people in a queue for this particular update. It was ready as of yesterday, your computer should have already downloaded and installed it. If yours did not, your antivirus is most likely getting in the way. I do not condone uninstalling any AntiVirus product as I did. I only did it to find out if Avast was stopping the update. You can draw your own conclusions.
EDIT: add additional info regarding Malwarebytes and remove some salty language :)
UPDATE: I responded to some questions, you can find them on Page 3, Reply #34 (link below)
click here (https://forum.avast.com/index.php?topic=212691.msg1439748#msg1439748)
-
Ihave Avast Pro antivirus 17.9.2322 build 17.9.3761.0 but do not have Allow Regkey. Even i do not have file QualityCompat!!! I do not understand.
-
I removed Avast from one of them and guess what - after rebooting the system (required to complete the uninstall of Avast) - UPDATES began immediately.
And for those with Malwarebytes installed as well (I have it on all my PC's), the computer I mention here has Malwarebytes installed and running before, during and after deleting Avast. No issues with that software preventing the update.
Exactly what happened for me, and I use MBAM as well.
-
Still not getting the Win10 patches for this security issue - on every PC I have Avast installed on. Avast is up to date on all of them. I have rebooted them multiple times. So, I take issue with your confidence that Avast is compatible!
I removed Avast from one of them and guess what - after rebooting the system (required to complete the uninstall of Avast) - UPDATES began immediately.
And for those with Malwarebytes installed as well (I have it on all my PC's), the computer I mention here has Malwarebytes installed and running before, during and after deleting Avast. No issues with that software preventing the update.
MS has no vested interest in putting people in a queue for this particular update. It was ready as of yesterday, your computer should have already downloaded and installed it. If yours did not, your antivirus is most likely getting in the way. I do not condone uninstalling any AntiVirus product as I did. I only did it to find out if Avast was stopping the update. You can draw your own conclusions.
EDIT: add additional info regarding Malwarebytes and remove some salty lanquage :)
I too have Malwarebytes and Avast. Like you I uninstalled Avast and left Malwarebytes installed. I have Win 10 build 1709 (Fall Creators Update). After my computer restarted I did an manual update check and immediately the update started downloading and installed perfectly. Apparently Windows Defender is the component that Microsoft requires for the security patch to work correctly. I am leaving Avast uninstalled for now.
-
rjsattler , TwasSnood , safeman
Didn't you tried "passive mode" rather than uninstalling avast ?
-
Also ended up installing the patch from Microsoft Update Catalog for Win10 1709:
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4056892
It seem to be the most reliable way.
Something is clearly wrong with Windows Update. Searching for info about KB4056892 not being offered by WU, I found reddit posts stating that some systems with Windows Defender only, didn't receive the update either. It looks like MS tried some new thing to avoid system disruption due to early release of the update, which isn't working properly...
-
avast, can you please test this. You have users stating that they have the latest version of your software installed, have verified that the registry key exists, but are not able to get the MS update until they uninstall avast antivirus, at which point they immediately are able to download the update through the normal Windows Update mechanism. You should be able to reproduce this issue and offer a solution.
-
Surprise: I'm supposedly not vulnerable!!
Doesn't this piece of software detect vulnerabilities in IME only? That's quite different from current problems.
-
Surprise: I'm supposedly not vulnerable!!
Yes you are!
This tool checks for a vulnerability in the Intel Management Engine. That is a completely separate problem from both Meltdown and Spectre.
This^
The IMEI vulnerability is a whole other issue than Meltdown and Spectre
-
For all of you that uninstalled avast and then managed to download the microsoft patch, did you reinstalled avast without issue afterwards? Another option I am thinking at would be to stop using avast and use another anti-virus...
I am a bit surprised that no one from avast is communicating on this issue...
-
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
The tool doesn't support MS-systems below W7!
;)
=Snake=
-
Still waiting for that registry key. Why am I not getting the micro-update? on windows 7 and using avast free.
-
Removed Avast on my newer Intel I7 based laptop, and did receive the update right after restart after Defender was activated, have not tried reinstalling Avast Free yet, but I might, as rest of the systems using Avast Free, Desktop did it manually with the windows catalog update way
don't know why couldn't get it from WIndows update with Avast installed, reg key was there, so makes no sense, Malwarebytes supposedly was up to date the program said
-
Hi,
if you have required registry value in QualityCompat key, then there is nothing more Avast can do, because Microsoft is controlling Windows update process, so please don't panic if the update was not delivered yet. It was not delivered to my development PC (no AV installed) too, although I was trying to check for update manually multiple time.
-
Hi,
if you have required registry value in QualityCompat key, then there is nothing more Avast can do, because Microsoft is controlling Windows update process, so please don't panic if the update was not delivered yet. It was not delivered to my development PC (no AV installed) too, although I was trying to check for update manually multiple time.
I'll wait and see what happens on patch Tuesday.
-
Hi,
if you have required registry value in QualityCompat key, then there is nothing more Avast can do, because Microsoft is controlling Windows update process, so please don't panic if the update was not delivered yet. It was not delivered to my development PC (no AV installed) too, although I was trying to check for update manually multiple time.
How do I obtain the key?
-
Still waiting for that registry key. Why am I not getting the micro-update? on windows 7 and using avast free.
I have the registry key for Windows 7, but not Windows 10. I can think of three options.
1. Uninstall / reinstall Avast! to see if the registry key is created
2. Uninstall Avast! and update Windows 10
3. Uninstall Avast!, update Windows 10, reinstall Avast!
Thoughts about how to proceed?
-
So would it be safe to reinstall Avast on machine I removed it from to obtain the update yesterday or should I wait til after Tuesday to do that?
-
Still waiting for that registry key. Why am I not getting the micro-update? on windows 7 and using avast free.
I have the registry key for Windows 7, but not Windows 10. I can think of three options.
1. Uninstall / reinstall Avast! to see if the registry key is created
2. Uninstall Avast! and update Windows 10
3. Uninstall Avast!, update Windows 10, reinstall Avast!
Thoughts about how to proceed?
I did item 1 above and the registry key has been created. I checked for updates and none were found. I suppose that I will wait for patch Tuesday and see if my machine catches any updates then.
-
I have Avast and MalwareBytes.
I am on the Fall CU Windows 10.
No install of the MS patch until I uninstalled Avast and replaced it with Avira. Instantly the patch download became available so there is clearly still an issue with Avast (BTW I had Free, but I followed a link from the Free forum over here as it appears that prem customers are also suffering)
-
i have the key in registry
Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD”
BUT, its data is set to zero... does the data of the key value matter in any way? should it be set to 1? should i mess with it?
my Avast is updated but windows 10 x64 1709 still won't detect and offer to install the update... maybe the data of the key is the problem?
tested on 2 computers:
-notebook with I5-6200U cpu
-desktop with I5-3570 cpu
-
Further information, I checked my registry and do not have the key I'm supposed to have. Please advise. Peter
CORRECTION: I was looking in the wrong place in the registry. I do have the required key. However, MS update isn't providing the patch. Should I wait until Tuesday or manually download and install the patch now?
-
Right after uninstalling Avast and checking for updates.
-
rjsattler , TwasSnood , safeman
Didn't you tried "passive mode" rather than uninstalling avast ?
No I didn't try passive mode. I can try that on my other PC's running Avast that still aren't getting the update. And for those that have asked, I have not yet re-installed Avast on the computers I uninstalled the program from.
We know Microsoft is looking for antivirus programs before attempting to even download the patch. Many others have reported having an issue with other AV programs. I simply removed the roadblock as I saw it. We also know that Microsoft has made this patch a priority, therefore users should not expect to wait for the patch as if they are in a queue. If you are running Win10, the patch is available NOW. If you are running any version previous to Win10 (8.1, 8, 7), that patch will be coming on Patch Tuesday (Jan 9, 2018).
I will update this message after trying passive mode on the other PC's running Avast.
UPDATE: As suggested, I configured Avast for Passive Mode on the PC's with Avast still running on them. In both cases, the exact same result occurred: After the obligatory reboot to enable the changes to Avast, I went to Settings, then Update & Security, and clicked on the Check for Update button. Windows Update showed an update was available (it is the correct one) and downloaded the file. It then stated it was starting the installation and STOPPED before the update was complete. "Your device is up to date. Last checked: Today 7:10 PM". Further investigation shows that the patch was NOT installed.
In conclusion, Passive Mode does not resolve the problem, at least on my PC's. It appears that Microsoft sees that an antivirus is not actively monitoring the system and downloads the patch. But in the process of installing it, maybe it finds the presence of an AV program and fails so it doesn't potentially brick the system. This is just conjecture on my part based on research I've done on the problem today. YMMV.
-
Hello,
I installed a fresh 1709 build today, installed avast and did all windows updates however noticed KB4056892 didnt show up at all, even after updating my Avast to lastest versions etc.
I then decided to download and manually install the KB4056892 patch from windows catalog, I did not check my qualitycompat reg thing prior to doing this, the patch installed without issue.
Can somebody please let me know if I've done the correct procedure? thanks
-
i have the registry setting but did not receive the update from MS... decided to download it manually from the catalog and discovered there are actually TWO updates.. one of them (KB4058702) updates the updating system itself and should be installed before the other - Servicing stack update for Windows 10 Version 1709: January 3, 2018
https://www.catalog.update.microsoft.com/Search.aspx?q=1709%202018%20x64%2010
i'm currently installing 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892)
will come back and edit this after it finishes correctly
edit: back after reboot, no BSODs so far and avast is running, even ran a smart scan :)
https://support.microsoft.com/en-gb/help/4056892/windows-10-update-kb4056892
-
No update with Avast installed. Removed Avast to change from Beta to Regular version.
A few minutes after the reboot, I saw this
(https://screencast-o-matic.com/screenshots/u/Lh/1515236721713-72366.png)
Rebooted and the update had been applied
(https://screencast-o-matic.com/screenshots/u/Lh/1515236334355-95715.png)
This needs to be addressed. I've already posted this on the developers channel
-
The support of Windows has told me that it will be progressively implemented throughout these days, I hope that is so. It's already on the way, with Avast Premiere two and a half weeks ago and you do not have to update it. I hope that what Windows has told me is true.
-
Here in Windows 10 the key in de register was missing.
After Avast repair (+reboot) the key appeared.
But I still did not get KB4056892.
Also running Windows update troubleshooter did not help.
IntelSA00086DetectTool say I am vulnerable !!
Any ideas ?
Do I wait till next Tuesday ?
Avast Repair > Control Panel > Programs and Features > Avast Antivirus > Change - from the next window select Repair.
-
Hi.
These days I had three laptops and one pc in my house, two without avast installed and two with avast (pc with avast internet security & portable with free avast).
The two laptops without avast have received the update on the same day three except those that have avast installed.
Well, after reading this post I decided to uninstall avast and when restarting I had the update available, I installed it and at the moment without problems.
Now my question is the following ¿reinstall avast?, I hope ?, I find it annoying that I pay for extra protection and that "protection" is what prevents my equipment from being safe.
I repeat my question reinstall avast? or what we do, greetings to all.
-
Same here:
- 2 PCs, both with Avast, and both had the expeceted registry key set by Avast last micro-update.
- none had the Microsoft KB proposed by Windows Update
- removed Avast from one of the 2 PCs, and I had the Microsoft Update proposed
My question is: is there actually someone who had the Microsoft Update proposed with Avast installed ?
(I mean, if there is at least one person, then it could at least mean that things are "normal" - slow but "normal". If absolutely no one has had an update with Avast installed, then it's time for serious questions)
-
I have a friend with another antivirus installed (avg) the problem is the same, there is no update.
Maybe the update has some relationship with windows defender and being disabled by having another antivirus running is nullifying the update (it's my guess).
-
For all those who don't have the update appearing in windows updates.... just install the update manually from the windows catalog, works with avast installed and no problems, no need to uninstall avast or wait for windows to push the update out.
-
For all those who don't have the update appearing in windows updates.... just install the update manually from the windows catalog, works with avast installed and no problems, no need to uninstall avast or wait for windows to push the update out.
It may work but it isn't right and needs to be addressed.
-
Now my question is the following ¿reinstall avast?, I hope ?, I find it annoying that I pay for extra protection and that "protection" is what prevents my equipment from being safe.
I repeat my question reinstall avast? or what we do, greetings to all.
Reinstall it. It works just fine with the patch.
This is probably one-time event that MS released a patch which is installed selectively. They are also known to mess up with Windows Update since Windows 10 (e.g. with recent Fall Creators Update installed automatically even if you explicitly set Windows Update to defer it). On the other hand, I still think Avast should investigate it though from their side and maybe work closer with MS to resolve it in future.
In past with Creators Update, Avast used to block Microsoft Malicious Software Removal tool, and disable Windows Defender Periodic scanning, with every single Avast update. Oddly enough the problem started after one of Microsoft patches, and was fixed with Fall Creators Update (although if you upgraded from CU to FCU you might still be unable to run MRT.exe). Same Avast version produced different results on different Windows 10 versions. There is probably something in Avast that MS doesn't like, but its purpose is to protect us from malicious software, not to be liked by Microsoft.
Nevertheless, perhaps Avast could push this critical Windows Update on its own, using their emergency updater or the software updater component? That would immediately solve all the problems concerning the January MS Update.
-
I think so, this should not be the case, it serves as a quick solution, not a definitive one.
-
in theory this Tuesday there will be an important security update, maybe it is convenient that all those who have uninstalled avast wait for that update to arrive, the windows defender does not seem bad, for waiting a couple of days nothing should happen (I think)
-
in theory this Tuesday there will be an important security update, maybe it is convenient that all those who have uninstalled avast wait for that update to arrive, the windows defender does not seem bad, for waiting a couple of days nothing should happen (I think)
The MS update related to the inlet chip problem was dated 1/3/2018
-
You would think the update would have been distributed smoothly from the onset. :-\
I downloaded and installed the Cumulative Update for Win 10 64 Bit from MS Catalog and all went very well
-
My question is: is there actually someone who had the Microsoft Update proposed with Avast installed ?
(I mean, if there is at least one person, then it could at least mean that things are "normal" - slow but "normal". If absolutely no one has had an update with Avast installed, then it's time for serious questions)
Nope, not yet. :( (Avast is in contact with MS, though...)
-
The MS update related to the inlet chip problem was dated 1/3/2018
The coming Tuesday is going to be the usual patch Tuesday though. MS is likely to release another update that day, hopefully with fixes discovered after January 3rd. Since in Win10 the new update should contain all previous fixes, it would also contain patches for Meltdown.
-
But then, what do we have Avast that we have to do to receive this update? Avast has contacted Microsoft to see what happens? For my part I will wait until Tuesday to see if it arrives, and if I do not install it manually.
-
I got tired of waiting and uninstalled Avast on my primary/desktop PC. (I'd been needing to do that anyway to get rid of a scheduled Quick Scan which, since Avast removed the Quick Scan feature, I could neither modify nor remove...SIGH. A+ work, Avast.) Upon reboot, WU immediately found & downloaded the update. It's now installed and my PC is still functioning normally.
My laptop, which still has Avast installed, still cannot find the update. I'll probably do the same removal/update dance on it when I have the time and energy. Or wait until Patch Tuesday and see what happens then.
I'm still debating reinstalling Avast on the desktop. This issue + unwanted feature creep + the Quick Scan issue have turned me off Avast a bit, tbh.
-
I got tired of waiting and uninstalled Avast on my primary/desktop PC. (I'd been needing to do that anyway to get rid of a scheduled Quick Scan which, since Avast removed the Quick Scan feature, I could neither modify nor remove...SIGH. A+ work, Avast.) Upon reboot, WU immediately found & downloaded the update. It's now installed and my PC is still functioning normally.
My laptop, which still has Avast installed, still cannot find the update. I'll probably do the same removal/update dance on it when I have the time and energy. Or wait until Patch Tuesday and see what happens then.
I'm still debating reinstalling Avast on the desktop. This issue + unwanted feature creep + the Quick Scan issue have turned me off Avast a bit, tbh.
I did the uninstall / install Microsoft update dance as well on my Windows 10 laptop.
After the update (but before reinstalling Avast!), I ran a quick and dirty benchmark. I didn't see much if any change in performance. I suspect that if I stress test MySQL on the laptop I'll lose about 10% performance. Since it's a development machine, I'm not too concerned at this point.
I reinstalled Avast! after the benchmark, and then rebooted the system. I haven't experienced any issues as of yet, but I've not stressed the environment. I have MySQL and Apache HTTPD running on the machine, so I'll do some development work, start up Tomcat (a Java servlet container), and then test. I don't anticipate any issues.
I will wait for patch Tuesday for my desktop systems since they're both running Windows 7. If the updates don't happen then, I'll do the Avast! uninstall and re-install dance for them as well.
Hopefully Avast! and Microsoft will have a conversation to get this straightened out soon. I don't want to uninstall and re-install Avast! for every major Windows 7 / 10 update.
TL;DR version:
1. Uninstall Avast! / reboot
2. Install Microsoft updates / reboot
3. Benchmark
4. Install Avast! / reboot
5. (knock on wood - no issues yet)
-
Well got the update installed on all household PC's
Each one had to remove Avast just to see the update though via Windows update, I hope that isn't the new trend for Windows 10 updates, right now I left Avast out on all of them, til I see what happens on Tuesday, then will decide if reinstalling or not at that point I guess.
Thankfully only 2 Windows 10 Desktops to do that with, and 1 laptop, can't imagine 4-5 machines going thru the hassle of removing, cleaning up, installing the update, reboot again
-
The following comes from Avast:This has been escalated to Avast's contact at Microsoft. Avast has done everything that Microsoft required, but the update is still not showing up. Until we resolve the issue with Microsoft, people can apply the patch that can be downloaded directly from http://www.catalog.update.microsoft.com/Search.aspx?q=KB4056892 (http://www.catalog.update.microsoft.com/Search.aspx?q=KB4056892) (link valid for Win10 1709). I know it’s a pain, hopefully it will get rolled out automatically to all users soon.
Apparently Avast isn't the only one with these same issues.
https://forum.eset.com/topic/14254-eset-and-kb4056892/
https://forum.kaspersky.com/index.php?/topic/385249-is-kav-kis-1800405f-working-with-windows-10-new-patch-for-meltdown-spectre-bugs/ (https://forum.kaspersky.com/index.php?/topic/385249-is-kav-kis-1800405f-working-with-windows-10-new-patch-for-meltdown-spectre-bugs/)
-
Avast Free does not permit successful installation of the two new MS update patches for XP!
See http://www.msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?do=findComment&comment=1149126 (http://www.msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?do=findComment&comment=1149126)
(and go backwards from that post).
-
I'm a Windows 7 user on a 64 bit system and I'm not seeing the registry key needed to allow for the Microsoft update. My copy of Avast free is the latest version and I tried repairing Avast, but the key is still absent!
-
I'm a Windows 7 user on a 64 bit system and I'm not seeing the registry key needed to allow for the Microsoft update. My copy of Avast free is the latest version and I tried repairing Avast, but the key is still absent!
I had to download a new installer from Avast!, uninstall the current version, and then reinstall it using the freshly downloaded installer in order for the registry key to appear.
This didn't happen on my Windows 7 systems. The registry entries were already present on those machines. I'll see if they get the Windows 7updates on Tuesday.
-
I am waiting for Tuesday and I also wait for Avast for some type of notification notifying that the problem is solved.
I find it annoying to pay for the internet security and that instead of protect unprotect the pc.
The antivirus companies in general can not have this type of failures, because windows defend according to the read works quite well and may not return to external antivirus.
-
Anyway you have to be aware that this update has been done extremely fast and I think that it has not given time to all the antivirus companies to have their product ready.
-
Anyway you have to be aware that this update has been done extremely fast and I think that it has not given time to all the antivirus companies to have their product ready.
It's a Microsoft problem.
The following comes from Avast:This has been escalated to Avast's contact at Microsoft. Avast has done everything that Microsoft required, but the update is still not showing up. Until we resolve the issue with Microsoft, people can apply the patch that can be downloaded directly from http://www.catalog.update.microsoft.com/Search.aspx?q=KB4056892 (http://www.catalog.update.microsoft.com/Search.aspx?q=KB4056892) (link valid for Win10 1709). I know it’s a pain, hopefully it will get rolled out automatically to all users soon.
Apparently Avast isn't the only one with these same issues.
https://forum.eset.com/topic/14254-eset-and-kb4056892/ (https://forum.eset.com/topic/14254-eset-and-kb4056892/)
https://forum.kaspersky.com/index.php?/topic/385249-is-kav-kis-1800405f-working-with-windows-10-new-patch-for-meltdown-spectre-bugs/ (https://forum.kaspersky.com/index.php?/topic/385249-is-kav-kis-1800405f-working-with-windows-10-new-patch-for-meltdown-spectre-bugs/)
-
I'm a Windows 7 user on a 64 bit system and I'm not seeing the registry key needed to allow for the Microsoft update. My copy of Avast free is the latest version and I tried repairing Avast, but the key is still absent!
I had to download a new installer from Avast!, uninstall the current version, and then reinstall it using the freshly downloaded installer in order for the registry key to appear.
This didn't happen on my Windows 7 systems. The registry entries were already present on those machines. I'll see if they get the Windows 7updates on Tuesday.
Well, we wait for news to see what happens.
-
If you are running Win10, the patch is available NOW. If you are running any version previous to Win10 (8.1, 8, 7), that patch will be coming on Patch Tuesday (Jan 9, 2018).
Other patches should also be already out - I've downloaded the one for Windows 7.
-
As far I'm concerned , I have updated W10 from 1703 to 1709 last week
Don't have kb4056892 to download neither installed (no more directly from catalog)
But when I have a look for W10 built version it is indicated "16299.192"
Does it mean that the patch was applied directly during the switch from 1703 to 1709 and that it is normal that the kb4056892 does not appear any more anywhere (to download and installed)?
nb:I also have right QualityCompat key in my registry
-
As far I'm concerned , I have updated W10 from 1703 to 1709 last week
Don't have kb4056892 to download neither installed (no more directly from catalog)
But when I have a look for W10 built version it is indicated "16299.192"
Does it mean that the patch was applied directly during the switch from 1703 to 1709 and that it is normal that the kb4056892 does not appear any more anywhere (to download and installed)?
nb:I also have right QualityCompat key in my registry
I highly doubt that since the update in question is dated as 1/3/2018
-
As far I'm concerned , I have updated W10 from 1703 to 1709 last week
Don't have kb4056892 to download neither installed (no more directly from catalog)
But when I have a look for W10 built version it is indicated "16299.192"
Does it mean that the patch was applied directly during the switch from 1703 to 1709 and that it is normal that the kb4056892 does not appear any more anywhere (to download and installed)?
nb:I also have right QualityCompat key in my registry
If you do not get the update automatically you will have to do it manually, or uninstall avast and use windows update.
-
https://support.avast.com/en-us/article/Meltdown-Spectre-vulnerability/
I found this information about the update. But it refers only to windows 10 what about windows 7 ? How do I check if i´ve got the new registry key ?
I have run windows update and it says there is no new updates for the computer. I´m running windows 7 home premium.
Yesterday when I started up my other pc with McAfee internet security installed I got the new microsoft security update downloaded and installed. But on this pc with windows 7 home premium and avast antivirus pro nothing is showing up. Any suggestions ?
-
No updates on my Win 7 machine either, or my wife's. We both have the registry key, both have updated avast! and Malwarebytes. I can only imagine this is something avast! has been slow to deal with.
Also, our motherboards are both really old. I have a cheapy MSI B85M-P33. Presumably I'll be waiting a good while for firmware updates there; the MSI website only mentions some gaming series' at the moment.
-
on this pc with windows 7 home premium and avast antivirus pro nothing is showing up. Any suggestions ?
No updates on my Win 7 machine either, or my wife's. We both have the registry key, both have updated avast! and Malwarebytes.
Just download this patch manually.
Patch for Windows 7 is already out in Microsoft Update Catalog
https://support.microsoft.com/en-us/help/4009469/windows-7-sp1-windows-server-2008-r2-sp1-update-history
Download whichever suits you better.
January 4, 2018—KB4056894 (Monthly Rollup)
info: https://support.microsoft.com/en-us/help/4056894
download: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4056894
OR
January 3, 2018—KB4056897 (Security-only update)
info: https://support.microsoft.com/en-us/help/4056897
download: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4056897
-
No updates on my Win 7 machine either, or my wife's. We both have the registry key, both have updated avast! and Malwarebytes. I can only imagine this is something avast! has been slow to deal with.
Also, our motherboards are both really old. I have a cheapy MSI B85M-P33. Presumably I'll be waiting a good while for firmware updates there; the MSI website only mentions some gaming series' at the moment.
If you have a very old motherboard, then the likelihood is you would have an old CPU also. This vulnerability is as far as I can tell is meant to be for the modern range of CPUs. That said I haven't found a source that specifically reports what CPUs are affected.
-
If you have a very old motherboard, then the likelihood is you would have an old CPU also. This vulnerability is as far as I can tell is meant to be for the modern range of CPUs. That said I haven't found a source that specifically reports what CPUs are affected.
I did have a link but can't yet find it. I have a Core i5 which was definitely on the list (as were the others in the range, of course). Since it was a small company that made the PC I have to find the patches manually, but yes, it seems at the moment the MSI website only lists some gaming 100, 200 and 300 series for BIOS patches; mine hasn't been touched for nearly three years.
My wife has an HP Pavilion but her particular one doesn't seem to be listed on HP's support site, just other (presumably newer) versions. She has an AMD processor so perhaps it's less important. Still, it's frustrating not being able to update either of those nor having the Win 7 update listed (I'd rather wait for that if possible. If it doesn't show for us on Tuesday I guess I'll manually do it, but neither of us are tech-savvy); I just feel sort of afloat.
-
https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability (https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability))
A slide from my current presentation
-
A slide from my current presentation
Your slide is about Intel ME vulnerabilities, not about Meltdown nor Spectre.
-
If you have a very old motherboard, then the likelihood is you would have an old CPU also. This vulnerability is as far as I can tell is meant to be for the modern range of CPUs. That said I haven't found a source that specifically reports what CPUs are affected.
Hi Dave, here you go: https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr
-
A slide from my current presentation
Your slide is about Intel ME vulnerabilities, not about Meltdown nor Spectre.
It's what Intel put out ???
-
A slide from my current presentation
Your slide is about Intel ME vulnerabilities, not about Meltdown nor Spectre.
It's what Intel put out ???
No Bob, Lexor is right. Not related to the bug discussed here.
-
It's what Intel put out ???
Here is more about Intel ME problems - it was previous year, not now.
https://security-center.intel.com/advisory.aspx?intelid=intel-sa-00086&languageid=en-fr
-
As far I'm concerned , I have updated W10 from 1703 to 1709 last week
Don't have kb4056892 to download neither installed (no more directly from catalog)
But when I have a look for W10 built version it is indicated "16299.192"
Does it mean that the patch was applied directly during the switch from 1703 to 1709 and that it is normal that the kb4056892 does not appear any more anywhere (to download and installed)?
nb:I also have right QualityCompat key in my registry
I highly doubt that since the update in question is dated as 1/3/2018
When I said last week it was more precisely the 1/4/2018 ,...,so already after the patch ;)
if I took care to specify that my built was the "16299.192" is because I read (in french) about this update Here (https://www.ginjfo.com/actualites/logiciels/windows-10/windows-10-microsoft-publie-la-mise-jour-cumulative-kb4056892-bilan-20180104) that it allows the OS to upgrade to version 16299.192.
In french : "L’installation de KB4056892 permet à l’OS d’évoluer vers la version 16299.192."
since the update of my OS in version 16299.192 has been done, I deduce that the patch is included in this new built , no ?
-
As far I'm concerned , I have updated W10 from 1703 to 1709 last week
Don't have kb4056892 to download neither installed (no more directly from catalog)
But when I have a look for W10 built version it is indicated "16299.192"
Does it mean that the patch was applied directly during the switch from 1703 to 1709 and that it is normal that the kb4056892 does not appear any more anywhere (to download and installed)?
nb:I also have right QualityCompat key in my registry
I highly doubt that since the update in question is dated as 1/3/2018
When I said last week it was more precisely the 1/4/2018 ,...,so already after the patch ;)
if I took care to specify that my built was the "16299.192" is because I read (in french) about this update Here (https://www.ginjfo.com/actualites/logiciels/windows-10/windows-10-microsoft-publie-la-mise-jour-cumulative-kb4056892-bilan-20180104) that it allows the OS to upgrade to version 16299.192.
In french : "L’installation de KB4056892 permet à l’OS d’évoluer vers la version 16299.192."
since the update of my OS in version 16299.192 has been done, I deduce that the patch is included in this new built , no ?
If you already have Build "16299.192" you already have the update, the previous Build is "16299.125".
-
No updates on my Win 7 machine either, or my wife's. We both have the registry key, both have updated avast! and Malwarebytes. I can only imagine this is something avast! has been slow to deal with.
Also, our motherboards are both really old. I have a cheapy MSI B85M-P33. Presumably I'll be waiting a good while for firmware updates there; the MSI website only mentions some gaming series' at the moment.
If you have a very old motherboard, then the likelihood is you would have an old CPU also. This vulnerability is as far as I can tell is meant to be for the modern range of CPUs. That said I haven't found a source that specifically reports what CPUs are affected.
I just had the 2 patches related to Meltdown for my xp yet with a very old CPU (but INTEL PIV) with old motherboard (P4C800E) ,
On the other hand, no patch proposed on my w7 and W8.1 with AMD CPU
So I think it's more of a manufacturer issue than obsolecense
-
https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability (https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability))
A slide from my current presentation
There appears to be a typo in your WiKi link https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability) (https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)) missing closed bracket.
-
If you have a very old motherboard, then the likelihood is you would have an old CPU also. This vulnerability is as far as I can tell is meant to be for the modern range of CPUs. That said I haven't found a source that specifically reports what CPUs are affected.
Hi Dave, here you go: https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr
Thank you.
-
Presumably I just keep checking the MSI website to update the BIOS if/when my motherboard eventually has a firmware update. Like I said my computer isn't from a large company and isn't supported; they basically just pre-made from various components so it's a bit of a DIY situation rather than going to them for installers.
As written my wife's is HP and isn't listed on their support page (lots are. Huh).
-
Presumably I just keep checking the MSI website to update the BIOS if/when my motherboard eventually has a firmware update. Like I said my computer isn't from a large company and isn't supported; they basically just pre-made from various components so it's a bit of a DIY situation rather than going to them for installers.
As written my wife's is HP and isn't listed on their support page (lots are. Huh).
I don't know who would be responsible for the update, as the CPU is a component and not an integral part of the MB and again it would depend on if your CPU is effected by this.
-
I don't know who would be responsible for the update, as the CPU is a component and not an integral part of the MB and again it would depend on if your CPU is effected by this.
Yes, the Core i5 is on the affected list. My computer was made by some company called CyberPowerPC. It's just some five+ year old cheaper-end computer and is not listed on their website or anything. If I don't get the update from MSI I doubt I could get it from CyberPowerPC, that's for sure. As I wrote before I found out the motherboard type (B85M-P33) but that's as far as I got.
-
I don't know who would be responsible for the update, as the CPU is a component and not an integral part of the MB and again it would depend on if your CPU is effected by this.
Yes, the Core i5 is on the affected list. My computer was made by some company called CyberPowerPC. It's just some five+ year old cheaper-end computer and is not listed on their website or anything. If I don't get the update from MSI I doubt I could get it from CyberPowerPC, that's for sure. As I wrote before I found out the motherboard type (B85M-P33) but that's as far as I got.
Is this your motherboard?: https://www.msi.com/Motherboard/support/B85M-P33
-
I don't know who would be responsible for the update, as the CPU is a component and not an integral part of the MB and again it would depend on if your CPU is effected by this.
Yes, the Core i5 is on the affected list. My computer was made by some company called CyberPowerPC. It's just some five+ year old cheaper-end computer and is not listed on their website or anything. If I don't get the update from MSI I doubt I could get it from CyberPowerPC, that's for sure. As I wrote before I found out the motherboard type (B85M-P33) but that's as far as I got.
If I remember rightly my PC was custom built by them also even longer ago than yours and I don't believe my Intel Core2Duo E8300 is on the affected list.
-
https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability (https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability))
A slide from my current presentation
Intel-SA-00086 Detection Tool does not seem to work with winxp ("... is not a valid win32 application"). :-[
However , works on my w7 (AMD) => not affected
-
Has anybody with both avast! and Windows 7 gotten the Windows Update automatically yet, by the way?
Is this your motherboard?: https://www.msi.com/Motherboard/support/B85M-P33
It is. No updates for this but the fact it's listed generally means hopefully at some point I'll be able to update from there (although that'll mean learning how to even do that!). I guess they feel newer motherboards take priority. It's a bit daunting I'll have to do it myself. I'm not really sure what it involves, or if there's multiple steps/installers.
If I remember rightly my PC was custom built by them also even longer ago than yours and I don't believe my Intel Core2Duo E8300 is on the affected list.
Lucky! I mean I guess, hah. But yes, all the Core iX's seem to be affected.
My wife has an HP Pavilion. Apparently that's a range as there's a bunch called that, but hers is an older p7-1234. No update on the product page (https://support.hp.com/us-en/product/HP-Pavilion-p7-1200-Desktop-PC-series/5187022/model/5231639) and I can't find it on the specific page with all the support files for this specific issue (https://support.hp.com/us-en/document/c05843704).
-
Just checked and HP X2 that I have received a BIOS update dated December 2017 addressing security in UEFI code. The other HP laptop that I have which is a lot older didn't receive anything yet and most likely never will.
-
Just been hunting for info regarding AMD and this issue.
Found this whch may be of interest if your machine is AMD powered.
https://www.amd.com/en/corporate/speculative-execution
Ed
-
No update today either. Running windows 7 home premium with avast pro antivirus >:( Windows update says there are no updates. I wonder what happens on tuesday if they are rolling out updates as usuall ? And if they will install?
-
No update today either. Running windows 7 home premium with avast pro antivirus >:( Windows update says there are no updates. I wonder what happens on tuesday if they are rolling out updates as usuall ? And if they will install?
I've been looking around the internet for a bit of information about it, if it is true that other antivirus companies have this same problem, but for now neither Microsoft nor Avast have communicated anything about this problem, but I do not think it will take a lot in solving it.
I have personally uninstalled Avast and am waiting for the update on Tuesday to reinstall Avast.
-
Just to let you know that I've joined the list of those who have *manually* installed Microsoft's KB4056892 (I had Win 10 version 1709), and no issue to mention.
- My Avast was up to date, but no update proposed by Windows Update
- I installed the MS patch manually without removing Avast
- No problem, no BOSD
-
Yes, I uninstalled avast! (just as a precaution) and the update popped up upon reboot, then I reinstalled it. My wife wants to wait on hers, though, since she's less sure of the avast! settings she'd have to reconfigure/change.
I'm really surprised this hasn't been addressed yet!
Neither of us can update our motherboards yet (for me, dauntingly, manually). That might be weeks or months, though, if ever. I guess all we can do is be careful in the meantime.
-
Avast does have a Backup settings option, that you can backup in the settings area, and then restore on reinstall--would think that would work properly or i'd hope lol, though I never tried it thus far to know for sure
-
Anyone have any more news period about this conflict with 1709's not showing up through WU and when it may be resolved? I could manually do them from the WU Catalog but I've had issues in the past that way and am hesitant to do so, especially if it is only going to be a day or so longer.
As a non-Avast side note, does anyone know if there somehow an update for Vista? I know they stopped support, but it was the same for XP and I thought I saw people talking about getting one for XP. It's not a big deal to me whether Vista gets one or not (I don't use it for anything important), but I'm just curious.
Thanks :)
-
Even with the latest version of Avast! and the proper registry key set I still wasnt seeing the update, so I just went and grabbed it manually off the Windows Update Catalog.
-
As a non-Avast side note, does anyone know if there somehow an update for Vista? I know they stopped support, but it was the same for XP and I thought I saw people talking about getting one for XP. It's not a big deal to me whether Vista gets one or not (I don't use it for anything important), but I'm just curious.
Thanks :)
I wouldn't expect one. The mentions about Win XP most likely refer to Windows XP Embedded, which Microsoft still needs to support. Some people modify the registry in their standard XP installation, to make it being discovered as Win XP Embedded, allowing to install patches. That's not supported though and may cause quite some issues.
-
Today I received the update.
I always check for, select and install updates manually. On Windows 7 64-bit. Without uninstalling Avast Free.
No errors so far.
-
Installed KB 4056894 on Win 7 without any problem (Intel CPU). AMD CPU users may expect BSOD after installing this monthly rollup. So don't install if you have any AMD CPU.
https://www.askwoody.com/2018/widespread-reports-of-blue-screens-0x000000c4-and-0x800f0845-with-meltdown-spectre-patches-for-win7-kb-4056894-and-win10-1709-kb-4056894/
-
Still no update on win10 1709 with Avast Free installed :(
-
Installed KB 4056894 on Win 7 without any problem (Intel CPU). AMD CPU users may expect BSOD after installing this monthly rollup. So don't install if you have any AMD CPU.
https://www.askwoody.com/2018/widespread-reports-of-blue-screens-0x000000c4-and-0x800f0845-with-meltdown-spectre-patches-for-win7-kb-4056894-and-win10-1709-kb-4056894/
AMD Radeon wasn't listed. I'm going to install.
-
AMD CPU users may expect BSOD after installing this monthly rollup. So don't install if you have any AMD CPU.
Sorry, I saw this too late. I already got the BSOD and W7 was going to start a systemstartrepair, but I refused. Do you or anybody else have a AMD processor listing? I didn't find any.
;)
=Snake=
-
Tried to check whether my Avast (v17.9, running on Windows 10 64 bits) engine and virus definition are up to date. Avast is set for automatic update. The Avast Update screen shows Engine up to date, but under Definitions it shows Current Version and Release Date unknown and "Connection not Established". Pressing the update button the program goes into a sulk and hangs.
Now, what do I do?
-
I use Avast free 17.9.2322. The day BEFORE Patch Tuesday this month I was offered the Jan 2018 security rollup for Windows 7, installed it and when Windows tried to restart I was presented with a blue screen and several 8 and 16 digit HEX numbers. Windows did the same when I tried starting in safe mode. The system is apparently bricked.
This was a tidy stable Windows 7 (64bit) which smoothly negotiated previous Patch Tuesdays for many years. I ask myself if the Spectre/Meltdown fixes were responsible for the BSOD. I am taking measures to protect several Windows 7 systems belonging to friend who also use Avast s by preventing automatic updates until a safe security rollup appears. I do not know if Windows 8.1 is affected.
How does one tell Microsoft that an update might be a bad one?
-
I have Windows 10 (64) 1709 and the latest version of Avast free. Unstalling Avast, download and install the update, reinstall Avast did the trick for me. No problems.
-
Today KB4056894 was available via Windows Update. I have AIS installed and updated. All 3 of my Win 7 SP1 Pro computers installed the KB successfully. 2 of the machines are in my signature and one is an I5. Avast caused no problems here.
-
Hi
Today I was offered an update on my windows 7 machine with avast installed. I downloaded and after download a message in windows update which said that the update was not needed ? When I checked no update was installed today. Latest was installed 2017.12.12.
I rebooted and in windows update it said that the same update was there for download marked as important. What shall I do ? just ignore the message ? Or should I go through the same procedure again ? Or hide the update ? Any good advice ?
Quick update to this. I did dowload the update again and it was installed. So if anyone has the same message that the update was not needed and then when starting windows update sees that there is an update try and download it again it worked for me. But i´m still confused about the message that 1 update was not needed after the first try and nothing was installed.
-
Finally I got KB4056894 via Windows Update. Installed without any problem.
(Windows 10 Pro x64, Avast Free 17.9.2322)
-
Hi
Today I was offered an update on my windows 7 machine with avast installed. I downloaded and after download a message in windows update which said that the update was not needed ? When I checked no update was installed today. Latest was installed 2017.12.12.
I rebooted and in windows update it said that the same update was there for download marked as important. What shall I do ? just ignore the message ? Or should I go through the same procedure again ? Or hide the update ? Any good advice ?
Quick update to this. I did dowload the update again and it was installed. So if anyone has the same message that the update was not needed and then when starting windows update sees that there is an update try and download it again it worked for me. But i´m still confused about the message that 1 update was not needed after the first try and nothing was installed.
This might help you.
http://www.msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?page=137
Check also pages 136 & 135
Cheers
-
This might help you.
Not at all. My W7 machine is already broken.
:(
=Snake=
-
This might help you.
Not at all. My W7 machine is already broken.
:(
=Snake=
Snake go to the windows 7 forum link below.
http://www.msfn.org/board/forum/165-windows-7/
Those guys can really help.
-
Picked up the 1709 update through WU today on both my W10 machines and all has seemed to go well, so whatever was conflicting to halt it being delivered must have been resolved :)
As a non-Avast side note, does anyone know if there somehow an update for Vista? I know they stopped support, but it was the same for XP and I thought I saw people talking about getting one for XP. It's not a big deal to me whether Vista gets one or not (I don't use it for anything important), but I'm just curious.
Thanks :)
I wouldn't expect one. The mentions about Win XP most likely refer to Windows XP Embedded, which Microsoft still needs to support. Some people modify the registry in their standard XP installation, to make it being discovered as Win XP Embedded, allowing to install patches. That's not supported though and may cause quite some issues.
Interesting, makes sense. Thanks :)
-
This might help you.
Not at all. My W7 machine is already broken.
:(
=Snake=
By the way, have you tried to uninstall the KB(s) in question ?
-
Microsoft halts security updates for select AMD devices (https://www.ghacks.net/2018/01/09/microsoft-halts-security-updates-for-select-amd-devices/)
-
Microsoft halts security updates for select AMD devices (https://www.ghacks.net/2018/01/09/microsoft-halts-security-updates-for-select-amd-devices/)
-> https://support.microsoft.com/en-us/help/4073707/windows-operating-system-security-update-block-for-some-amd-based-devi
-
FYI
Running Avast Free v17.9.2322 (Build 17.9.3761.0) on W10 v1709 (Build 16299.192) laptop, with Intel Core M-5Y10c CPU
Reg.Key correctly created when I did an in-place update to current Avast Version (over weekend). KB4056892 auto-downloaded by Windows Update, last night and installed with no probs, just now.
Nice when something actually works correctly!
-
FYI
Running Avast Free v17.9.2322 (Build 17.9.3761.0) on W10 v1709 (Build 16299.192) laptop, with Intel Core M-5Y10c CPU
Reg.Key correctly created when I did an in-place update to current Avast Version (over weekend). KB4056892 auto-downloaded by Windows Update, last night and installed with no probs, just now.
Nice when something actually works correctly!
That's because you waited long enough for them to get the bugs out. :)
-
Hey guys. Received KB4056892 today (finally!), installation seems to ran fine but Windows Update history says that it failed with error 0x80070643. Check for Updates states that there are no updates available. My build is now displayed as 16299.192. Ran /wmic qfe list in cmd and it also shows KB4056892 as installed. So the update installed in fact? Anybody here with the same issue?
-
Known Issue, installed correctly but erroneous error message
See here https://support.microsoft.com/en-us/help/4056892/windows-10-update-kb4056892
-
I uninstalled and reinstalled Avast and I'm still not getting the registry key to appear on my Windows 7 desktop. What should I do?
-
Microsoft halts security updates for select AMD devices (https://www.ghacks.net/2018/01/09/microsoft-halts-security-updates-for-select-amd-devices/)
-> https://support.microsoft.com/en-us/help/4073707/windows-operating-system-security-update-block-for-some-amd-based-devi
What are the list of affected AMD Devices?
-
Edit: Nvm
-
Everything You Need to Know About Meltdown and Spectre Vulnerabilities (https://www.askvg.com/guide-everything-you-need-to-know-about-meltdown-and-spectre-vulnerabilities/?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+AskVG+%28AskVG%29)
A very comprehensive Guide and tutorial on the topic.
-
To be secure i need update my web browser, install windows patch and update BIOS. So all motherboards will now have new BIOS for download? My motherboard is 4 years old and latest BIOS was released in 2015. I don't belive they create new bios for all motheboards.
-
@bob
Hi!
Please tell/write me, which systems have PowerShell. Thanks.
=Snake=
-
@bob
Hi!
Please tell/write me, which systems have PowerShell. Thanks.
=Snake=
Does this answer your question ???
https://docs.microsoft.com/en-us/powershell/scripting/setup/windows-powershell-system-requirements?view=powershell-5.1
-
@bob
Hi!
Please tell/write me, which systems have PowerShell. Thanks.
=Snake=
Does this answer your question ???
https://docs.microsoft.com/en-us/powershell/scripting/setup/windows-powershell-system-requirements?view=powershell-5.1
Yes. But shall I wait until Avasts micro update arrived here?
=Snake=
-
I suggest you wait till someone who runs Windows XP can answer that question for you.
-
Thanks,bob, for quick answer.
:)
=Snake=
-
Sorry I can't be of more help. :(
-
Bob is right on target. Unfortunately, as of this morning, we XP people still don't have a micro-update from Avast that corrects the new file-copy problem (and therefore impairs the current updates, including for Meltdown and Spectre).
If anyone can get Avast to post here (and in a few other threads on this board) when to expect this fix, please do! Thanks.
-
Bob is right on target. Unfortunately, as of this morning, we XP people still don't have a micro-update from Avast that corrects the new file-copy problem (and therefore impairs the current updates, including for Meltdown and Spectre).
If anyone can get Avast to post here (and in a few other threads on this board) when to expect this fix, please do! Thanks.
The micro-update from Avast to correct the new file-copy problem was released 3 hours ago. The fix will automatically roll out within the next 12 hours but you can do it manually now.
Running AVEmUpdate.exe as admin from Avast directory and rebooting or you can execute: schtasks.exe /Run /TN "Avast Emergency Update"
-
https://www.youtube.com/watch?v=S4o-5GjNujw
-
@bob
Hi!
Please tell/write me, which systems have PowerShell. Thanks.
=Snake=
Does this answer your question ???
https://docs.microsoft.com/en-us/powershell/scripting/setup/windows-powershell-system-requirements?view=powershell-5.1
Yes. But shall I wait until Avasts micro update arrived here?
=Snake=
Well I have one system with XP, but it doesn't require an XP user to answer. The link provides gives the OS requirements for Windows PowerShell 3.0, 4.0 or 5.0 and XP (nor Vista) are on the list.
However, given that we are in the MS Security Update for Meltdown topic - I suspect you are looking for something else, e.g. does avast add the required registry key for MS to install the fix. The answer to that would appear to be a no, there is no HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\QualityCompat key in my XP registry. There is in my win10 system and I have got the update, though I didn't wait and went to the update catalogue to download and install it.
So if MS were even going to include an update for XP (POS, point of sale, aka sp4), then there is no registry key to trigger it.
-
1.
However, given that we are in the MS Security Update for Meltdown topic - I suspect you are looking for something else, e.g. does avast add the required registry key for MS to install the fix. The answer to that would appear to be a no, there is no HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\QualityCompat key in my XP registry. There is in my win10 system and I have got the update, though I didn't wait and went to the update catalogue to download and install it.
2.
So if MS were even going to include an update for XP (POS, point of sale, aka sp4), then there is no registry key to trigger it.
Hi David!
Point 1: Please, be so kind as to see my sig. I have ... QualityCompat in almost every Registry except
on 'W2k' and the 'Twin-OS', for the last one is in another town!
Point 2: Concerning XP, I'll wait like for th other systems.
=Snake=
-
hello
as I said on the other subject, the key is also present on my xp and I did not create it manually
-
as I said on the other subject, the key is also present on my xp and I did not create it manually
I've seen it and did like you (not created manually).
=Snake=
-
hello
as I said on the other subject, the key is also present on my xp and I did not create it manually
I didn't create it and Avast hasn't either, nothing like consistency. I have no idea what avast may be looking at to determine if it should create the key or not.
My real issue is even if it did create it what difference would it make as MS don't appear to be interested in XP or Vista in relation to Meltdown.
-
hello
as I said on the other subject, the key is also present on my xp and I did not create it manually
I didn't create it and Avast hasn't either, nothing like consistency. I have no idea what avast may be looking at to determine if it should create the key or not.
My real issue is even if it did create it what difference would it make as MS don't appear to be interested in XP or Vista in relation to Meltdown.
Following on, I ran AvEmUpdate.exe as Administrator, ran a manual program update and I rebooted and still nada. Not to mention, the Avast Emergency Update - AvEmUpdate.exe - is also in my list of Scheduled Tasks.
-
@bob
Hi!
Please tell/write me, which systems have PowerShell. Thanks.
=Snake=
Does this answer your question ???
https://docs.microsoft.com/en-us/powershell/scripting/setup/windows-powershell-system-requirements?view=powershell-5.1
Only to your information:
- I downloaded and installed it for 8.1: No problems after.
- Did the same for AMD_LE_1620 (W7): Machine crashed, but i was able to get it back at work.
;D
=Snake=
-
Last night I had a file quarantined in virus chest which I believe is automatic downloaded update (i.e. not solicited by me) relating to Spectre / Meltdown fix for AMD users. Virus was labelled "Win64:Malware-gen" affecting file "inetcpl.cpl". Others Avast users with same issue reported it here before me:
https://forum.avast.com/index.php?topic=212994.msg1441549#msg1441549
The file has gone for analysis as false positive. I have released it and scanned using latest MWB and no threat was detected.
Ed
-
hi,
how can I know if I have the security patch? Which is the KBxxxxxx?
-
hi,
how can I know if I have the security patch? Which is the KBxxxxxx?
https://support.microsoft.com/en-us/help/4073757/protect-your-windows-devices-against-spectre-meltdown
Look under January 2018 Windows operation system update schedule
-
hi,
how can I know if I have the security patch? Which is the KBxxxxxx?
https://support.microsoft.com/en-us/help/4073757/protect-your-windows-devices-against-spectre-meltdown
Look under January 2018 Windows operation system update schedule
yes, and exatly there is my problem.
For Win7 there are 2 patches : kb4056894 and kb4056897, which is relevant and why there are 2 different?
-
hi,
how can I know if I have the security patch? Which is the KBxxxxxx?
https://support.microsoft.com/en-us/help/4073757/protect-your-windows-devices-against-spectre-meltdown
Look under January 2018 Windows operation system update schedule
yes, and exatly there is my problem.
For Win7 there are 2 patches : kb4056894 and kb4056897, which is relevant and why there are 2 different?
KB4056897 Is security-only, meaning it's the patch for the Spectre/Meltdown fix only. KB4056894 is a monthly roll up patch, containing all the fixes for the month. As far as I can tell having either one is want you want.
-
As far as I can tell having either one is want you want.
I dont understand this, sorry for my poor English, could you please try to explain better. Thanks
-
Install BOTH
-
Found a Source that highlights all Meltdown/Spectre affected CPU's
https://www.techarp.com/guides/complete-meltdown-spectre-cpu-list/
Source Tech Arp
-
Hi everyone,
I'm using Win 10 Home, 1709 (build 16299.125), Avast Free Antivirus 17.9.2322 and had to manually modify the registry to enable the Microsoft security update. It worked fine
Bye
-
Hi everyone,
I'm using Win 10 Home, 1709 (build 16299.125), Avast Free Antivirus 17.9.2322 and had to manually modify the registry to enable the Microsoft security update. It worked fine
Bye
If your AV was up to date, that should not have been necessary.
-
I'm using Win 10 Home, 1709 (build 16299.125), Avast Free Antivirus 17.9.2322 (build 17.9.3761.278). When I check for updates in both windows and avast, it says that there are no updates. However, I cannot see the windows update (kb4056892). Neither do I see the QualityCompat registry. I don't think that either has been added/updated but I don't understand why.
-
I'm using the following software.
* Avast Free Antivirus 17.9.2322
* Malwarebytes Anti-Malware 3.3.1.2183
Avast didn't set the registry key after updating the program. However, Malwarebytes did set the registry key. Why didn't Avast set the registry key?
Isn't it a problem that there are multiple programs that set the registry key? One program may be compatible, but another program may not.
I'm running the AMD Phenom II X2 555 Black Edition processor on Windows 7 SP1 32-bit and that processor is in the list below. And I read that machines won’t boot specifically with the Phenom II processor.
I'm going to wait for the February 2018 rollup instead of installing the January 2018 KB4056894 rollup in Windows Update.
Windows security updates and antivirus software
http://support.microsoft.com/help/4072699
Complete Meltdown Spectre CPU List
http://www.techarp.com/guides/complete-meltdown-spectre-cpu-list/
Machine won’t boot specifically with Phenom II processor
http://www.reddit.com/r/Amd/comments/7ulc6a
Edit:
The February 2018 KB4074598 rollup worked fine.
-
I will also wait for the new package, (https://www.misbolsosonline.es/carteras-hombre-31) greetings.
-
You need to use the current version of Avast:
https://forum.avast.com/index.php?topic=216700.msg1451035#msg1451035
-
April 10, 2018 Status Update
We are lifting the AV compatibility check for Windows security updates for supported Windows 7 SP1 and Windows 8.1 devices via Windows Update. We continue to require that AV software be compatible, and in cases where there are known issues of AV driver compatibility, we will block those devices from updates to avoid any issues. We recommend customers check with their AV provider on compatibility of their installed AV software product.
March 13, 2018 Status Update
Our recent work with our anti-virus (AV) partners on compatibility with Windows updates has now reached a sustained level of broad ecosystem compatibility. Based on our analysis of available data, we are now lifting the AV compatibility check for the March 2018 Windows security updates for supported Windows 10 devices via Windows Update. We continue to require that AV software is compatible and in cases where there are known issues of AV driver compatibility, we will block those devices from updates to avoid any issues. We recommend customers check with their AV provider on compatibility of their installed AV software product.
-> https://support.microsoft.com/en-us/help/4072699/windows-security-updates-and-antivirus-software