x86
machine scopecpu-z_2.07-en.exe
- SHA-256
- 7db6a1512934be9b32798b670fa0c7c54279c8a87ebbc467c5702505ba5df9b3
CPUID CPU-Z · earlier release
The URL CPUID, Inc. published for this release, and the SHA-256 of every file in it, so you can prove the copy you have is that one and not something else wearing the same name.
CPUID CPU-Z is now on version 2.21. An older build stops getting security fixes, so install one only when you have a reason: a plugin that broke, a machine that cannot run the new one, a bug you need to reproduce. If you just want CPUID CPU-Z, take the current version.
cpu-z_2.07-en.exe
cpu-z_2.07-cn.exe
The scope label says who the installer writes for. A user build installs into your own profile and needs no administrator rights; a machine build installs for everyone and does. On a work laptop where you cannot elevate, the user build is often the only one that will run at all. Silent install switches are on the same data.
Windows does this without installing anything. In PowerShell:
Get-FileHash .\cpu-z_2.07-en.exe -Algorithm SHA256
Compare what it prints with the value above. If they match, your copy is byte-for-byte the one CPUID, Inc. published. If they do not, it is a different file, whatever it is called and wherever it came from. Paste a hash into the verifier and it will tell you which release it belongs to.
If PowerShell is blocked by policy on the machine, the same thing works from plain cmd with certutil -hashfile cpu-z_2.07-en.exe SHA256. On macOS or Linux it is shasum -a 256 cpu-z_2.07-en.exe.
Publishers retire old releases, and we do not host copies, so a link from an earlier version can stop working without notice. Two ways it fails: an honest 404, or — more confusing — the server answers normally but hands you the current downloads page instead of the file. If what arrives is a few kilobytes of HTML rather than an installer, that is what happened.
The hash on this page stays useful either way. It still identifies CPUID CPU-Z 2.07 wherever you find a copy, which is the whole point of publishing it: you can accept a file from somewhere else and still prove it is the one CPUID, Inc. built.
Every CPUID CPU-Z release we index · where this data comes from