Microsoft May Already Have a Reliability Strategy

Adalwar · 13 Sep 2016

"Forced updates for this OS is a bad policy... Plain and Simple."

Totally agree.
I am having issues with long restart times (up to 1min. 40s) with release 1607.105.
Now, if I uninstall KB3176938, system goes back to 1607.0 which is a release with major issues.

Steve C · 13 Sep 2016

Adalwar said:

That is what I feel it is going on.
Testing takes almost 75% of the hole Costs on Software products!
Further, Windows is growing and growing , what makes it more difficult to test, and the Time for testing increases so that to have a fully tested release will take many months.
After all there is the question around the strategic of offering new Builds as "free", so we may have to accept some "flaws" .

Does MS work to ISO software QA standards and are they subject to external QA audits to assist in the production of quality software? If so, then the process is falling sown somewhere.

alphanumeric · 13 Sep 2016

Getting back to the original article from the first post, unless I missed something? I didn't see anything to back up his claims of a staggered rollout to "known-good configurations first'? It was a staggered rollout but as far as I know it was more region specific than anything else. My one PC that got it via Windows update was the one I lost my 1 TB dive on. That would seem to contradict his reasoning? My other PC's that had no issues never saw it via Windows update. I eventually just did the upgrade manually a couple of days after the release of the AU. I haven't seen any similar info to match his claims anywhere? I'm not saying that that's not what Microsoft is doing, I just haven't seen anything official saying so.