Host Integrity faild after installing "2024-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5040430)"

[Julia]

Hello Community, 

After installing the cumulative update 2024-07 for Windows 10  (KB5040430)
the SEP client shows the following: 

Security logfile shows:

Fail to execute Host Integrity check.

Error Type: 0x00100001, Error Code: 0x00000000

We searched for the error code and found this page:
https://knowledge.broadcom.com/external/article/227412/host-integrity-check-is-not-working-fai.html

The path in the article is incorrect and the file also exists: RegSSHelper.exe
does not exist on our Clients

Is there anyone with similar problems? 

Julia 

------------------------------
[Country]
------------------------------

[Murat Unver]

Hi Julia, I also have a Host Integrity problem. I have tried many ways to solve it, but the situation is the same and it persists on several computers. Have you found a way to solve the problem or does unistalling kb solve the problem?

[Cyberwise ProductSupport]

Hello,

 

We're having the same problem. Does unistalling KB fix the problem?

[Numan Firat]

Hi Julia,

I'm having the same problem, but I didn't realise it was caused by an OS update.

When you look at the debug logs on the client, do you see a log like "Script Engine is not trusted"?

Have a good day.

[Cyberwise ProductSupport]

Hello Julia,

 

I have the same problem. However, I didn't think it could be caused by windows update, but I didn't follow the update operations, so thank you for this information. Did you find a way to solve the problem? Does unistalling the KB fix the problem?

 

Thank you.

[Julia]

Hello 

we opened a case with Symantec Broadcom support, and they investigated on the issue. It nearly sure that there is any Problem with the certificate of cscript.exe witch is requested from the HI before using.  We can not say what is not working at this moment, but it did not look like a Symantec issue. So we opened a case with Microsoft, too.

They still investigate the issue. 

It seems that only Windows 10 LTSC 2019 is affected. 

Yes, uninstalling the update solve the problem. But there are security patches in the cumulative update, so I think to forego the update is not really a good solution. 

You should open a case with Microsoft, for getting help with that issue. 

Have a good day!

Julia 

------------------------------
[Country]
------------------------------

[BenjaminL]

Hi Julia

We have the same issue, any follow up?

Thank you.

[Julia]

Hello Benjamin, 

our Symantec support told us that there might be a solution by installing this KB5022661
https://support.microsoft.com/en-gb/topic/kb5022661-windows-support-for-the-trusted-signing-formerly-azure-code-signing-program-4b505a31-fa1e-4ea6-85dd-6630229e8ef4

The KB for Windows 10 1809 is KB5005625. 

This information is not verified from our side.

Julia 

------------------------------
[Country]
------------------------------

[BenjaminL]

Hello Julia,

I verified earlier that the KB of ACS has been updated. My environment will show that this KB update is not applicable.

 

At present, this problem is mainly caused by the Microsoft update updated to 2024-07. This month's Microsoft update should contain the ACS update (KB5005625).

 

It seems that this problem still needs to be solved by Microsoft. If Microsoft has any progress, please share it with me. Thank you so much.

[Julia]

Hello Benjamin, 
we have also tested KB5005625 and with the same result "not applicable".

Microsoft has asked us to do further testing. I will share the progress when we get more information. 

 Julia 

[YaoJung Ho]

Hello Julia

Looking forward to your feedback. Thank you very much.

John

[David Receveur]

I am experiencing this issue on 70+ Windows 10 x64 LTSB 1607 and Windows 10 x64 LTSC 1809 workstations.  The issue started once they were rebooted following the install of the 2024-07 cumulative updates.  When the host integrity check fails it causes the workstation to drop its network connection about 5 minutes after it reboots.  Prior to discovering SEP was involved we rolled back the patch level to 2024-06 to restore network connectivity.  Later I discovered that unloading SEP using "SMC.exe -stop" from an elevated command prompt also resorted connectivity.  I later found this was due to a quarantine firewall policy that gets applied when the host integrity check fails.  I also have cases open with both Microsoft and Broadcom to investigate the root cause. 

[YaoJung Ho]

Hello

Broadcom has already released a KB article regarding this issue and is currently investigating it. We can only wait until a solution is provided.

Failed to Execute Host Integrity check after installing July 2024 Microsoft Updates (broadcom.com)

[Julia]

Hello, 

I would like to share some good news: 

Our Symantec supporter told me today that they are working on a fix that will be distributed via live update. 

So maybe help will come soon. :-) 

Julia 

[Julia]

Update:

The definition to fix the issue will be available on EAS (Early Adopter System Server) at the end of August. If there are no problems, the definition will be published on LiveUpdate in early September. The rollout will be slow so that it will be available for everyone in mid-September. 

Julia