Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The only temp-fix was to disable "fTMP" in your UEFI BIOS .. try to disable fTMP, restart your machine, and re-enable ti again, maybe this will help ..
Updating motherboard drivers / bios, chipset drivers and other hardware drivers and controllers might help too ..
You should check some news and guides within the world wide web .. Well, there are explicite guides and reports between MSI MB's, AMD Processors and TMP 2.0
https://www.msi.com/blog/How-to-Enable-TPM-on-MSI-Motherboards-Featuring-TPM-2-0
What BIOS version are you using? If it's not the latest, have you tried updating? Have you tried clearing the CMOS/resetting the BIOS to defaults?
Are you sure you're not just conflating "I passively saw issues once upon a time involving some of these variables so I'm going to presume it's normal not to work at all"? Because I admittedly get that impression from this. If you have a specific source showing that it is confirmed to not work properly on MSI motherboards, then could you provide that instead of deferring to "check the web". What exactly are we looking for? Random occurrences of any issue whatsoever?
It's functional for me on an MSI motherboard (MAG X570S Tomahawk Max) and that was/is with a pair of AMD CPUs (Zen 2 and Zen 3).
Then you need to do a clean OS install while those are enabled.
Before any of this, update to latest BIOS first
Secure Boot= standard/enabled
ftpm= enable
Isn't TPM supposed to have a standardized interface exposed without requiring any drivers?
also them requiring tpm/ftpm 2.0, instead of allowing tpm/ftpm 1.2 like microsoft allows... or simply not requiring it at all.
they are essentially locking customers out of their platform.
anywho, as mentioned by others, you need to enable it in bios (and do w/e else to make it work...), though i personally dont know how amd runs with it, or intel for that matter, i have tpm 1.2, but i bypassed that tpm nonsense, it causes more issues than its worth.
vanguard from riot also requires tpm/ftpm...
and valorant.
Actually, Microsoft requires TPM 2.0 for Windows 11.
TPM 1.2 is not good enough to meet the requirements.
under the registry key..
HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup
https://support.microsoft.com/en-us/windows/ways-to-install-windows-11-e0edbbfb-cfc5-4011-868b-2ce77ac7c70e
they actually put it in the iso's now a days, instead of having people do it themselves, you can download an iso right now and check the registry during first menu on install, by using shift f10 and typing "regedit" and looking for that key in the registry.
whether they disabled or still have it enabled now, im not sure, but when i installed win 11 pro, said registry entry was already in my registry and still is, despite using a batch file script, to bypass everything.
or use rufus.
you can also simply bypass everything manually, by simply editing it in, the same registry key as microsoft supplied under "MoSetup", erasing the supplied dword from microsoft and adding the ones below, so there is no confilcts.
you can as well, create your own key manually, name it and edit in those registry entries, while removing the key "MoSetup" and bypass that way.
or in the above, create your own batch script (with notepad++ or even notepad) with said entries and do the same by simply running it.
you can also export that registry key, or your whole registry, to "be safe" and import back to fix issues, or simply reinstall the OS with a clean registry, if you somehow mess it up, which is very unlikely.
(in the below quote, is what you would see in a batch file script, and/or the entries you would manually edit into your registry with the instruction in the above quote from microsoft).
you can find all this info, ect.. on the net.