Win10 version 2004 is here but… surprise!

Topic

New Reply

Win10 version 2004 has been officially released. Microsoft’s been testing it since December. We’ve been getting official notices about 2004’s status f
[See the full post at: Win10 version 2004 is here but… surprise!]

6 users thanked author for this post.

GCG1000, Elly, abbodi86, geekdom, GreatAndPowerfulTech

Reply | Quote

Replies

Despite the issues listed there, I intend to upgrade when it comes out on WU (which is normally not what I do) because the windows store is broken and nothing I do fixes it. None of the issues there are relevant to my system since my PC lacks bluetooth and my nvidia drivers were updated today.

Reply | Quote

Well, at 1530 IO gave it a shot on my laptop.  And got bupkis.  It just said I was up to date.

Reply | Quote

I installed it on an old System 76 Meerkat I have laying around. Looks like the build number is 19041.264.

 

Red Ruffnsore

Reply | Quote

Using Windows Update? MCT? downloaded ISO?

Reply | Quote

[Mr. Natural]

MCT as mention in Susan’s earlier post. I stumbled across the new MCT just as it was being released.

Red Ruffnsore

• This reply was modified 4 years, 11 months ago by Mr. Natural.

Reply | Quote

Thanks Woody. A nice list of bugs there. In fact, the sort of list of known issues that you’d be given when a beta version was issued, not the final release version.

Reply | Quote

Apparently you can no longer defer feature updates in 2004 according to this person on reddit.

 

https://www.reddit.com/r/Windows10/comments/grqfjj/has_ms_removed_option_to_defer_feature_updates/

1 user thanked author for this post.

cyberSAR

Reply | Quote

Saw that here but haven’t had much time to play with it.

Reply | Quote

AWU,

It’s available in the Group Policy Editor.
HTH 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

5 users thanked author for this post.

Elly, lanceboil, R, CADesertRat, woody

Reply | Quote

Point well taken, but the question is… does the Policy work?

MS has changed and deprecated so many Windows Update policies over the years it’s very hard to keep track. Even tho the policies are there, they don’t do what they used to do — or don’t do anything at all.

Reply | Quote

So the same ‘bug’ as with the introduction of 1903 is back…?

Reply | Quote

Adding the registry keys (which represent the missing deferral UI options) manually still works

2 users thanked author for this post.

Elly, woody

Reply | Quote

But it also removed my setting for delaying quality updates. That would mean I have to go in each month to delay them rather than going with a set deferral period.

Reply | Quote

I upgraded using the MCT tool. The upgrade Assistant didn’t apear to be working and it did not offer it when checking for updates.

IT installed with no problems and i am on version 19041.264

 

Barry
Windows 11 v23H2

Reply | Quote

[bbearren]

Now running Windows 10 Pro Version 2004 (OS Build 19041.264). Used the MCT to create USB installation media, signed in as a member of the Administrators group and ran Setup.exe from there. Those aggravating Special Folders reappeared, so I used Process Hacker to run regedit as trusted installer and imported my .reg file that strips them from the registry, then deleted the empty folders for User Profiles. File Explorer is clean once more, and its Search box works fine; one click places the cursor in the text box. It only found one *.tmp file, but I had run a thorough cleanup before the update.

I used extended cleanmgr to get rid of Windows.old and the other installation detritous. My next move wiill be to update WinRE, then update that to TBWinRE.

Everything is running nominal, no hiccups, no issues.  As for the list in the OP, I don’t have anything in my system that might be affected.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

• This reply was modified 4 years, 11 months ago by bbearren. Reason: added link

Reply | Quote

Got the Windows Recovery Environment updated, then upgraded that to TBWinRE, and all of that went quite smoothly.

Then I went to All settings > Update & Security > Recovery > Advanced startup and clicked the Restart now button.  The system rebooted into the Windows Recovery Environment with Image for Windows front and center, as well as the usual recovery options.

All systems nominal, no hiccups, no issues.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

woody

Reply | Quote

When I was satisfied with the A side of my dual boot, I rebooted over to the B side.  The configuration of that installation is well outside a Microsoft supported installation.  I was anticipating some hiccups there, and I was not disappointed.

