Windows 10 2004 roll out


I have a couple of questions:

My work computer clearly state that I cannot get the update at this time, due to a blocker. That is great, clear communication. Could be more detailed, but ok. Looking at the blocking list, I sort of guess the Connexant audit chip is the issue. So HP needs to deliver a newer driver.

Now my home computer and my Surface Pro 4, when I check Windows Update it tells me nothing!

Does that mean it is OK to manually install the update? Or is the blocking message just failed to display? Or are they just not making the feature update available to me at this time because my machines is not yet on the targetted list / group?

This to me is where it breaks down. Either make the thing available when you say it is available. Or be clear that it is available, but they have not specifically targetted your computer yet for an upgrade. Or simply move away from all this and state, we will automatically upgrade computers. If you download the manual tools, we will at the time of install apply compatibility / know issue checks before allowing you to proceed. This will be an online only experience going forward.

Oi Microsoft, can you please just communicate!

Comments (21)

21 responses to “Windows 10 2004 roll out”

  1. madthinus

    The picture has not posted :-(

  2. anderb

    I haven't been offered the update yet on my vanilla home build box but I did notice MS changed the update text from the very fake news "your device is not ready for it" to the more accurate "when it is ready for your device".

    • StevenLayton

      In reply to anderb: "Fake news"? Not heard that term on this site before! But you're right, the terminology was wrong.

    • anderb

      In reply to anderb:

      So according to Microsoft, the 2004 update is blocked on my PC because I'm using Intel integrated graphics. I guess it's my fault for selecting such an obscure graphics platform!

      Variable refresh rate not working as expected on devices with Intel iGPU

      Intel and Microsoft have found incompatibility issues when using a monitor with Variable refresh rate (VRR) plugged into an Intel integrated graphics processing unit (iGPU) display adapter and Windows 10, version 2004 (the Windows 10 May 2020 Update). Enabling VRR on affected devices will not enable the VRR for games using Direct X 9.

      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.

  3. epguy40

    well well,

    looks like MS "patch Lady" Susan recently had one of her machines that got automatically upgraded to v2004 without her consent or approval:

  4. epguy40

    from Softpedia news - Windows 10 Version 2004 Released for More Users

    And MS has lifted the 2004 upgrade block for those using old nVidia graphics devices & old nVidia display drivers on Aug. 13:

    "Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows Server, version 2004 is offered."

  5. jimchamplin

    To be fair, I did a fresh install on my Thinkpad last night after my annual Linux check-in and didn't even realize I'd installed 1909! I honestly couldn't tell a difference. If you're expecting a dramatic improvement in performance, or finding some crazy-go-nuts new feature, you'll be disappointed. Just sit tight, or if you really want it, grab an ISO and do it the old-fashioned way :D

  6. epguy40

    looks like the Win10 v2004 version is still not being rolled out to some MS Surface users, including Ms. Foley of ZDNet:

    "Update (July 7) Still no release of the block for Windows 10 2004 on my Surface Laptop 3 or other blocked Surface devices, according to readers I’m hearing from. I’ve asked Microsoft twice more what’s going on, given this was supposed to be unblocked within 48 hours as of June 29. Still no word back."

  7. winner

    Microsoft communication training for new employees. When asked a question or to comment on a Microsoft solution or situation, choose one of:

    a - obfuscate, answer with many words but little meaning

    b - answer "We don't have anything to say about that at this time"

    c - Don't address the item at all in your communication

    Under no circumstances should you provide a clear concise answer.

  8. navarac

    In answer to the last sentence, they don't and never have been capable of communicating! Don't ask for the impossible :)

  9. epguy40

    this guy got the May 2020 (v2004) update on his Surface Pro 4 device:

    • epguy40

      In reply to epguy40:

      also saw this on Bleeping Computer recently - Microsoft fixed bug blocking Windows 10 2004 on Surface devices

    • Dave P

      In reply to epguy40:

      I just bought a used Surface 3 (!) with Windows 10 Pro and 4GB RAM. I am running the May 2020 Update with no problems. :)

  10. madthinus

    I moved this weekend using the upgrade assistant to 2004. No real issue to report, worked as expected.

    The Windows 10 as a service model to me has always been wrong headed and the twice yearly update even more so.

    Although they have given some control over the process, it is no where near to where I think it should be. The process is still slow on a mechanical drive and running in the back ground even more so. Plus it is still happening to many times unexpectedly. And lastly, having updated an older computer recently, it is still a dumb process. It wanted to update 1709 to the latest cumulative update and download 1909 at the same time, resulting in both failing. So yeah, lots more to fix in the Windows update process.

      • hastin

        In reply to paul-thurrott:

        I will say, the experience upgrading a new-to-me Surface Book 2 was pretty easy. It was running 1803 (MS Surface recovery image), and I got a page during OOBE that there was a new feature update (with option to install it). After setup, it downloaded only the feature update (1909) and not other patches, and installed it at the first reboot.

  11. epguy40

    There's a recent report from this ComputerWorld page saying that some Win10 PCs are being upgraded to the version 2004 update without user consent:

    I wonder what Mr. Thurrott's opinion or reaction to this recent Computerworld article would be :)

    • Paul Thurrott

      I've never heard of such a thing myself. Certainly, there have been times in the past where Microsoft pushed updates without consent, and other times where this has happened by mistake.
    • miamimauler

      In reply to epguy40:

      The article writer in Woody Leonhard states the following,

      "Some are convinced the forced upgrade is intentional. Others – including me – think these particular forced upgrades occur because of a bug"

      These stories have yet to be confirmed but for the sake of the discussion let's assume the reports are accurate.

      I'm curious what your view is epguy40. Do you believe it be be a deliberate action by MS or do you believe it is a system bug?

      • epguy40

        In reply to miamimauler:

        it's more of a "bug" than deliberate as only very few people had been inadvertently upgraded to v2004 w/out consent, miamimauler

        btw, there's this ZDNet article saying that MS has lifted the 2004 upgrade block for some MS surface devices (or was supposed to remove the upgrade block but a few people who have surface devices are still unable to upgrade to 2004):

  12. jimchamplin

    Just use the media creation tool and install it from USB. It doesn't really care what you're installing on. I'm not sure it even checks on a clean install!

  13. epguy40

    ehh, I may skip the 2004 release on some of my PCs and just wait for 20H2 to come out next month since 20H2 is almost ready for public release and will upgrade to that one instead