midlc.exe
Microsoft IDL Compiler file version info
Program on Windows 3 known copies with hashes
Is it the real midlc.exe?
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\x64\C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86\3 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\midlc.exe · signed by Microsoft Corporation
0f24504d86bc5ea1dc8b6297b13627bfac1b9326b254df7936a04427e7fdcc8b10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86\midlc.exe · signed by Microsoft Corporation
2dac377ece0c1bf4f793d4741894e356fe9eaa7d1f54c9cc0fdf7e50b3e46e6c10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm64\midlc.exe · signed by Microsoft Windows Kits Publisher
5f5973119bcc0faf3bbb8bcd039acb979b831b490415efcf8e98fb5141b50231From 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.