It choked on the Windows Update route (it was queued up ready for download).  It took longer, and couldn’t quite get there.  I did get to a sign in screen, had the correct background but a generic avatar.  Getting things ready took a looooooooong time.  It kicked StartIsBack++ (the A side didn’t even notice), I reinstalled that and tried a reboot.  It got worse from there.  I finally decided to go the MCT-USB route and restored my drive images for 1909.

Updating through the USB worked, but took about four times as long as the A side.  The Admin account takes about 20 minutes to load.  The two standard user accounts are quite snappy.  All settings are in place, only StartIsBack++ needed attention.  Puzzling through the long signin time for the the Admin account is gonna give me something to do for a while.

The most interesting part of that adventure is that Windows 7/8/8.1 would not have let me keep my apps and settings.  All three would have only allowed a clean install.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Considering the way that the standard user accounts were behaving normally and briskly, I dug into the registry, did some editing and also realized that my Admin account was corrupted.

Next I enabled the default Administrator account, signed into it, and deleted the corrupted Admin account.  I rebooted, signed back into the Administrator account and created a new Admin account, making it a member of the Administrators group, which is where I am now, typing this.

After deleting/creating the Admin account and signing back into it, I disabled the default Administrator account.  I’ve done a few reboots from A to B in my dual boot, and everything is copacetic once again.  I’m not sure when or how the Admin account got corrupted, I rarely sign into that account other than when required by limitations like updating from 1909 to 2004.

The whodoos with the first attempt at the online update may have contributed to the corruption, but all is well once more.

Once again, there is simply no substitute for having a recent drive image at the ready.  Since the second attempt was successful but exceedingly drawn out, the Admin profile was likely already corrupt, and not the fault of the update; the update just brought it to light.

It’s all good now, though, and everything is running fine.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

No way I am ever gonna seek out a upgrade from Microsoft on the day its available. Definitely not when there is a laundry list of potential issues. Seeker = sucker as far as I am concerned.

Reply | Quote

Yep, this is for those that like to play and definitely not for those on production systems.

Red Ruffnsore

Reply | Quote

Finally installed more memory so need to update my desk top. It’s currently at version 1803 and windows update is only offering 1809.  Can I go straight to version 1903 or 1909 or do these updates build on one another?

 

thanks, Bill

Reply | Quote

Woody recommends going to v1909.
You can go directly to either, don’t have to make any stops in between.

1 user thanked author for this post.

woody

Reply | Quote

I assume (hope…) that deferral settings are respected this time too…? I am at 1903 and for sure don’t want to be forced to update to a buggy 2004. And what about this post regarding in 2004 the option to defer feature updates? If that’s not a bug and intended, 1909 will be the last version of Windows that will be used here.

Reply | Quote

Make sure you read my Computerworld article.

As long as 1909 isn’t near end of life, the only way you’ll get moved to 2004 is if you quite deliberately click Download and install.

1 user thanked author for this post.

R

Reply | Quote

[RetiredGeek]

Hey Y’all,

Got my test system imaged and went searching. Couldn’t get the update all morning but after lunch it showed up. Tried to install but it got after the reboot at 91% for about 1.5 hours. I had to power off to break out of it. When I restarted Windows duly reverted me to 1909.

Next up, download the MCT took about 19 minutes to get the USB drive loaded.

Start the install process and wait…took 1 hour 8 minutes. Everything seems to be working honky dory so far. Messed around with updating VSCode and played with some PowerShell and all is good.

Here’s a little oddity. This is the first time I used MCT to update my test machine and it didn’t record the update in history!

HTH 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

• This reply was modified 4 years, 11 months ago by RetiredGeek.
• This reply was modified 4 years, 11 months ago by RetiredGeek.
• This reply was modified 4 years, 11 months ago by RetiredGeek.

Reply | Quote

Of course I did, actually I set my systems to 365 days deferral for feature updates, 1903 works ok for me. The differences between the versions are near zero lately. Only new features seem to be bugs :-/

 

Greetings & thanks,

Ron.

Reply | Quote

Hey Y’all,

My bad on the update not showing. Actually what windows records is the version being updated from the values in the registry do not show the version updated to! I’m going to change my script to capture the Date Updated for a more realistic output.

HTH 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

1 user thanked author for this post.

Elly

Reply | Quote

Hey Y’all,

Ok, I updated my Get-WinVer PowerShell program to better reflect what the registry is reporting. I also fixed the problem with narrow scrollbars if you get enough entries in the update tabs.

