Windows 20h2

[Hopper64]

Uh, tried updating to 20h2 I think 3 times and got a blue screen 3 times. It was time for a windows clean installation anyway so I just completed that today. Just used the media creation tool for 20h2. No problem encountered, but I noticed the file system looks to be different. It doesn’t look to be GPT anymore? Maybe that’s why I was unable to update the current build?

Anyone have insight on this? Thanks.*

[G75rog]

My Insider 19 series self updated to 20H2 with no issues on a GPT 960 Pro.
The Win10 Pro 1903 on a GPT 970 Pro has yet to update.

[restsugavan]

20241.1005 Build running smooth

[Hopper64]

I used the update advisor downloaded from Microsoft initially, but never got it to work. Since it had been a few months since my last rebuild, I just downloaded the 20h2 iso and did a clean install. Worked fine. I still think there’s a difference in the way the partitions are laid out on the clean build though. ??

[Hopper64]

OK. So here's my confusion. I'm used to 3 smaller partitions of NTFS files followed by the larger partition with most of the data. The new build has 2 small partitions followed by the OS then a smaller partition. It's different from the pattern I'm used to. Here are screens of the new build on paragon's software:







That's why I was thinking the update advisor isn't such a good idea to update. Windows update probably would have been better. So that's when I burned an iso of 20h2 on a flash disc and reinstalled (overdue anyway-6 months old build). I'm thinking it caused the blue screens because the partition structure is different. ??? Just a theory.