Windows 10: PowerShell script for CPU information, incl. CPUID Solved

Page 1 of 3 123 LastLast
  1.    18 Mar 2018 #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 current microcode revision.

    Download the CPU-info.zip file and extract the included "CPU-info.ps1" script on your desktop.

    Open PowerShell and run the following commands:

    Code:
    cd $HomePath\Desktop
    Set-ExecutionPolicy Bypass -Scope Process –force
    .\CPU-info.ps1

    You will get an output similar to that.


    Click image for larger version. 

Name:	CPU-info.png 
Views:	9 
Size:	29.1 KB 
ID:	201574

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

    I hope that helps somebody.

    UPDATE: The CPU-info.ps1 script, now provides the revision of the microcode installed in the system.
    BIOS/UEFI microcode revision, is the μcode currently installed in your BIOS/UEFI
    Current microcode revision, is the μcode currently running. This might be different from the one installed in your BIOS/UEFI, since it might have been updated by a Microsoft Update.
    Last edited by ddelo; 01 Sep 2018 at 06:51. Reason: Updated the PowerShell script to include μcode
      My ComputerSystem Spec

  2. Masterchiefxx17's Avatar
    Posts : 419
    Windows 10 Professional 64bit
       18 Mar 2018 #2

    Neat script, I like it!
      My ComputerSystem Spec

  3.    18 Mar 2018 #3

    Masterchiefxx17 said: View Post
    Neat script, I like it!
      My ComputerSystem Spec

  4.    31 Aug 2018 #4

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

  5.    31 Aug 2018 #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--

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	134.7 KB 
ID:	201606
      My ComputersSystem Spec

  6.    31 Aug 2018 #6

    EdTittel said: View Post
    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--

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	134.7 KB 
ID:	201606
    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 ComputerSystem Spec

  7.    31 Aug 2018 #7

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

  8.    31 Aug 2018 #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 ComputerSystem Spec

  9.    31 Aug 2018 #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 ComputerSystem Spec

  10.    31 Aug 2018 #10

    muchomurka said: View Post
    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 ComputerSystem Spec


 
Page 1 of 3 123 LastLast

Related Threads
The PowerShell script execution policies enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer. Windows PowerShell has four different execution policies: Execution Policy Description ...
One of many PowerShell security features is that you can't run a script simply by double clicking it's icon on desktop or in a folder. Doing so will by default open script in Notepad for editing instead. You can right click script and select Run...
A Powershell Script for HandBrake in Software and Apps
Here's the thing. My system is an age-old i3-530 overclocked to 3.5GHz coupled with GTX 1050 2GB. I have around 1.5TB of tutorial videos that I have to encode due to dearth in HDD space. I want to encode the videos while keeping the folder and...
Hope I'm in the right place! I am trying to get a Powershell script to run daily in the task scheduler. It basically purges a folder on one of my drives: Get-ChildItem –Path “D:\Dropbox\Quicken\Backup” –Recurse | Where-Object CreationTime...
A .ps1 script file is a text file that contains one or more Windows PowerShell commands or expressions. A .ps1 file will open with Notepad by default. To run a .ps1 file with PowerShell, you would right click or press and hold on the .ps1 file and...
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 22:03.
Find Us