Here’s the updated program: Get-WinVer
.zip MD5 Hash: 98C15C3D34199EDF51DE93D3AA8E27BA
.ps1 MD5 Hash: 3B150790F8690E1E729D8281267703CD

HTH 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

They didn’t mention the update cleanup bug or the defragment status bug in “Optimize Drives”
surprise 😀

Reply | Quote

Hardware driver issues shouldn’t happen..unless of course there are alterior motives behind the issues that have been introduced just prior to RTM and only just listed during release.

Windows - commercial by definition and now function...

Reply | Quote

I’m affected by the Conexant audio issues on both my work and personal laptops (both HP). So I’ll have to hold off on this one for a while.

Reply | Quote

So what happens if after checking its not listed on Windows Update? Your PC isnt compatible?

Reply | Quote

Be sure Metered connections is OFF, turn off Pause and/or deferrals, turn off any third-party update blockers, and wait until it’s offered.

Reply | Quote

Yea done all that and still not there.

Reply | Quote

You should be on 1903, 1909 to receive 2004.

You can always download MCT tool, download 2004 ISO and run the updates. No need to wait for Microsoft.

Reply | Quote

It may take a few weeks.  The Microsoft blog post states “You may not see Download and install on your device as we are slowly throttling up this availability over the coming weeks”

Reply | Quote

Now available via WSUS for your test group.

Red Ruffnsore

Reply | Quote

Tried using the update assistant on a couple home PCs. One computer worked fine. The other (on 1909 Pro) boot looped 3 times and went to “undoing changes”. Don’t feel like chasing down the problem as this is also my WFH PC. Guess I’m stick with 1909 for a while.

Reply | Quote

FYI – admins…

RSAT will need to be re-installed as has been the case with every other version upgrade.  (sigh)  🙁

Red Ruffnsore

1 user thanked author for this post.

NetDef

Reply | Quote

Heidoc.net has added the 2004 ISO.

Reply | Quote

[EP]

Looks like Microsoft’s own Surface Pro devices are not getting the version 2004 update yet

comment from Paul Thurrott’s site about the May 2020 update:
https://www.thurrott.com/windows/windows-10/235690/windows-10-version-2004-is-now-available

Surface Pro 7 has a compatibility blocker.

Edit – I think it’s noted here for known issues for 2004:

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004

those using MS Surface Pro or other MS Surface devices will definitely have to wait at least one more month to update to version 2004

• This reply was modified 4 years, 11 months ago by EP.

1 user thanked author for this post.

woody

Reply | Quote

Good grief. Didn’t something similar happen to 1909?

‘Course MS has been beta testing Win10 2004 on Surface Pro 7 laptops for, what, five months now?

Barb Bowman also reports blocks on the Surface Laptop 3 and the Surface Pro X.

https://twitter.com/barbbowman/status/1266099774991863815

UPDATE: SL3 block is acknowledged here:

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004#421msgdesc

Surface Pro X problem described here:

https://answers.microsoft.com/en-us/surface/forum/all/cannot-upgrade-surface-pro-x-to-windows-10-version/5e2c62df-89b7-4fc0-8e01-04df443e81e1

Reply | Quote

Hey Y’all,

Has anyone seen the KB# for this update? The only one I can find is 4556803 and it still references Insider-Build. 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

WSUS does not show a KB reference for the 2004 upgrade. It’s listed as “Feature update to Windows 10, 2004”. If I click the link associated with 2004 in WSUS it takes me to the Windows 10 update history page which still has no references to 2004.

Doesn’t appear to be in the Windows Update Catalog yet.

Red Ruffnsore

1 user thanked author for this post.

RetiredGeek

Reply | Quote

Microsoft Catalog never show or list Windows 10 Feature Updates

2 users thanked author for this post.

PKCano, Mr. Natural

Reply | Quote

D’OH! I knew that… heh heh…..I was testing you. Good job, you passed! (running away)

Red Ruffnsore

2 users thanked author for this post.

woody, PKCano

Reply | Quote

Reading this list of bugs, I can’t help but wonder, what are they changing in the Core OS between versions and especially this time to cause these issues? It’s certainly not adding frivolous superficial stuff or moving Cortana around that create those low level problems? What do we get in exchange? Do they break things while improving security and we just don’t realize what they do?

