Reports of Win10 1909 users getting pushed onto version 2004

Topic

New Reply

It happens every time Microsoft rolls out a new upgrade. A certain percentage of users get upgraded without asking for or expecting it. In most cases,
[See the full post at: Reports of Win10 1909 users getting pushed onto version 2004]

2 users thanked author for this post.

Floki, Elly

Reply | Quote

Replies

Even with Windows Update set for automatic download, nothing paused, only driver updates blocked via Group Policy, my NAS on 1909 did not get the push update, nor was I offered the update when I clicked Check for updates.  I got “Your system is up to date.”

I had to use the MCT USB to update my NAS to 2004, which completed without incident or issue.

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

The problem is about having Pause set and the time running out. Your setup doesn’t seem to fit those circumstances.

2 users thanked author for this post.

Elly, woody

Reply | Quote

My win10 Home 1909 is on pause for the next few weeks like many others.  I guess I’m waiting to see if anyone clicks on ‘resume updates’ in the coming days and gets forced to 2004.  It sounds like we may be OK as long as we ‘resume’ manually and don’t let the timer run out on it’s own.  But I’ve still got a bad feeling that clicking on resume may still trigger the 2004 download

1 user thanked author for this post.

woody

Reply | Quote

My hope is that:

(1) We can definitively track down the circumstances and

(2) Get Microsoft to fix it (if, indeed, there is a bug) before it becomes a mainstream problem

1 user thanked author for this post.

Brocktoon

Reply | Quote

We have two workstations at home.  Feature updates are deferred for 75 days.  I have not seen messages on either machine about the availability of 2004 and both are happily running 1909.  I also have the monthly updates deferred for 15 days which seems to be just fine to avoid the first day shock of the monthly updates.  Since moving to Windows 10, neither my wife or myself have encountered any issues.

Reply | Quote

[CADesertRat]

I have Group Policy set to defer Feature Updates for 365 days and pause updates set to 7/6/20 (via the pause button in Settings>WU). So far, no 2004.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

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

Reply | Quote

The problem is about having Pause set and the time running out. Not about having deferrals set.

2 users thanked author for this post.

Elly, CADesertRat

Reply | Quote

Hi Woody, the combo of settings with Pause Updates appears to be what occurred on the machine I posted about a few days ago Re: my domain connected machine.
on another PC, the 2004 update was pending install on restart, but I paused updates until July and that should delay it.

Will J Stewart
Independent IT 25 years
Austin, Texas

1 user thanked author for this post.

woody

Reply | Quote

More recent Windows 10 2004 feature update issues have been reported over on WindowsLatest
Lenovo devices seem to be taking the brunt at the moment. If you encounter a BSOD using a Lenovo device during the update, their advice is to roll back the feature update, more info within the above link. Lenovo and MS are aware of the issues.(so in essence these devices shouldn’t be feature updated to 2004 yet) right?

Windows - commercial by definition and now function...

1 user thanked author for this post.

woody

Reply | Quote

I saw that. When things settle down here (it is Patch Tuesday after all!), I’ll take a deep dive into Parmar’s report.

Which is highly recommended, as usual.

1 user thanked author for this post.

Microfix

Reply | Quote

woody wrote:

I saw that. When things settle down here (it is Patch Tuesday after all!), I’ll take a deep dive into Parmar’s report.

Which is highly recommended, as usual.

No word if these Lenovo PCs with 2004 were declared by Microsoft as 2004 compatible and had been updated, or users used ISO to install 2004 on a incompatible devices.

Lenovo Y530, 2004 not compatible with my laptop.

1 user thanked author for this post.

woody

Reply | Quote

That’s a very good point – and something I’ll keep in mind after the Patch Tuesday deluge hits.

Reply | Quote

Alex5723 wrote:

No word if these Lenovo PCs with 2004 were declared by Microsoft as 2004 compatible and had been updated, or users used ISO to install 2004 on a incompatible devices.

The five Thinkpad issues were originally listed as “Limitations” at the bottom of the table of Thinkpad systems tested by Lenovo, where they provided workarounds:

Lenovo devices tested for Windows 10 version 2004 (May, 2020)

(Which you linked to yesterday.)

1 user thanked author for this post.

Microfix

Reply | Quote

b wrote:

Alex5723 wrote:

No word if these Lenovo PCs with 2004 were declared by Microsoft as 2004 compatible and had been updated, or users used ISO to install 2004 on a incompatible devices.

The five Thinkpad issues were originally listed as “Limitations” at the bottom of the table of Thinkpad systems tested by Lenovo, where they provided workarounds:

