If you click the Checks Failed button, you’ll see a message like this:
This means there are 3 categories of problems:
can be fixed with firmware updates,
can be resolved with specific BIOS/EFI settings,
require hardware replacement to be fixed.
In your case, the version of TPM might be incorrectly reported by the firmware.
Usually you can do nothing about it other than looking for firmware updates and complaining to the hardware vendor if the warranty is still valid.
So in this instance, I am unclear whether I should just ignore this and carry on.
Or try and update via W11 drivers if there is any (I am looking to avoid this option). I doubt I will make much progress complaining to the HW Vendor as the laptop is a few years old and out of warranty. Alternatively, carry on looking for some firmware updates.
I am not sure if there is an option for me to look at this line or perhaps a red herring
[ 7.834698] systemd: systemd-pcrmachine.service - TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
It seems possible that even W11 would not be able to assist.
That laptop was released late 2017 so is about 6 years old. The chip may not be quite new enough for the full support of TPM 2.0 even though the bios indicates so. I seem to recall that there was an early release of TPM 2.0 then a later updated spec so your laptop may be compatible with the earlier version but not the current version.
A bit of research may reveal info about that possibility.
A quick check of wikipedia shows the below and implies it may not have the correct chipset or CPU (intel 7th gen vs intel 8th gen)
Thanks @computersavvy - I tried some more research and came across this post in the Red Hat Customer Portal Knowledgebase but it was restricted to users… so I couldn’t view the solution but sharing here in case it helps others.
Some further digging I found this article and managed to fix this!