As a major aspect of the June 9 Patch Tuesday, Microsoft discharged a fix for one of the issues that has obstructed a few Windows 10 clients – and Surface gadget clients specifically – from having the option to apply the May 2020/2004 element update. In any case, significantly subsequent to fixing, Surface Pro 7 and Surface Laptop 3 clients (among others) despite everything won’t have the option to get the May Update right away.
Subsequent to declaring on May 27 that it was beginning to make the May 2020 element update accessible by means of Windows Update, Microsoft additionally discharged a rundown of around twelve beforehand undisclosed issues which possibly could mess up anybody applying the May Update.
One of those issues has to do with potential surprising restarts for gadgets with more than one Always On, Always Connected system connector. Surface Pro 7 and Surface Laptop 3 both qualify as these sorts of gadgets.
Microsoft released today KB4557957 (OS Build 19041.329), which, as per its documentation, mitigates this Always On, Always Connected issue. Nonetheless, the Microsoft documentation for this additionally says “To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004.”
(Windows 10 clients with 1903 and 1909 likewise ought to physically introduce the KB4560960 (OS Builds 18362.900 and 18363.900) fix before KB4557957. In any case, that despite everything doesn’t make Windows 10 2004 accessible quickly, either.)
Any “seekers” with the Always On, Always Connected issue who physically check for refreshes with expectations of downloading and introducing the Windows 10 May 2020/2004 update will in any case get this message significantly subsequent to applying the June 9 patches:
“The Windows 10 May 2020 Update is on its way. We’re offering this update to compatible devices, but your device isn’t quite ready for it. Once your device is ready, you’ll see the update available on this page. There’s nothing you need to do at this time.”
Microsoft authorities have declined to clarify why the dozen or so late-breaking blockers for the May 2020/2004 update were not revealed until May 27, despite the fact that that element update had been in trying for almost six extra months past its consummation date.
They’ve gotten notification from a portion of their contacts that these issues might not have been generally experienced until Microsoft started testing with Release Preview Ring clients and introductory standard rollout recipients. Be that as it may, nobody from Microsoft has expressed this openly.