Windows 10 Anniversary CLEAN install: a nightmare!

dalchina
What I suggest is to try a clean install of 1511 and see what happens. You had 10240 on your PC, but as I understand it, the upgrade failed, but you didn't try a clean install. Do that without doing updates during the installation. You can do those later.

That's the only thing I can think of in case you are experiencing freezing issues with 1607

Lio said:

I understand your opinion, but I think it would create more trouble.
Install an OS already surpassed in place of the new one (the Anniversary one) that in fact is not an update but a new OS, seems to me really weird.
Also because we already know that Anniversary as update gives many issues.
And, over all, I cannot believe that Windows can make such a mess!

But, thanks anyway :)

TBH what D man says is entirely plausible and and nothing that isn't done routinely especially in winbeta world , it's impossible to validate a given biuld on all the variable configurations out there and that moreover includes customs & unusual or uncommon configurations or HDWE pairings and maybe a loud Game OC / + voltage at CPU and or d/GPU and maybe memory . OTOH a DVM and voltage rail check for PSU rail sagging or a bad ground would also be plausible if it's unstable on any other OS in there

A clean install can fix many things including random freezing (just ask around here ) and is the only best way to instal windows period or establish a legitimate base point for diag anyway and should have been your first remedy attempt if it wasn't followed by a *clean roll back like D man says if those clean install (s) didn't work it's not unheard of and you could sit it out for the duration for another build .

IF MS has your telemetry on an uncommon aftermarket configuration and custom random parts pairing that is causing this don't put any money on a finish resolution anytime soon if at all they likely go for broad market OEM retail, CTO or common custom OD vendor configurations out in the field first .

IOW If you beta test that's always a contingency ,rolling back nothing weird ..........all of it just is or isn't in beta testing without an out of hand fix or an official fix or a reg hack or file hack or string ( *that works ) and may equally apply to the AU

OTOH there are some new found issues out in the field with some (a lot) of Samsung SSD's so maybe you might want to Google search all that drama and see if your SSD is one of those

I've maybe done it both ways ,clean install and upgrade dirty and easy more times than you can count on 10 hands and then more than that since win 3.0 and DOS and I've seen DIY /ODM configurations and upgrades that all together without a HDWE and or driver change just wouldn't work on any given win OS .
ppffttt I could write chapters about dial up modems,modem strings and persistent IRQ things .

FWIW my critical daily driver PC and the family's PC are always new or passed from me validated HP PC's without exception and not the entertainment PC here beyond the web or media and the beta OS are always a separate drive. I don't do customs anymore beyond maybe significant upgrading of an assy line PC here like the Core i7 playing BF1 beta in the music PC game room addition right now or my driver at some point should the need arise .