Author Topic: MS Security Update for Meltdown  (Read 60395 times)

0 Members and 1 Guest are viewing this topic.

Offline Michal256

  • Jr. Member
  • **
  • Posts: 32
Re: MS Security Update for Meltdown
« Reply #45 on: January 06, 2018, 02:54:49 PM »
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.

REDACTED

  • Guest
Re: MS Security Update for Meltdown
« Reply #46 on: January 06, 2018, 03:23:26 PM »
I think so, this should not be the case, it serves as a quick solution, not a definitive one.

REDACTED

  • Guest
Re: MS Security Update for Meltdown
« Reply #47 on: January 06, 2018, 03:31:56 PM »
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)

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 47576
  • 62 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: MS Security Update for Meltdown
« Reply #48 on: January 06, 2018, 05:49:31 PM »
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
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v21H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 22.5, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://

Offline schmidthouse

  • VIRUS FREE A Long Time
  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 7130
  • When you think you know, Think Again
Re: MS Security Update for Meltdown
« Reply #49 on: January 06, 2018, 05:59:53 PM »
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
***HP ENVY 15K LT W10 Pro 21H2 64Bit/250GB SSD/16GB Ram/ADU v.22.3b/VS/SANDBOXIE-plus/MailWasherPRO
**HP Compaq 8510p LT W10 Pro 21H2 64Bit/1TB HD/8GB Ram/ADU v.22.3b/VS/SANDBOXIE/HotSpot Shield
 Avast Mobile Security (Android)
LAYERED SECURITY SOFTWARE

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76115
  • Urlaub/Vacation
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: MS Security Update for Meltdown
« Reply #50 on: January 06, 2018, 06:05:58 PM »
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...)
W8.1 [x64] - Avast PremSec 22.7.7366.BC [UI.713] - Firefox ESR 91.11 [NS/uBO/PB] - Thunderbird 91.11
Avast-Tools: Secure Browser 103.0 - Cleanup 22.2 - SecureLine 5.18 - DriverUpdater 22.2 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline Michal256

  • Jr. Member
  • **
  • Posts: 32
Re: MS Security Update for Meltdown
« Reply #51 on: January 06, 2018, 06:10:59 PM »
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.

REDACTED

  • Guest
Re: MS Security Update for Meltdown
« Reply #52 on: January 06, 2018, 07:20:44 PM »
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.

REDACTED

  • Guest
Re: MS Security Update for Meltdown
« Reply #53 on: January 06, 2018, 07:27:34 PM »
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.

Offline toastman

  • Jr. Member
  • **
  • Posts: 23
Re: MS Security Update for Meltdown
« Reply #54 on: January 06, 2018, 07:42:08 PM »
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)


Offline Patrick2

  • Poster
  • *
  • Posts: 489
Re: MS Security Update for Meltdown
« Reply #55 on: January 06, 2018, 07:59:36 PM »
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

Windows 10 Pro 64bit 1909 18363.476, Intel I7 7700 Nvidia Geforce 1050 16gb DDR4, WD 250GBSSD, 1tb Storage, Avast Free 19.8.2393
HP Omen Laptop Intel I7 7700HQ, 8gb Of Ram Windows 10 Home x64 1909 18363.476 128GB SSD, 1tb Storage, Avast Free 19.8.2393

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 47576
  • 62 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: MS Security Update for Meltdown
« Reply #56 on: January 06, 2018, 08:27:32 PM »

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 (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/
« Last Edit: January 06, 2018, 08:30:03 PM by bob3160 »
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v21H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 22.5, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://

Offline glnz

  • Sr. Member
  • ****
  • Posts: 300
Re: MS Security Update for Meltdown
« Reply #57 on: January 06, 2018, 08:54:41 PM »
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

(and go backwards from that post).
Various Dell Optiplexes running XP Pro SP3 32-bit, Win 7 Pro SP1 64-bit and Win 10 Pro 64-bit.  Firefox with security add-ons.

Offline crimsoncricket

  • Newbie
  • *
  • Posts: 16
Re: MS Security Update for Meltdown
« Reply #58 on: January 06, 2018, 09:08:34 PM »
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!

Offline toastman

  • Jr. Member
  • **
  • Posts: 23
Re: MS Security Update for Meltdown
« Reply #59 on: January 06, 2018, 09:16:35 PM »
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.