TPM issue

L

legend

New Member
Messages
4
Reaction score
0
hey so im making a heavy debloated iso but for some reason games doesnt recognize TPM, im sure i have selected every component related to TPM such as:

-Security devices (drivers)
-Smart cards (drivers)
-TPM & Virtual smart card (component)
-TPM management console
-Servicing stack

heres my preset
 

Attachments

Are you sure it's actually TPM and not Secure Boot? Games themselves don't require TPM to run. What they want is TPM + Secure Boot enabled, so Core Integrity can do the hard work of blocking cheat drivers from loading.
 
garlin said:
Are you sure it's actually TPM and not Secure Boot? Games themselves don't require TPM to run. What they want is TPM + Secure Boot enabled, so Core Integrity can do the hard work of blocking cheat drivers from loading.
Click to expand...
I dont think fortnite needs core integrity i have it disabled on my current os and works fine
This is what i get in the game
 

Attachments

  • image-1.png
    image-1.png
    78.2 KB
Do you have a TPM 1.2 module, instead of TPM 2.0? Are you running in pure UEFI mode (no CSM extensions)?

If you're using a HW bypass to get Windows installed, it does nothing to fool the game.
Code: 
powershell -C Get-Tpm
 
I have 2.0 and tried on other pcs aswell, no im not bypassing
I think its just a componnent but cant really tell what it is
 
It is very important in these cases to know that the unedited ISO of the same Windows version on the same machine is tested.
To that all your other tweaks that you probably do, skipping only NTLite.
If that works fine, then we can continue, otherwise it can be a BIOS/driver/bug/Windows thing.
And try not to guess, actually try all the same, install on another partition.
If you want NTLite for image editing, that is fine, then keep all Components, to isolate something.
 
i tested the stock and it works fine i grabbed it from uup dump, i didnt apply any tweaks after installing the modified version and still no tpm ill try what u sent in mail and let you know but i dont think its a bios issue

"Did you tamper with context menus at all?" only made it the old context one from w10
"Defender and Security Center" dont think thats the issue either

im sure its something in the components or a driver getting removed
 
You must log in or register to reply here.
Back
Top