WSManHTTPConfig.exe
WSMan HTTP Configuration File file version info
Program on Windows 16 known copies with hashes
Is it the real WSManHTTPConfig.exe?
C:\Windows\system32\C:\Windows\SysWOW64\16 known copies
10.0.22000.282 (WinBuild.160101.0800) · C:\WINDOWS\system32\WSManHTTPConfig.exe · signed by Microsoft Windows
278a323e24d649623b121eb7d79edd48c76225e408cf96834f5c2ee236962bfb10.0.22000.282 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\WSManHTTPConfig.exe · signed by Microsoft Windows
7f042423a768874c2ee0d20921ebb206fa706ae2a83efd42b56f840b78049c6410.0.19041.488 (WinBuild.160101.0800) · C:\Windows\system32\WSManHTTPConfig.exe · signed by Microsoft Windows
a152a611d0ab437a194a199fb36b3ae35302124f5935d6991af9083e2bbac5ce10.0.19041.488 (WinBuild.160101.0800) · C:\Windows\SysWOW64\WSManHTTPConfig.exe · signed by Microsoft Windows
af31760fafeb4a2080923fc42f098b2f05a5f68153f8acd42ad9dc3955c5831310.0.19041.1202 (WinBuild.160101.0800) · C:\Windows\SysWOW64\WSManHTTPConfig.exe · signed by Microsoft Windows
055e7cea988f93dc9b0c43eba274f93e2dc00f6580197482b849979a41439ba610.0.19041.1202 (WinBuild.160101.0800) · C:\Windows\system32\WSManHTTPConfig.exe · signed by Microsoft Windows
eafcb43a413d3b66575c0f20274b6433fd9f46f585d608da4df5788f90448c5e10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\WSManHTTPConfig.exe · signed by Microsoft Windows
6afc2fcf2ce1dc46b2746a969f771614a3ac75fca85d04c69c567405c40150d710.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\WSManHTTPConfig.exe · signed by Microsoft Windows
a89a3bd52b156aa71292c50a5b7bcb0489b8bb208b2e83d85ee41a693a30418410.0.18362.693 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\WSManHTTPConfig.exe · signed by Microsoft Windows
23470e9964c1b84ca6aa73fb7da932e52f0c3e3848aaf88843fccc75015328fe10.0.18362.693 (WinBuild.160101.0800) · C:\WINDOWS\system32\WSManHTTPConfig.exe · signed by Microsoft Windows
330e312d77405e8f7cf6d4b2d77ab4e05846b84d72f4d38af6d4fe5239e5f84e10.0.17763.134 (WinBuild.160101.0800) · C:\Windows\system32\WSManHTTPConfig.exe · signed by Microsoft Windows
587852fa20ac5f36047f3d51041298873bd6d4986490a0c2dd433efde109691710.0.17763.134 (WinBuild.160101.0800) · C:\Windows\SysWOW64\WSManHTTPConfig.exe · signed by Microsoft Windows
aa19ab5f5c954583c46e2c4099a2765432c6cccb5d20803167fcc1727ae5416c10.0.14393.479 (rs1_release.161110-2025) · C:\Windows\system32\WSManHTTPConfig.exe · signed by Microsoft Windows
717b8776a9461bfeb6d4850859c304c845abc9af5fc295bcf0e7650aa145816410.0.14393.479 (rs1_release.161110-2025) · C:\Windows\SysWOW64\WSManHTTPConfig.exe · signed by Microsoft Windows
98273c32560e75bba3b19eff2747b42aef2e351f8cb0ea970e69346fdba79b466.3.9600.17415 (winblue_r4.141028-1500) · C:\windows\SysWOW64\WSManHTTPConfig.exe · not signed
933c402506a218e34c36b4661f98c3c3576a5bb16839a90f839c5dbd172d0b5a6.3.9600.17415 (winblue_r4.141028-1500) · C:\windows\system32\WSManHTTPConfig.exe · not signed
c651969c4f00f127fc58a0ffb0087d8a69a287f7036a443af0aee5f223d83756From 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.