Microsoft has faced significant challenges with Windows 10, particularly since the release of version 1809. Users have encountered various issues, such as orange screens, high CPU usage, and Wi-Fi connection failures. To shed light on these problems, a former Microsoft employee shared a video on his YouTube channel explaining the underlying reasons.
Jerry Berg, who worked for 15 years at Microsoft specializing in Windows test automation tools, reveals that the company has changed its system for testing new versions, inadvertently leading to increased errors.
Berg provides insight into the testing process from 2014 to 2015 and how it has evolved in Windows 10. Previously, Microsoft had a dedicated team solely responsible for testing the operating system. This involved thorough testing of builds, drivers, and codes.
Whenever a new tool or change was introduced, the team would convene to discuss and address any bugs and conduct manual testing on real devices. They possessed various equipment with different processors, hard drives, video cards, and sound cards to test various configurations. The version will be released only when everything (or most) works correctly.
However, the company has now altered its approach. According to Berg, the testing team was largely downsized, and the focus shifted to virtual machines rather than testing on real devices.
Additionally, employees now use their own devices for testing new versions, enabling them to provide feedback on any issues within the operating system. Berg notes that this “self-host” model is not as widely adopted in larger companies.
Another significant change is that the primary data source for testing now comes from Telemetry and feedback from users enrolled in the Windows Insiders program. These individuals willingly test the company’s latest developments in exchange for providing feedback.
Berg emphasizes that these users may not always be willing to report problems, and the telemetry data may be inaccurate. In the previous system, the testing team gathered information and guided engineers on resolving issues. However, now they rely solely on telemetry to identify and address problems independently.
Lastly, Berg mentions that Microsoft recognized the risks of releasing updates, prompting adopting a phased approach. Updates are initially released to test users and developers before reaching the end users.
These changes in Microsoft’s testing process and release strategy have resulted in a different approach to ensuring the stability and reliability of Windows 10, addressing both the challenges faced and the evolving needs of the user community.