Windows 11 compatibility Powershell scanner

I've implemented the Powershell scanner from the Bonus Content on github. Seems like it's working okay, except I've discovered at least one system model it's reporting incorrectly and I can't figure out why.

It says the Dell Latitude 7389 2-in-1 is capable, including the CPU. The CPU in those systems is an Intel Core i5-7300U CPU @ 2.60GHz, which is definitely NOT in the compatible CPU list. I even double checked the .CSV that was created, and it's not in there.

Any ideas why it might be incorrectly reporting as an acceptable CPU?




Date Votes
  • What does this return on the target? You can use a Tool in Inventory for this.

    Get-CimInstance -class CIM_Processor | Select-Object Name
  • Name                                    
    Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz

  • Huh, strange. That definitely shouldn't match.

    Add this line to Win11Compatablilty.ps1, just above line 17:

    Write-Verbose "'$($' matched '$cpu'"

    Then add this to the Parameters field of the PowerShell Scanner you created:


    Run the scanner on the troublesome target, then check the Output Log (blue link at the top of the PowerShell page of the Computer window).

  • AHA! 

    [11/30/2021 1:47:20 PM] VERBOSE: Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\cimv2,'className' = CIM_Processor'.
    [11/30/2021 1:47:21 PM] VERBOSE: Operation 'Enumerate CimInstances' complete.
    [11/30/2021 1:47:21 PM] VERBOSE: '@{Name=Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz}.name' matched '300U'
    [11/30/2021 1:47:22 PM] VERBOSE: Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root/cimv2/Security/MicrosoftTPM,'className' = win32_tpm'.
    [11/30/2021 1:47:23 PM] VERBOSE: Operation 'Enumerate CimInstances' complete.

  • Looks like that's from the AMD list:

  • I suppose with some more selection logic, I could avoid that, but I think I'll just remove the AMD CPUs from the list. We don't have any AMDs at this time.

    Thanks for digging into it Colby!


Please sign in to leave a comment.

Didn't find what you were looking for?

New post