Further evidence of forced upgrade to Win10 version 2004, possibly due to a “Pause updates” bug

Topic

New Reply

I had a chance to go back over the evidence, and it sure looks to me like some folks are getting upgraded from Win10 1903 and 1909 Home and Pro to Win
[See the full post at: Further evidence of forced upgrade to Win10 version 2004, possibly due to a “Pause updates” bug]

3 users thanked author for this post.

abbodi86, Elly

Reply | Quote

Replies

Is Microsoft paying attention?  Old news, but from their own blog

https://blogs.windows.com/windowsexperience/2020/05/27/how-to-get-the-windows-10-may-2020-update/

Beginning today, the May 2020 Update is available for customers who would like to install this latest release. If you are ready to install the update, open your Windows Update settings (Settings > Update & Security > Windows Update) and select Check for updates. Once the update appears, you can select Download and install. (Note: You may not see Download and install on your device as we are slowly throttling up this availability over the coming weeks, or your device might have a compatibility issue for which a safeguard hold is in place until we are confident that you will have a good update experience.) Once the download is complete and the update is ready to install, we’ll notify you so that you can pick the right time to finish the installation and reboot your device, ensuring the update does not disrupt your activities. This new “Download and install” capability is available for devices running Windows 10, version 1903 or version 1909.

Reply | Quote

That’s the original promise…. and it’s a great change from the old “push the button and see if it explodes” approach.

Reply | Quote

Woody maybe i am wrong but i thought that was the way its supposed to work. You basically have 3 options now

Use the pause option and whenever the pause ends it would automatically install all updates

Never hit check for updates and you will never get updates

Or like me always install all updates as soon as they are available

I dont use it and i know in reading about it it was very confusing but that was my impression. Not saying its good or bad just the way i thought it was supposed to work.

 

Barry
Windows 11 v23H2

Reply | Quote

Microsoft has never rescinded the “Download and install” post. So I don’t think it’s supposed to work that way.

Reply | Quote

ZDNet has just posted Windows 10 2004 rollout: We’re slowly throttling up availability, says Microsoft – Still haven’t been offered Windows 10 version 2004? It might be coming soon to your PC. At  https://www.zdnet.com/article/windows-10-2004-rollout-were-slowly-throttling-up-availability-says-microsoft/

It provides a little more insight as to what is going on with Windows 10 2004.

Reply | Quote

I noticed too the Windows Media creation tool now is on 2004 and not 1909 version.

Reply | Quote

_Reassigned Account wrote:

I noticed too the Windows Media creation tool now is on 2004 and not 1909 version.

MCT switched to 2004 since May 27.
If you need 1909 (or any other version of Windows 10/Windows 7/Office) use Heidoc.net tool.

Reply | Quote

Updated while pc was on sleep, woke up to find that my computer restarted, all unsaved work was gone and yes, the new Edge was installed and ready to give me a tour and tell me why it’s the best browser in the world.

Also I’m just curious why would the update Edge on my pc when “receive updates for other microsoft products” was disabled???

1 user thanked author for this post.

geekdom

Reply | Quote

We have 2 desktops & 3 laptops. On both desktops & 1 laptop the first sign of having updated to 2004 was the restart button. All are on 1909. I have not booted the other 2 notebooks yet. The only problem encountered so far is having to reinstall scanner software. We didn’t get the download & install button.

Reply | Quote

Resuming updates from a paused state did not install 2004 on a 1903 desktop that I updated last Saturday.

2 users thanked author for this post.

Brocktoon, Barry

Reply | Quote

After OS was updated to 1909 build 18363.900, pause updates was set (10 June) and allowed to expire (11 June).  2004 was not offered or installed.  Windows update displays “You’re up to date”

Win 11 home - 24H2
Attitude is a choice...Choose wisely

Reply | Quote

I’m on 1909 after installing the May 2020 updates during the time when you had the DefCon set to 4 in early June.  I have updates paused until 7/6/2020.  I also have Feature Updates set for a 129 day delay and Quality updates set for 30 to add a little more safety.  When I checked the Windows Update page today I noticed that it automatically started checking for updates.  However, the little ‘pausing updates’ symbol was still showing on the updates icon.   See attached screen shot.

