Windows 10: Cumulative Update KB3176938 Windows 10 build 14393.105

A very good and enjoyable post, I do myself read everything on here and I love reading what is coming in the next build, I think all you beta testers do an excellent job, so that when we the general public get it is 99% working as I should do.
Keep up the good work

 

In principal I agree with you, BUT .....

Will someone that knows, please explain why the Anniverary update was almost immediately followed a pretty large update ( this one) within the same month of release??

I see two possibilities here:

(1) That all the beta testers and MS involved missed a massive problem which non testers unearthed almost immediately --- A very unlikely possibility.

or
(2) The royal "Everyone" knew about the problem. However, Marketing was NOT prepared to delay the release, telling "everyone" that they can fix it with an update, but the Anniversary release WILL go ahead regardless ... ??*Huh

 

Thank you for the good words, kind sir.

I think it's good that End Users read Insider stuff, since it will give y'all a "heads up" on features to come.

Also of note is that when "cumulative updates" come out for Build 14393.xxx, we Insiders have already tested the bits. However, I must say that even though we've tested, Microsoft can sometimes figure out a way to mess up all our testing. *Smile

 

I think this is one of those cases that my post just above this one describes, which bears repeating:

Replace "cumulative updates" with Anniversary Update in the above quote to be a little more accurate with the situation you describe. Although it was the Anniversary Update, we testers are not the last word when Microsoft releases new Builds.

The Anniversary Update worked exactly as it should have for me on both my Desktop and my Laptop; however, when the "cumulative update" for the Anniversary Update came down the pike, it did its best to destroy my Laptop. Since I don't have all the knowledge of Microsoft's coders, I haven't a clue as to what went wrong with AU the first time around.

Most likely not what happened. Most likely, it has more to do with a combination of software/hardware on particular systems that were bitten.

or

As I've said above, the Anniversary Update was totally stable on my machines . . . from both an Insider version and the End User (AU) version. Microsoft doesn't usually tell us exactly what went wrong, but at this point, I don't believe Microsoft had any inkling that things would go so far South as they did. Some coder pressed the wrong key and things went Boom!

 

I think #2 is more correct. With the aggressive push from MS to get everyone upgraded to 10 and a set date for the AU release I think MS felt it was better to go ahead and release it as promised.

 

I'd say it was more of a "wrong button pushed" at the last minute. It's happened before and it will happen again.

 

I think MS knew about the problems and felt it was better to go ahead and release the AU on the promised date than to push it back. MS has made a lot of bad decisions starting with Windows 8.

 

Oh, the bad decisions didn't start with Windows 8!

I tested Vista and we BTs told Microsoft it wasn't ready for prime time, but did they listen? H E double toothpick NO, they didn't.

Same thing to a lesser extent with Windows 7. We told them specific areas where it was lacking, but did they listen? H E double toothpick NO, they didn't.

This time, though, I think they're listening a little better, which is why I'm thinking someone made a boo-boo. I know of at least one instance and possibly two or three where this did happen and MS told us about it.

 

There are 2 sorts of feedback - the User feedback, and the telemetry (Windows Error Reporting) that automatically gets back to Microsoft. This covers the user experience -which may be reported in a very subjective manner, and the technical processes that underlie the user experience.

When the Build 14393 was released to Insiders on July 20th, there were 2 weeks of this multi-stranded feedback to work its initial resolutions into the cumulative update issued shortly after 14393 was introduced on August 2nd as the Anniversary Update. An almost identical situation happened after the original RTM 10240 build the year before. Pretty much the same for 1511 too.

Then the real wide scale testing began for each Feature Release, with regular cumulative updates.

As I mentioned here, some of the bugs introduced with cumulative updates, as well as with new builds, may be deliberate in order to debug known problems over a range of different devices and hardware configurations. Then with enough telemetric data, the problem code can be rewritten properly and the development debug code may be removed in the next CU.

 

It was more obvious to the general user with Windows 8 because MS had that you take what we give you and like it attitude. We all know how that went over.

 

Yeah, that was Sinofsky and his "firing" of all the "at large" beta testers. He decided he knew better than all the best minds at Microsoft, but was a miserable failure and is, thankfully, long gone.

He almost sent me to Linux . . . but not quite to Apple!

 

That was Sinofsky's attitude but I doubt one person had all the say. I'm sure he had others agreeing with his decisions. And I totally agree that if I was to abandon Windows I would choose Linux over Apple any day. *Smile

Edit: I did stray from Windows for awhile. I switched from Windows to Linux Mandrake for awhile. Being a Windows 7 tester brought me back to Windows. I do use Linux Mint in a VM to play around in. I do like it but not enough to stop using Windows 10 as my main OS. With all it's pluses and minuses Windows 10 is the number one OS in my book. *Smile

 

This is a great topic to read. And thank you to Wynona for laying it all out so clearly. I don't think I've seen it all as clearly explained before.

i agree that MS may of cleaned up its act and starting listening to users. There is a lot I don't like about Windows 10 and still too many bugs in the public build for my liking but it's heading in the right direction. I don't think they intend to release bugs into public code and make mistakes. It's just for someone with little spare time to enjoy the PC I find the mistakes hard to swallow and get cross.

that being said MS are much better than apple. I use their iOS devices and apple are the worst offenders for releasing new iOS despite known problems which are reported repeatedly during beta. I find that pretty inexcusable. I think even if there was a crippling bug in the iPhone iOS that prevented users reliably making phone calls (or another core feature) they'd still just go ahead and release it for bragging rights! Their mantra of 'it just works' seems pretty far fetched. So in comparison MS approach (while far from perfect) seems much better than the other software juggernauts.