api-ms-win-core-memory-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-memory-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:\Windows\system32\downlevel\api-ms-win-core-memory-l1-1-0.dll · signed by Microsoft Windows
12e1b1299659686c57674477cbb7fe9092593bab4119a9b0e79138d2a3e715c810.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-memory-l1-1-0.dll · signed by Microsoft Windows
1541b5811a7af089ece0c781f934da011f0c5667a83f3d1234b4ee5403eb334f10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\downlevel\api-ms-win-core-memory-l1-1-0.dll · signed by Microsoft Windows
186c2a5b27afa1ecbeead7254a7f965a222cbad1f365c7bc89bdb7bde343581f10.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-memory-l1-1-0.dll · signed by Microsoft Windows Kits Publisher
88ede9e0db1e86d6cdd6673321761c818410930fa033a236d2fb894592c2b15a10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\api-ms-win-core-memory-l1-1-0.dll · signed by Microsoft Windows
bbf2556eff6f0bc6a11d73821aca2c14d5c8235143ceeb16b55b47eee453f17910.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-memory-l1-1-0.dll · signed by Microsoft Windows
e7c72a3db22143283d7b4d9ed66fb98a37fa9de06ea1296b076941d22c2120f110.0.14393.33 (rs1_release_sec.160727-1952) · C:\Program Files (x86)\Cisco Systems\Cisco Jabber\api-ms-win-core-memory-l1-1-0.dll · signed by Microsoft Corporation
50bf87da10ae3f442c457e42d6666993b0fca7c5d4df521e8cd0959995fbcddcFrom 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.