Both KB4056897 (security-only) and KB4056894 (monthly rollup) are causing massive problems for AMD users (notably failure to boot up with BSOD) and should definitely not be installed yet, especially as the monthly rollup is generally not checked and is therefore not intended to be ready for installation.
One problem with the security-only update is that by downloading it from the MS Windows Catalog and installing it you are bypassing the registry key test that determines whether your machine is suitable for it.
If you have installed one of these updates and can't boot the machine try to boot into repair mode and then use System Restore to roll back the computer to a date prior to the update being installed.
It looks highly likely, however, that both updates will either be pulled shortly or else replaced on Patch Tuesday. In the meantime it would be prudent to leave well alone, especially on AMD machines.
Computer Type: PC/Desktop System Manufacturer/Model Number: Custom build by PC Specialist OS: Windows 7 Home Premium 64 CPU: AMD Phenom II X4 955 Motherboard: Asus M4A78T-E Memory: 8GB Corsair XMS3 DDR3 Graphics Card: Gigabyte Geforce GTX 960 2GB Sound Card: SB Audigy Monitor(s) Displays: BenQ 24" Screen Resolution: 1920 x 1080 Keyboard: Corsair Mouse: Logitech PSU: 1010W Quiet Quad Rail Case: Antec 900 Cooling: Fenrir Hard Drives: 500GB Serial ATA Internet Speed: 20mbps Browser: Chrome Antivirus: MSE plus MBAM 2.x Free Other Info: Second desktop different spec but similar level.
As for replacing your AV, as long as the reg key has been set by the new provider then it should not be a problem
Believe Avast has but mine Panda hasn't NO WAY i would swop until ALL AV's have updated
In reality there are 4 parts to fixing the "Meltdown +" issue
MS - Manfacturer(intel/AMD) - OEM - AV
In my eyes the correct order to update
Manufacturer (note Intel have issued a check tool)
AV
MS
OEM
Its been handled piecemeal which doesnt help us,
Even the COMPLETE MS patch comes in 2 parts
(the 2nd is in the monthly cumulative - for IE and Edge browsers)
when the OEM's patch the BIOS, were going to hit another problem are they going to issue it for older machines as well - DONT think so
(that includes my 2009 rig)
Make sure that any Intel check tool actually relates to the Meltdown issue, there are a lot of posters on multiple forums linking an old Intel check tool that was for a different problem entirely and if applied to this situation it will give a false sense of security.
AMD don't believe that their processors are at significant risk from Meltdown, and there is currently insufficient reason to worry about Meltdown if you have an AMD machine.
Remember too that with Windows Updates you can usually uninstall them or roll back the machine if they cause issues. However, BIOS updates and firmware updates generally don't typically have the same option so only consider any such updates with extreme caution and, most crucially in the light of the many problems being reported all over the place - not yet!
Computer Type: PC/Desktop System Manufacturer/Model Number: Custom build by PC Specialist OS: Windows 7 Home Premium 64 CPU: AMD Phenom II X4 955 Motherboard: Asus M4A78T-E Memory: 8GB Corsair XMS3 DDR3 Graphics Card: Gigabyte Geforce GTX 960 2GB Sound Card: SB Audigy Monitor(s) Displays: BenQ 24" Screen Resolution: 1920 x 1080 Keyboard: Corsair Mouse: Logitech PSU: 1010W Quiet Quad Rail Case: Antec 900 Cooling: Fenrir Hard Drives: 500GB Serial ATA Internet Speed: 20mbps Browser: Chrome Antivirus: MSE plus MBAM 2.x Free Other Info: Second desktop different spec but similar level.
That's an old tool relating to the Management Engine Critical Firmware Update and is nothing to do with the present Meltdown issue. As such it won't tell you whether you're vulnerable to it.
Computer Type: PC/Desktop System Manufacturer/Model Number: Custom build by PC Specialist OS: Windows 7 Home Premium 64 CPU: AMD Phenom II X4 955 Motherboard: Asus M4A78T-E Memory: 8GB Corsair XMS3 DDR3 Graphics Card: Gigabyte Geforce GTX 960 2GB Sound Card: SB Audigy Monitor(s) Displays: BenQ 24" Screen Resolution: 1920 x 1080 Keyboard: Corsair Mouse: Logitech PSU: 1010W Quiet Quad Rail Case: Antec 900 Cooling: Fenrir Hard Drives: 500GB Serial ATA Internet Speed: 20mbps Browser: Chrome Antivirus: MSE plus MBAM 2.x Free Other Info: Second desktop different spec but similar level.
Computer Type: PC/Desktop System Manufacturer/Model Number: Gateway DX4831-01e (Mid-Tower Desktop) OS: Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019 CPU: Intel i3 530 2.93GHz, 2933MHz 2 Cores 4 Logical Processors Motherboard: Gateway H57M01 133 megahertz Memory: 6GB of 1,333MHz DDR3 SDRAM Graphics Card: 32MB Intel Graphics Media Accelerator HD IGChip Sound Card: Realtek High Definition Audio Monitor(s) Displays: Gateway HX2000 20inch TFT active matrix TN Screen Resolution: 1600 x 900 x 59 hertz Keyboard: Natural Ergonomic Keyboard 4000, see Other Info Mouse: Orig. Gateway wore out now using Insignia USB wired optical PSU: 300watts. Case: Mid-Tower Desktop Cooling: Stock from Gateway Hard Drives: WDC WD10EADS-00M2B0 [HDD] (1000.20 GB) -- drive 0,
HL-DT-ST DVDRAM GH41N [CD-ROM dr]
Four card readers, and Four USB 2.0 Internet Speed: Vz FIOS 10ms png 57.64Mbps down 65.53Mbps up Speedtest.org Browser: IE11.0.9600.19399-Upd ver11.0.135, Firefox 68.0.1 x64 Antivirus: Zamana Anti-logger with Anti-malware, MSE, Windows Firewall, Other Info: System Specs by Belarc.
BIOS: American Megatrends Inc. P01-A0 11/17/2009
Replaced the MS 'Natural' Standard PS/2 Enhanced 101-102 Keyboard with a new Natural Ergonomic Keyboard 4000 on August 1st 2014.
Canon Pixma MG3222 Printer.
Updated to IE11 on 12102015 | Fios Quantum Router g1100
Additional AV: SpywareBlaster, manual Mbam, SAS
I checked for the registry key prior to installing the rollup. I had the key, so I went ahead, making a restore point. I have an AMD FX-8350 and there were no problems with the update. The computer is running just fine.
Maybe the issue is only affecting certain AMD cores? The complaints that I've seen from AMD users are older cored models, such as Brisbane and Windsor that have been out of production for years. Perhaps MS forgot to make allowances for these older models in the patches. I have not seen any reports from users of Vishera, Bulldozer or Ryzen cores yet, though I may have missed them.
Computer Type: PC/Desktop System Manufacturer/Model Number: Mellon Labs (custom build) OS: Win 7 Pro x64/Win 10 Pro x64 dual boot CPU: AMD FX 8350 Vishera @ 4200 Motherboard: ASUS M5A97 R2.0 Memory: 16 GB Mushkin Blackline DDR3-2400 @ 1866 (9-10-10-10-31) Graphics Card: XFX Radeon R9 280 Double D Black Edition Sound Card: Realtek HD Audio on MB. Sounds great. Monitor(s) Displays: Acer 24", Acer 22" Screen Resolution: 3840 x 1080 Keyboard: Logitech G710+ Mouse: Logitech G500s PSU: Corsair TX-750 Case: CoolerMaster HAF 912+ Cooling: Coolermaster Seidon 240M Liquid AIO. 6 case fans Hard Drives: 1 x Mushkin Chronos 120 GB SSD (Win 10)
1 x Samsung 850 EVO 250 GB SSD (Win 7)
1 x WD 1TB SATA Blue
1 x WD 1TB SATA Green Internet Speed: Much better since I got fiber, but still way overpriced. Browser: Firefox Antivirus: MSE, Malware Bytes for scanning Other Info: Corsair VOID USB headphones.
A Mellon Labs X-1 - LCD Smartie driven system status display.
Brought to you by the letter E
I've seen on the news this morning that intel processors are at risk from the Meltdown issue but patches/updates (?) are being issued for intel processors that are up to five years old. My trusty laptop is 6 years plus old.
Then there's the issue of whether McAfee have released the update for the registry part.
I don't know whether to install this update or not, even if I do, will it protect my laptop and now given this latest intel issue, whether it could potentially wreck my laptop.
Sources:
Can I sign in to Skype with my Facebook account? | Skype Support
How do I transfer contacts from one Skype account to another? | Skype Support
Source: January 2016 Security Update Release Summary - Microsoft Security Response Center - Site Home - TechNet Blogs
See also:
Microsoft Security Bulletin Summary for January 2016
Security Advisories 2016