Windows 10 Version 20H2 Inches Towards Completion

Posted on July 14, 2020 by Paul Thurrott in Windows 10 with 12 Comments

Yes, I know it seems early, but today’s release of a cumulative update for Windows 10 version 20H2 indicates that this release is nearly complete.

Windows 10 version 20H2 is currently testing in the Windows Insider Beta channel, or what used to be called the Slow ring. Today, Microsoft released build 19042.388 (KB4565503) to testers, describing it as a cumulative update that only includes quality improvements.

Those improvements include:

  • A fix for an issue that might prevent users from using PowerShell to change the system locale on Server Core platforms.
  • A fix for an issue that might cause certain games and applications to have visual distortion when resizing in windowed mode or switching from full screen to window mode.
  • A fix for an issue that causes lsass.exe to fail with the following error message, “A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000008. The machine must now be restarted.”
  • A fix for an issue that might prevent some applications from printing documents that contain graphics or large files after installing Windows Updates released June 9, 2020.
  • A fix for an issue that might prevent users from connecting to OneDrive using the OneDrive app. This issue occurs on some older devices or on devices that have older apps, which use legacy file system filter drivers. As a result, this might prevent these devices from downloading new files or opening previously synced or downloaded files.

Additionally, this cumulative update includes security updates to the Microsoft Scripting Engine, Windows App Platform and Frameworks, the Microsoft Store, Windows Graphics, Windows Input and Composition, Windows Media, Windows Shell, Windows Fundamentals, Windows Management, Windows Kernel, Windows Hybrid Cloud Networking, Windows Storage and Filesystems, Windows Update Stack, Windows MSXML, Windows File Server and Clustering, Windows Remote Desktop, Internet Explorer, Microsoft Edge Legacy, and the Microsoft JET Database Engine.

Join the discussion!


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

Comments (12)

12 responses to “Windows 10 Version 20H2 Inches Towards Completion”

  1. bart

    After the whole fiasco with the 2004 update, I am stunned at the pace the Beta channel is receiving updates. They might as well still call it Slow ring. Or Slow channel for all I care. Proves Paul's point this whole re-naming is only that.

  2. anderb

    Sounds familiar. Wasn't 2004 "done" last November?

  3. ghostrider

    Does anyone even care anymore? It'll just be another buggy update.

    • Paul Thurrott

      Yeah, I care very much.
      • pesos

        In reply to paul-thurrott:

        Paul is far from alone in the caring lol. Many of us work with this stuff for a living. 2004 Enterprise was a fantastic release - release bumps and all - and the 20h2 evolution will be one we ride out for a good long while.

    • blue77star

      In reply to ghostrider:

      To be honest I did not have any problems with Windows 10 since 1903. Everything prior that was a miss. I know a lot of people still have issues and with the pace Microsoft is moving, it is a difficult to make all variations of PC hardware happy. We are not talking only about OEM but ton of custom built computers. Maybe Microsoft should slow down giving us more meaningful updates.

  4. winner

    By this time next year, the rings that became channels are due to transform to lanes.

    Also don't expect those UI consistency improvements we've been waiting for since we were in diapers.

    Meanwhile, where else can we put ads, and which clipboards can we spy on to send back to the mother ship?

  5. michael_goff

    Do you think this one will actually ship on time? Or will it be another case of a pile of "stopping bugs" that didn't get announced throughout the process?

  6. tboggs13

    I think the definition of &"completion" has changed over the years. My definition is it isn't complete until it can run on every Surface device I use. So far, 20H1 hasn't even started, how can 20H2 be complete.
  7. blue77star

    I already moved to this build 19042.388. Works fell. It is basically finalized, it will keep getting patched as part of Tuesday patch until Microsoft is ready to make it public.

  8. epguy40

    20H2 released to the RP channel this Sept. as build 19042.508 (with the defrag bugfix included)