Lenovo devices tested for Windows 10 version 2004 (May, 2020)

(Which you linked to yesterday.)

“Go back to the previous version of Windows 10” is a workaround for ‘limitations’?

Lenovo list just Thinkpad ‘limitations’ but not ‘limitations’ for the other hundred Lenovo PCs.

Reply | Quote

Alex5723 wrote:

“Go back to the previous version of Windows 10” is a workaround for ‘limitations’?

Apparently. For one specific model. Thinkpad P70. If sleep/hibernate is used and resumed.

Alex5723 wrote:

Lenovo list just Thinkpad ‘limitations’ but not ‘limitations’ for the other hundred Lenovo PCs.

Perhaps there weren’t any? Lenovo do claim on that page to have tested 2004 on all models listed (including four Y530 variants).

Reply | Quote

I have one of my test devices (Lenovo T450) updating right now to 2004.
It was paused before, but had it cleared.

Reply | Quote

When you say “had it cleared” – does that mean you clicked Resume updates?

Did you click “Download and install?

Reply | Quote

I did not click on clear updates. I edited the registry and cleared it there.
I did not click Download and Install. I just saw it when I went to Updates & Security.

I had feature updates deferred to 120 days, so in theory I should not get it.
btw, the feature update failed to install with error 0xc190012e .

1 user thanked author for this post.

woody

Reply | Quote

