Microsoft's own operating system should finally start working on its own hardware ... 'in the coming weeks'
(2020/06/10)
- Reference: 1591788088
- News link: https://www.theregister.co.uk/2020/06/10/windows_10_2004_surface_fix/
- Source link:
Lurking within the epic patch dump offloaded on Windows 10 2004 users last night came the news that Surface Pro 7 and Surface Laptop 3 owners have been waiting for: fixes for glitches.
The unexpected restarts and errors afflicting Always On, Always Connected devices have been rectified as part of [1]KB4557957 .
Not that the support article for the 9 June emission of fixes for Microsoft's latest edition of its flagship OS makes any mention of it. You have to turn to the [2]Windows 10 health dashboard for the revelation that the safeguard hold on the devices will be lifted in "the coming weeks."
So a bit longer to wait then.
The Surface Pro 7 and Laptop 3 devices are not the only ones blocked from receiving the May 2020 update. One Register reader has been in touch to say that his i7 Surface Pro 6 was on the receiving end of the dread from Windows Update: "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".
Another reader possessed of a variety of Intel and AMD-based gear, Frank Reitz, noted that the published issues in the health dashboard didn't apply to his hardware, and yet Windows 10 2004 was still blocked. "Is this a Microsoft virtual release of 2004," he remarked, "that the vast majority of Windows 10 users can't access?"
Issues cropping up on non-Microsoft hardware are understandable, but quite why its own Surface gear should choke remains a mystery. Social media is jam-packed with the company's staffers loyally waving their devices around; surely at least a couple must enjoy tinkering with a preview build?
We contacted Microsoft to find out why, after spending more than a year in testing, it had managed to emit a version of Windows that was blocked on its own most recent devices. The company has yet to reply. ®
Sponsored: [3]Taking the Cloud-Native Approach with Microservices
[1] https://support.microsoft.com/en-gb/help/4557957/windows-10-update-kb4557957
[2] https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004#421msgdesc
[3] https://go.theregister.com/tl/1956/-8470/taking-the-cloud-native-approach-with-microservices?td=wptl1956
The unexpected restarts and errors afflicting Always On, Always Connected devices have been rectified as part of [1]KB4557957 .
Not that the support article for the 9 June emission of fixes for Microsoft's latest edition of its flagship OS makes any mention of it. You have to turn to the [2]Windows 10 health dashboard for the revelation that the safeguard hold on the devices will be lifted in "the coming weeks."
So a bit longer to wait then.
The Surface Pro 7 and Laptop 3 devices are not the only ones blocked from receiving the May 2020 update. One Register reader has been in touch to say that his i7 Surface Pro 6 was on the receiving end of the dread from Windows Update: "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".
Another reader possessed of a variety of Intel and AMD-based gear, Frank Reitz, noted that the published issues in the health dashboard didn't apply to his hardware, and yet Windows 10 2004 was still blocked. "Is this a Microsoft virtual release of 2004," he remarked, "that the vast majority of Windows 10 users can't access?"
Issues cropping up on non-Microsoft hardware are understandable, but quite why its own Surface gear should choke remains a mystery. Social media is jam-packed with the company's staffers loyally waving their devices around; surely at least a couple must enjoy tinkering with a preview build?
We contacted Microsoft to find out why, after spending more than a year in testing, it had managed to emit a version of Windows that was blocked on its own most recent devices. The company has yet to reply. ®
Sponsored: [3]Taking the Cloud-Native Approach with Microservices
[1] https://support.microsoft.com/en-gb/help/4557957/windows-10-update-kb4557957
[2] https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004#421msgdesc
[3] https://go.theregister.com/tl/1956/-8470/taking-the-cloud-native-approach-with-microservices?td=wptl1956
Sums up Microsoft's quality control
It's a huge embarrassment to have their own software fail with their own hardware. Clearly the quality of their code sucks, and either the quality control is terrible, or they just don't care. Or both.