The existing DB and the one downloaded will be different. The issue may have occurred either while comparing the DB’s or while loading the files. When the AV database is updated, a temporary directory is populated. The temporary directory includes a test DB. The test DB is compared to the worker DB to determine what needs to be updated.
If you are seeing the issue reptitively then the resolution shared the in the KB that pradkm shared should do the trick:
- Turn off the auto update in the AV and unlink the avp.set file.
The F/W might have not experienced the same error again while performing an auto-update of AV pattern, hence you saw the log one time only.
Tks,
Abhishek
Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too!!!