GridinSoft Threat Intelligence
avkmgr.sys file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2019-09-02 17:43:48 (6 years ago); latest analysis 2026-05-13 20:01:14 (2 weeks ago).
Company metadata: Avira Operations GmbH & Co. KG. Product metadata: Avira Product Family.
Signed by Avira Operations GmbH & Co. KG. ThreatInfo marks this publisher as trusted for this record.
ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.
Recommended action
What to do next
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
avkmgr.sys is a Windows file recorded in the ThreatInfo database. It is associated with Avira Product Family. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2026-05-13 20:01:14 (2 weeks ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Avira Product Family |
| Company Name: | Avira Operations GmbH & Co. KG |
| MD5: | 20894c53c0b9db8f86993d9ecb78f9d5 |
| Size: | 35 KB |
| First Published: | 2019-09-02 17:43:48 (6 years ago) |
| Latest Published: | 2026-05-13 20:01:14 (2 weeks ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2026-05-13 20:01:14 (2 weeks ago) |
Overview
| Signed By: | Avira Operations GmbH & Co. KG |
| Status: | Trusted Publisher |
ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.
Common Places:
| %programfiles%\totalav\savapi\on_access\win32 |
| %programfiles%\scanguard\savapi\on_access\win32 |
| %programfiles%\pcprotect\savapi\on_access\win32 |
| %commonappdata%\totalav\updates\savapi 6.0.0\on_access\win32 |
| %commonappdata%\totalav\updates\savapi 5.0.0\on_access\win32 |
| %commonappdata%\totalav\updates\savapi 8.0.0\on_access\win32 |
| %appdata%\shield antivirus\motiflib\on_access\win32 |
| %commonappdata%\totalav\updates\savapi 8.0.1\on_access\win32 |
| %commonappdata%\totalav\updates\savapi 9.1.1\on_access\win32 |
| %commonappdata%\totalav\updates\savapi 10.0.1\on_access\win32 |
ThreatInfo has observed avkmgr.sys in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
Geographic signal
Observed country distribution
ThreatInfo has seen avkmgr.sys across 113 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 12.5% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for avkmgr.sys is Windows 10 with 84.8% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
avkmgr.sys is identified as pe for 32-bit systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
37d92d92e8a225ad5844873dea8fe6e8
d5d0606030a3099277dd99478436f254
9bbfca478134e09a2244d5b9c143250b
54e0d37517d49e8d03800d0b2ee801b5
9bd7838db29cf912e20d61b948291d0e
79cf51bdc4a52940a7f84172e26d97ff
fec8e668f16c40e436f71a52ab7f07b6
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
Report conclusion
This hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.