Still running Win10 v1809 or earlier? Watch out for KB 4023057!

Topic

New Reply

The Infamous “Let us help you get upgraded” patch KB 4023057 has once again raised it’s ugly head. Each time it is re-released, the newer version make
[See the full post at: Still running Win10 v1809 or earlier? Watch out for KB 4023057!]

10 users thanked author for this post.

STBC Mapper, Norio, Fred, Berserker79, abbodi86, TJ, ve2mrx, GreatAndPowerfulTech, Kirsty, Bluetrix

Reply | Quote

Replies

[PerthMike]

“Still”? We only just rolled 1809 out in the last month. LOL

Nice to see though, that  it’s not being offered via WSUS. Carry on…

No matter where you go, there you are.

• This reply was modified 3 years, 3 months ago by PerthMike.

Reply | Quote

I didn’t know that. I didn’t know that! And I have my connections as metered on!!

I miss Windows XP...

Reply | Quote

Sorry for the double post but it seems that having metered on didn’t allowed 1909 to be downloaded.

I even managed to hide them.

I miss Windows XP...

Reply | Quote

My tip for this is to always disable Windows Update, and when you have to install Updates or things from the store , enable them, ACTIVATE, metered connection then, Wushowhide

it has worked so far for me.

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

Reply | Quote

… if only that was an option that worked in Windows 10 (without the machine taking it upon itself to ignore all settings to the contrary – private beef, sorry)

Reply | Quote

This patch is a bit too intrusive for my taste and I always avoid it like a plague. Thinking about how it works, I can’t help thinking that it is the closest we get to an officially sanctioned malware… 🙂
Sadly, skipping this patch is not enough to prevent a forced Feature update.

Reply | Quote

[PerthMike]

PerthMike wrote:

“Still”? We only just rolled 1809 out in the last month. LOL

Nice to see though, that  it’s not being offered via WSUS. Carry on…

• This reply was modified 3 years, 3 months ago by PerthMike.

1809 EOL in 3 months, May 12, 2020 . Enterprise and Education on May 11, 2021.

Reply | Quote

Berserker79 wrote:

Sadly, skipping this patch is not enough to prevent a forced Feature update

Metered connection (both lan and wi-fi) + hide with wushowhide.diagcab will prevent all updates.

1 user thanked author for this post.

Berserker79

Reply | Quote

Thanks Alex. That’s exactly my strategy to avoid unwanted updates (including Feature updates). 🙂 The annoying part with this strategy is that every time a new build of the latest Win10 version is released we need to run wushowhide to hide the unwanted Feature update. Still better than being forced to updatewhe I don’t want to. At least, wushowhide gives me a measure of control on the updates.

Reply | Quote

Despite Woody’s suggestions to upgrade to 1903 or 1909, I’m still running version 1809 Pro (currently Build 17763.973) and happy to be so – given the problems with Search and KBs 4524244 and 4532691 on those versions. (I hope to be able to wait with upgrading to 1903/1909 until MS has solved these problems.)

Updates are controlled and deferred by gpedit.msc settings. I also got WUMT and WuMgr, but only use them nowadays to see what/if something is being offered.
Today I checked WUMT and it came up with KB 4023057, so I hid it.

Don’t know if these actions will prevent MS to push KB 4023057 onto my system though…

1 user thanked author for this post.

PerthMike

Reply | Quote

Same here, still prefer to stick to 1809 for the same reasons you mention. I understand that Woody suggested to move to 1903 because of the “defer updates” feature, but I still prefer to use wushowhide to delay unwanted updates because I feel like it gives me more control on the update process.

Anyway, from past experience on 1803, so far wushowhide was always successful to avoid KB4023057 from being installed on my system. However, you still need to manually run it every once in a while to check whether that pesky updates is being pushed. It is usually issued on a monthly basis during Patch Tuesday, but occasionally pops out on other weeks as well (like this week).

1 user thanked author for this post.

PerthMike

Reply | Quote

[PerthMike]

Alex5723 wrote:

PerthMike wrote:

