After this year Intel AMT fiasco, we’ve got not a new TPM madness. I ❤ IT

If you don’t know what it’s about, please take the time to read first the Microsoft Advisory ADV170012

Now, let’s quickly jump into the only question we care about: How do I find out whether I’m affected or not?

The PowerShell script provided on this page is supposed to help IT achieve this task.



Unfortunately, it doesn’t scale very well and Microsoft doesn’t give you too much details and just tells us to use PSRemoting to scale and query multiple computers.

The script has other major issues like:

it doesn’t send an object through the pipeline and just uses Write-Host to paint/color my console

it doesn’t handle gracefully the fact that you must be running the script with elevated user rights (Run as Administrator).

(please note that there’s a warning about administrative privileges in bold in the forewords)

(please note that there’s a warning about administrative privileges in bold in the forewords) it uses aliases which is not a best practice

it doesn’t respect the Verb-Noun format for function names

worse, it uses Get-TPM that is cmdlet that was introduced as of Windows 8 and that isn’t available on Windows 7

Don’t get me wrong, the script is good enough for my home computer and the code exposes very well the core logic to determine if my device is affected.

I especially love the way the return statement is used in the switch block.

Anyway, I rewrote the script to ease the scoping of this TPM madness 😀



Let’s see how to use it:

# Example 1: $c = Get-Credential $targets = @( 'PCHPModel1', 'PCHPModel2', 'PCFujitsuModel1', 'PCFujitsuModel2', 'PCLenovoModel1', 'PCLenovoModel2' ) Invoke-Command -ComputerName $targets -ScriptBlock ${Function:\Test-InfineonTPMVulnerability} -ErrorAction SilentlyContinue -Credential $c | Select -Property ComputerName,TPMVersion,Vulnerable,Unknown,ClearRequired,Reason | Format-Table -AutoSize

# Example 2: Invoke-Command -ComputerName $targets -ScriptBlock ${Function:\Test-InfineonTPMVulnerability} -ErrorAction SilentlyContinue -AsJob -Credential $c | Wait-Job -Any | Receive-Job | Out-GridView

Bonus 1 :

In Windows 7, you cannot use the new Suspend-Bitlocker cmdlet introduced as of Windows 8.

You can use manage-bde.exe

Manage-bde.exe –protectors –disable c:

or you can use WMI

$HT = @{ Namespace = 'root/cimv2/Security/MicrosoftVolumeEncryption' Class = 'Win32_EncryptableVolume' } (Get-WmiObject @HT -Filter 'DriveLetter="C:"').DisableKeyProtectors()

Bonus 2 : On Windows 10, if you want to use the detection option 1 and query events from the Event Source TPM-WMI, the fastest way to achieve this is by using an XML query that only targets the microsoft-windows-tpm-wmi provider like this:

$xml = @' <QueryList><Query Id="0" Path="system"><Select Path="system">*[System/Provider[@Name='microsoft-windows-tpm-wmi']]</Select></Query></QueryList> '@ Get-Winevent -FilterXml $xml -ErrorAction SilentlyContinue

Happy TPM madness scoping 😎