How to get the Windows 10 Fall Creators Update

only thing i could see stopping this is a wired message i get about PCR7 binding issue, the error inside, system info is this Device Encryption Support Reasons for failed automatic device encryption: PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, not sure if that is related or not but it was never there before once i fixed things for windows 10 with TPM and so on.

i notice that my laptop keeps getting these feature updates such as Anniversary Update, creators update, and fall creators a lot faster than my desktop. Like on day 1. Does anybody know how M$ handles theses updates?

Tonyb said:

only thing i could see stopping this is a wired message i get about PCR7 binding issue, the error inside, system info is this Device Encryption Support Reasons for failed automatic device encryption: PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, not sure if that is related or not but it was never there before once i fixed things for windows 10 with TPM and so on.

You definitely have a hardware compatibility issue. Did your computer come with TPM already installed or did you go through a procedure involving gpedit.msc allowing TPM to work before installing BitDefender?.

i bought the TPM at the same time i built the pc myself, I just never installed it until i re did my system when windows 10 came out, i had not one issue till this fall creator update, tpm.msc give now TPM errors and inside device manager it claims to be working 100% fine. is so strange only thing i can think of is something changed in the creator update.

Tonyb said:

i bought the TPM at the same time i built the pc myself, I just never installed it until i re did my system when windows 10 came out, i had not one issue till this fall creator update, tpm.msc give now TPM errors and inside device manager it claims to be working 100% fine. is so strange only thing i can think of is something changed in the creator update.

Sorry, that's true you have mentioned that you bought the TPM. Like I said, the best thing to do is to roll back since your computer was working normally before FCU referring to my post # 370. I know sometimes it is a big hassle to roll back, but the inconvenience of it outweighs the frustration of living with the problem you are facing.

i may give it a try or live with it does not seem to affect anything that i can see :)

Hello,

I've updated my system using Windows 10 Update Assistant one day after the update became available. On the 17th of October, though, before using the Assistant, I got the official ISO.

This morning, 22-October, I downloaded the official ISO again.

Why is the following happening?



Has the ISO changed, has it been updated since the 17th?

My apologies IF this has been already mentioned-answered, I have not read the entire thread.

Thank you.

imeem said:

i notice that my laptop keeps getting these feature updates such as Anniversary Update, creators update, and fall creators a lot faster than my desktop. Like on day 1. Does anybody know how M$ handles theses updates?

Who knows? It's my understanding that newer hardware is supposed to get major updates sooner. But my laptop got the FCU immediately after it was made available and it had Vista installed when it was new. A friend with a much newer laptop hasn't been offered the FCU yet.

IronZorg89 said:

Sorry, that's true you have mentioned that you bought the TPM. Like I said, the best thing to do is to roll back since your computer was working normally before FCU referring to my post # 370. I know sometimes it is a big hassle to roll back, but the inconvenience of it outweighs the frustration of living with the problem you are facing.

so my error with device encryption is normal as i just looked mine is a older TPM 1.2 , but it does meet UEFI secure boot functionality so as to why that stopped working with the update is beyond, me i think i may give MS a call tomorrow and see what they think. hope this chart thing and that page helps others on stuff. god bless and thanks for the help.

taken from TPM recommendations (Windows 10) | Microsoft Docs
TPM and Windows Features

The following table defines which Windows features require TPM support.

Windows Features	TPM Required	Supports TPM 1.2	Supports TPM 2.0	Details
Measured Boot	Yes	Yes	Yes	Measured Boot requires TPM 1.2 or 2.0 and UEFI Secure Boot
BitLocker	Yes	Yes	Yes	TPM 1.2 or 2.0 is required
Device Encryption	Yes	N/A	Yes	Device Encryption requires InstantGo/Connected Standby certification, which requires TPM 2.0.
Device Guard	No	Yes	Yes
Credential Guard	No	Yes	Yes	Windows 10, version 1507 (End of Life as of May 2017) only supported TPM 2.0 for Credential Guard. Beginning with Windows 10, version 1511, TPM 1.2 and 2.0 are supported.
Device Health Attestation	Yes	Yes	Yes
Windows Hello/Windows Hello for Business	No	Yes	Yes	Azure AD join supports both versions of TPM, but requires TPM with keyed-hash message authentication code (HMAC) and Endorsement Key (EK) certificate for key attestation support.
UEFI Secure Boot	No	Yes	Yes
TPM Platform Crypto Provider Key Storage Provider	Yes	Yes	Yes
Virtual Smart Card	Yes	Yes	Yes
Certificate storage	No	Yes	Yes	TPM is only required when the certificate is stored in the TPM.

Tonyb said:

so my error with device encryption is normal as i just looked mine is a older TPM 1.2 , but it does meet UEFI secure boot functionality so as to why that stopped working with the update is beyond, me i think i may give MS a call tomorrow and see what they think. hope this chart thing and that page helps others on stuff. god bless and thanks for the help.

taken from TPM recommendations (Windows 10) | Microsoft Docs
TPM and Windows Features

The following table defines which Windows features require TPM support.

Windows Features	TPM Required	Supports TPM 1.2	Supports TPM 2.0	Details
Measured Boot	Yes	Yes	Yes	Measured Boot requires TPM 1.2 or 2.0 and UEFI Secure Boot
BitLocker	Yes	Yes	Yes	TPM 1.2 or 2.0 is required
Device Encryption	Yes	N/A	Yes	Device Encryption requires InstantGo/Connected Standby certification, which requires TPM 2.0.
Device Guard	No	Yes	Yes
Credential Guard	No	Yes	Yes	Windows 10, version 1507 (End of Life as of May 2017) only supported TPM 2.0 for Credential Guard. Beginning with Windows 10, version 1511, TPM 1.2 and 2.0 are supported.
Device Health Attestation	Yes	Yes	Yes
Windows Hello/Windows Hello for Business	No	Yes	Yes	Azure AD join supports both versions of TPM, but requires TPM with keyed-hash message authentication code (HMAC) and Endorsement Key (EK) certificate for key attestation support.
UEFI Secure Boot	No	Yes	Yes
TPM Platform Crypto Provider Key Storage Provider	Yes	Yes	Yes
Virtual Smart Card	Yes	Yes	Yes
Certificate storage	No	Yes	Yes	TPM is only required when the certificate is stored in the TPM.

I would not venture to say there is probably a problem in your motherboard settings. I know, however, for a fact, that when one first runs the update assistant to install FCU, the first thing appearing is a window telling one whether or not there is a compatibility issue. If everything is checked "OK", one is invited to click "Next" for the download to begin. Do you remember that window?.

If your decision is to roll back, make sure to check (troubleshoot) the items mentioned in my post # 370. I would also invite you to confirm in your BIOS that you are on UEFI and not Legacy mode before reinstalling FCU. On the other hand, if you opt to call Microsoft, I really would like you to post back on what has come out from the conversation with them..