![]() ![]() This feature first appeared in Windows Insider Preview build 15002 this week, though it was also in a leaked build we discussed at the end of 2016. You are either getting updates or you’re not.īut to its credit, Microsoft is adding a feature in the Creators Update-in Windows 10 version 1703, that is-that will let you “pause” non-critical updates for up to 35 days. And while I think it’s OK that we’ve crossed this line into a future where everyone needs to be kept up to date, my issue is that there’s no gray area. ![]() That is, when things are working properly, the update can go out faster, and when things are not, it can be scaled back.īut the problem with Windows 10 for far too many people, of course, is that they no longer have control over updates. The problem is so bad that I called on Microsoft to consider a formal Reliable Computing Initiative.īut the staged rollout of the buggy Anniversary Update provides some clues for a potential solution: By staging or delaying updates for normal users, Microsoft can gather real-world telemetry data as it goes, and this ever-growing body of information can inform the speed at which updates are deployed. As I noted in 2016 Was a Monster of a Year for Windows 10, Microsoft spent much of last year scrambling to fix the problems it created with its Windows as a service strategy. While this addition is well-intentioned, it doesn’t go far enough.įortunately, there’s still time for Microsoft to correct this mistake: It will not complete the Creators Update-which will upgrade Windows 10 to version 1607-for another two months. As you may know, Microsoft is adding the ability to pause updates in Windows 10 version 1703. ![]()
0 Comments
Leave a Reply. |