CmdID

CmdID / Files

SystemPropertiesComputerName.exe

Change Computer Settings file version info

Program on Windows 12 known copies with hashes

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

Is it the real SystemPropertiesComputerName.exe?

file version info and known copies
Installed inC:\Windows\system32\
C:\Windows\SysWOW64\
Signed byMicrosoft Windows
ProductMicrosoft Windows Operating System, Microsoft Corporation
DescriptionChange Computer Settings

12 known copies

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

379edfff7ad75e0b32bb3bf0060f361e79103f55f525fd687a5ef093f3e0f547

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

936f26bc9f324032e96e0628fdd3f7855cd4f5278e0c59d52789fa99a1fd0744

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

aef9cb5cda480566b3a8e1e0267f31d52f2b48b96cd3d04006b69345eb207820

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

bd3a97327326e2245938ec6099f20059b446ff0fe1c10b9317d15d1a1dd5331e

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

01a7e56721577c3a30364c8e46af46480133033c14e118872422ecfaa350f80a

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

f0e6827000034517f46fed2ae02159c916ba93a62bf02f3c2ce2b1cd162f773c

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

1425d610beb0e3cc092ebe55ca1817ad0ae703489a20bfcabe52e0e2473a8a54

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

aca5320eeb23777b050f7ab1483c216d5f951e34c1c350b93ead5d59bd83bf81

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

ee2b5fdce2a54b39fbf61456ba6f9facc39e0eee70716e218d0e828695c3c485

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

fda5a4254fb23840e18168e00957916da81df464d457a082e407ae842cac28af

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

16cc00cecede422846acf63b6f7cc489e20e3fb059606a9537de4d4a04b60043

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

c70905fe4679f6792ed5a139d75bbaa0bb37cbf5707ac4fe0fee57e39b3f7c25

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.