From the point of view of a user, you don’t care that the programmers have very good technical reasons to move to this or that technology or model under the hood or for handling the search tool. You want things that worked to continue working and you don’t want things like your search not working because something on the Internet happened. You will tolerate bugs on new features, but those specific bugs for Win 2004 seems to be regressions when they are not accompanied by proper explanations of what you get at the normal or a bit more sophisticated user level (i.e. when Windows tells you it updates, not if you have to look yourself on a web site to find out the changes).

So, you, normal casual home user, you get offered a “production ready” update that you are invited to download if you like to try new stuff, but you don’t really understand what you get and what you loose or why. Microsoft doesn’t tell you, but you don’t really a get a production ready version. Nobody calls it beta although those issues look more like they belong in a beta. It seems to me that the mostly security only model of Windows 7 generated much less issues of this sort. If the user gets something better more frequently at the low level from these type of bugs, maybe he/she would like to know it.

Meanwhile, with Windows 10 as a service, I still don’t have an easy included sandboxing feature to put my favorite browser in, they deprecated the imaging feature and they removed support for ReFS that protects my mirrored data from the Pro and Home version. It is not always progress at the OS level for these updates. I’m still waiting for that killer feature that feature updates bring in exchange for the trouble they bring.

 

1 user thanked author for this post.

ryegrass

Reply | Quote

Win10 version 2004 is here but surprise – there’s a recent Forbes article saying not to “Press Windows 10 2004 ‘Update Now’ Button”

https://www.forbes.com/sites/daveywinder/2020/05/28/dont-press-windows-10-2004-update-now-button-microsoft-warns-some-users-may2020-windows10-update-warning/

wahaha 🙂

Reply | Quote

Pshaw. I’m surprised that didn’t make it into the headline somehow. Microsoft warns hundreds of millions of customers not to press a button that doesn’t do anything anyway…

Reply | Quote

My Dell Latitude E5420 (circa early 2011) got the push today, I just RDP’d into it and clicked download and install.  I’ll see how that goes.

Nothing on my NAS yet.  It has the same motherboard/CPU as my desktop, so I don’t anticipate any difficulties.  It’s a standard installation of Windows 10 upgraded over Windows 7 Pro.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Sorry but, all this hype for what?  To say you have Windows 2004?

Last I looked Windows 10 ver 1909 is good until May 11, 2021 !

Yes 2021!

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Tex265 wrote:

Sorry but, all this hype for what?  To say you have Windows 2004?

What hype?

It has many minor improvements:

the latest Windows 10 feature update has a lot to offer

All the security features added in the Windows 10 May 2020 update

1 user thanked author for this post.

AlexEiffel

Reply | Quote

b wrote:

It has many minor improvements

Most everyday things that we do with apps that run on top of Windows will be pretty much the same – other than they will still work.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

2 users thanked author for this post.

ryegrass, woody

Reply | Quote

I’m skeptical, too.

I still don’t see any compelling reason to upgrade – and I’ve been running 2004 on test machines forever.

Reply | Quote

Tex265 wrote:

Most everyday things that we do with apps that run on top of Windows will be pretty much the same – other than they will still work.

Isn’t that what everyone wants from an upgrade? 😕

Reply | Quote

Woody has mentioned this before but there are generally 2 types of participants here. The home computer user and then there are those in the corporate environment. Those that manage systems in a corporate environment need to be on top on new things as they arrive in order to be educated and prevent future disasters from occurring.

There is absolutely no need to upgrade to 2004 unless you enjoy the challenges it may provide.

Red Ruffnsore

Reply | Quote

My PC is still on 1903 Pro. Is it possible to upgrade to 1909 and not 2004? Thanks.

 

Reply | Quote

My only hope is for people that is reading this, to not install this right away, some people like bbearren  do it, because they have alot of experience, thousands of backup and know what they are doing in case something goes wrong.

My advice is that if you don’t know anything about windows 10 and its many recovery tools (whether internal or third party ones) you should wait until its safe to install it.

Just someone who don't want Windows to mess with its computer.

2 users thanked author for this post.

AlphaCharlie, woody

Reply | Quote

I would add to that… even if you DO know about Windows’ recovery tools, don’t install this thing until it’s rock solid.

