New
#200
These early builds always have major bugs that make it pretty hard to use on a daily basis.
Apparently the issue with the settings crashing is limited to the Home versions.
Now I am a positive person and a great advocate of the W10 Insider program.
To suggest they have been fault free is naïve in the extreme, after all that is why the Insider program exists to unearth these anomalies.
Finding bugs does not make a person negative in outlook, all I can suggest is you have either been very lucky, or not doing much testing.
3rd option, I'm not that picky
But seriously, my Insider build is a Hyper-V virtual machine, so I would hope there is no driver issues, as it uses Microsoft's virtual hardware.
Basically, I have been testing how each upgrade goes, and the new or improved default apps in it.
Also, I make sure, my "most important" 3rd party software survives the upgrade.
There are some things the VM cannot test, such as Samsung Magician(some have had problems after a clean install of the anniversary update.
On my two physical machines though, The only clean install was after the initial "RTM" release. I prefer to just upgrade as it comes, like Microsoft plans, so working software & drivers(ones that don't meet the new strict enforcement of signing now) remain working, where as others after a clean install are now having problems, because a hardware manufacture slopped on getting his drivers digitally signed, even though they had a year warning or so.
I have been running W10 since first version as insider and nary a glitch. Must admit I was skeptical first couple of month and run it as dual boot with 8.1 but since than it's been my daily driver 24/7.
I do have W7 and couple of Linux distros for fallback though as this is my main computer and other ones are nowhere close to it's performance and capabilities. A laptop is still on XP.
I just never figured out why some members/users feel they "Must" do a clean install after every milestone upgrade.
There is really no need for it, unless the user messes something up.
If the upgrade goes awry, reimage, clean up what might have caused the problem, and try again.