usbview.exe
Microsoft Windows(TM) USB device viewer file version info
Program on Windows 4 known copies with hashes
Is it the real usbview.exe?
USBView in the file’s header: a renamed copy still carries itC:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\4 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\usbview.exe · signed by Microsoft Corporation
1269ab6473eeb011fe099cd41e945d4510291b8071d5881f8ec3187a7714236f10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\usbview.exe · signed by Microsoft Corporation
4eb5dadfa86ccffe209a050e20a526beeb7c3a116229cf0465de4278b387508010.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\usbview.exe · signed by Microsoft Corporation
5240369de615b076f7de548523cdda51d720078d130985b177e00f3c05c4eb9610.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\usbview.exe · signed by Microsoft Corporation
df27cf370ed330851796238fb07f48882b25b0ab3e9eec91151188d2590c22faFrom 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.