I was a little nervous, but when the updating animation stopped it went back to normal and didn’t actually try to give me either the June Patch Tuesday updates or the dreaded May 2004 version.

Is is possible that I was saved by having the other delays set in addition to just pausing updates?

Reply | Quote

From you screenshot, I think you may have been saved due to you device not being compatible.  If not for that, I wonder if you would have been auto-upgraded.

Reply | Quote

I was offered v2004 om May 29. Because I have preparations I need to find time to do before installing this Feature Update I set Pause updates to July 7.

This weekend I saw posts on WindowsTenForums saying that this Feature Update would not install automatically, that you had to choose to install the update before it would start. So I figured I’d stop pausing updates since I knew there was a CU KB4560960 available and I figured I could install it, without installing 2004.

Today I did the deed. The minute I hit “Resume Updates” the 2004 Feature update began downloading (even though I have my Network settings on Metered Connection, and Don’t Download Updates on a Metered Connection set.)

I really can’t install this thing right now so I immediately shut down and on startup reset WU to Pause Updates – this time to July 17.

So technically I did not have the 2004 Feature Update forced on me, but it would have if I let it go.

W10 1909. Desktop, 17-9700K, Asus Prime Z390-A, M.2 Nvme 500GB, 16GB RAM

 

Reply | Quote

Some of my machines are offering the Download and install 2004 when you are ready.

However one of my Windows 10 Pro machines went ahead an downloaded and updated to 2004 without asking and when I went to check my updates there it was sitting there asking to Restart to finish the install.

This is a Pro machine NOT Home !!

My bad for not pausing updates but I think it is Criminal for them to force this stuff on people when it is just released especially if yo have Windows 10 Pro.

We are all their Beta testers and they simply do not care any more.

Reply | Quote

Desktop i7-9700K here

Yes, mine is Windows 10 Pro also. That could be the link.

Reply | Quote

arbrich wrote:

This is a Pro machine NOT Home !!

It seems that only Pro machines “suffer” from the auto 2004 updates.

Reply | Quote

I reported my particular “forced update” experience on a different thread here on the site, but, yeah, mine was Pro too

Reply | Quote

2 Windows Home laptops, both Updates paused till June 16th; yesterday (15th) on both I pressed Resume updates. They installed the June updates; 2004 did not show up at all (yet).

~Annemarie

Reply | Quote

Omg. I’m still working on July 2019 invoices because an update snuck in & ate up my excel sheet. Then over 30 on-board Ms techs killed it. I’ve clean installed, and am almost there. I used everything -powershell, update page deferrals. Yesterday, all choices grayed out. Today, turned on & it began downloading. I killed its service-6 times til it finally died. Now I’m starving (no income) and waiting for Microsoft to inject its poison.

Susan

Reply | Quote

I’m running Win10 1909 HOME … after the May updates I had updates paused until 6/28.  I had some free time today, so I backed up my important files and decided to ‘resume’ updates.

After pressing ‘resume’ I was offered the June Cumulative, Adobe Flash update, a driver update AND the OPTION to ‘download and install’ 2004.

2004 was not forced on my Home system.  I’m now running v18363.900.  Windows update is now un-paused with the feature update still available as a ‘download and install’ option.  I’m not going to risk the ‘check for updates’ button … I’ll just let WU run when it wants.

This does seem to be another piece of evidence showing Win 10 HOME users may be safe, and that the forced download bug may be inherent in PRO versions

1 user thanked author for this post.

Elly

Reply | Quote

Luckily, this new introduced policy in v2004 is very worthy, specially since it works for versions 1803 and later

following this article by Ed
Changed to Feature Updates in Windows 10 v2004

and this by Microsoft
Optimize on-premises monthly update delivery using the cloud

For devices on Windows 10, version 1803 or greater:
If you need your devices to remain on their current feature update beyond when deferrals would allow or until the current OS version reaches end of service, then you should specify a specific version for the device to stay on until end of service or until the policy is changed to a newer Windows 10 feature update.

