To understand why Windows 10 customers are so upset, it helps to look at the Windows Update advanced options in Win10 Creators Update, version 1703 (screenshot below).įolks who want to take control of version changes in Windows 10 set those advanced options to (1) force Microsoft to wait until a new version is declared “Current Branch for Business,” then (2) after the version has hit CBB, to wait an additional 365 days before upgrading to the new version, (3) hold off on cumulative updates until 30 days after they’re sent out the Windows Update chute, and (4) overriding all of that, hold off on all updates - cumulative updates and version changes - for 35 days.Įxcept, golly, Microsoft hasn’t followed anyof those settings. Makes you wonder if the patching group now has its own PR department. But the notice didn't go out until Friday evening.
Microsoft's getting better at the bad news game. That fits in with the KB update history logs, which show the patch KB 4023057, Update to Windows 10 Versions 1507, 1511, 1607, and 1703 for update reliability was released on March 8. Microsoft mitigated this issue on March 8, 2018. Microsoft is aware that this notification was incorrectly delivered to some Windows 10 Version 1703 devices that had a user-defined feature update deferral period configured. That article was modified during the Friday night news dump period to add: Windows 10 version 1607 and version 1703 are not yet at "end of service." However, they must be updated to the latest versions of Windows 10 to ensure protection from the latest security threats. Windows Update will then try to update your device… If you're currently running Windows 10 Version 1507, Version 1511, Version 1607 or Version 1703, you can expect to receive a notification that states that your device has to have the latest security updates installed.
0 kommentar(er)