There’s very, very little benefit to installing it. And plenty of downside.

2 users thanked author for this post.

AlphaCharlie, AlexEiffel

Reply | Quote

woody wrote:

I would add to that… even if you DO know about Windows’ recovery tools, don’t install this thing until it’s rock solid. There’s very, very little benefit to installing it. And plenty of downside.

@RG and others here at AskWoody have already installed 2004, just as I have.  There is NO recovery tool that can outperform a drive image.  Correspondingly, having a current drive image equates to NO downside to installing this update outside a work environment.  As a matter of what I consider best practices, I install every Windows update offered to my machines, and have been for a couple of decades, now.  I have yet to encounter a real issue with any of them.

I see 2004 as just another Windows update, and I treat it as such.  With updates, I go after them with my desktop, and wait for the push to my laptop and NAS.  You, Susan and everyone else who adds a blog post here at AskWoody frequently say, “Backup first”.  The introduction to my website is, “For experienced users and those users who wish to become more experienced, I offer some self-help ideas here on this site for preventive maintenance, troubleshooting techniques and corrective measures to employ when Windows is misbehaving.

My #1 suggestion, my top recommendation for success as a Windows user, is to commit to an established regimen of regular drive imaging.”  I follow my own advice.  I always have a current set of drive images.  In this post in this thread, I give some detail to what I encountered on the B side of my dual boot due to a corrupted Administrators group user account, and what I did to correct it.  Restoring my drive images was part of the corrective process, and exposed the existence of that corrupted profile.  I know how to fix those.

I have no issues with either side of my dual boot now.  The only problem I’ve detected with 2004 is that it has resurrected those “Special Folders” that I had expunged from Windows and added even more registry entries regarding them.  Those I will ferret out and once again expunge the “Special Folders”, I’ll be good to go, I’ll continue to follow my own advice, and continue to report my results here, until I get voted off the island.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

2 users thanked author for this post.

Barry, Zaphyrus

Reply | Quote

Or You could wait until enough people fall  into  Microsoft’s traps and install it when the upgradee is stable.

Even if people think that the upgrade went smoothly issues tend to appear within 2 weeks or 2 months.

as I said, most experts install it right away this because they  have experience and programs in case something goes wrong.

Just someone who don't want Windows to mess with its computer.

Reply | Quote

woody wrote:

I would add to that… even if you DO know about Windows’ recovery tools, don’t install this thing until it’s rock solid.

There’s very, very little benefit to installing it. And plenty of downside.

Appears rock solid without any downside to Fred:

Earlier this week, Microsoft released the semi-annual refresh of Windows 10, this one dubbed “2004,” meaning it was finished last month, 2020-04.

So far, I’ve updated four PCs, including my primary-use, personal system. All have gone smoothly, with nary a hiccup.

Microsoft’s install routines seem to be getting better at picking up existing software, too. After the upgrade from Win10 1909 to 2004, the only software I had to reinstall was an exotic and optional SSD caching tool. As far as I can tell, all other third-party drivers and apps were left intact and as before — including even some old, third-party apps that normally require full reinstall after an upgrade.

It was a very smooth transition, so far.

New Win10 version (“2004”) first impressions, Posted on 2020-05-29 by Fred Langa

1 user thanked author for this post.

Barry

Reply | Quote

Yes i noticed that it carried over all my software and did not change any settings. I have had it installed for 2 days and seen no problems at all.

Barry
Windows 11 v23H2

1 user thanked author for this post.

b

Reply | Quote

Microsoft doesn’t usually hide what changes without good reason, but Microsoft posts patch notes and change logs for their updates with every update. Requiring users/admins to visit a page to see what changed is basically no different than expecting anyone who knows to actually ask what changed to find out, which I personally don’t think is unreasonable in any way. Even if Microsoft wanted to try and force people to look at what changed from patch to patch, or update to update.. the overwhelming majority of people would just speed-click through everything anyway.

Reply | Quote

I’m an admin for an SMB, and my entire environment is already running 2004 (has been since April, as I run the environment with Preview enrolled). I’ve yet to have any noteworthy issues with 2004 besides one or two devices requiring one or two attempts to complete the upgrade installation to 2004. Ironically, I have had more issues with Office installs for two or three specific users of late than I have with Windows out of the 100ish devices I manage that are running Windows 10. All that said, the users I’ve been having issues with are all the most irregular and complex usage cases in my organization besides IT, so the probability of their seeing issues is/has always been higher anyway.

 