i tested this on 1803 Pro (build 17134.799), by adding the TargetReleaseVersionInfo registry values manually, without any deferrals
and it worked great

specifying 1809 gave me Feature update to Windows 10, version 1809 (17763.1282)
specifying 1909 gave me Feature update to Windows 10, version 1909 (18363.900)
specifying 1803 gave me Cumulative Update for Windows 10 Version 1803 (17134.1345) – and no feature update

it’s basically a Feature Update chooser/nuker

9 users thanked author for this post.

migongo, jburk07, georgea, schwabel_ronald, wavy, geekdom, woody, Paul T, Alex5723

Reply | Quote

Where does the TargetReleaseVersionInfo entry go in the Registry?

Is it a String value?

Reply | Quote

[woody]

I think I found it (on Ed’s Blogue):

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\

Windows\WindowsUpdate]

“TargetReleaseVersion”=dword:00000001
“TargetReleaseVersionInfo”=”2004”

• This reply was modified 4 years, 10 months ago by woody.
• This reply was modified 4 years, 10 months ago by woody.

Reply | Quote

Precisely where does what go into the registry to set the version in stone?

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

It’s easier to add the values via command prompt (as administrator)

reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /f /v TargetReleaseVersion /t REG_DWORD /d 1

reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /f /v TargetReleaseVersionInfo /t REG_SZ /d 1809

4 users thanked author for this post.

migongo, jburk07, geekdom, woody

Reply | Quote

abbodi86 wrote:

reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /f /v TargetReleaseVersion /t REG_DWORD /d 1

I understand the second command specifies the version to stay on, but what is the purpose of the first command?

Reply | Quote

[PKCano]

The first TargetReleaseVersion says that key is either on (1) or off (0) (in use or not)
The second one gives the version targeted.

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

1 user thanked author for this post.

Reply | Quote

Is this ability to choose a version only effective for Windows 10 Pro?

Reply | Quote

Pro, Education and Enterprise

Reply | Quote

Because another person asked elsewhere whether these version selection keys would work on a Windows 10 Home installation I added the registry entries as an experiment.

I’ll follow up with a yes or no if Microsoft still tries to push a different version of Windows.

Reply | Quote

Yes, using the setting ‘TargetReleaseVersionInfo 1809’, the blocking scheme does work there are no forced offerings of a new feature update.

Maybe I broke something but this months cumulative update is not offered even after resetting the update cache. 🙂

Reply | Quote

If you are using Win10 Pro, the Registry entry has an equivalent in Group Policy. See #2276103. If you removed the Reg entry, you might check to see that the GP entry is no longer there also.

Reply | Quote

Thank you, the blocking of new feature updates is what I wanted for Windows 10 home.

As for the lack of new cumulative updates, a possible fix would be a manual installation of the latest servicing stack?

Reply | Quote

You may need the SSU (SSU first, reboot), the CU and the Flash update.
On Home, be sure you don’t have Metered connections ON, any Pause set, or have hidden the updates with wushowhide before you go to the trouble of manual updates.

Reply | Quote

Thank you, apparently manually updating to July’s servicing stack cleared the fault.

Reply | Quote

Also testing on my 2 W10 Home machines.

cheers, Paul

Reply | Quote

Set TargetReleaseVersionInfo to 1903 on two Home machines.

Post June patches.
One machine offers no updates to a newer version, the other has the “optional” 2004 update showing.

cheers, Paul

1 user thanked author for this post.

Elly

Reply | Quote

Hi I can tell you without a doubt, I was forced to update! I was on version 1909 and all was good, last weekend. I keep my PC shut down/off most of the week cause I’m at work etc. I turned it on last weekend and everything was running a little slower, I looked at update and it was indeed installing feature update 2004. I thought well it’s already installing I’ll leave it alone. When it had finished and rebooted, everything was slow, and MS Edge wouldn’t open at all! No matter what! I just started a new job 2 weeks ago and I have to attend an online class next week, from home! Great now my PC is messed up! I did manage to restore it using a system image but it was an older image 1903, at least it works. Now I can update to 1909 again because update switched 1909 to 2004. I’m really mad because I didn’t want to update it at all! Certainly not till after I pass my class! I need help with it, but MS wants me to pay for their help in fixing my PC for something they did!!

