New
#101
Your point isn't completely lost, it was more of the way it was made, than the content.
I install a TP rls two ways, Windows Update and Clean ISO install. Then I run a set of consistent tests on each rls, adding new tests for new features.
When that is all said and done - I personalize the machine to my liking. Some of that requires registry mods because MS does not provide a UI to make the change. This doesn't mean that it is an unofficial modification, the registry keys and values are there to be set if you understand what they are. There are and will be MS sanctioned registry mods as part of a solution.
Will some mod break the system? Probably, but MS should know about that too.
Plain vanilla testing is the domain of MS, we're given the opportunity to the drive the OS. How I drive or how you drive is up to each individual. All feedback is useful to MS, there's no possible way for them to do what 2 million individuals might change or install. That's the real point of the TP - not just geeks, but how will regular users 'break' the system.
The real feedback is the telemetry they pull from your system - if they see a registry mod in the data, they know they either need to fix the code that caused the app or system crash or ignore the key/value.
Bill
.
It seems that MS is making registry tweaking easier for everyone probably through feedbacks MS is getting from Windows Insider hub.
They may be monitoring the Registry Editors too more that they read our feedbacks. :)
http://www.neowin.net/news/windows-1...-between-hives
The operative word being MAY!!!
Purely a subjunctive opinion M$ would find it extremely difficult to keep tabs on the registry modifications made on millions of computers on an experimental O/S especially if one takes into account some of the mooted points pointed out by ROGER in post #96 and these are just some of the problems encountered in installing this latest preview.