CPUPRINT.EXEfor Microsoft® Windows® NT decodes and prints the information gathered from the processor’s
CPUPRINT.TXTshow typical outputs for Intel® Core™ processors;
CPUPRINT.AMDshows typical output for an AMD® Athlon™ processor.
CPUPRINT.EXE enumerates the
processor capabilities alias features
as well as the presence of the
model specific register, introduced by
with firmware alias microcode updates to fix the vulnerabilities
alias Branch Target Injection,
alias Bounds Check Bypass,
alias Rogue Data Cache Load,
better known by their nicknames
It also enumerates the processor capabilities alias features PCID, introduced in first generation Intel Core processors with
Westmere microarchitecture, and
introduced in fourth generation Intel Core processors
Haswell microarchitecture, both available only in
long mode, i.e. to 64-bit operating systems, which are
necessary to reduce the performance impact of the fix for
shows the output for an
Intel® Core™ i7-7500U
processor with microcode update applied and all features present.
Note: when started per double-click, i.e. in its
CPUPRINT.EXE waits for a
keypress before it exits and the
console window closes.
CPUPRINT.EXEsupports multiple specifications of (real and virtualised) x86 and x64 processors from several vendors:
CPUPRINT.EXEis a pure Win32 binary executable, written from scratch in ANSI C, built with the platform SDK for Windows Server 2003 R2 without the MSVCRT libraries, for use on Windows XP and newer versions of Windows NT as well as Windows PE.
CPUPRINT.EXE is available for the I386
alias x86 and AMD64 alias
x64 processor architectures of
Note: on the IA64 processor architecture the
CPUID instruction is supported in the
emulated I386 alias x86 execution
CPUPRINT.EXE is neither based
on other outdated tools like
nor related to any of them!
CPUPRINT.EXEis digitally signed using an X.509 certificate issued by WEB.DE TrustCenter E-Mail Certification Authority.
Download and install the CA and root X.509 certificates of WEB.DE to validate and verify the digital signature.
-----BEGIN RSA PUBLIC KEY----- MIIBCgKCAQEA6ipnm9vAs63w+TM+9UcG1yQ8CRIxMz/tTXry9MCbeHpkiM/qdPaRWlwVTW2j PhC81xwIPZXgE1FE4DgE1eImb33DG2YfEBY/ARpMaGUnme+85WmExWWc/YMUAaHOMYQ3TQDX 0V/7yuhfa9Uc29ljtQ2AB0MjhXTJvGguvZZTI5A3rcN4+AKwmETdYH+8OQKMU2s+2H9CVfaD waX0aj9CeibGNooLTgDchzCBIC5J47qHned/3ZqnMDjYCv3Yc1HNgcbM+ZKzPoD8jShb/ptI wWPo9s00KEs9ti68RsmejqKovAmdLSzFLGARbue2uiqs4piJkxI0LS5+NTTPyZjsSwIDAQAB -----END RSA PUBLIC KEY-----
Note: due to its counter signature alias timestamp the digital signature remains valid past the X.509 certificates expiration date!
Use the X.509 certificate to send S/MIME encrypted mail.
Notes: I dislike
even weirder formats too) in email, I prefer to receive plain text.
I also expect to see a full (real) name as sender, not a nickname!
Emails in weird formats and without a proper sender name are likely to be discarded.
I abhor top posts and expect inline quotes in replies.
as iswithout any warranty, neither express nor implied.