interop.taskscheduler.dll
Library on Windows 4 known copies with hashes
Is it the real interop.taskscheduler.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\x86\interop.taskscheduler.dll · signed by Microsoft Corporation
3dcb78d7a32393079f0962919d6ce882999b0ab23a9fb646c7a06a9133263e9710.0.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm\interop.taskscheduler.dll · signed by Microsoft Windows Kits Publisher
a7b9ff840a9fdf9c9905a2b1b34cd1cdc4681374a616faaf0b86c5bc2c68615210.0.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\interop.taskscheduler.dll · signed by Microsoft Corporation
ba0c06ce23d181287d6b895c9b90aa909d319c82e9829181e858bf290afbe1bc10.0.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm64\interop.taskscheduler.dll · signed by Microsoft Windows Kits Publisher
f1bafbd529dd3dc5279853541bd3b08a95a524678cd544f0bd1b3109e52798f9From 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.