Just a couple of hours ago we talked about the expected release of a package of updates for Windows 10 that has been referred to as Service Release 1 (SR1).
Well an update released a short while ago to all Windows 10 systems has been labeled Cumulative Update for Windows 10: August 5, 2015 (325MB). It has no markings as Service Release 1 although many tech sites are labeling it as such.
I asked Gabe Aul on Twitter if this was in fact SR1 and he responded by saying it was just a cumulative servicing update. As a follow on I asked if that meant the expected Service Release 1 was still pending.
As of the time of this writing I have not had a reply back yet.
Whether this is SR1 or not it brings up a question about the entire discussion of Windows as a Service (WaaS) and the flighting of updates through both Microsoft's internal testing rings and the external Windows Insider rings.
This update was pushed through Windows Update today to all Windows 10 PCs running build 10240. That meant it went to both Insiders and non-Insiders - and with no testing through the Insider Fast or Slow Rings. While I am sure it was tested internally and vetted, it is curious to see a release hit systems before testing with Insiders.
We have been told along the Windows 10 development process that the flighted testing through these rings would be the norm for any prospective updates to the OS. It is strange to see the first post release update hit systems without that Insider testing phase.
I guess it could be that Microsoft has not yet officially launched the post release Windows Insider Program, even though it is possible to opt in our systems to receive Insider builds now, and this update was simply handled just like previous Windows Updates are handled.
If you are looking for what was fixed in this cumulative servicing update then you are not going to find much more than a list of files and the date they were changed.
In my opinion Microsoft would gain a lot of goodwill by simply summarizing what has been addressed in an update so users do not have to go looking for it.
One confirmed fix from Rod Trent is that Microsoft Edge no longer lockups on dual monitors when moving tabs.
Have you noticed any other fixes after the update?
