inspect.exe
Inspect Object (32-bit UNICODE Release) file version info
Program on Windows 4 known copies with hashes
Is it the real inspect.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\arm\C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\4 known copies
7.2.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm64\inspect.exe · signed by Microsoft Windows Kits Publisher
7c4d3080e314819d13d0a4f704068357d22db5c447a2462980766065f5c40d847.2.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\arm\inspect.exe · signed by Microsoft Windows Kits Publisher
a678c604be37eb2bff3b88c59b7bf2928c223932bb04ae45e477833dbb27bbc27.2.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\inspect.exe · signed by Microsoft Corporation
ed318c1025044df2df14cd15c74c881b7298ae7a35c8f3750560c0bc6ba6c91b7.2.0.0 · C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86\inspect.exe · signed by Microsoft Corporation
fc527011f17b3dcba93d914ab7322c1f3bc6fe3872c361082307a80984e660f5From 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.