PowerShell script for CPU information, incl. CPUID Solved

Page 6 of 7 FirstFirst ... 4567 LastLast
  1.    #51

    humbird said: View Post
    Perfect. Thank you!
    You're welcome!
      My ComputerSystem Spec

  2.    #52

    Thanks @ddelo!
    Works ok.
      My ComputerSystem Spec

  3.    #53

    emilcioran99 said: View Post
    Thanks @ddelo!
    Works ok.

    You're welcome.
    Stick around, I'm working on an update, which should be posted within the next days.
      My ComputerSystem Spec

  4.    #54

    Still works like a champ! Be sure to post an upgrade notice on the first post in this thread.
    Click image for larger version. 

Name:	image.png 
Views:	29 
Size:	39.8 KB 
ID:	236137
    Thanks!
    --Ed--
      My ComputersSystem Spec

  5.    #55

    EdTittel said: View Post
    Still works like a champ! Be sure to post an upgrade notice on the first post in this thread.
    Click image for larger version. 

Name:	image.png 
Views:	29 
Size:	39.8 KB 
ID:	236137
    Thanks!
    --Ed--

    Thanks Ed. I sure will....and you'll also get your personal notification!!!!

    I just noticed that you have an older version. You can always try v2.3 from the 1st post!
      My ComputerSystem Spec

  6. Ztruker's Avatar
    Posts : 8,181
    Windows 10 Pro X64 1903 189362.439
       #56

    I just ran v2.3 on my Lenovo K450:

    Click image for larger version. 

Name:	image.png 
Views:	1 
Size:	33.4 KB 
ID:	236161
      My ComputersSystem Spec


  7.    #57

    Update, Version 2.4 has been added to the 1st post
      My ComputerSystem Spec

  8.    #58

    @ddelo,

    I just finished running your PS script (new version) and here is the result for my Windows 10 version 1809:

    Click image for larger version. 

Name:	CPU-infoB.ps1 result with new version.png 
Views:	2 
Size:	126.7 KB 
ID:	236268

    Thanks again mate!. I don't know if I am mistaken, but the result seems to be the same as last time, which was very recently.
      My ComputersSystem Spec

  9.    #59

    IronZorg89 said: View Post
    @ddelo,

    I just finished running your PS script (new version) and here is the result for my Windows 10 version 1809:

    Click image for larger version. 

Name:	CPU-infoB.ps1 result with new version.png 
Views:	2 
Size:	126.7 KB 
ID:	236268

    Thanks again mate!. I don't know if I am mistaken, but the result seems to be the same as last time, which was very recently.
    No, you're not mistaken at all. I have only added the CPU signature field, plus the Disclaimer (for you and one other member who both have an old BIOS), plus fixed a couple of bugs for the AMD processors.

    As you can see your BIOS is 1064 days old, but the Registry reports an updated BIOS microcode version, which is wrong. Somehow the Registry has been erroneously updated by the latest Microsoft microcode update...for reasons completely unknown to me.
    That's the reason you get the Disclaimer which explains what the problem is. And it seems to be working as it's supposed to.
    Thanks a lot for the test buddy!!!
      My ComputerSystem Spec

  10.    #60

    ddelo said: View Post
    No, you're not mistaken at all. I have only added the CPU signature field, plus the Disclaimer (for you and one other member who both have an old BIOS), plus fixed a couple of bugs for the AMD processors.

    As you can see your BIOS is 1064 days old, but the Registry reports an updated BIOS microcode version, which is wrong. Somehow the Registry has been erroneously updated by the latest Microsoft microcode update...for reasons completely unknown to me.
    That's the reason you get the Disclaimer which explains what the problem is. And it seems to be working as it's supposed to.
    Thanks a lot for the test buddy!!!
    As far as I remember the latest Intel Microcode guidance page didn't list my CPUID (306C3). The reason why it has been updated in the registry is also a mystery to me. MS probably has the answer to that, but for now My PC is running super fine with 1809. Yesterday, I had a harrowing experience trying to upgrade to 1903; it was so bad that I don't think it is worth talking about it.
    Take care mate. Tx again!
      My ComputersSystem Spec


 
Page 6 of 7 FirstFirst ... 4567 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:38.
Find Us