After months of complaints, Microsoft has finally opened a Windows 10 Update History web site that will document the changes it makes to its flagship OS.
“After listening to feedback regarding the level of disclosure for Windows 10 updates, we decided to implement a new system for communicating updates to the operating system,” a Microsoft representative told me. “Today we are rolling out the Windows 10 update history site, a hub for the release notes that will accompany each update and serve as a historical record of prior release notes.”
Microsoft promised last October to become more transparent about the updates it provides for Windows 10. And as you might expect, Windows 10 Update History is similar to the way that Microsoft documents its Surface firmware updates.
As an example, here’s what’s provided for KB3135173, which Windows Update would have in the past unhelpfully described as “Updates for Windows 10 1511”. Yes, this is new (and hasn’t even shipped yet):
February 9, 2016 — KB3135173 (brings system to 10586.104)
This update includes quality improvements and security fixes. No new operating system features are being introduced this month. Key changes in this update include:
- Fixed issues with authentication, update installation, and operating system installation.
- Fixed issue with Microsoft Edge browser caching visited URLs while using InPrivate browsing.
- Fixed issue that didn’t allow simultaneous install of apps from the Windows Store and updates from Windows Update.
- Fixed issue that delayed the availability of songs added to the Groove Music app in Windows 10 Mobile.
- Improved security in the Windows kernel.
- Fixed security issues that could allow remote code execution when malware is run on a target system.
- Fixed security issues in Microsoft Edge and Internet Explorer 11 that could allow code from a malicious website to be installed and run on a device.
- Fixed additional issues with the Windows UX, Windows 10 Mobile, Internet Explorer 11, Microsoft Edge, and taskbar.
- Fixed additional security issues with .NET Framework, Windows Journal, Active Directory Federation Services, NPS Radius Server, kernel-mode drivers, and WebDAV.
For more info about the security fixes in this update and a complete list of affected files, see KB3135173.
This is exactly the kind of transparency that I, other Windows watchers, and Microsoft’s customers have been asking for. It’s too bad it took so long, but I’m quite happy with the results.