CmdID

CmdID / Files

typeperf.exe

Command line performance monitor file version info

Program on Windows 14 known copies with hashes Command typeperf

Opens CmdID with your command. It is read in your browser and sent nowhere.

Is it the real typeperf.exe?

file version info and known copies
Installed inC:\Windows\system32\
C:\Windows\SysWOW64\
Signed byMicrosoft Windows
ProductMicrosoft Windows Operating System, Microsoft Corporation
DescriptionCommand line performance monitor

14 known copies

10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\typeperf.exe · signed by Microsoft Windows

2b8ef4dba0da835cb701a396edda38213c6b8e0a190f5f58e5f7bd75765dff54

10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\typeperf.exe · signed by Microsoft Windows

3b9c3916765d0280401720ed7e61b6b68bc6f881e6d93bd000cf024dd9a2ecd3

10.0.19041.546 (WinBuild.160101.0800) · C:\Windows\SysWOW64\typeperf.exe · signed by Microsoft Windows

7bc9b82f3dce94d42b13e93ea134864715c7ce2f6e1e62c0fe7f0dd4e18664aa

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\typeperf.exe · signed by Microsoft Windows

6189863e404821412177546146bf39be81603229f5fcc7d669e4737dd8ff7b7e

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\typeperf.exe · signed by Microsoft Windows

7da4fb590c5bcb0a98bab84bc587ccc728defdfff7139fc7994734f192cac385

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\typeperf.exe · signed by Microsoft Windows

d036bcd15fb7054aa1951bd72c776e3ba089c3e6ab5020a850a1b52ed0ed2f08

10.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\typeperf.exe · signed by Microsoft Windows

1cd1d9c12e247c788e526a84576c9b2b06740c2c3618bf444c19da1bdc38880c

10.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\typeperf.exe · signed by Microsoft Windows

7222afa59b7326736769bc835a4771248dcb3986f0f085df200b53503d52a6b8

10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\typeperf.exe · signed by Microsoft Windows

1d0b5daf3b8cf646e277597709a1592731d44c816a6665818ee3a1ef54e65fc2

10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\typeperf.exe · signed by Microsoft Windows

2747462e89fcdbf41ab73f46a8efb67057792fd659d5af9f54f1f8cf19f555d9

10.0.14393.0 (rs1_release.160715-1616) · C:\Windows\SysWOW64\typeperf.exe · signed by Microsoft Windows

1f7a57b166faeb48e2c4475af2a4d18327aafb62d2b4a4a2b89a9eee6309322a

10.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\typeperf.exe · signed by Microsoft Windows

3d3b3a8d528a2f12f1d1414a88781082d68a6367d47b054dfe111148e88de15d

6.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\typeperf.exe · not signed

8959c4f253f33bb139f788350d0e6d0035455ab9a56bfac9f3070e66f25ac10e

6.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\SysWOW64\typeperf.exe · not signed

ef1e50f0cc9fa1751838b6e0ecd533cbd446bf90733938509fe255cbcb4c4309

From 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.