interop.searchapi.dll
Library on Windows 4 known copies with hashes
Is it the real interop.searchapi.dll?
C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm64\C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm\C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\4 known copies
10.0.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm\interop.searchapi.dll · signed by Microsoft Windows Kits Publisher
4d1e3e39ffe5c7ce083104a056dc78359e3d13d42f8fad145401612ea83c7f2d10.0.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\interop.searchapi.dll · signed by Microsoft Corporation
5f10e6ca57038ac8cdb0d1fc136e9f4df24aa6962709e1a3183d612c24d61f5310.0.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm64\interop.searchapi.dll · signed by Microsoft Windows Kits Publisher
63f09e8fff8a4fff3565d7ff526186e77ddf0eeb164a61aa2361a950d9325d2210.0.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86\interop.searchapi.dll · signed by Microsoft Corporation
b543ff26b00c61f1bcbc934bc77b00189c3cccd58932db7f64987a6e0b35ee71From 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.