I have a Lenovo e545-win7 (2014 vintage) that would not install win10. error every time and no help from lenov(IBM sold to China) . Something is causing the cpu to overheat so I haven’t used it in a few months.(replaced CPU, added SSD (from SATA HDD) and added Kingston RAM. Lenovo says MoBo needs replacement at their shop- but even if I did that what would windows 10 Pro think of that???

I bought a pro key from a (Then) Legit company (checked their license first) and with help from Msft, was able to get it installed. Seems Lenovo isn’t too interested in cooperating w msfts intent, based on the number of complaints from lenovo owners here on AW.

Reply | Quote

b wrote:

Alex5723 wrote:

“Go back to the previous version of Windows 10” is a workaround for ‘limitations’?

Apparently. For one specific model. Thinkpad P70. If sleep/hibernate is used and resumed.

Alex5723 wrote:

Lenovo list just Thinkpad ‘limitations’ but not ‘limitations’ for the other hundred Lenovo PCs.

Perhaps there weren’t any? Lenovo do claim on that page to have tested 2004 on all models listed (including four Y530 variants).

Microsoft disagree with Lenovo.

Reply | Quote

Just checked our home computers for information related to Windows 10 2004 and none of them have been pushed to Windows 10 2004.

A summary of their Windows 10 status follows:

COMPUTER – HP ENVY DESKTOP – 795 – 005:

• Microprocessor Intel Core i7 – 8700 @3.20 GHz;
• System memory 16 GB;
• Graphics NVIDIA GeForce GTX 1060; and
• Audio Andrea PureAudio USB.

Windows specifications:

• Windows 10 Pro 64 – bit; Version 1903;
• Installed on 12/23/2019
• OS build 18362.778; and
• Has the Windows 10 2004 notice that it is coming but the computer is not quite ready.

COMPUTER – HP ELITE DESKTOP MODEL 800 G2 (P4K19UT#ABA)

• Microprocessor Intel Core i7-6700 3.4 GHz
• System memory 8 GB
• Graphics Intel HD Graphics 530
• Audio DTS Studio Sound

Windows specifications:

• Windows 10 Pro 64 – bit; Version 1903;
• Installed on 12/23/2019
• OS build 18362.778; and
• Does not have any reference to Windows 10 2004

COMPUTER – LENOVO THINKSTATION E20 (4222-67U)

• Microprocessor Intel Core i3-540(3.06GHz);
• System memory 8 GB;
• Graphics NVIDIA Quadro FX580
• Audio Realtek ALC662 codec

Windows specifications:

• Windows 10 Pro upgraded earlier this year from Windows 7 Pro
• Has the Windows 10 2004 notice that it is coming but the computer is not quite ready.

COMPUTER – LENOVO THINKSTATION E20 (4222-67U)

• Identical to the machine above
• Has no information re. Windows 10 2004

COMPUTER – LENOVO THINKPAD EDGE 14  0578-A99

• Microprocessor Intel Core i5 CPUN 480@2.67 GHz
• System memory 4 GB;
• Graphics Intel HD Graphics
• Windows 10 Home upgraded earlier this year from Windows 7 Home Premium 64-bit
• Has no indication that windows 10 2004 is available

COMPUTER – TOSHIBA SATELLITE A505

• Microprocessor Intel® Core™ 2 Duo processor T6600
• System memory 4 GB;
• Graphics NVIDIA® GeForce® GT 230M
• Audio Built-in harman/kardon® stereo speakers

Windows specifications:

• Windows 10 Home (Version 1909 OS build 18363.836) upgraded earlier this year from Windows 7 Home Premium 64-bit
• Has notice that Windows 10, version 2004 is on way but computers not quite ready.

It is interesting that the two identical Lenovo E20s have different Windows 10 2004 statuses.

 

Reply | Quote

Hi

I had exactly the situation you described.

I had paused updates, the pause period expired, and the first I knew the ÿour device needs to restart to install updates””appeared in the icon on the system tray

This happened with no intervention on my part

Appears a significant bug – unless it is deliberate and MS is trying to force the upgrade

1 user thanked author for this post.

woody

Reply | Quote

I think it’s highly unlikely that this is intentional.

Reply | Quote

I have 4 machines, all were on 1909. One machine got the 2020 update without asking and it got installed on my next boot. The others stayed on 1909. So I downloaded the installation USB stick from MSFT and installed 2020 on all my other PCs, with zero drama. The Intel Compute Stick PC is running on a dedicated wall-mount TV as a smart digital photo frame.

Paul

1 user thanked author for this post.

woody

Reply | Quote

PKCano wrote:

The problem is about having Pause set and the time running out. Not about having deferrals set.

It seems like when pause time is out or selecting resume from pause Microsoft takes this as ‘check for updates’

“‘Current 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.”

https://www.askwoody.com/forums/topic/coming-to-a-pc-near-you-win10-2004-the-may-2020-update/#post-2271124

Reply | Quote

Alex5723 wrote:

It seems like when pause time is out or selecting resume from pause Microsoft takes this as ‘check for updates’

Looks like where we need to break this down:

• Does Win act like ‘check for updates’ only when pause runs out, or does it also happen when selecting resume?  I don’t know if we have a confirmed case of someone clicking resume and getting 2004 pushed
• It seems like this is mostly happening with Win10 Pro.  Is this also happening with win 10 Home? (I’d have to comb through the posts)

Reply | Quote

[EP]

so far Brocktoon I have not seen this happen on Win10 Home

I have checked for updates for a full two weeks on my father’s Toshiba Satellite C55Dt-A (2013) laptop running Win10 Home v1909 since May 27 (wifi connection is not metered) and version 2004 still is not being offered thru WU on there

guess my dad’s Toshiba 2013 laptop is still not worthy to receive 2004 (and I already updated many of the drivers on there including AMD Radeon 8400 graphics & Realtek HD Audio) after checking for updates from WU for 14 straight days

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

1 user thanked author for this post.

Brocktoon

Reply | Quote

[EP]

doh!

looks like I forgot to UN-pause the updates on the Toshiba laptop. I click on the Resume Updates button a few hours ago today 6/11 and now Windows Update is offering the version 2004 feature update WITH the Download and Install option listed – no “forced” upgrade to v2004 on there running Win10 v1909 Home edition on the Toshiba laptop

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

1 user thanked author for this post.

Brocktoon

Reply | Quote

If this is all true, as a W Home-user you are in a pickle.

a) If you don’t want to install monthly updates promptly, you have to click on Pause updates. But if you do resume at some point, you”ll likely get 2004 as a ‘bonus’

b) You do not click Pause updates and so will receive the monthly updates immediately, with all their dangers. But you should get the 2004 Download and install-option

Not the 2 best things to choose between
 

~Annemarie

Reply | Quote

EP wrote:

no “forced” upgrade to v2004 on there running Win10 v1909 Home edition on the Toshiba laptop

It seems only Pro have been hit.

1 user thanked author for this post.

Elly

Reply | Quote

Whoops, posted without signing in …

Yep … it’s probably still too early to tell, but another post mentioning Pro … https://www.askwoody.com/forums/topic/are-win10-version-1909-users-being-pushed-onto-version-2004/#post-2271751

I’m wondering if we may looking at an issue with Pro and not Home.

Reply | Quote

Question 1: What can/should I do to further delay/defer any and all updates to 2004?

Windows update shows that the 2004 update is available, but my device is not quite ready for the update. Also appearing on screen is “Windows Update might update itself automatically first when checking for other updates.”