“Still”? We only just rolled 1809 out in the last month. LOL

Nice to see though, that  it’s not being offered via WSUS. Carry on…

• This reply was modified 3 years, 3 months ago by PerthMike.

1809 EOL in 3 months, May 12, 2020 . Enterprise and Education on May 11, 2021.

Actually, since most of us here do not do updates until Woody changes the defcon rating, which is usually the following month just before Microsoft issues new updates, so we have until around the middle of JUNE not May to safely run 1809 with all current security updates applied.

I only got 1809 in the end of November 2019…so not even three months I’ve had it. I won’t upgrade to 1903 until the end of support of 1809. Windows Updates never jumps a version so I assume I will get 1903 when I do allow an update.

1 user thanked author for this post.

PerthMike

Reply | Quote

As someone who does MSP-work (and automation), I have our onboarding scripts delay patching across all systems like so:

Feature updates – Delayed for 120 days

Cumulative/security updates – Delayed for 14 days

This removes most of the gotchas.

I do push this patch from time-to-time to improve feature updates as they become mature, because some systems can be very recalcitrant about upgrading.  I do like that they’re working to add system cleanup features to improve things.

Windows 10 1909 wouldn’t be half bad if they could simply fix the file search issues.  That, and I can’t stand (but this is personal) the “grouping” feature that Downloads and several other places defaults to; I’ve already got mine set the way I want it, and this overrides that until I disable it.

We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.

Reply | Quote

I’m a bit confused {as usual :)}.  This morning, windows update included the dreaded “2019-12 Update for Windows 10 Version 1809 for x64-based Systems (KB4023057)”.  I promptly “hide”ed it.    Is this the update that’ll take me to 1903?  If so, since Woody has recommended that we move on from the 2018 versions, should I just unhide it and go do it? {after I’ve done a full image backup, of course}, or should it stay hidden?

Reply | Quote

First, we are on DEFCON-2, so it is not time yet to be installing Feb updates (which is what you will get if you upgrade).

Second, unless you have Win10 Pro, and set the Feature deferral date correctly, you will get 1909, not 1903 if you unhide KB4023057 and let it roll. There is a chance it may even move you to 1909 anyway.

If you want to move to 1903, I would suggest EITHER leaving it hidden and set deferral days to get 1903 instead of 1909 (if you have Pro) OR see if you can hide 1909 with wushowhide so that the “Download and install now” shows 1903 instead (if you have Home), OR use a 1903 ISO to install.

In any case, I’d wait till Woody gives the go-ahead.

Reply | Quote

I’m on Windows 10 1809 home edition and I have never been offered 1903 as my new laptop was only started for the first time on Feb 12 of this year. So the laptop shipped with probably 1803 and once it was started 1803 was already EOL and the windows updated to 1809 and I also got the Feb 2020 KBs installed as well. But KB4023057 was installed on my 10/1809 system 0n the 18 Feb and 1809 home edition has no choice for patch delays.

Reply | Quote

You can use Metered connections then hide updates with wushowhide. You have to clear the Windows update queue after that or wait till the next time Windows checks for updates on its own for the patch to not be available.

Reply | Quote

Is there a way to get Outlook 2016 to download my e-mail with Windows being set on a metered connection? When I set it to metered, it won’t get my mail.

Reply | Quote

I don’t use Outlook, so I cannot verify this.
But there may be a setting in Outlook that allows it to ignore metered connections.

Reply | Quote

[Mr. Natural]

I had a Outlook 2016 user that kept getting a warning that O365 couldn’t update on her pc because it was on a metered connection, but she still received email. Somehow she enabled the metered setting and I turned it off to get rid of the message. I’d need to look further on those settings to know more. I believe email should still work though.

Perhaps it still worked because the AD/Azure environment we are in. Or maybe check your metered connection limit. You can adjust that.

Red Ruffnsore

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

Reply | Quote

I wonder if Microsoft is quietly pushing people towards getting everyone back on one supported version of Windows? I don’t hear much buzz on an upcoming release for Window 10 like we used to.

