Cause: This can occur due to the G DATA Administrator being open during the installation of the update. Another cause can be unexpected database entries during the conversion of the database. …
On the affected clients, please temporarily deactivate the functionality "Use Spam Filter" in the G DATA Administrator under "Clients/Client Settings/AntiSpam". We are trying to provide you with…
We are happy to offer you many new useful features with the latest version of our business solution. Unfortunately we noticed some issues during the roll-out process. In order to enable you to…
Please rename the file "NativeMessagingWP.exe" temporarily into "NativeMessagingWP.exe.tmp" and restart the terminal server. We are trying to provide you with an automated solution as soon as…
The following reasons could prevent you from logging in to G DATA Administrator:
Cause 1: The user credentials are not recognized
Cause 2: The ManagementServer is not reachable
Cause 3: The…
In the event of a G DATA Security Clients showing the status « No connection to server » under the column Security Status, there can be several different causes. Not all of them indicate…
All of the following has to be done on the computer where the Security Client which presents the issue is installed.
Step 1. Download DebugView from Microsoft by clicking here.
…
Background information:
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…
Background Information:
To ensure the integrity of our update process, we are using SHA2 encryption for our security certificates.
Windows Server 2003 (prior to R2) cannot natively receive…
This is a rare issue which could happen after a software update to 14.0.1.122, resulting in the G DATA Driver Framework not being correctly installed.
As a result, the G DATA Security Client…
