CmdID

CmdID / Files

UserAccountControlSettings.exe

UserAccountControlSettings 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 UserAccountControlSettings.exe?

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

12 known copies

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

9d9f35733e5d12586b3ce1f4d9f6620b7c4d22dca1b62adc18fcbbdfb70ea350

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

b16024706b4a50090c717b58246ee9cd35501f5612b1501e1358011ac1cf23f6

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

daa00a8c9f3531100df87fc5d4226b6e8a476d80e2d109274128ca65701197c5

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

eb4c62e672647c1ad1a247356ffd738feea55ff0390edff2a2bde89d9362250e

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

80ae4dd23ebb1379c874e4eb9221d45bdd7424725c3f9b4e0f8edcb4425da6d0

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

f5eb8472b58452e0ae570c52f6d6418d6a25e5e7c4e3c3299586e84bb1fd2b4b

10.0.17763.1075 (WinBuild.160101.0800) · C:\Windows\SysWOW64\UserAccountControlSettings.exe · signed by Microsoft Windows

07ada4f22b7a3cf3b56e3e687a9a03a6517ada894911e398253dc8d36d84423e

10.0.17763.1075 (WinBuild.160101.0800) · C:\Windows\system32\UserAccountControlSettings.exe · signed by Microsoft Windows

51afe88d1828724912800ce6507af145838c3457ee6105b4a33782819d3944a7

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

316d2114f785f7b576545f0565050a3fc9fad26de258b450a768c643cdb845c7

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

abd38d1510072f2d241fcd356a71a399307047523b3ccb0cb5a6233a242e44cb

6.3.9600.17415 (winblue_r4.141028-1500) · C:\windows\system32\UserAccountControlSettings.exe · not signed

4a039bfd71687144f174dafcf3614a5060d56e95ccd3ccb7166b6c52ae71befe

6.3.9600.17415 (winblue_r4.141028-1500) · C:\windows\SysWOW64\UserAccountControlSettings.exe · not signed

df2e72f49ca58ffaebf87fd9800132d27d647825f2aafb1fa4d4114b6579540c

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.