In a new post on its Windows Blog, Microsoft details its Windows Update mechanism so that we can collaborate in the corporate process to see how the precious updates are rolled out. While some Windows updates obviously have not gone according to the plan, the vast majority, and in view of the complexity and scope of these updates, it is actually surprising that we do not see even more problems than we do.
According to Microsoft, it provides updates of about a thousand units per second eventually peaked one billion units per month. It's not just Windows 10, but all versions whose windows like Microsoft still support – even if that support seems unlikely. Windows XP is linked to these numbers since some companies have chosen continued support with the now old OS.
Most people are familiar with Patch Tuesday, which is the first day a month when Microsoft rolls out the latest update to its customers. It is internally known as the "B" release, but C and D releases are also available. Interesting, C and D updates can be enjoyed by manually checking for updates – it's so easy. By doing so, it means that you essentially get preview of some code that will make it to next Patch Tuesday. In particular, Microsoft notes that "the purpose of these releases is to provide visibility and enable non-security testing that will be included in the next update Tuesday release (we make these optional to avoid users being started more than once per month). " So, yes, in some cases, your system is a test guinea pigs for Microsoft, if you are looking for manual updates and pulling Windows Updates, instead of waiting for them to be pressed.
Under any circumstances, where a security update needs to be pushed out as quickly as possible, Microsoft has that opportunity – even if it's a rare one. Similarly, Microsoft even fixes issues before these issues are known to the public – and it is done very with purpose. It is also a process that requires collaboration across the industry.
To ensure that the updates we receive are as trouble-free as possible, Microsoft uses as much automation as possible in the test so it can quickly break anything if it can be corrupted. Despite that, the strange error still occurs, which only emphasizes just how complicated an expensive Windows (or any OS) really is.