For a little background, I have been running my environment enrolled in Preview for over a year, and have really had only one issue in the past 14-16 months that was caused by a Windows Update.

Reply | Quote

Like with covid 19 I will continue being safe Thus with Win 2004 I set the GPE to 30 days and from time to time ck here and on other tech website chats regarding the update

Win 10 pr o 64 version 1909 build 18363.836

Thank You

 

Reply | Quote

FYI, the bugs list at https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004 has been updated to include the DISM bug:

DISM might incorrectly report corruption is still present after repair
After running DISM /restorehealth, DISM might incorrectly indicate corruption is still present after repair.

2 users thanked author for this post.

woody, abbodi86

Reply | Quote

looks like Microsoft is scheduled to fix the DISM bug in mid-June

Reply | Quote

[krzemien]

Really heart-warming that one can issue a major OS release with such a bug. if DISM gives inconsistent results, where’s the source of truth?

Also, does it not imply (yet again) that this release was pushed out of the door hastily and prematurely (yet again)?

One really wonders what else is there to be found.

• This reply was modified 4 years, 11 months ago by krzemien. Reason: SPELLING

1 user thanked author for this post.

woody

Reply | Quote

It’s 5 months old, nothing that premature 🙂

1 user thanked author for this post.

b

Reply | Quote

Here’s are the features being deprecated or removed in Windows 10 version 2004

2 users thanked author for this post.

AlexEiffel, ScotchJohn

Reply | Quote

Microsoft blocks May 2020 updates for PC with HVCI enabled

1 user thanked author for this post.

AlexEiffel

Reply | Quote

[EP]

Tex265 wrote:

Last I looked Windows 10 ver 1909 is good until May 11, 2021 !

Yes 2021!

EOL for v1909 Home & Pro is May 2021, Tex265
I use 1909 Education which is supported until May 2022 – enterprise & education editions of 1909 get additional year of support

• This reply was modified 4 years, 11 months ago by EP.

Reply | Quote

Yeah after 5 years of this stuff I am so over these upgrades. Now that we have the option to delay them, I much prefer the LTS option per say then these upgrades.

Reply | Quote

Have not been offered the upgrade on any of my machines. I consider them pretty bland and shouldn’t be affected by these issues. I fine with waiting weeks or months until things get ironed out with this upgrade. Nothing much impressing me about it anyway.

Reply | Quote

Another surprise, 2004 has difficulty waking from sleep (giving a blank screen on waking) on my AMD-based PC; the only fix is to reboot. So, I restored Win 1909. The 2004 upgrade is going to wait for a while.

Reply | Quote

_Reassigned Account wrote:

Yeah after 5 years of this stuff I am so over these upgrades. Now that we have the option to delay them, I much prefer the LTS option per say then these upgrades.

I wish Microsoft would sell LTSC to everyone, but then Microsoft will lose Telemetry, force updates, Microsoft Store, Edge browser, c*** apps,…

Reply | Quote

numike wrote:

Thus with Win 2004 I set the GPE to 30 days

Why use GPE ? Why not just use Advanced Options and deffer for 365 days ?

Reply | Quote

[PKCano]

Updated last night using Update Assistant. No problems – everything works just as expected so far. My laptop is not a production machine so I decided to take a look at it. Have not encountered anything that looks or performs differently. OS build is 19041.264.

• This reply was modified 4 years, 11 months ago by PKCano.
• This reply was modified 4 years, 11 months ago by mossrock.

Reply | Quote

This notice now appears on my Windows Update:

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

Possible reason for incompatibility issue is  explained here:

https://www.bleepingcomputer.com/news/microsoft/windows-10-2004-upgrade-may-be-blocked-due-to-old-graphics-drivers/

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

I have none of the beepingcomputer conditions and yet I still received the notice shown below.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Why am I even seeing this when I have Feature Update deferral set at 365 days?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Tex265 wrote:

Why am I even seeing this when I have Feature Update deferral set at 365 days?

Look at 2004 update screen Apparently, the Feature Update deferral was changed by the availability of 2004.

Reply | Quote

Isn’t this also the official release of “Chredge”? If you update to 2004 and open Edge you are prompted to update to the wondrous world of Chredge.

