PowerShell script for CPU information, incl. CPUID

Page 1 of 14 12311 ... LastLast

  1. Posts : 2,450
    Windows 10 Pro x64
       #1

    PowerShell script for CPU info, incl. CPUID and μcode version


    With all this mess with the newfound Spectre and Meltdown hardware-based vulnerabilities, users look for solutions from both Microsoft and CPU vendors.
    The microcode updates, posted almost daily, are released based on CPUID.
    The CPUID signature and microcode revision cannot be easily found by the average user.

    So, I created a little PowerShell script to get basic CPU information, including the CPUID signature and the system's current microcode revision.

    Download the updated (v2.6) CPU-info.ps1 file and save it on your Desktop (don't forget to unblock it!).

    Open PowerShell as Administrator and run the following commands:

    Code:
    cd ~\Desktop
    Set-ExecutionPolicy Bypass -Scope Process -Force                                                                                                                                                                                                                                                                     
    .\CPU-info.ps1

    You will get an output similar to that.

    PowerShell script for CPU information, incl. CPUID-cpu-info_2-6.png

    Feel free to use and make changes to the script, to suit your needs.

    I hope that helps somebody.

    Version 2.6 (26-Jan-2022)
    Release notes
    1. Updated CPU Family and Upgrade Method lists from the latest (v.2.53.0) DMTF schema
    2. Verified Windows 11 compatibility
    Last edited by ddelo; 02 Feb 2022 at 06:45. Reason: Updated the PowerShell script to version 2.6
      My Computer


  2. Posts : 516
    Windows 10 Professional 64bit
       #2

    Neat script, I like it!
      My Computer


  3. Posts : 2,450
    Windows 10 Pro x64
    Thread Starter
       #3

    Masterchiefxx17 said:
    Neat script, I like it!
      My Computer


  4. Posts : 2,450
    Windows 10 Pro x64
    Thread Starter
       #4

    First post has been updated, to include the installed microcode revision.
      My Computer


  5. Posts : 4,224
    Windows 10
       #5

    Small syntax error: your runtime instructions use an underscore character in the filename -- namely .\CPU_info.ps1. The filename actually includes a dash or hyphen/minus-sign character. So that line should read .\CPU-info.ps1 instead. Otherwise, works like a champ! Thanks,
    --Ed--

    PowerShell script for CPU information, incl. CPUID-image.png
      My Computers


  6. Posts : 2,450
    Windows 10 Pro x64
    Thread Starter
       #6

    EdTittel said:
    Small syntax error: your runtime instructions use an underscore character in the filename -- namely .\CPU_info.ps1. The filename actually includes a dash or hyphen/minus-sign character. So that line should read .\CPU-info.ps1 instead. Otherwise, works like a champ! Thanks,
    --Ed--

    PowerShell script for CPU information, incl. CPUID-image.png
    Great observation Ed. Thanks. Just changed it.

    The one with underscore was the 1st version. I changed it now to be more PowerShell-like
      My Computer


  7. Posts : 4,224
    Windows 10
       #7

    Good work, Dimitri. Please, keep it up. Always fun to learn more PowerShell.
    Best wishes,
    --Ed--
      My Computers


  8. Posts : 2,450
    Windows 10 Pro x64
    Thread Starter
       #8



    Thanks Ed.
    I will shortly post a new one, I was working on, to create a cabinet file, from the contents of a folder. Stay tuned.
      My Computer


  9. Posts : 913
    CP/M
       #9

    Nice job, ddelo.

    Btw after observations of visible performance drop during regular use (and catastrophic while using nested virtualization) I decided to disable all that protections on all my home systems using InSpectre & downgrade BIOSes when necessary. Am I alone?
      My Computer


  10. Posts : 2,450
    Windows 10 Pro x64
    Thread Starter
       #10

    muchomurka said:
    Nice job, ddelo.

    Btw after observations of visible performance drop during regular use (and catastrophic while using nested virtualization) I decided to disable all that protections on all my home systems using InSpectre & downgrade BIOSes when necessary. Am I alone?
    If you're aware of the risks involved, by not implementing the mitigations, it's your computer and you're the only one who evaluates the pros and cons and decides what's best for you!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:22.
Find Us




Windows 10 Forums