PowerShell script for CPU information, incl. CPUID

Page 12 of 14 FirstFirst ... 21011121314 LastLast

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

    IronZorg89 said:
    Sorry for being late. Just want to be part of the discussion and I think the latest version (CPU-Info Version 2.5) is working fine. Here is my result:

    Attachment 269237

    No problem bud.
    It's sure working just fine. And the UEFI microcode version seems to be correct now. Remember, it was 0x27. Now how this was changed, I really have no clue. Maybe an update fixed it. Who knows.
      My Computer


  2. Posts : 2,557
    Windows 10 pro x64-bit
       #112

    ddelo said:
    No problem bud.
    It's sure working just fine. And the UEFI microcode version seems to be correct now. Remember, it was 0x27. Now how this was changed, I really have no clue. Maybe an update fixed it. Who knows.
    It has to be an update from MS, for I have not gotten any BIOS/UEFI update from the manufacturer in a long time. As a matter of fact, I will go and check right after this post.

    - - - Updated - - -

    No luck as evidenced in the screenshot below. Note that it shows Windows 8.1 (64-bit) because that is the version with which the machine came when I first bought it in 2015. Since then, it has been upgraded to Windows 10 (64-bit). And my ROM Family SSID is the one in red square (2AF7):

    PowerShell script for CPU information, incl. CPUID-recent-bios-uefi-update-unavailable.png

    - - - Updated - - -
    @ddelo,

    Your PM has been answered.

    Cheers!
      My Computers


  3. Posts : 4
    Windows 11 Pro (64-Bit)
       #113

    Hey, I like your script. Out of curiosity, is there any reason to avoid something like:
    Code:
    Get-ComputerInfo |ConvertTo-JSON >C:\ComputerInfo.json
      My Computer


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

    Iocalhost said:
    Hey, I like your script. Out of curiosity, is there any reason to avoid something like:
    Code:
    Get-ComputerInfo |ConvertTo-JSON >C:\ComputerInfo.json
    Thanks and welcome to TenForums.
    No reason I can think of, although I haven't tried it.
      My Computer


  5. Posts : 144
    windows 10
       #115

    hi

    i used the script to check my system but for some reason report legacy boot even if they are in uefi.


      My Computer


  6. Posts : 2,557
    Windows 10 pro x64-bit
       #116

    blueskyler said:
    hi

    i used the script to check my system but for some reason report legacy boot even if they are in uefi.


    Maybe you have to enter the BIOS Settings and make sure UEFI mode is on. The way to enter the BIOS settings varies from one manufacturer to another. You will have to check the manual that came with your machine or maybe you know how to do that already.
      My Computers


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

    blueskyler said:
    hi

    i used the script to check my system but for some reason report legacy boot even if they are in uefi.



    You're the second one who reports such a problem.
    The script uses bcdedit to determine the FirmwareType, which is supposed to be the best and flawless way to decide the type of firmware.

    This command currently used in the script, in PowerShell is

    Code:
    $bcdeditOutput = & "$env:windir\System32\bcdedit.exe"
    if ($bcdeditOutput -like "*winload.efi") { $FirmwareType = "UEFI" }
    else { $FirmwareType = "Legacy BIOS" }
    $FirmwareType

    Another way of finding the firmware type is the following:
    Code:
    if ($env:Firmware_Type -eq "UEFI") { $FirmwareType = "UEFI" }
    else { $FirmwareType = "Legacy BIOS" }
    $FirmwareType
    You can run both of them in an elevated PowerShell console and see what you get.
      My Computer


  8. Posts : 14,009
    Win10 Pro and Home, Win11 Pro and Home, Win7, Linux Mint
       #118

    Tried both of them and both failed on the word else.
      My Computers


  9. Posts : 16,938
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #119

    Berton said:
    Tried both of them and both failed on the word else.
    It's the line return before Else in both. It should be on the same line as the rest of the If statement.

    Denis
      My Computer


  10. Posts : 8
    Windows 10 LTSC 1809
       #120

    My pc is so ancient (fast nontheless) that it's not supported anymore....i guess

    Checked with InSpectre seems the meltdown vulnerability is protected. Anyways, runned for the fun, and it shows as a x64 system. To my knowledge it's a x86 system. Getting a x64 iso just to test it

    Thx for stuff like this, always good to check the details.

    Code:
    Computer Model               : System Product Name
    Computer Name                : HAZ3-PC
    Processor Type               : Central Processor
    Manufacturer                 : GenuineIntel
    CPU Family                   : Other
    CPU Architecture             : x64
    Name                         : Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz
    Description                  : x64 Family 6 Model 23 Stepping 10
    Number of Cores              : 2
    Number of Logical Processors : 2
    Current Clock Speed          : 2793
    Socket Designation           : Socket 775
    Upgrade Method               : Socket LGA775
    CPUID                        : 0001067A
    Display Family               : 06H
    Display Model                : 17H
    Processor Signature          : 06-17-A
    
    Running microcode revision   : 0x (loaded by Microsoft Windows7 Ultimate-6.1.7601-SP1 Final Build )
    BIOS CPU microcode revision* : 0x
    
    Boot Mode                    : Legacy BIOS
    Legacy BIOS Version          : BIOS Date: 03/11/09 15:37:33 Ver: 08.00.12
    Legacy BIOS Manufacturer     : American Megatrends Inc.
    Legacy BIOS Serial Number    : System Serial Number
    Legacy BIOS Release Date     : 3/11/2009 (4095 days ago)
      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 08:03.
Find Us




Windows 10 Forums