api-ms-win-core-interlocked-l1-1-0.dll
ApiSet Stub DLL file version info
Library on Windows 7 known copies with hashes
Is it the real api-ms-win-core-interlocked-l1-1-0.dll?
apisetstub in the file’s header: a renamed copy still carries itC:\Program Files (x86)\Cisco Systems\Cisco Jabber\C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\arm\C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\x64\7 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\arm\api-ms-win-core-interlocked-l1-1-0.dll · signed by Microsoft Windows Kits Publisher
2d6e39bf747c2845d89efbf9db453c0d646354216b2a3cae1dce297eda7b837110.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\api-ms-win-core-interlocked-l1-1-0.dll · signed by Microsoft Windows
52df3c5ded71786cf0f4f7545d59f5e6e168e6a499862c59b5985f6071f201ab10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\downlevel\api-ms-win-core-interlocked-l1-1-0.dll · signed by Microsoft Windows
7854c9b8e70b0e261784492db82873c7f84e427d9411686bb41c1172fecbf15210.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\downlevel\api-ms-win-core-interlocked-l1-1-0.dll · signed by Microsoft Windows
9ae7004f2870197c1fdaf8e6ad212b46a8a7fc2a6ddd7b507d8630e614ff25f810.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\x86\api-ms-win-core-interlocked-l1-1-0.dll · signed by Microsoft Windows
e378bc303f7008a76a845736d5a6b0d56746e4904a9792fdb642cddd52028b4b10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\x64\api-ms-win-core-interlocked-l1-1-0.dll · signed by Microsoft Windows
f57902b8877ade936a37448317a01cd79b36cda8159a17d3cd86a08d53ba724010.0.14393.33 (rs1_release_sec.160727-1952) · C:\Program Files (x86)\Cisco Systems\Cisco Jabber\api-ms-win-core-interlocked-l1-1-0.dll · signed by Microsoft Corporation
ff482f69f2183b5fd3c1b45d9006156524b8f8a5f518e33d6e92ea079787e64dFrom 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.