api-ms-win-crt-stdio-l1-1-0.dll

ApiSet Stub DLL file version info

Library on Windows 10 known copies with hashes

Is it the real api-ms-win-crt-stdio-l1-1-0.dll?

file version info and known copies

Original nameapisetstub in the file’s header: a renamed copy still carries it

Installed inC:\Program Files (x86)\Cisco Systems\Cisco Jabber\
C:\Program Files (x86)\Cisco Systems\Cisco Jabber\x64\
C:\Program Files (x86)\Microsoft Office\root\Client\

Signed byMicrosoft Windows

ProductMicrosoft Windows Operating System, Microsoft Corporation

DescriptionApiSet Stub DLL

10 known copies

10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\x64\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Windows

1ea135cde9495900f7d1339384f4a93dd00053796209f8d625f49c3a3d191ae4

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\downlevel\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Windows

2a466648affd3d51b944f563bb65046a3da91006a0d90fb2c0b123487a1fc1b3

10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\x86\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Windows

38b98b4e2f41867da273a37c9224a4a111974cc68f7daba4560bc2dd9e404b39

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-crt-stdio-l1-1-0.dll · signed by Microsoft Windows Kits Publisher

3be5b92bba348935ab1be3be1140daf598e91bf19764002bd928ad919ec10185

10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Windows

550ea9556ba9197b25b7eb9d12ca9dd9ad0e820e4dba91f94dd54b57a2e6934f

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\downlevel\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Windows

d6b21c2d5d385c60299f3974ed531f3d780fbe7b191a7a9842402558d46c354e

10.0.14393.33 (rs1_release_sec.160727-1952) · C:\Program Files (x86)\Cisco Systems\Cisco Jabber\x64\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Corporation

b89c2c17ab436bd6191eba6419d9a531360f424a4461c31195ed5c6497982b1b

10.0.14388.0 (rs1_release.160709-1635) · C:\Program Files (x86)\Cisco Systems\Cisco Jabber\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Corporation

e0e3f1342a83ed2cfd3daac678343c0b402abd80bf43f861df6266c818dfb731

10.0.10240.16384 (th1.150709-1700) · C:\Program Files (x86)\Microsoft Office\root\Client\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Corporation

104a76b41cbd9a945dba43a6ffa8c6de99db2105d4ce93a717729a9bd020f728

10.0.10240.16384 (th1.150709-1700) · C:\Program Files\Common Files\microsoft shared\ClickToRun\api-ms-win-crt-stdio-l1-1-0.dll · signed by Microsoft Corporation

293c76a26fbc0c86dcf5906dd9d9ddc77a5609ea8c191e88bdc907c03b80a3a5

From 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.