📎 AI Summary:
The thread discusses the lengthy and often stuck installation process of Windows Insider builds, specifically build 17666.1000, with users sharing experiences ranging from several hours to over six hours for the update to complete. Despite troubleshooting efforts, some users report being stuck at 100% preparing to install, highlighting variability likely influenced by hardware and internet speed. Overall, the sentiment emphasizes patience during extended update times, with some noting improvements in subsequent builds.
The thread discusses the lengthy and often stuck installation process of Windows Insider builds, specifically build 17666.1000, with users sharing experiences ranging from several hours to over six hours for the update to complete. Despite troubleshooting efforts, some users report being stuck at 100% preparing to install, highlighting variability likely influenced by hardware and internet speed. Overall, the sentiment emphasizes patience during extended update times, with some noting improvements in subsequent builds.
My machine was built in early 2017. Maybe it doesn't have that. I'm sure I'd have been scratching my head over that one. The TPM thing threw me for a loop.
If you want to I'd be interested.
Sent from my SM-G935T using Tapatalk
Sent from my SM-G935T using Tapatalk
nmsuk
Essential Member
Yeah that would have freaked me out totally. If you know what all that means then my hat's off to you sir. I see where it gives a couple choices. How do you deal with that?
nmsuk
Essential Member
You stare at and then sigh and type exit and it boots to windows. Have it fixed but still it was a shock. Only popped out for a cup of tea and came back to that. So another tea was grabbed while I sorted it out. Can see the funny side now but a couple of days back not so. I wanted Gates head on a stick. 
Lol. That's funny. But still, you had to reinstall. That sucks. I hope they fix this.
Last edited:
Correct me if I'm wrong but I remember about 10 years ago there was talk of putting a TPM on just about every Motherboard to be made. Isn't secure boot info stored in it?
Yeah the info I'm finding says it's mostly about encryption. W10 Home doesn't natively do that. My TPM.Msc says its ready for use. I guess I'm wrong about it storing Secure Boot info.
It says mine doesn't support Attestation. I take it that means all it does is store info but can't affect anything else.
I'm still puzzled about why the new update made me clear it.
It says mine doesn't support Attestation. I take it that means all it does is store info but can't affect anything else.
I'm still puzzled about why the new update made me clear it.
Last edited by a moderator:
nmsuk
Essential Member
Indeed never too late to learn something new. Is one of the more interesting parts of life.
Sent from my CLT-L09 using Tapatalk
It's a bit confusing. There is EFI booting and legacy. EFI requires the signed EFI boot loader and a GPT formatted disk. Then secure boot does require a TPM to validate the trusted boot loader. There is also Trusted Boot and Measured Boot which are more secure.
Secure boot itself stores data in NV RAM.
Secure the Windows 10 boot process
Secure boot itself stores data in NV RAM.
Secure the Windows 10 boot process
Last edited:
So are these different ways computers boot up owing to different security needs of businesses or maybe government agencies?
