Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Software update installation freezes on System Center Configuration Manager clients


View products that this article applies to.

Symptoms

During an Operating System deployment of Windows 10 via Configuration Manager, the Install Software Updates task sequence may freeze when large numbers (for example, 50 or more) of updates are applied. When this problem occurs, the CCMExec and TSInstallSWupdate processes appear to be in hanging state. If the thread count is monitored with Task Manager or other tools, the TSInstallSWupdate process shows that approximately 774 threads are in use.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


Important notes about this hotfix

This hotfix is available for installation in the Updates and Servicing node of the Configuration Manager console for version 1602. If the service connection point is in offline mode, and this issue occurs after the update is imported, you will need to re-import the update so that it is listed in the Configuration Manager console. Refer to Install Updates for System Center Configuration Manager for additional detail.

For Configuration Manager version 1602, this hotfix can be installed before or after the Update Rollup for System Center Configuration Manager current branch, version 1602 (KB 3155482). Because this hotfix does include an updated version of the Configuration Manager client, it contains all of the same client-related changes from the Update Rollup. The Installation Notes from KB 3155482 also apply to this update.

Prerequisites

To apply this hotfix for System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager, you must have the following installed.

Description of Cumulative Update 3 for System Center 2012 Configuration Manager Service Pack 2 and System Center 2012 R2 Configuration Manager Service Pack 1

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

System Center Configuration Manager, version 1602

File nameFile versionFile sizeDateTimePlatform
Configmgr1602-client-kb3174008-x64.mspNot Applicable2,039,29611-Mar-201621:20Not applicable
Wuahandler.dll5.0.8355.1307610,48011-Mar-201621:20x64
Configmgr1602-client-kb3174008-i386.mspNot Applicable1,638,40011-Mar-201621:20Not applicable
Wuahandler.dll5.0.8355.1307389,80811-Mar-201621:20x86

System Center 2012 Configuration Manager and System Center 2012 R2 Configuration Manager

File nameFile versionFile sizeDateTimePlatform
Configmgr2012ac-sp2r2sp1-kb3174008-x64.mspNot Applicable5,361,15214-Jan-201602:15Not applicable
Wuahandler.dll5.0.8239.1415590,00014-Jan-201602:15x64
Configmgr2012ac-sp2r2sp1-kb3174008-i386.mspNot Applicable3,780,09614-Jan-201602:15Not applicable
Wuahandler.dll5.0.8239.1415378,03214-Jan-201602:15x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: kbqfe, kbautohotfix, kbsurveynew, kbexpertiseadvanced, kb, SCCM, ConfigMgrCB

↑ Back to the top

Article Info
Article ID : 3174008
Revision : 3
Created on : 9/19/2017
Published on : 9/19/2017
Exists online : False
Views : 407