CmdID

CmdID / Files

appidtel.exe

Initializes Appid ManagedInstaller and Smartscreen Telemetry file version info

Program on Windows 15 known copies with hashes

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

Is it the real appidtel.exe?

file version info and known copies
Installed inC:\Windows\system32\
C:\Windows\SysWOW64\
Signed byMicrosoft Windows
ProductMicrosoft Windows Operating System, Microsoft Corporation
DescriptionInitializes Appid ManagedInstaller and Smartscreen Telemetry

15 known copies

1.00 (rs1_release_d.170807-1806) · C:\Windows\system32\appidtel.exe · signed by Microsoft Windows

c8f93ffee5e0e267e1d2225ef73d6b6b938cc7e6a0907645cf955ebe6163edc8

1.00 (rs1_release_1.191001-1045) · C:\Windows\SysWOW64\appidtel.exe · signed by Microsoft Windows

16a1394d25071e3825daa5e2fe0b07dd524e0aa92cb35aa220431e18547bab8e

1.00 (WinBuild.160101.0800) · C:\Windows\SysWOW64\appidtel.exe · signed by Microsoft Windows

162f20270b04ec1cc1d899d1cf87f4aec08458c2fdb8e0030a72dd27f26e0e5f

1.00 (WinBuild.160101.0800) · C:\Windows\SysWOW64\appidtel.exe · signed by Microsoft Windows

24a53fdb11310d8e797729c90600ae694a49ead6c4b277110662028a11f946be

1.00 (WinBuild.160101.0800) · C:\Windows\system32\appidtel.exe · signed by Microsoft Windows

2ecfeaa5c9788fe9197d1a1b34cf5128ab4ee7e7828113b3fa83700bfb4680a7

1.00 (WinBuild.160101.0800) · C:\Windows\system32\appidtel.exe · signed by Microsoft Windows

30d867e5b3bfed0223af5d178dce1cf48bdba3d83e6808411650cfac05ee00d4

1.00 (WinBuild.160101.0800) · C:\Windows\SysWOW64\appidtel.exe · signed by Microsoft Windows

6f6067fe2d9ff65bccd9fb974c57e6efe707756cbb672e839d01486b116985c2

1.00 (WinBuild.160101.0800) · C:\Windows\system32\appidtel.exe · signed by Microsoft Windows

902f327bff5a5f4b2333f5ae28f843a1ac705bc0e04b4b37cee3d9158f8f017c

1.00 (WinBuild.160101.0800) · C:\Windows\system32\appidtel.exe · signed by Microsoft Windows

a5d3bb75d551b3465b11067c2564faa6b54355d1f8d129aac2e61580d7bb90d6

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

bd27c729cb376cc4ac19c0300ce017f837b91eabc323d0221a8bf74f82588cc3

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

c55e4eb223b638b74fdfd890ba57e45e4fe30afff56246800e4beda0f4c716c2

1.00 (WinBuild.160101.0800) · C:\Windows\SysWOW64\appidtel.exe · signed by Microsoft Windows

cb10609902a1b3d71d36e73965eb4c93818e072b001453818a7b4835d84c17e6

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

e5c092055f07da776ccacdcb16ace7d2f3086fbb9df0cfcb07eca06479976c93

1.00 (WinBuild.160101.0800) · C:\Windows\system32\appidtel.exe · signed by Microsoft Windows

f65a8737a20f54aa7a245524fcaa3e8d21aa08dc7725c5409551d35793ce4f2e

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

f9f6ff3939beb458f7b7c3f50061978a47a901f46cccf5ab8ba0982c92f05afa

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.