CmdID

CmdID / Files

SystemUWPLauncher.exe

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

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

14 known copies

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

367601956d6255163f07cffd6ba93deb654773b297ac5c30f532f0b906ac0c14

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

6365be4bcb7d9d50f82a70b258aebeb852ac17401256bccbc86e44def7a52820

10.0.19041.746 (WinBuild.160101.0800) · C:\Windows\system32\SystemUWPLauncher.exe · signed by Microsoft Windows

7c9dc8ebb27cbafa8cc93e58505b6ac34456693f72118b69c764624114811251

10.0.19041.746 (WinBuild.160101.0800) · C:\Windows\SysWOW64\SystemUWPLauncher.exe · signed by Microsoft Windows

f005bc916dd91bba3a69d4ca31d37a573f0db67b2c520027defcca2e1dc1492e

10.0.19041.388 (WinBuild.160101.0800) · C:\Windows\SysWOW64\SystemUWPLauncher.exe · signed by Microsoft Windows

393462f20a4892225d4634b67a586f019b98c0a36a6966d2f9d2b9ee81711a4d

10.0.19041.388 (WinBuild.160101.0800) · C:\Windows\system32\SystemUWPLauncher.exe · signed by Microsoft Windows

510ede28028a3bbbaed028804ae5f0d8e5a5864f134021476b0a006a8e69be2c

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

410f049e2daafa15ed9f3486099bc78bbeab1befb109e18991a7c6b2765a8d73

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

8d0befa34203e90b314a69e6dd8c677318a27f7aea9cd2750d2e42dd8034dd44

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

25245a06a93732fa7e3765fc95f596df78c6f3b21a68c19066876a2518a7f4db

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

7817e2167bc070f37a39dbcc0cd5915a5062f3af558c1ca671fb2fcc2b97ccc0

10.0.17763.1339 (WinBuild.160101.0800) · C:\Windows\SysWOW64\SystemUWPLauncher.exe · signed by Microsoft Windows

2068b64ab16ff39acdbad5f7f3a86066cf80ac84dacea84457370070b9c9a69f

10.0.17763.1339 (WinBuild.160101.0800) · C:\Windows\system32\SystemUWPLauncher.exe · signed by Microsoft Windows

73b60714e59c471924707f7ec6a77d6f24b4868173c2640d711a80fd880f90fd

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

d12ed72f4f60cbb4c0fca2b02ccf21d9ae757fe0787ea80dc85a777ff47b9bbe

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

eb10676bb918d14b74929941471ecf6d02cd189e391549f1d03a692fff62eba2

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.