CmdID

CmdID / Files

ByteCodeGenerator.exe

AppX Deployment Bytecode Generator EXE file version info

Program on Windows 14 known copies with hashes

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

Is it the real ByteCodeGenerator.exe?

file version info and known copies
Installed inC:\Windows\system32\
C:\Windows\SysWOW64\
Signed byMicrosoft Windows
ProductMicrosoft Windows Operating System, Microsoft Corporation
DescriptionAppX Deployment Bytecode Generator EXE

14 known copies

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

75dc8211bf053eba421d02f7fa7da01bb8d9501d457d555082d6f2ac097c5e30

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

8bf577435eaae954cd2442ec53aa11c9e321bd418865027ebee8b7901b605670

10.0.19041.1081 (WinBuild.160101.0800) · C:\Windows\SysWOW64\ByteCodeGenerator.exe · signed by Microsoft Windows

eb4fb4c2d84e6987a3b89ae8b54705eabe2c61ea596992cce18d2727aeb5b81d

10.0.19041.1081 (WinBuild.160101.0800) · C:\Windows\system32\ByteCodeGenerator.exe · signed by Microsoft Windows

f039a40eca1b054536afa700df4297a51cae72d22ff6326f95b89290b7ad615e

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

2a3445ccebde3cff3d78f7fd8b02155cbcbabfa3eafc7304bf99b6748f1969b0

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

83a7df7c45f6d7f39534dbdacd49ef8b49f9fa789578836d63b01252ddad7161

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

0ea43164b733b7aceec01d15f2e586f389d9befbd722538879d903b31a7eee9b

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

1ec4d8548461cf788a788cae759cb31da18ab19c28215f72e675dfdacf30e883

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

a0bb35738d10a16190f279a30c27e1e217a5e121ec0b2a2608506dd107342c6a

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

e2a97da4efd83513bd97010f00bcd746c9ac3f73ed0a6b9d398851ac59fc19cc

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

7f0e550497d89eceb66b64301f1a55bbfe9fb12d83086ffc34fd83f964dc1c57

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

8eaba705068d576ecf9beeaf62de53a8189ff9f339905e4a71ea3fdf5e3c90b2

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

01b38fd2c1df5dafdaaff096fb5d4f93697428afcb98efeaafd80c1c55fbb462

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

19e5361d92719cc2ed58c98d4115ce9d87fa584eb190c51afe3824805709ff2d

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.