Windows 10 2004 build

[Sky-Knight]

@britechguy Yes, but that doesn't apply in this case. This is an Asus Vivobook 15 F512D. It has an identical twin behind me on the floor, and 5 other siblings in use by a customer that's geographically two blocks from here. That proximity lets me experiment a bit, because I'm always on hand to sort things out cheaply.

Anyway, the twin is on 2004, after displaying the availability of the update. So this platform shouldn't be excluded, unless Microsoft is excluding things based on more than simply the hardware profile.

The unit in question is manually updating via USB 2004 install media, and setup.exe currently.

 

[Diggs]

Another thing I'm seeing, 2004 isn't available on this unit after upgrade to 1909. So it seems to reject further upgrading for some time too.

From what I understand Microsoft was preventing some machines from upgrading to 2004 until they had time to work out some issues particular to those machines.

 

[Sky-Knight]

From what I understand Microsoft was preventing some machines from upgrading to 2004 until they had time to work out some issues particular to those machines.

Yes but see above, that doesn't apply on this hardware platform. I have a 2nd.

I think there's an additional delay, which would make some sense as you have the ability to roll back for a month. It probably would have popped up if I waited another month to clear the rollback period for 1909.

 

[britechguy]

Well, and it's well known (or should be, by now) that even on hardware deemed ready, the roll out occurs in cohorts. Not every HP 15 series like the three I have is going to get the update even presented as available at the same time, necessarily.

Telemetry is constantly monitored, and closely for machines where, as @Diggs has put it, "some issues particular to those machines," were identified. And by machines, I mean with a given hardware configuration known to Microsoft. I have even seen instances of machines that had been exhibiting the Download and install link revert to "not quite ready" state when late breaking issues with the specific hardware came to light later during a roll out period. Not often, mind you, but it has occurred.

But once I see a single piece of hardware go to "ready" state, I expect all others with that configuration to do so within a few weeks in most cases. I also don't hesitate to upgrade using the ISO file method on those that have not yet gone to "ready" state if I know for certain that they are the hardware twin of another machine that has and where the update worked without issue.

 

[GTP]

I manually run the download and install link but if it's not there, I skip all the aforementioned BS and just run the 2004 .iso on client machines, even some older systems that are still on Windows 7.
Not one issue so far.

 

[fincoder]

Yes but see above, that doesn't apply on this hardware platform. I have a 2nd.

Certain software and driver versions can also delay the update.

 

[Sky-Knight]

Certain software and driver versions can also delay the update.

I'm aware, but once again this other machine is a TWIN. Same image, same update level. Well, except one was on 2004 already and the other hadn't gotten there yet. But started their lives at 1903, the first I updated to 1909 a few months ago, and subsequently had the option for 2004. This one, was left on 1903 on purpose.

 

[Galdorf]

Something has happened with latest updates and 2004 for some reason it takes forever to boot and shutdown have been getting machines in for same symptoms need to track the kb doing this takes almost 10 mins to boot on my personal gaming system which use to boot in 6 secs.