cancel
Showing results for 
Search instead for 
Did you mean: 

Windows 20h2

Hopper64
Level 14
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.*
MZ790A Bios 2002, GSkill F5-8000J3848H16GX2-TZRK, 13900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.0, Asus Strix 4090 w/ Optimus block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Samsung 990, Windows 11 Pro
3,634 Views
4 REPLIES 4

G75rog
Level 10
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
Level 13
20241.1005 Build running smooth
W11CANARY 26063.1000 Core i9 7980XE 02007006 MCE ME 11.12.95.2499 R6E OFFICIAL BIOS 3801 SAMSUNG OG9 FW 1019.0 SSD 970 EVO PLUS 1 TB x 3 NVIDIA RTX 4090 GAME READY 551.61 64GB GSKILL DDR4 3200MHz JBL 9.1 Sound Bar DTS-X

Hopper64
Level 14
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. ??
MZ790A Bios 2002, GSkill F5-8000J3848H16GX2-TZRK, 13900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.0, Asus Strix 4090 w/ Optimus block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Samsung 990, Windows 11 Pro

Hopper64
Level 14
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:

86602


86603


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.
MZ790A Bios 2002, GSkill F5-8000J3848H16GX2-TZRK, 13900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.0, Asus Strix 4090 w/ Optimus block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Samsung 990, Windows 11 Pro