Reset Search
 

 

Article

KB45145 - Host Check gets stuck at compliance and fails on Endpoints running Windows 10 1909.

« Go Back

Information

 
Last Modified Date4/19/2022 12:46 PM
Synopsis
This article describes an issue where Host Checker gets stuck at Compliance check and fails on endpoints running Windows 10 1909.  
Problem or Goal
On Windows 10 1909 endpoints, host check get stuck at compliance and fails due to long a delay in API response on operations such as GetFirewallState, CheckRTPState, and GetDataFileDetails. This is observed on Windows 10 1909 machines running patch below August 26, 2021—KB5005103 (OS Build 18363.1766) Preview (microsoft.com) and using ESAP version 3.9.6 or greater.
Cause
ESAP 3.9.6 and above uses WMI-related APIs. When another AV product is installed on the machine, the system will disable Windows Defender automatically, and this also causes Windows Management Instrumentation (WMI) provider host process to stop working.
Solution
A different method has been incorporated from ESAP 3.9.9. (April last week release – Tentative) to overcome this issue.

Microsoft has also fixed this issue in their August 2021 patch update - August 26, 2021—KB5005103 (OS Build 18363.1766) Preview (microsoft.com). Therefore, updating Windows would help resolve the problem.
 
Related Links
Attachment 1 
Created ByRaghu Kumar

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255