It makes no sense to me why we have all these different versions of Windows 10. Perhaps Windows Updates could be tested more extensively if they didn’t need to release updates for numerous versions of the same OS. Makes no sense to me from a business standpoint either.

Red Ruffnsore

Reply | Quote

Since versions 1903 and 1909 are basically the same (same CU, same SSU, etc) it is most likely where MS is going. I look for Win10 becoming a VM on Windows servers (Azure?) and you have a C2R subscription. What “Features” you have will be what extra you pay MS to turn on. I think we are headed back to dumb terminals – where we came from in my early computer days.
[/speculation]

2 users thanked author for this post.

David F, RamRod

Reply | Quote

I suspect you may be right as it guarantees lock-in and a constant income flow.

There will of course be much wailing, wringing of hands and gnashing of teeth then everything will carry on the same, as users will simply put up with it and comply.
[/speculation]

Reply | Quote

1809 will expire in May 2021 unlike 1903 which will expire this year december

Reply | Quote

Win10 1809  consumer Editions (Home, Pro, etc.) reaches EOL on May 12, 2020 unless you have Education or Enterprise Edition, which has an additional year.

Reply | Quote

as listed here

Reply | Quote

[PerthMike]

Alex5723 wrote:

PerthMike wrote:

“Still”? We only just rolled 1809 out in the last month. LOL

Nice to see though, that  it’s not being offered via WSUS. Carry on…

• This reply was modified 3 years, 3 months ago by PerthMike.

1809 EOL in 3 months, May 12, 2020 . Enterprise and Education on May 11, 2021.

Fully aware of that.

We’re on Enterprise. 🙂 We’re a govt department, and when we planned the migration (six months ago), 1903 and 1909 were still too immature to be considered stable, so we went with 1809, as that had the stability we needed at the time.

Also, this was our move-from-Windows-7 migration, so we had to be extra careful (inc. teaching users the new interface, etc.).

No matter where you go, there you are.

Reply | Quote

then stay in 1809,  You don’t have a reason to move to others versions yet, enjoy the privilege of having an enterprise version.

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

Reply | Quote

Does MS think they own your soul too? In way, this kind of update is harassment. They think they can do whatever they want and you have to say “yes, please, some more.” Just put in the shoes of most people: they don’t know how to stop this, how to defer updates, etc. And, no, Linux is not an option for them either. I hope at some point a class action or some three-letter org fines them for some billions.

Reply | Quote

Win 10 1909 still does not appear to be stabilized, given the desktop issues this month.  1903/1909 seems to be shaping up as another troubled version best avoided.  We are remaining on Win 10 1803 Pro, which continues to be problem free for us.  1803 Pro can still be updated monthly by manually downloading the monthly cumulative updates from the MS Update Catalog and applying these standalone.  Hoping that MS can produce a stable release in 2020 that we can adopt as an upgrade.

Reply | Quote

Be sure you also get the Servicing Stack if there is a new one issued. The latest for 1803 is KB4523203 which was issued in Nov 2019.

Reply | Quote

Hey, does anyone know whether the fact that at some point my Win10 1809 Home system was offered KB4023057 is the culprit for the appearance of the following message in the Windows Update screen (sorry that it is not English, anyway the message is nagging me about the fact that 1809 is nearing EOL and is suggesting to move to a newer version to keep receiving updates)?

Now, I did not install KB4023057 when it was offered last Tuesday, my connection is set to metered and I hid KB4023057 using wushowhide as soon as it showed up as an available update, but that message still showed up. My hunch is that WU detected the availability of the patch when it did its automatic check (indeed, the screen above shows a “Last checked on 18/2/2020” date and I never check for updates manually) and this was enough for the message to appear. As said, the same day I hid KB4023057 with wushowhide, but from previous experience I’ve seen that the WU screen is not refreshed right away and it can take several days before a message linked to the availability of a certain update disappears after hiding that update.

Does the above sound right to you? Is the availability of KB4023057 causing that message to appear? Or is it something else altogether?

Reply | Quote