Client machine runs Windows System Assessment Scan at 100% CPU utilization and often times out.
Last Updated January 09, 2014
Client machine runs Windows System Assessment Scan (WSAS), manually or on schedule, and the scan takes over 12 minutes to complete and utilizes 100% CPU.
Often the WSAS fails to complete as it takes over the 20 minute default time to complete. The WSAS will still show running in the STPatchAssessmentScan.log file, but the process on the Agent will be cut off after 20 minutes.
GUI shows: Task Stopped
Appears there are software conflicts when MSXML4 is installed on the Client.
This issue was resolved in PMImport version 7.1.497 release.
Also see KM: TECH204960, for it details other resolution steps pertaining to this issue topic.
Patch Management 7.1, SP1, SP2, MP1.x & PM 7.5
Imported Document ID: TECH213155
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe