CmdID

CmdID / Files

diskperf.exe

Disk Performance Configuration Utility file version info

Program on Windows 14 known copies with hashes Command diskperf

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

Is it the real diskperf.exe?

file version info and known copies
Installed inC:\Windows\system32\
C:\Windows\SysWOW64\
Signed byMicrosoft Windows
ProductMicrosoft Windows Operating System, Microsoft Corporation
DescriptionDisk Performance Configuration Utility

14 known copies

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

b596915231e3390d1940545e8cd54d04d554a0f445e6c9310c861823b02de7ce

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

fd9840901413b61b3ca8da59535835984b643eadaccae870df818fa32f2a2a3a

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

9175dcdc9d866e0fd09ff4dabf8783a203201809489b1e73486e2183960c6a4d

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

293044b6001452f9855ce34bbf26f8a5c9d44a5cd2fbe9d8ac0651398c0f5fcb

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

29bc6751b20eafaa4e2748370b5358f0c7ae679627df2e01808615d96aa89a32

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

e9d5ae57a518963d3f6c290b81e77fcee79a0837046b5064b9c5393ebd073e16

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

b75f91ab4bb8411ee2c01c3f80e8565257ac223b9755276797afcab0a0fe0b3b

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

d7f1468580a04f101c5ab726b7e9d73cb71c9f1d5e94da51eee0f65e9631c78a

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

1839a4aad437b18b30e9fe880edbda89eea9b76dd0725dad2c99029ceb4e64bc

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

3a6d5e97dc08b85ea6e0372791d4f68cb93dc0020d195823c0ce1ad8b891b3f5

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

75062f46b66137e69a8570ff73d52dc217b6347491c7a5932b51d51903b62016

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

bfaa29161f3a1c6b7e427ea7a7bd39fcf47bf84448b3800e2ed686b062453f71

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

6d1dfe10bf4482151db3a8f34601dfdb527cc7ea107c0a74d8498dfa54e4e976

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

b6f71bcf28a4861d4dd1ed4e43f51e21452396805549e617729a20bf7112ba01

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.