licensingdiag.exe
Licensing Diagnostic Tool file version info
Program on Windows 11 known copies with hashes
Is it the real licensingdiag.exe?
C:\Windows\system32\C:\windows\SysWOW64\11 known copies
10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\licensingdiag.exe · signed by Microsoft Windows
1df13ad98e70fadbdccdf2cd778f0929ca13120e980922f74d4f4f94eeee257510.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\licensingdiag.exe · signed by Microsoft Windows
60f6d17d45fa08702a0d58f6aff601a4f4bc5a35d24b35773d1a41237a69d68510.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\licensingdiag.exe · signed by Microsoft Windows
8ea4b6fd90420f67cdd0501dc200be05ae58f365b7b4d36ad09369750d621b9810.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\licensingdiag.exe · signed by Microsoft Windows
adad0b6ab83d50334d217fa217e9876b4937aa25b3fa65614bb25bca14dc55d110.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\licensingdiag.exe · signed by Microsoft Windows
efc01e7c6e0f807895c385c5b6d2510a20a47275c9ffce76a75b976567b44e5810.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\licensingdiag.exe · signed by Microsoft Windows
ff38d4b6218f037aca7b773876aff7718e26e50d2c9ffba0b401c86738d4483610.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\licensingdiag.exe · signed by Microsoft Windows
e4e1e4ba82ea6f1388f8803a1272794cb44dc820beed9f668588b3e9cd7454a410.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\licensingdiag.exe · signed by Microsoft Windows
ad50d6f3f21a34d2fe251d5c3cc0e0f42170e2c70e45b7712bdbda0543b8bbf810.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\licensingdiag.exe · signed by Microsoft Windows
1a7dd1ce81b334ba211e0eec122855add5321bd3d30d4a851dd5a0cc5af229596.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\licensingdiag.exe · not signed
cfe4e82e2b43b00a59a94b6c7583163b381914a976c09f3ae4a70791c3b48c5f6.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\SysWOW64\licensingdiag.exe · not signed
dabbb9fd97db00d5b683b6ee45e9a1e1ff097bea8d2f22541bd7f0b77d01e4c4From 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.