I'm pretty sure I know the answer to this question because it would have been posted already, but just to get it off my mind, I'll ask.
Is there any way to tell which of the numerous block issues is affecting the hold on any particular machine?
I don't think there is any way of telling which "Block" is in effect or if you are just being delayed because of roll out plan.
Very frustrating.
Would be nice if MS could invest a little to actually tell us.
Of course we probably make up such a small portion of their overall world wide install base they really can't be bothered.
If you try to install 2004 using the update assistant, and there is a problem with some files/drivers, it will stop at the problem and tell you what the problem is. Then it recovers the previous version and you can correct the problem and try again. I had to do this 4 times before the installation completed. There were three drivers that 2004 didn't like, so I deleted them (rename them if you are nervous about deleting them.)
I've now installed it on four computers; two laptops and two desktops. Only one had no problem drivers.
My title is what my old granny used to tell us children when we said we couldn't do something!!
bob Frost
I used to be in the Slow lane and installed this version on my AMD HP Envy 2 in 1 on the 12/12/19, everything went ok and not had any real problems, any minor glitches were easy fixes or were just one-offs.
A few days ago it was offered on my Acer desktop so I downloaded and installed it. Oh my, I couldn't do a thing on the machine, everything would just freeze or if it did load it took so long, click on the edge browser button and wait and wait and wait, if it did arrive or when it did it was just a white blank page, if or when it finally showed anything you couldn't go anywhere it was just frozen and if you tried to bring the Task bar up to end task that would just be a white box and frozen.
Put up with it for a couple of days and I've reverted back and told updates to delay for 35 days to see how things go.
There is still my Asus laptop to do plus hubbies desktop which is the same make and model as mine and a Toshiba laptop.
I use the Known Issues list that Microsoft publishes -
https://docs.microsoft.com/en-us/win...indows-10-2004
On one of our laptops, the Conexant drivers are older than the versions listed in the KI, so that's likely a blocking factor for that system.
However, I ran Upgrade Assistant and it told me it was good to go.
I actually updated from the ISO, and had no issues with the Conexant device.
There were issues with the Catalog Database (ESENT errors) and Defrag thinking a 1 TB external HDD was an SSD (both mentioned earlier).
I rolled back to 1909 after a couple days testing.
Source: https://docs.microsoft.com/en-us/win...indows-10-2004Current status as of June 9, 2020
Windows 10, version 2004 is available for users with devices running Windows 10, versions 1903 and 1909 who manually seek to “Check for updates” via Windows Update. We are continuing our measured approach on initial availability, as we listen, learn, and adjust. Today we are increasing the number of devices that will be offered the May Update. The recommended servicing status is Semi-Annual Channel.
Geez Microsoft, don't tease us to death
It's now available in Bora Bora and parts of Antarctica.Source: https://docs.microsoft.com/en-us/win...indows-10-2004
Geez Microsoft, don't tease us to death
I think most early adopters (seekers) use the ISO, so they probably don't care what the blocks are.
They'll roll the dice and see what happens.
Windows Update said it was blocked, and Upgrade Assistant said it was good to go, on one of our systems.
As long as a disk image is made prior to the dice roll, it's not a bad strategy.
I use the KI to give me an idea where the build is, at any given point in time.
We're not in any hurry.
Quote
