Meltdown patch windows 10 kb download - authoritative
Knowledge Center
Technical Articles ID: KB
Last Modified: 10/28/
Last Modified: 10/28/
Environment
Multiple McAfee products
NOTE: This article applies only to McAfee business and enterprise products. If you need information or support for McAfee consumer or small business products, visit rushbrookrathbone.co.uk
To view the article for McAfee consumer products, see TS
NOTE: This article applies only to McAfee business and enterprise products. If you need information or support for McAfee consumer or small business products, visit rushbrookrathbone.co.uk
To view the article for McAfee consumer products, see TS
Summary
This article provides updated information to our blog post titled "Decyphering the Noise Around 'Meltdown' and 'Spectre'."
Recent updates to this article
McAfee has completed testing to ensure product compatibility with operating system patches related to “Spectre” and “Meltdown.” This document contains the status of our testing.
For more information about the “Spectre” and “Meltdown” attack methods, see our blog “Decyphering the Noise Around ‘Meltdown’ and ‘Spectre’”:
rushbrookrathbone.co.uk
Microsoft introduced a new registry key with this update to control if the update is available through the Windows Update service.
Automated mechanism to deploy the registry key update
Starting with the January 10 DAT () updates for Endpoint Security (ENS) and later, the registry key will be automatically updated for customers.
NOTE: Safety Pulse, which is enabled by default, must be enabled to download ENS DAT
Starting with the January 12 DAT (), customers who use VirusScan Enterprise (VSE) and receive DAT updates will have the registry key automatically updated.
The DAT adds the check for the registry key, and sets it if it is not present. Customers who have already set a registry key will not have any issues.
For customers using ENS or earlier, see KB - How to deploy the required registry key via automated executable.
NOTE: Microsoft no longer performs AV compatibility checks for supported Windows 10, , and 7 SP 1 devices. But, McAfee will continue to set this registry key to ensure compatibility for other devices. For more information, see the following Microsoft article: Important: Windows security updates and antivirus software.
Manual methods to deploy the registry key update
To receive patches through Windows Update, customers are advised to create the following new registry key:
In environments with Active Directory, this key can be deployed through GPO. Instructions on how to deploy through GPO are available at: rushbrookrathbone.co.uk%28v=ws%aspx
Customers who are not using Windows Update can directly download and apply the Windows Update from the Windows Update Catalog at: rushbrookrathbone.co.uk
NOTE: When you download Windows updates, Windows 7 operating systems must be updated to SP1 to pull updates from Microsoft Windows Update.
Recent updates to this article
| Date | Update |
| October 28, | Removed End of Life product versions. |
| September 18, | Removed KB article link to unpublished End of Life (EOL) content. Updated links to product documentation and blog. |
McAfee has completed testing to ensure product compatibility with operating system patches related to “Spectre” and “Meltdown.” This document contains the status of our testing.
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
For more information about the “Spectre” and “Meltdown” attack methods, see our blog “Decyphering the Noise Around ‘Meltdown’ and ‘Spectre’”:
rushbrookrathbone.co.uk
Windows product compatibility for McAfee products
Microsoft has requested security vendors to perform additional testing with their January 3 update, to ensure compatibility with that update.Microsoft introduced a new registry key with this update to control if the update is available through the Windows Update service.
Automated mechanism to deploy the registry key update
Starting with the January 10 DAT () updates for Endpoint Security (ENS) and later, the registry key will be automatically updated for customers.
NOTE: Safety Pulse, which is enabled by default, must be enabled to download ENS DAT
Starting with the January 12 DAT (), customers who use VirusScan Enterprise (VSE) and receive DAT updates will have the registry key automatically updated.
The DAT adds the check for the registry key, and sets it if it is not present. Customers who have already set a registry key will not have any issues.
For customers using ENS or earlier, see KB - How to deploy the required registry key via automated executable.
NOTE: Microsoft no longer performs AV compatibility checks for supported Windows 10, , and 7 SP 1 devices. But, McAfee will continue to set this registry key to ensure compatibility for other devices. For more information, see the following Microsoft article: Important: Windows security updates and antivirus software.
Manual methods to deploy the registry key update
To receive patches through Windows Update, customers are advised to create the following new registry key:
RegKey="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name ="cadca5fedbb7fb-acc"
Type="REG_DWORD"
Data="0x"
Value Name ="cadca5fedbb7fb-acc"
Type="REG_DWORD"
Data="0x"
In environments with Active Directory, this key can be deployed through GPO. Instructions on how to deploy through GPO are available at: rushbrookrathbone.co.uk%28v=ws%aspx
Customers who are not using Windows Update can directly download and apply the Windows Update from the Windows Update Catalog at: rushbrookrathbone.co.uk
NOTE: When you download Windows updates, Windows 7 operating systems must be updated to SP1 to pull updates from Microsoft Windows Update.
The following products have been tested and are confirmed as compatible:
Testing is complete for all McAfee products and no compatibility issues with the Microsoft update have been found.
- Application and Change Control and later
- AV Engine and later
- Data Exchange Layer and later
- Data Loss Prevention and later
- Database Activity Monitor/Sensor and later
- Drive Encryption and later
- ePolicy Orchestrator (ePO) and later
- ePO MER and later
- ePO MVT and later
- Endpoint Intelligence Agent and later
- Endpoint Security and later
- File and Removable Media Protection and later
- Host Intrusion Prevention System Update 4 and later
- McAfee Active Response and later
- McAfee Agent and later
- McAfee Client Proxy and later
- MOVE Antivirus Multi-Platform and later
- Management of Native Encryption and later
- Network Security Manager and later
- Policy Auditor for Windows and later
- Rogue System Detection and later
- SaaS Endpoint and later
- Security for Domino Windows and later
- Security for Microsoft Exchange and later
- Security for Microsoft Sharepoint and later
- SiteAdvisor Enterprise Update 3 and later
- System Information Reporter and later
- Threat Intelligence Exchange Client for VSE and later
- VirusScan Enterprise Update 5, General Availability and later
- VirusScan Enterprise for Storage and later
Linux and macOS compatibility for McAfee products:
Testing is complete for Linux and macOS-based products. No issues have been found. - Application and Change Control
- Data Loss Prevention for Mac , ,
- Endpoint Security for Linux
- Endpoint Security for Mac
- Endpoint Protection for Mac
- File and Removable Media Protection for Mac
- Host Intrusion Prevention for Linux Update 11 and later
- Management of Native Encryption for Mac
- McAfee Active Response for Linux , , ,
- McAfee Active Response for Mac
- McAfee Agent and later
- McAfee Linux Firewall
- Policy Auditor for Linux , ,
- VirusScan Enterprise for Linux ,
Cloud services for McAfee and Skyhigh products:
Appliance compatibility for McAfee products:
Testing on McAfee appliance-based products is complete. - Advanced Threat Defense (ATD) - The following releases updated the MLOS kernel to address these vulnerabilities.
These updates are included in all subsequent ATD releases. This fix is implemented in software and microcode because both components are required.
While the microcode component could be resolved using a BIOS update, engineering chose to implement them via a software update. - Data Exchange Layer (DXL) - The following DXL hotfixes provide security fixes for vulnerabilities related to Meltdown:
- DXL Hotfix 3
- DXL Hotfix 10
- DXL Hotfix 8
- DXL Hotfix 11
- DXL Hotfix 8
- McAfee Active Response (MAR) Server Hotfix 4. See SB for reference.
- MOVE Antivirus Agentless
- Network Data Loss Prevention (DLP) - The following releases provide kernel updates to address the Meltdown and Spectre vulnerabilities:
- Network Security Manager Linux Appliance
- SIEM - SIEM is a closed system. Unprivileged local users are not able to execute arbitrary code. Nevertheless, SIEM expects to address this vulnerability in a future version update. See SB for reference.
- Threat Intelligence Exchange (TIE) Server Hotfix 3. See SB for reference.
- Vulnerability Manager
- Web Gateway 7.x - The following releases provide kernel updates to address the Meltdown and Spectre vulnerabilities:
- Web Gateway - For a list of resolved issues, see the Release Notes.
- Web Gateway - For a list of resolved issues, see the Release Notes.
-
-