Recommended Posts

On 29/08/2016 at 11:24 AM, Hum said:

Where in the BIOS is TPM, and how did you replace it ?

Have no idea where it is on yours. Or if it's even in the BIOS. And if it is, depends if it can be upgraded (looks like some laptops can be updated to TPM 2,  like a BIOS update).

 

But if it cant be updated, (or if the chip / whatever in it cant be removed / replaced) not much you can do about it. You cant use TPM 1.2 with the AU.

 

You may have to reinstall a prior version to before the AU came out. Since this is what causes the 0xc000000d error I posted

 

In my case, since it was an ASUS TPM 1.2 module, all I had to do was remove / replace it with a TPM 2 module.

 

Which is installed now. ASUS 20 pin TPM 2 module

 

It's the 14-1 pin  (for Skylake ASUS mobos) TPM 2 module equivalent for non-skylake ASUS mobos

 

Had to get it from EBay, because I dont think it exists here yet.

 

But if it did, it would cost more than what I paid for it on Ebay (around $29 NZ)

Edited by John.D
On 29/08/2016 at 11:50 AM, PGHammer said:

If Secure Boot is enabled (which is HP's default in their UEFI systems), that can trigger it as well (that is, in fact, by design).  What I mean is, in ANY system with EFI security (which is where Secure Boot itself is defined), it is, in fact, designed to stop unauthorized installations in their tracks.  In other words, it's Secure Boot doing it's job.  That is whether TPM is installed or not.  (Contrary to some schools of thought, Secure Boot does NOT require TPM - not when it comes to UEFI.)

I didnt say secureboot requires TPM.

 

But TPM was enabled on this. I did read that MS if you installed the AU will REQUIRE TPM 2. 

 

On new PC's. Which means anything that uses TPM 1.2. This computer isn't new. I built it just over 2 yrs old ago.

 

Now that I've removed the TPM 1.2 module, and replaced it with a TPM 2 module, it boots into windows. And secureboot is still enabled
 

I didnt disable secureboot to see if this was the prob when I started getting this 0xc000000d error. As soon as I disabled TPM in the BIOS, this error never came back. And wont now, since I installed a TPM 2 module

 

2 hours ago, John.D said:

But if it cant be updated, (or if the chip / whatever in it cant be removed / replaced) not much you can do about it. You cant use TPM 1.2 with the AU.

 

You may have to reinstall a prior version to before the AU came out. Since this is what causes the 0xc000000d error I posted

 

Had to get it from EBay, because I dont think it exists here yet.

My Asus motherboard is a legacy -- no TPM.

 

Which explains why no Settings were found in the BIOS.

 

You are so right about reinstalling my original OEM W10 dvd -- which is what I did.

 

I am certainly not replacing my motherboard to accommodate Windows 10.

 

And, TPM is available from Amazon:

 

https://www.amazon.com/Asus-TPM-M-R2-0-14-1-Module/dp/B01DQQLH74/ref=sr_1_5?s=pc&ie=UTF8&qid=1472778583&sr=1-5&keywords=tpm+module

 

 

Edited by Hum
14 minutes ago, Hum said:

My Asus motherboard is a legacy -- no TPM.

 

Which explains why no Settings were found in the BIOS.

 

You are so right about reinstalling my original OEM W10 dvd -- which is what I did.

 

I am certainly not replacing my motherboard to accommodate Windows 10.

 

And, TPM is available from Amazon:

 

https://www.amazon.com/Asus-Accessory-TPM-FW3-19-BitLocker/dp/B0085E4WQQ/ref=sr_1_1?s=pc&ie=UTF8&qid=1472777293&sr=1-1&keywords=tpm+module

Thats a TPM 1.2 module. Which was installed in this and I replaced it with a TPM 2 module.

 

Wont be buying anything from Amazon. By the time they convert it to my $ then add postage / freight whatever, the cost triples

 

And that cant be shipped to my address anyway

 

 

14 minutes ago, Hum said:

 

 

 

4 hours ago, John.D said:

I did read that MS if you installed the AU will REQUIRE TPM 2. 

 

On new PC's. Which means anything that uses TPM 1.2. This computer isn't new. I built it just over 2 yrs old ago.

Only for OEM certification.  If you're not building machines (and putting a Windows 10 ready sticker on it) for other people you can use TPM 1.2 fine.

Obviously it doesn't work for everyone (if it's meant to)

 

Like I said, if TPM was enabled in the BIOS, it wouldn't boot into Windows

 

Could be the module that I was using. TPM 1.2 may work fine for other people who use another chip, but obviously it kills TPM 1.2 if you're using an ASUS 1.2 module

 

I wasnt using Bitlocker, nothing was encrypted. Having the TPM enabled in the BIOS, caused the error I posted

 

I'm not that bothered now since I've installed a TPM 2 module, and it's been fine since

 

 

 

 

 

 

 

 

This topic is now closed to further replies.