Critical Note on Meltdown Patching

The proven solution to stopping a breach is to patch the vulnerability. While this is indeed the case for Meltdown, caveats apply and in some situations it may be best to hold off on patching immediately.

In particular, be aware:

If you are running antivirus software from partners that have NOT YET confirmed their software is compatible with the January 2018 Windows operating system security update, then you should NOT attempt to patch your machines. To help prevent errors caused by incompatible antivirus applications, Microsoft is only offering the Windows security updates released on January 3, 2018 to systems that have compatible antivirus or to systems that have the registry key bypass value set. Attempting to patch before prior could result in BSOD or simply systems not actually receiving this important update.

You should NOT manually set this value unless you are certain that your antivirus is compatible. Microsoft has published a list of antivirus solutions and their status at

https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?sle=true#gid=0

Read more about How to Not Have a Meltdown over Meltdown and Meltdown and Spectre FAQs. Then, head over to the Kaseya Automation Exchange for a Meltdown Vulnerability Check. The Meltdown Vulnerability Check will scan for the Meltdown Vulnerability on your endpoints, and update the custom field “Meltdown” to let you know if your systems are safe or need to be patched.

We will continue to aggressively monitor Meltdown and will post updates and news as they develop.

Leave a Reply

Your email address will not be published. Required fields are marked *