CmdID

CmdID / Files

imjpuexc.exe

Microsoft IME 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 imjpuexc.exe?

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

14 known copies

15.0.9600.18514 · C:\windows\system32\IME\IMEJP\imjpuexc.exe · not signed

28864235401eaa2d677d42bd8e7a40da432757731dcea54a260fcf5d6657723e

15.0.9600.18514 · C:\windows\SysWOW64\IME\IMEJP\imjpuexc.exe · not signed

c8bebe08952543ba996ca294b5638deb26c2f55695d87de2de1282888642e449

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

5e23ea52c847af73d4f4053890d526a3603a89a0ca8b0f39c9ad27685c9b01c4

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

6847e60a56b215611dcce810eed693c33aead8e63ce648a655df92a6e0b9907f

10.0.19041.844 (WinBuild.160101.0800) · C:\Windows\system32\IME\IMEJP\imjpuexc.exe · signed by Microsoft Windows

285347777551dee98ecc8a4ab3b95d4885aabbcf488ef2adf5b6a327e1705211

10.0.19041.844 (WinBuild.160101.0800) · C:\Windows\SysWOW64\IME\IMEJP\imjpuexc.exe · signed by Microsoft Windows

589b3adf1e27ca32805b9f64d8f6f20eda17549441f3ce24168459ccfb16ed27

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

5b5afef9cec9b575ed8ca192f579ab5f8982de276118d243daa73498df4b4fec

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

71f269f30ba467e1ab201035e41bcc0ae16737cb22f5db66814964c7369e9595

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

74c543139ed0bb8bd671470e854439f566130c6eed1ff3bcb714d2d899ee4c94

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

d7cf437a2c40e46a5df4d19871c6cd4b1e0499ba335cdf49001cd65e3630233d

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

ccf5768e6a6e2d9c263da61344d5348828b81ded7bd5135bf2b0c3a94bf7505a

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

d3cd759cba9aa5299501331cf4c7a4a9855996beca9d2eb76d750b6338af7353

10.0.14393.2457 (rs1_release_inmarket.180822-1743) · C:\Windows\SysWOW64\IME\IMEJP\imjpuexc.exe · signed by Microsoft Windows

96df891a74d3b37e310f09577cc5d8187b7aac9c9fc0957b2aa1cf0851870f3c

10.0.14393.2457 (rs1_release_inmarket.180822-1743) · C:\Windows\system32\IME\IMEJP\imjpuexc.exe · signed by Microsoft Windows

c0ea23bd848c8947e553e94b2702045b91f660a8c0276ad00c184ec0e6b4e5af

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.