Reply | Quote

If you are using win10 PRO, check post #2275486 for info on how to stop(hopefully) your system on the version you are currently using. Search AskWoody for info on how to get 1909 iso.

Reply | Quote

Wait for @PKCano to respond. He can advise you on how to move from 1903 to 1909 and to stay on 1909 for a good while. 1903 reaches its end of life on Dec 8, 2020.

Reply | Quote

If you don’t want to update you have to tell Windows. The best (current) method is to set TRV – see this post.

If you set it to 1909 your PC will update on its own.

If you want to control the update, download the Heidoc tool and obtain a 1909 update ISO.
Disconnect from the internet.
Double click on the 1909 ISO and run setup.exe from the new drive that opens in Explorer.

cheers, Paul

p.s. if your machine updates to a later version you have 7 days to roll back to the previous version – no restore required.

Reply | Quote

AKV2000016 Guide for Windows Update Settings for Win10.

IF you have the Home Edition:
Read Section 1 of AKB2000016, then follow the instructions in Section 2 for the TargetReleaseVersion settings. Depending which version you want, use 1909 or 2004 (if you want version 20H2, use 2010). Woody recommends staying on v1909 for a while longer. It is not EOL until May 2021.

IF you have the Pro Edition:
Read Section 1 of AKB2000016.
Follow the instructions in Section 3 for the TargetReleaseVersion settings. Depending which version you want, use 1909 or 2004 (if you want version 20H2, use 2010).

There are screenshots at the bottom to show where the settings are located.
If you need help, create a topic with a Title describing your question.

1 user thanked author for this post.

abbodi86

Reply | Quote

FWIW I upgraded to 2004 but it was my choice to do it.  When 2004 started up the first few times I also noticed that it was very slow and thought seriously about restoring from a backup of 1909 that I had taken shortly before I upgraded.  After a few days it did start to speed up so it is usable now.  There was a lot of disk activity and I guessed that it might have been re-building the search index or some other post-install optimization.  It still seems to take a lot longer to start up though.

Reply | Quote

If it’s that much slower you should fire up Task Manager and see what is consuming the resources. If there is nothing in particular you should roll back – after making an image backup. If it’s still slow in 1909 then maybe it’s time for an SSD.  🙂

cheers, Paul

Reply | Quote

It looks like sometime in the last eight hours, while my screen was locked, Win 10 2004 was downloaded and installed. When I unlocked the screen, there was a message imploring me to restart Windows. The Settings>Windows Update screen/dialog indicates  “Feature update to Windows 10, version 2004 || Status: Pending restart” It has been at least a week since I looked at Settings>Windows Update, and I have, many times, noticed and ignored the “optional” update to version 2004 in the past. No one else would have accessed my system, let alone looked at or clicked anything in Settings>Windows Update in the past 48 hours.

I saw a mention of something expiring in the CW article “How to block the Windows 10 October 2020 Update, version 20H2, from installing”, but I don’t see anything in Advanced settings about anything expiring in Windows Update Advanced Options except for Pause Updates.

Anyway, it doesn’t seem like it will be worth the time to try to prevent the now installed 2004 from being activated upon restart.

Still, I remain interested in learning more about this topic.

Reply | Quote

We have a comprehensive guide on the subject. See post #2309914 for more details.

cheers, Paul

Reply | Quote

I was running Win10 home 1909 with updates un-paused.  On 11/6, without manually checking for updates I was auto updated to 2004 in the background.

I help with IT troubleshooting for some of my neighbors, and two of them who were both using Win10 Home 1909 were auto-pushed to 2004 earlier this week.

Not a lot of data points to go by, but it sure does look like MS is increasing the amount of 1909 users who are getting 2004 forced on them

Reply | Quote

Brocktoon wrote:

Not a lot of data points to go by, but it sure does look like MS is increasing the amount of 1909 users who are getting 2004 forced on them

You, and anyone who wished for, could block the upgrade to 2004 using ‘TargetRelease..settings (GP/Registry).

Reply | Quote