I like it… discuss among yourselves.

Red Ruffnsore

Reply | Quote

[Carl D]

Downloaded Windows 10 2004 and installed it on a spare SSD (the same one I briefly tried out an evaluation version on last week).

As I suspected, it looks and behaves pretty much the same as 1909.

Couple of things I’ve noticed:

The chipset drivers for my motherboard (Gigabyte B250M-D3H) will no longer install. The last chipset driver release for this 3 year old board were for Windows 10 1903 so that’s probably not surprising even though they worked for 1909 – don’t know why Microsoft keep making things like this incompatible after a few releases? The rest of the drivers from the Gigabyte website seemed to install OK though.

Played around with it for a while and decided to clean install 2004 again. This time I let Windows install its own drivers and I didn’t use the Gigabyte ones. I had the PC disconnected from the Internet (as always) during the install and Windows installed most of its own drivers except for about 3 or 4 – can’t remember what they were since I’ve gone back to my 1909 SSD for now.

When I went online with 2004 I went to Device Manager and did a search for the missing drivers and Windows found them all. I assume these drivers will work OK if I just use them and not bother with any from Gigabyte (which they probably won’t ever have anyway since they stopped providing them at 1903).

The other thing I noticed was that ‘Defragment and Optimize Drives’ keeps “forgetting” that I’ve run it after a reboot. Keeps telling me that its never been run and the drives need optimizing (I have 2 SSD’s with several partitions on each). Tried running it several times but after a reboot it “forgets” that it has been run.

Never seen that one until this 2004 release. Good one, MS.

 

• This reply was modified 4 years, 11 months ago by Carl D.
• This reply was modified 4 years, 11 months ago by PKCano.

Reply | Quote

I know the disk utility issues have been mentioned before, but since you mentioned it I decided to check. I haven’t checked my other systems yet but my main home pc has 2 nvme ssd’s. Defrag (optimize drives service) was set to run automatically on a schedule. This should be off since there are no spinning drives.

If you only have ssd drives on your computer you will want to either disable or set to manual the “optimize drives” service.

Red Ruffnsore

Reply | Quote

Mr. Natural wrote:

If you only have ssd drives on your computer you will want to either disable or set to manual the “optimize drives” service.

I believe that is incorrect. SSDs should be optimized (trimmed and defragged):

Windows’ Windows’ Optimize drive tool – what’s the consensus?

1 user thanked author for this post.

rc primak

Reply | Quote

I thought only mechanical drives needed optimizing (defrag). Has that utility now changed with the advent of ssd’s? Earlier versions of Windows would turn off defrag if it recognized ssd’s in the system.

Red Ruffnsore

Reply | Quote

I’m thinking the utility has changed with the reference name change to “optimize and defragment”.  There’s technically 2 different things there. I thought trim was originally only on the ssd’s that included it in the firmware and was at first managed by the ssd. Windows later included the feature….. perhaps.

Perhaps someone can confirm.

Red Ruffnsore

Reply | Quote

[rc primak]

Many SSDs do their own Trim. But running Optimize monthly on my SSD (Samsung) does not seem to do any harm. Basically all it does is garbage collection. Windows does not try to defragment SSDs. The very term does not apply to SSDs because of how they store data.

-- rc primak

• This reply was modified 4 years, 11 months ago by rc primak.

1 user thanked author for this post.

Mr. Natural

Reply | Quote

rc primak wrote:

Windows does not try to defragment SSDs. The very term does not apply to SSDs because of how they store data.

It does, monthly:

The real and complete story – Does Windows defragment your SSD?

1 user thanked author for this post.

Reply | Quote

