This guide explains how to solve a possible issue causing the Engine B of G DATA clients to not update.
On 24 October 2016, a signature update replaced the G DATA engine (Engine B) with a new version (GDAV.dll). As part of the update, the code signing certificate that we use to sign our files was replaced, in order to use a different root certification authority.
Usually, Windows automatically downloads the required root certificates directly from Microsoft, but we have recently discovered that this does not always seem to be the case. This phenomenon seems to occur particularly in connection with clients that obtain their updates from a WSUS.
The group policy that disables root certificate downloads may have been enabled (Computer Configuration\Administrative Templates\System\Internet Communication Management\Turn off Automatic Root Certificates).
How to identify the issue:
The virus signatures of Engine B are outdated for a particular client, however Engine A remains up-to-date.
How to fix the issue:
If the certificate does not exist, you can download the necessary “R3 GlobalSign Root Certificate” here and install it on the client:
The certificate can also be distributed via a GPO.