File Security v9 problems after Windows Patchday December 23

[StotheR 0]

Hello Community,

we have a rather big amount of systems with problems with File Security v9 after installing current Windows updates. Every system which installed the freshly released Windows updates looks like:

Windows server versions from 2016 to 2022 are affected like this. 

The update on Windows Server 2022 from yesterday is KB5033118, and on Windows Server 2016 it is KB5033373.

 

Any help would be appreciated.

Kind regards

 

Edited December 13, 2023 by StotheR

[StotheR 0]

Maybe the problem isn't related to Windows Updates, 

 

[Marcos 5,725]

You have an older version installed, the latest v9.0.12018 or v10 don't have this problem with Entrust cert. expired on Dec 7 and the server being subsequently rebooted. Do you have v9.0.12013 installed on all servers?

We are preparing a workaround via an automatic module update, however, it will be necessary to upgrade to the latest v9 or v10 afterwards.

You can fix it yourself immediately by:
1, Uninstalling ESET in safe mode using the ESET Uninstall tool and installing the latest v9 or v10.
2, Changing the system date to a day from before December 7, rebooting the server and upgrading to the latest version v9 or v10.

[StotheR 0]

Yes, all affected servers have 9.0.12013.0 installed and rebooted last night. And there will be a lot more reboots this night. 

How can we fix this? File Security Update fails with Windows Eventlog messsage error 1922

Edited December 13, 2023 by StotheR

[StotheR 0]

A technical support told me steps how to fix this:

-Deactivate HIPS
-Restart
-Update ESET Installation
-Restart
-Activate HIPS
-Restart
-ESET installation is happy like never before

Worked for me

Edited December 13, 2023 by StotheR

[offbyone 10]

We have still some customers with v9.0.12017 on Windows 2008 R2 in disconnected environments. As v9.0.12018 needs Azure Code Signing it will not work in those environments.

Is there any workaround for this setup?

THX

Edited December 14, 2023 by offbyone

[offbyone 10]

Just rechecked the installations and rebooted one of our test systems

The systems we are running with v9.0.12017 seem not to be affected by this issue.

Maybe someone can shed some light on this.

Cheers

[Marcos 5,725]

4 minutes ago, offbyone said:

The systems we are running with v9.0.12017 seem not to be affected by this issue.

Yes, version 9.0.12013.0 was the last affected. Newer versions were not.