One bit more of the modification for bypassing two qualifications, please.

Claus Debanker 21

In testing anew the MoSetup modification by way of a VHDX Win 11 environment, I have discovered the reg-word with numbering (1) at the 'AllowUpgradesWithUnsupportedTPMOrCPU' recreated DWORD, was only enough to bypass the CPU unsupported limitation; the other condition for TPM remained alone in the final result.

Can we review an older instruction to make room for another try?

Unless you don't agree the initial instruction was half-way the job, is there a different option to number that entry?

Claus Debanker 21 Reputation points

2024-06-20T07:14:58.7+00:00

I mean, (1) is likely inclusive of the CPU only; could (2) be inclusive of both? (Other examples from registry entries sometimes have a nominal mismatch for numbering an answer.)
Claus Debanker 21 Reputation points

2024-06-20T15:59:07.4+00:00

By the way, what it means if the TPM owner authorization value in the registry is not any one number listed as possible in TPM Group Policy Settings? I see for OSManagedAuthLevel 0, 2 ,4.

If the module is totally absent from the hardware configuration, it can take a different numbering than these three ones?

Share via

One bit more of the modification for bypassing two qualifications, please.