I have 2 rigs both running Win 10 Pro v1909 and am concerned about when my Pause Updates expires this Saturday, 6/20, and Monday, 6/22 on the other…I only have a few days to hopefully get things figured out.

Updates are paused until 6/20 and 6/22, and I’m not currently “up to date.”
Feature updates are deferred for 365 days.
Quality updates are deferred for 30 days.

I was unable to squirrel away a clean 1909 iso file using Media Creation Tool, however have a clean copy of 1903.

Question 2: Is there any way at this time, with the situation outlined above, where I can get the security patches up to date, and not install 2004?
Any other advice or recommendations are appreciated. Thanks!

ASUS TUF SABERTOOTH Z170s Motherboard, Intel i7-6700k CPU, Corsair 32GB DDR4-3200 RAM, ASUS ROG STRIX GeForce GTX-1070 Video Card, 1x BPX M.2 240GB NVMe SSD, 1x Samsung 850 EVO 1TB SSD, 2x WD Black 6TB HDD, Windows 10 Pro 64bit v1909

Reply | Quote

Windows is not supposed to update to 2004 unless you click on the install button, but some Pro machines seem to have updated regardless. There is no solution at present, so backup and keep your fingers crossed.

If you do get the update you should be able to roll it back immediately – and let us know.

cheers, Paul

Reply | Quote

Please read AKB2000016, particularly Section4 about using Pause and Deferrals. Unless MS changes things, you will probably get v2004 when the Pause runs out or you “Resume Updates.”

It is possible (maybe, a chance) that this might avoid your getting v2004 downloaded and installed if you do it before the Pause end date. This works for Win10 Pro only (no Group Policy in Home).
+ Disconnect from the Internet.
+ Set Windows Update settings per Section 4 of AKB2000016, set Quality deferral with the pulldown in the GUI to 0 days. (Feature deferral = 365, Automatic Updates = Enabled, value 2 (notify download/install). There are screenshosts below in AKB2000016. Do not use Windows Update for business – everything “not configured”. Set the deferrals in the Settings App\WU\Advanced Settings. The only deferral settings should be now done with the pulldowns in the WU\Advanced Settings and the only GP setting should be the “2.”
+ Resume updates – it won’t find the updates b/c you are disconnected, but it should reset the Pause. Do not turn Pause back on.
+ Reconnect to the Interned and let the computer check for updates on its own (may take a day). The “2” setting in GP should keep the updates from downloading automatically. You should have to click on the “Download button.” If the 2004 Feature Update shows up, use wushowhide to hide it.

Try it on one computer first. If it works, do the other.

 

1 user thanked author for this post.

Paul T

Reply | Quote

Speed Racer wrote:

Feature updates are deferred for 365 days.
Quality updates are deferred for 30 days

As long as Feature updates are deferred to 365 days (and 2004 isn’t compatible with your PC) you have nothing to worry unless Microsoft disregards your deferrals.
In any case you should have:
1. a copy of 1909 pro ISO
2. a full backup image backup of your system.

Reply | Quote

I have a Windows 10 Pro Version 1909 desktop PC.
After waiting a week after Patch Tuesday I decided to apply the June updates today.
I was a bit nervous about:
1) Getting a forced upgrade to Win 10 Version 2004.
2) My printer no longer working (HP ENVY 5640 attached via USB).

I am glad to report that I seem to have survived:
1) I was not automatically upgraded to Windows 10 Version 2004 or offered it as a download.
2) My printer still seems to work.

In case it is useful to others this was the sequence of actions that I carried out.

Settings, Update & Security, Advanced options:
The initial settings were –
Pause updates until 19 June 2020.
Feature update deferred by 365 days.
Quality update deferred by 30 days.

I changed quality update deferral to 0 days and then clicked the Resume updates button.

KB4560960 and KB4561600 were downloaded and installed.
I rebooted the PC.

Before connecting to the internet I went to Settings, Update & Security, Advanced options
and set:
Pause updates until 21 July 2020.
Quality update deferred by 30 days.

AP

Reply | Quote

Mine got pushed, woke up to a “Pending Restart for Windows 2004”. Didn’t click anything, it just downloaded all by itself.

https://i.postimg.cc/J4TK7YNR/ver-2004.png

Reply | Quote

Pro or Home?
Did you update anything else?
When was the last time you updated / used the machine?

cheers, Paul

Reply | Quote

Born has written this recent post about more “forced” updates to 2004:
https://borncity.com/win/2020/07/24/windows-10-zwangsupdate-auf-2004-fr-altversionen/

Reply | Quote