I opened the Defragment and Optimize app and learned that it is set for weekly for my SSD drive. I didn’t know that this app existed until now, so apparently, the manufacturer (Dell) set it or maybe, that’s the default. For the life of the SSD, is it better to set for monthly, given that Win10 version are updated twice a year? (I am an average non-business user, mostly creating or modifying personal data files daily, weekly, monthly or yearly and updating Win10 versions twice a year (after cautious wait time, of course).

I started with 1803 and now I am up to 1909. Each time a new version is installed, this involves a lot of writing, right?

Reply | Quote

WCHS wrote:

For the life of the SSD, is it better to set for monthly

No!
SSDs do not have short lives – TechReport article.

cheers, Paul

Reply | Quote

rc primak wrote:

Many SSDs do their own Trim

Not quite, the operating system sends a Trim command to the SSD and it does the work when it has time.

cheers, Paul

Reply | Quote

TRIM for SSDs should be routine/regular, but SSD Optimization is basically just performing TRIM operations. SSDs do not/should not be defragmented frequently (Windows already does so automatically on a monthly basis to prevent wasting storage space). Unlike platter-driven storage that stores data across multiple platters, and benefits from re-arranging where exactly on which platters data is stored for optimum read/write performance, SSDs are purely digital and have nothing remotely equivalent to platter drives splitting/spreading of data across multiple physical media inside the casing of the units.

 

That said, files can be moved messily within the SSD storage, just like with platter storage. Like all storage devices, SSDs are prone to slowing down once they get to a certain level of capacity usage (in my experience, it’s usually imperceptible until somewhat <80% capacity use). TRIM basically syncs the storage drive with the OS, thereby ensuring that the storage device knows what the OS is actually considering in use, and what is not, ultimately enabling the storage device to clear/drop data that is no longer in use more quickly/readily. The defragmenting of an SSD is functionally different from defragmenting an HDD, but practically the same activity for somewhat different reasons. For anyone interested in more detailed explanation, that also includes some input from some members of the Windows Storage Development Team as I understand, I would encourage you to visit the following link: https://www.hanselman.com/blog/TheRealAndCompleteStoryDoesWindowsDefragmentYourSSD.aspx

Reply | Quote

I managed to install v2004 on one of my test v1909 Win10 Pro VMs today (5/30). I “encouraged” it to show up by setting the Feature update deferral to 2 days and clicking on “Check for updates.”

No good news for Windows Update control.
The GUI deferral settings are gone (as reported). The last time they disappeared, the associated Registry settings were still there. Although I haven’t had time for a thorough search, I think they are also history.

The Group Policy deferral settings seem to still be intact under Windows Update for Business. Who knows if MS will restrict the use to Enterprise and leave the Pro User and SMBs with no control.

Maybe MS is headed for “Update in the background/no User control” like they are currently doing with the Taskbar and Search.

The Windows.old was 24.8GB. This was a test machine – no data, maybe 1GB of third-party installers (Libre Office, BitDefender Free, Malwarebytes Free, Irfanview, Adobe Reader, etc). It’s going to be REAL HARD for machines with less than 128GB storage to update.

3 users thanked author for this post.

AlexEiffel, Alex5723, woody

Reply | Quote

Did a clean install of 2004 on my second SSD yesterday. I used all the drivers (motherboard, audio, etc.) from Windows Update and everything is working perfectly so far. The only drivers that I installed separately were the latest driver from NVIDIA for my graphics card and the drivers and utilities for my 2 printers.

One of the first things I installed was Macrium Reflect (paid version) and I made backups every half hour or so during the installation of my programs, etc. Better safe than sorry (and having to start from scratch if anything serious goes wrong).

I was surprised that my copy of Paint Shop Pro 9 (from 2004) still works perfectly with Windows 10 as do my copies of Microsoft Train Simulator (from 2001) and Microsoft Flight Simulator 2002 – the only “issue” with FS2002 is that it doesn’t show the ‘rotating 3D’ models of the selected aircraft prior to commencing a flight. Been like that with every release of Windows 10 as far as I know. Not a big deal. Used Windows XP SP2 compatibility mode for all of them although they did seem OK without it.

Defragment and Optimize Drives still “forgets” that it has been run after a reboot but I can also live with that for the time being.

I’m so confident now with Windows 10 2004 that I’ve ‘erased’ my other SSD which had 1909 on it since last November and put it away ready for the next Windows 10 release which will presumably be later this year. I like to be brave and daring these days 🙂

Reply | Quote

Carl D wrote:

I’ve ‘erased’ my other SSD which had 1909 on it

You could have left it on there until the next upgrade.

cheers, Paul

2 users thanked author for this post.

rc primak, Carl D

Reply | Quote

This information appears to be mostly Windows 10 2004:

https://answers.microsoft.com/en-us/windows/forum/all/windows-10-may-2020-update-is-now-available/cb13d2e7-de29-4d78-bf14-486bd2fb2227

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote