About the Author
I’m out of luck considering the process of deploying the first version of Windows 10. The version that many people have been waiting for, but few want to receive in the form presented in the Insider Preview. In many ways, Ten is better than the hypothetical Windows 8.2. The problem is it was decided that the new release should offer more than “8.2”, but it’s not ready for that yet. Unfortunately, this doesn’t affect the release date.
When Windows 10 popped up in its predecessor Windows Update, it wasn’t ready at all. The new Edge browser is less capable than Internet Explorer and full sync doesn’t work on it. The UWP application is dramatically unfinished. Many elements are very unstable. The documentation mount has become obsolete, the workaround for previous versions has stopped working. Ten performed worse than Windows 8, which received the 848MB update as a result.
But for many users, this is not a problem. On thousands of computers, Windows 10 can’t be installed (and often, without being invited, he really wants it). My laptop needs a clean install as upgrading from Windows 8.1 is not possible. Installation failure ends with the legendary message “Something went wrong” (Something’s happened). On many PCs, this has been the main motive for the next version.
Automatic Updates always has risks. Over the past twenty years, there have been known problems with, for example, reboot loops that appear after downloading and installing new patches. However, in the case of Windows 10, the number of such stories has become enormous. Reading the IT portal headlines the second day after the new update was released, you can assume that Windows 10 is basically working magically, by accident.
If it’s so bad, why is it so good?
Meanwhile, it is the most popular operating system for PC. This constitutes the majority of installations on personal computers, and the server edition is a staple in many companies. Like it or not, but if does not workhe won’t be around Lots. So what happened? Where has the update quality changed? I will try to answer this from the perspective of the latest Dozens of users.
All updates are cumulative
One of the most important changes to Windows Update, from a quality standpoint, doesn’t make it any harder to disable. After all, this is not where the stability of the update depends. A significant change is the discontinuation of the separate patch. Back then, when 30 holes were found in 20 materials, about 20 updates were released. We always get today one, cumulative.
This means fewer paths to test and should translate into higher quality. In practice, however, the update process has taken an “all or nothing” form: operations are extremely complex and demanding at all times. A single-component failure ends in a complete rollback, and it doesn’t always work. In addition, optional components are mixed with critical components and installed immediately. It is impossible to temporarily stop the erroneous search engine update installation today or rely on the fact that it will not install alongside the important patches in remote desktop services. Both of these will be updated simultaneously.
There are more system versions
Windows 10 is not a system. These are twelve different releases, most of which are still getting updates, prepared separately. Such a significant increase in software volume should translate into more problems. Microsoft finally saw the clear and switched, in a sense, to the one-year model. Will that help? Probably not. But it won’t hurt.
There are many more types of devices
The PC platform has undergone a solid diversification over the last few years. Computers are starting to become very different from one another, and even “mainstream” computers, made up of almost the same components (compelled by eg Intel vPro), exhibit diversity beyond reason. Many devices, such as the Thunderbolt bus, require complex driver infrastructure to be reinstalled, simply not “in the box.”
It’s not Windows that makes money
Finally, remember that Windows is not the main source of income at Microsoft. Over the past decade, the company has successfully re-oriented itself to Azure. Microsoft doesn’t even have a separate team to work on Windows. Any Windows problem that doesn’t end in worldwide paralysis doesn’t need to be fixed because it won’t make the company money. Otherwise, we wouldn’t have three Control Panels for long.
Lastly, the final, least important and most frequently cited reason for a quality disaster is the dismissal of the examiner. Indeed, the transition to quick releases and quality control by Insiders has degraded quality. But it doesn’t matter if it weren’t for the impossibility of a very fast publishing schedule. Windows 7 was written for 1.5 years, and the second was spent on correction. Today is a scenario from another world.
Okay, but that only explains why it’s worse. Why doesn’t the world collapse from it? In short: these problems are rare and people have no choice. One percent of the damaged installations were small from a quality control perspective, but high for the number of users. As a result, this creates an isolated but frustrating (and sometimes quite spectacular!) Scenario that fills your headlines.
With such a scale of complexity, it is impossible to deliver a system without glaring errors at current speeds, and the market does not allow slower speeds. Therefore, you are not creating a solid and reliable system, only one that will work well in most scenarios.
And like that today. The system has hundreds of known bugs. Microsoft doesn’t pretend otherwise, including Windows Server. Release notes often report issues that will be “fixed in the future” over the next two years. Windows 10 will never reach the stability level of Windows 7. But by reading the documentation carefully, you’ll find that this is not the goal.
Most users will have no problems with Windows 10. People interested in the topic get something like “confirmation bias”: the huge amount of information about issues on the IT portal creates this misunderstanding of quality. The number of issues, at the current scale, is too small, and the quality of support is too high for any difficulty with Windows 10 to impact its popularity.
The situation will get worse. The system will not lose weight, but will gain weight. Reducing the number of releases will eliminate the risk of losing quality control, but will not make repair a priority. And that wouldn’t be if Azure paid the bills on Redmond and not Windows.