acpikd.dll
ACPI debugger extensions file version info
Library on Windows 4 known copies with hashes
Is it the real acpikd.dll?
C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\winxp\C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\winxp\C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winxp\4 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\winxp\acpikd.dll · signed by Microsoft Corporation
1c4f0419802099eabd8737e0931cc925b7730b9ff97acf2b37f696d0e4bb018510.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\winxp\acpikd.dll · signed by Microsoft Windows Kits Publisher
4c42657b5468023b98d9dec2d298219457bbce5f9e216b8cfe0ed6ca2a93095e10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\winxp\acpikd.dll · signed by Microsoft Windows Kits Publisher
50b64c53ea6b946a9d968096c3f52c750f5982dd6f2198a58243b86451571de010.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winxp\acpikd.dll · signed by Microsoft Corporation
df14b2bbec8de88ed142ed016c757e4ceae33a125ad82b785d1c735d16078732From the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.