Windows upgrade using SCCM 1910 hangs with Endpoint Security
Last Modified: 2021-12-09 12:45:45 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Windows upgrade using SCCM 1910 hangs with Endpoint Security
Technical Articles ID:
KB92372
Last Modified: 2021-12-09 12:45:45 Etc/GMT Environment
Endpoint Security (ENS) Threat Prevention 10.x Microsoft System Center Configuration Manager (SCCM) 1910 Microsoft Windows 10 Problem
After you upgrade from SCCM 1906 or earlier to SCCM 1910, a Windows 10 in-place upgrade task sequence might hang on a system with ENS installed.
Solution
Install Microsoft Update Rollup for Endpoint Configuration Manager, version 1910 (KB4537079). For more information, see this Microsoft article on the rollup. This issue is also resolved in ENS 10.6.1 April 2020 Update and ENS 10.7.0 April 2020 Update. Our product software, upgrades, maintenance releases, and documentation are available on the Product Downloads site.
NOTE: You need a valid Grant Number for access. See KB56057 - How to download product updates and documentation for more information about the Product Downloads site, and alternate locations for some products. WorkaroundRevert to using the previously known working version SCCM 1906 or earlier. Or, you can try to implement the following workarounds. The following workarounds have allowed the task sequence to complete in some environments.
Workaround 1: Disable Restart Manager
Affected ProductsLanguages:This article is available in the following languages: |
|