Windows 10 2004 build

[Porthos]

This is definitely a "big" feature update. My systems still have HDDs in them, and it took over 2 hours to install on all of them. This does not include very much download time, as I used the Version 2004 ISO, mounted as a virtual DVD, to perform the update. There was some downloading of updates that were made after the ISO had been generated.

That is correct. it does take time on spinner drives. I have seen it take longer as well. The 2004 upgrade ids the big one for the year. 2009 will be very small like a monthly update.

 

[britechguy]

Well, even in the category of "big" feature updates, some have been bigger than others. This one is "bigger than the median" as far as time required not only for the install, but on first login afterward to put on the finishing touches.

The next one will be very much like Version 1909 was, minimal.

 

[fincoder]

It's slower doing in-place upgrades using the ISO, rather than via Windows Update. By the time Windows Update says it's ready to install, it has already downloaded it (or partially). The updates during the ISO-based upgrade take a long time, not sure what it actually does but it might be downloading most of the ISO again!

For ISO-based upgrades I often change to the option of no updates to speed it up and haven't had an issue. Even when there's no internet connection this speeds up the upgrade a little (maybe it retries the internet connection for a while before giving up).

But anyway, AMD APU plus HDD equals a slow experience doing pretty much anything...

 

[britechguy]

It's slower doing in-place upgrades using the ISO, rather than via Windows Update. By the time Windows Update says it's ready to install, it has already downloaded it (or partially).

Well, our experiences differ. When I have used either the Update Assistant or the Download and install link in Windows Update that kicks off the download of the whole shebang, and that takes forever, often as much time or more than the actual install phase itself.

I agree that when using the ISO method declining to download updates speeds things up considerably, and I often do that since Windows Update itself will take care of things afterward if it's not done during the upgrade.

 

[GTP]

I use several methods, all of which seem to work flawlessly. I either copy the .iso to the desktop and run it from there as an inplace upgrade, backup and reformat then run setup from my IODD (preferred) or start off the update from Windows Update.
On a good fast system it usually takes about 20 mins? but mileages vary with different hardware.
I leave it connected to the inernet all the while too.

I dont care how long it takes, it could take all day if it wants. I just want it to work afterwards, which it does everytime.

On my own (and a couple of client systems) that have been modified with NTLite it took about 3 mins? Remained disconnected from the internet while it ran. Applied several updates afterward when reconnected.
Didn't change anything cosmetically as far as I can tell.

 

[Galdorf]

My personal machine tried to install 2004 from 1909 without my permission i have set settings that prevent feature updates from installing i still think 2004 is still not ready with some issues still not resolved.
Looks like they are rolling out 2004 as some of my customers have said it just started installing on its own from 1909.

 

[Porthos]

Looks like they are rolling out 2004 as some of my customers have said it just started installing on its own from 1909.

Have not seen it with 1909 but several from 1903.

 

[britechguy]

I, too, have not seen any automatic updating from 1909, and even 1903, though I can believe that 1809 and 1903 will soon start triggering automatic updates if the end user does not apply the latest feature update.

At this point you have plenty of time where you can wait if you wish to, but eventually as the version you're on becomes, or gets close to becoming, unsupported Windows Update will trigger an automatic update then.

I expect a wave of automatic updates from 1809 in the coming months for those who've not applied any later feature update themselves. And at this point that would be a jump straight to Version 2004.

 

[Galdorf]

I have double checked my gaming pc indeed it is 1909 2004 is on hold after it triggered the update i have it set so if a feature update tries to install it notifies me and will not install unless i give it permission.

Also there seems to be an issue with 2004 and external hard drives i keep running into the only fix i found was to roll back to 1909.

It can also be fixed by doing a fresh install of 2004 seems something gets messed up during the upgrade process.

https://www.askwoody.com/forums/topic/reports-of-win10-1909-users-getting-pushed-onto-version-2004/

 

[fincoder]

i have set settings that prevent feature updates from installing

What settings? Using the deferral feature, or undocumented registry tweaks?

 

[Galdorf]

What settings? Using the deferral feature, or undocumented registry tweaks?

Registry tweaks and policies a combo seems to work well on pro don`t think it can work on home though.

 

[GTP]

Also there seems to be an issue with 2004 and external hard drives i keep running into the only fix i found was to roll back to 1909

All smiles here with upgrades to 2004.
Not a single issue with either residential or business.

 

[Galdorf]

On a few upgrades all customers programs were removed it only kept the data looked at program files and program files (x86) both were default fresh install.

Took hours to re-install all the software again it was only a few but there are reports of this happening to other people even while i was fixing windows updates on a customer machine after downloading all updates it forced update to 2004 all programs were removed but it kept the data.

 

[britechguy]

Well, other than my stupid self-inflicted overheating situation on one machine due to not keeping up with my hardware cleaning protocol, I've had not a single issue with 2004 yet, either.

Even the machine that overheated during the initial update, and which I restored to 1909 and reapplied, is working perfectly swimmingly now.

I just took in a client machine this morning that I will update as part of the "routine service" if it's showing the Download and install link in the Windows Update pane.

Even the reports here (and links to others where issues are reported) appear to be largely isolated incidents. When you've got hundreds of millions of machines being updated, regardless of what OS is involved, there will always be a few (thousand, probably) out there that will burp as part of that process. The law of averages at work . . .

 

[Sky-Knight]

Yep, and those problems are happening to me in a few isolated cases now, because I have machines updating during MONSOON.

And it's not the update's fault the power grid can't maintain a solid ground because of a storm.

This was last night: (Power Outage Map, Purple pins are 1000+ homes without service)

And yet here I sit, with server 2012 R2 servers that auto-installed KB4578013 LAST NIGHT, and they're fine. But I have a few workstations that needed a reboot to recollect their sanity this morning. But if the updates had gone south, I'd still not be blaming Microsoft. Not with this much dirty power flying around. You can UPS all the things, and still get bad voltage in these conditions.

 

[Galdorf]

Finally i found an open source tool to do manual updates

https://www.bleepingcomputer.com/ne...-updates-manually-with-this-open-source-tool/

And 2009 is almost ready for release even though 2004 still has not hit many users yet.

 

[Sky-Knight]

Tangentially related note, I'm starting to see 1903 machines forcibly update to 1909 now.

So it seems that Windows 10 will update itself once it gets within 90 days of the support termination date.

 

[britechguy]

Tangentially related note, I'm starting to see 1903 machines forcibly update to 1909 now.

So it seems that Windows 10 will update itself once it gets within 90 days of the support termination date.

I had always heard that this was the case, but have never left a machine go un-updated for long enough to witness it. It makes perfect sense, too, as you don't want any machine running an unsupported version of Windows, and old versions of Windows 10 count as being out of support.

 

[Sky-Knight]

@britechguy Exactly, which is precisely why I left these laptops on 1903, I wanted to confirm those suspicions.

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.

 

[britechguy]

I know of a number of people on 1909 where Settings, Update & Security, Windows Update Pane is still saying they're not quite ready. I fully expect that there will be a large number of machines that go directly from 1909 to 20H2 when all is said and done.

My own laptops only very recently changed status to ready, at which point I updated all of 'em.