PackagedCWALauncher.exe
Packaged CWA Launcher file version info
Program on Windows 10 known copies with hashes
Is it the real PackagedCWALauncher.exe?
C:\Windows\system32\C:\Windows\SysWOW64\10 known copies
10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\PackagedCWALauncher.exe · signed by Microsoft Windows
bb22c7893394bfacc3378a8572e48f950b088d3da16276bd5abb170168fb469d10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\PackagedCWALauncher.exe · signed by Microsoft Windows
bce34f788bc93a0a34f40ddbd9bd86f84221901539d1860d1bd8dfc589598b6110.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\PackagedCWALauncher.exe · signed by Microsoft Windows
22401de528f379922a04d7b8abeb5f4e895aa2064adb700b28bfb4496c15002d10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\PackagedCWALauncher.exe · signed by Microsoft Windows
c81f1f7a9fc42b2996b963fcc3d1f63adec73ec55b25e63fe351d43aa1d37dc610.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\PackagedCWALauncher.exe · signed by Microsoft Windows
142c50de65596c5ca9ebe97759b1a394b31d7b09d278cf73a015d3024fa7582210.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\PackagedCWALauncher.exe · signed by Microsoft Windows
4b9a85c67878eaef2f3bde0276e7533cea0a32dcef00200d09723ec1f5250dba10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\PackagedCWALauncher.exe · signed by Microsoft Windows
b3c953e34ae93919586941129884fae101a410c93af0a2975c190ba31a32c65a10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\PackagedCWALauncher.exe · signed by Microsoft Windows
c6aa828881ce6871f1c15f9a4ce466f9db9d459a5e81950dcc069a3cf2d81c3e10.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\PackagedCWALauncher.exe · signed by Microsoft Windows
62f68e3b2367257a4f2a901a2782f4beb7f628229a9961fc2c5e41dba18f0d2710.0.14393.0 (rs1_release.160715-1616) · C:\Windows\SysWOW64\PackagedCWALauncher.exe · signed by Microsoft Windows
bee117aca87d1bc29414792fdca229e51e1439e190217e0c04e8e30a88107698From 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.