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

bob3160 · « **Reply #120 on:** January 09, 2018, 01:18:33 PM »

Quote from: pastyman on January 09, 2018, 01:01:11 PM

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.

raena.exml · « **Reply #121 on:** January 09, 2018, 01:25:09 PM »

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?

REDACTED · « **Reply #122 on:** January 09, 2018, 01:40:19 PM »

Known Issue, installed correctly but erroneous error message

See here https://support.microsoft.com/en-us/help/4056892/windows-10-update-kb4056892

crimsoncricket · « **Reply #123 on:** January 10, 2018, 04:53:40 AM »

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?

Hopper15 · « **Reply #124 on:** January 10, 2018, 06:32:01 AM »

Quote from: Asyn on January 09, 2018, 12:14:09 PM

Quote from: bob3160 on January 09, 2018, 12:13:09 PM
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?

micbenste · « **Reply #125 on:** January 10, 2018, 02:23:53 PM »

Edit: Nvm

bob3160 · « **Reply #126 on:** January 10, 2018, 03:01:57 PM »

Everything You Need to Know About Meltdown and Spectre Vulnerabilities
A very comprehensive Guide and tutorial on the topic.

TheOwner · « **Reply #127 on:** January 10, 2018, 05:16:27 PM »

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.

=Snake= · « **Reply #128 on:** January 10, 2018, 06:24:16 PM »

@bob
Hi!

Please tell/write me, which systems have PowerShell. Thanks.

=Snake=

bob3160 · « **Reply #129 on:** January 10, 2018, 06:44:57 PM »

Quote from: =Snake= on January 10, 2018, 06:24:16 PM

@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

=Snake= · « **Reply #130 on:** January 10, 2018, 06:57:59 PM »

Quote from: bob3160 on January 10, 2018, 06:44:57 PM

Quote from: =Snake= on January 10, 2018, 06:24:16 PM
@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=

bob3160 · « **Reply #131 on:** January 10, 2018, 07:09:37 PM »

I suggest you wait till someone who runs Windows XP can answer that question for you.

=Snake= · « **Reply #132 on:** January 10, 2018, 07:55:47 PM »

Thanks,bob, for quick answer.

=Snake=

bob3160 · « **Reply #133 on:** January 10, 2018, 08:05:05 PM »

Sorry I can't be of more help.

glnz · « **Reply #134 on:** January 10, 2018, 08:20:15 PM »

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.