Microsoft Delivers May 2020 Update to Surface Pro 7, Laptop 3

Posted on June 10, 2020 by Paul Thurrott in Microsoft Surface, Windows 10 with 10 Comments

As part of this week’s Patch Tuesday updates, Microsoft fixed a blocking issue that allows it to bring the May 2020 Update to some of its own computers.

“Some devices using the Always On, Always Connected feature might have compatibility issues with Windows 10 version 2004 ([, which is delivered by] the Windows 10 May 2020 Update),” a Microsoft support document explains of the original blocking issue. “Affected devices will have more than one Always On, Always Connected capable network adapter, such as the Microsoft Surface Pro 7 and Microsoft Surface Laptop 3, and might receive errors or unexpected shutdown or restart.”

Well, that blocking issue is now mitigated by KB4557957, a cumulative update that the software giant delivered on Tuesday. Oddly, this CU includes a number of fixes of wildly different purposes and related to such things as Windows Mixed Reality, Microsoft Edge, Microsoft Office, Xbox, Microsoft Store, and many more.

As is so often the case, you may not get it immediately, though I’ve already heard from several people who are now being offered the May 2020 Update on Surface Pro 7 or Laptop 3. “The safeguard hold is estimated to be removed in the coming weeks,” Microsoft notes.

Tagged with ,

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (11)

11 responses to “Microsoft Delivers May 2020 Update to Surface Pro 7, Laptop 3”

  1. Avatar

    Sihaz

    Did the firmware update on my Pro 7 and then tried to update using a usb stick I'd made with the media creation tool. still no dice...

  2. Avatar

    jt5

    Got the Firmware update and the cumulative update- but it still says my device is not quite ready for it. I wonder if some models of the Surface Pro 7 are getting it sooner? Anyway- more annoying than a big deal right now.

  3. Avatar

    jt5

    I got the updates as well- but it is still blocked...

  4. Avatar

    remc86007

    Still no update with AMD SL3. Ordinarily I wouldn't care so much about getting a feature update, but the May 2020 update includes a fix for hardware acceleration running in chromium engine browsers on AMD APUs. Right now, I have to use the dev version of the new Edge to prevent the black flashing window bug when running hardware acceleration. I have confirmed that it is fixed for the stable version of Edge and Chrome in 2004. I guess they aren't going to issue a hotfix for it for 1909 + stable Edge/Chrome.

  5. Avatar

    pbeiler1

    I have surface Pro 3, 4, 5, 6 in my shop. The 3 & 4 are getting the updates.

  6. Avatar

    SvenJ

    Surface Go getting it now. Surface Pro 7, several minor updates in succession (thought we were past that), then May 2020 Update coming soon, but no upgrade for you.

  7. Avatar

    dexman335

    I downloaded and applied Patch Tuesday files to my old Suface Pro 3 (I donated it to my church a while ago).


    Microsoft notified that 2004 is now available for that unit. Out of caution, I activated the 7 day delay to see how 2004 behaves out in public.


    My Surface Laptop (1) and Surface Pro 7 are still showing the not yet ready message.

  8. Avatar

    MacLiam

    My 2017 Surface Pro ("SP5") is not yet deemed fit to receive the 2004 update, but at least I'm parked on 18363.900, the most recent 1909 build. I'm hoping there isn't much more to be done to let the 2004 update come in.


    My old ordered-on-day-one Studio is also at 18363.900, but on a return trip. I have twice now attempted to upgrade to 2004 on this machine, and each time the installation was so faulty and unstable that I was forced to roll back. The first was a month ago, when I put the machine in the Release Preview ring because the upcoming version looked stable on other machines I had it on. Wrong. After rolling back I took the machine out of Insider RP, put it on a 35-day hold and waited for the formal release. Microsoft wasn't blocking it, and there had been a lot of talk about late improvements and bug fixes to 2004, so I let it install again day before yesterday. It was the same catastrophe, with incomplete system loads, frozen desktops, clicked apps that opened a blank frame but never figured out how to put anything in it, and Bluetooth problems (mouse and keyboard). Event Viewer reported a blizzard of error states, most of them DCOM related. Server X (long alphanumeric name with a few hyphens) could not connect to something else before timing out, some apps didn't have authorization to use Server Y, and so forth. I absolutely do not expect Microsoft to be able to help me with this, so I will just keep it on 1909 while I try to learn enough about permissions and authorizations to see if I can fix it myself. If that never happens, I guess I am up for a Reset experience, or maybe even a clean install of 2004.

Leave a Reply