Microsoft re-re-re…releases KB 4023057, the “blast a way to the next version” patch

Topic

New Reply

And here we go again. Microsoft has just re-released KB 4023057, the “Update to Windows 10, versions 1507, 1511, 1607, 1703, 1709, 1803, 1809, 1903, a
[See the full post at: Microsoft re-re-re…releases KB 4023057, the “blast a way to the next version” patch]

7 users thanked author for this post.

Norio, rontpxz81, geekdom, Tom-R, Great Lake Bunyip, jburk07, Microfix

Reply | Quote

Replies

I’ll be contrarian.  If you DO see it you need to evaluate your machine.  That’s a sign that you don’t have enough space, networking is messed up, corruption is seen on the machine.  Maybe you want to bite the bullet and rebuild your PC.  It’s not offered up to all, only those that it’s having issues offering the feature release to.

Susan Bradley Patch Lady

6 users thanked author for this post.

CADesertRat, Great Lake Bunyip, jburk07, WildBill, Microfix, woody

Reply | Quote

So if this patch is offered, your system OS is non-compliant to MSFT’s AI control regime?
Even if you attempt to thwart their intentions, ‘Thou shalt not evade the upgrade’.
Monthly CU with embeded kb4023057 coming to your systems soon..
kb2952664 ring any bells?

Keeping IT Lean, Clean and Mean!

3 users thanked author for this post.

lanceboil, madquack, rontpxz81

Reply | Quote

• This update may request your device to stay awake longer to enable installation of updates.

  Note The installation will respect any user-configured sleep configurations and also your “active hours” when you use your device the most.

• This update may try to reset network settings if problems are detected, and it will clean up registry keys that may be preventing updates from being installed successfully.
• This update may repair disabled or corrupted Windows operating system components that determine the applicability of updates to your version of Windows 10.
• This update may compress files in your user profile directory to help free up enough disk space to install important updates.
• This update may reset the Windows Update database to repair the problems that could prevent updates from installing successfully. Therefore, you may see that your Windows Update history was cleared.

I’ve not seen it offered to my contrarian Lenovo that for the longest time was complaining about hard drive space if I ran the logging to see why it wasn’t being offered.

Susan Bradley Patch Lady

2 users thanked author for this post.

rontpxz81, Great Lake Bunyip

Reply | Quote

so tempted! have spare cloned drive want to try on. SO FRUSTRATED🤒

Should I go for it?

Running 2012 stock intel I5 with 8gig lotsa drive space no grfx card

https://www.cnet.com/products/hp-compaq-elite-8300-sff-core-i5-3470-3-2-ghz-4-gb-250-gb-c5m14usaba/

be well, breathe and honor wabi sabi

Reply | Quote

Susan Bradley wrote:

That’s a sign that you don’t have enough space, networking is messed up, corruption is seen on the machine.

I have Win10/Pro, version 1909, FU=365 days, QU=0 days, GPE #2–notify download/install. I have the August 11 patches hidden until MS-DEFCON=3+

KB 4023057 showed up in my WU queue on Aug 20 and I hid it, following the advice of abbodi86 – #2290269.

I don’t think it showed up in the queue because I have these problems. As a matter of fact, on June 27 I received the announcement that my machine was not yet ready for 2004 and then on July 27, that announcement disappeared, which I assume means that my machine is now ready. I did DISM’s ScanHealth and sfc /scannow on August 26 and no problems were reported. I am using only about 30% of my 512GB SSD.

All signs are that I am ready for 2004, that is, were it not for FU=365 days. I think KB 4023057 appeared because it wants to override this FU setting.

5 users thanked author for this post.

ceruleandaze, woody, rontpxz81, jburk07, abbodi86

Reply | Quote

I get it on 1903 Enterprise, but not Pro or Home
go figure 🙂

setting TargetReleaseVersion policy/registry prevent it

1 user thanked author for this post.

geekdom

Reply | Quote

abbodi86 wrote:

setting TargetReleaseVersion policy/registry prevent it

So if I remove TargetReleaseVersion, KB4023057 might show as an update?

Carpe Diem {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.1778 x64 i5-9400 RAM16GB HDD Firefox115.0b2 MicrosoftDefender

Reply | Quote

On a system with Win10 1903 Enterprise, I have the TargetReleaseVersion hack in place, and KB4023057 showed as an available update, which I then hid.

Reply | Quote

Susan Bradley wrote:

It’s not offered up to all, only those that it’s having issues offering the feature release to.

Microsoft has issues offering 2004 to my 1909 pro, yet I don’t have any of your mentioned “blocks”.
It is just a Lenovo y530 with 16GB RAM, 256GB NVMe SSD, 1TB HDD…with plenty of free space.
I don’t remember getting KB 4023057 (not on the list of installed/uninstall Patches).

1 user thanked author for this post.

rontpxz81

Reply | Quote

This patch sometimes shows up as an installed program – not an update. Check in your installed programs.

1 user thanked author for this post.

rontpxz81

Reply | Quote

Windows 10 KB4023057 x86/x64 was first released May 30th 2017 replacing kb4022868 with multiple revisions ever since.
Windows Setup Remediation

Expediteupdater.exe
Qualityupdateassistant.dll
Sedplugins.dll
Uhssvc.exe
Unifiedinstaller.dll

Looks like v2004 won’t be getting this.
Reading between the lines, there will no doubt be a big push to v2004 from older versions in the near future.
Extended support for 1803 seems IMO, more like a gimmick to trap the unwary..better check your settings.

Keeping IT Lean, Clean and Mean!

Reply | Quote

I see 4023057 in WUShowhide and in the Windows 10 Windows Update not because I have a corrupted or mis-configured PC. I have Windows 10 1809 Home and installed a third-party blocker that takes out the WaaSMedic completely.

I get no Windows 10 monthly or feature updates unless I go looking for updates. I install the patches manually while disconnected from the Internet. I may upgrade to 1909 six months after the 1809 End-of-life.

1 user thanked author for this post.

rontpxz81

Reply | Quote

Susan was right in that 4023057 was offered because Microsoft sees my workstation as misconfigured for its purposes – to upgrade my workstation to a feature update when Microsoft sees fit.

2 users thanked author for this post.

madquack, rontpxz81

Reply | Quote

can i dowload vis MS catalogue?

be well, breathe and honor wabi sabi

Reply | Quote

The last one in the Catalog is June 2020.

Reply | Quote

PKCano wrote:

The last one in the Catalog is June 2020.

read abbodi86 – #2290150 for why the August release is not in the MS Catalog.

Reply | Quote

Using WUShowHide, I saw 4023057 waiting in the wings ~ but this was on a laptop that is already running v2004. I just hid it as usual and proceeded with the monthly CU.

1 user thanked author for this post.

jburk07

Reply | Quote

I immediately hid the KB4023057 update with wushowhide.diagcab when it was offered thru WU on my dad’s Toshiba laptop running Win10 v1909 home (that’s 1909 not 1809)

1 user thanked author for this post.

rontpxz81

Reply | Quote

So, if I’m following this correctly, since I have GP set to defer 2004 and then we hit Defcon 3 for August patches, I may get KB 4023057 in the mix of August patches. Is that correct?

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

Reply | Quote

I was already offered KB4023057 earlier this month, and simply hid it with wushowhide and then cleared the update queue, and now I’m no longer offered it.

I’m on v1909 with Feature updates deferred for 365 days and Quality updates not deferred at all.

2 users thanked author for this post.

rontpxz81, jburk07

Reply | Quote

Coldheart9020 wrote:

I was already offered KB4023057 earlier this month, and simply hid it with wushowhide and then cleared the update queue, and now I’m no longer offered it.

But, it’s still in wushowhide, right?

Reply | Quote

WCHS wrote:

But, it’s still in wushowhide, right?

Yes, but hidden. It’s not once made its way back into the Windows Update cache, however, since it was hidden.

1 user thanked author for this post.

rontpxz81

Reply | Quote

Just updated 1 of my computers with Aug. updates and KB 4023057 was installed. I do not have the registry hack in place but I do have Target 1909 set in Group Policy along with Feature Updates at 365 days. Today’s update didn’t change any Group Policy settings.

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

Reply | Quote

KB 4023057 is not a Feature Update, so is not included in Feature deferral = 365, nor in the “version holder” TargetReleaseVersion = 1909.

You have to hide it with wushowhide before it installs.

Reply | Quote

Interestingly my AMD 2700X didn’t have KB 4023057 offered at all.

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

Reply | Quote

Just noticed today that KB 4023057 is only showing up on my older Intel machines and never showed up on my AMD machine built in Sept. 2019 (although it showed up in the past).

Another thing is that on the Intel machines that got KB 4023057, when going to Progs. & Features, only the old instances of KB 4023057 are listed. There are no new dates behind the older entries so I’m guessing that this is just a refresher in case you never got it in the past.

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

Reply | Quote

No KB4023057 here.

Carpe Diem {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.1778 x64 i5-9400 RAM16GB HDD Firefox115.0b2 MicrosoftDefender

Reply | Quote

Well I just found KB 4023057 lurking as available on my laptop with Win 10 Pro 1909.

This is a month old (new) factory refurb Dell with a fresh out of the box install of Win 10 Pro 1909 OEM, that hasn’t been offered 2004 yet.

I think I will make an image this weekend, and then go for it! 🙂

Windows 10 Pro 22H2

Reply | Quote

What if you have the TargetReleaseVersion registry setting?

https://www.ghacks.net/2020/06/27/you-can-now-set-the-target-windows-10-release-in-professional-versions/

1 user thanked author for this post.

ceruleandaze

Reply | Quote

Recall another person’s prior post on Ask Woody referring to Win 10 as a “rolling train wreck”. My experience for last 6 months has been similar. My plan is to keep mine permanently with V 1909, updating Tbird, Ffox and Seamonkey, and also Vivaldi; and switch permanently to my Linux Mint 20 Cinnamon Ulyana.
…..
My 1909 machine is build 18363.959: Win 10 Pro. My target version has been set at V1909 for a month or more, in the registry and in Group Pol. In spite of that, Win has seemed insistent to get 4023057 on my PC, and my experience has been that WUshowhide was unreliable at various times, as to whether it would block the KB, or not.
…..
See my prior posts on AW, post nos. 2290474 and 2291048.

https://www.askwoody.com/forums/topic/another-round-of-optional-non-security-c-d-week-patches-for-win10-1909-1903-1809/#post-2290474
and later post 2291048, immediately following on that page.

And Susan: I ~have~ evaluated my Win10 Pro PC since I bought it new, in March 2020. ~That~ is why I’m so intent on moving to Linux. PS: I have a number of port. HDDs in use; Many TBs of space available, in addition to the small Solid-State HDD it came with.

I am liking Linux steadily and more, because it_just_works. Good luck!

2 users thanked author for this post.

rontpxz81, jburk07

Reply | Quote

RamRod wrote:

This patch sometimes shows up as an installed program – not an update. Check in your installed programs.

Thanks.
Got it on Apr 3 2020. 🙂

Reply | Quote

[hansR]

I’m running 1909 x64 Pro Build 1016; Target version set to 1909, Feature updates deferred for 365 days and Quality updates set to 15 days, GPE #2–notify download/install.

I was never offered KB 4023057, neither wushowhide nor WU.

But silently (!) – on Aug 22 – “Microsoft Update Health Tools” appeared in the list of my installed programs, and shows up in Update History as KB 4023057.

GPE rules remain unchanged, as well as registry settings. no visible change.

Should I remove it ?

(Fun fact: On my HP notebook and my Virtual Box based instances of 1909 – both on build 1016 – KB 4023057 does NOT show up)

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

• This reply was modified 2 years, 9 months ago by hansR.

1 user thanked author for this post.

rontpxz81

Reply | Quote

In addition to this question of “should I remove the update,” is it enough to uninstall “Microsoft Update Health Tools” from the Programs list? Or are further measures required?

Reply | Quote

System version 1903   gpedit
Computer Configuration > Administrative Templates > Windows Components > Windows Update
Configure Automatic Updates = Disabled
and
Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business
Select when Preview Builds and Feature Updates are received = Enabled 365
Select when Quality Updates are received = Enabled 30
Manage preview builds = Enabled Disabled
After receiving 2020-07 cumulative update shows up another policy
Select the target Feature Update = Enabled 1909
So windows update installs 1909 and keeps the system at version 1909

Reply | Quote

[geekdom]

A quick test:

• TargetReleaseVersion=1909 was set to TargetReleaseVersion=2004
• Rebooted and looked for updates using WUMgr
• Featured 2004 showed available in WUMgr
• KB4023057 not anywhere including installed programs.
• TargetReleaseVersion=2004 was set to TargetReleaseVersion=1909
• Rebooted and looked for updates using WUMgr
• Featured 2004 not shown in WUMgr

Conclusions:

• My system is ready to go full bore with 2004 anytime I set TargetReleaseVersion=2004
• KB4023057 not necessary on my system

Carpe Diem {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.1778 x64 i5-9400 RAM16GB HDD Firefox115.0b2 MicrosoftDefender

• This reply was modified 2 years, 9 months ago by geekdom.

3 users thanked author for this post.

ceruleandaze, Paul T

Reply | Quote

Can someone enlighten me re “security intelligence update for microsoft security essentials” (Windows 7)
I can SEARCH for updates and almost always another one of these will pop up – usually saying they were created TODAY. I got 1 yesterday of 20mb then several more showed up later. I install all of them and don’t have a problem. I think most use recycled KB #s.
But do they really constantly add to these updates…like hourly?

 

 

Reply | Quote

These are updates to your anti virus / malware defender .
Updates are coming couple of times each day.

https://www.microsoft.com/en-us/wdsi/defenderupdates

1 user thanked author for this post.

RockJohny

Reply | Quote

Ok, I acknowledge my technical understanding of things MS seriously lags behind most of the techies on this forum…so allow me to pose a question, please.  (Win 10 1909 Home)

Does KB4023057 supersede the metered connection hack to stop updates?  Likewise, does it blow away the “pause updates” settings?  If it does either of these things, then I clearly understand why I don’t want this update, since I want to update to 2004 at a time of my chosing.

But if it does neither of the above, and if it corrects issues with my computer (that I may not be aware of)  blocking a feature update that I will eventually need and want, why wouldn’t I want KB4023057?

From the list of functions performed by this update per Susan B’s post above, seems like things that I would want fixed, but not necessarily comfortable doing myself.

I not being contrary here…just in need of educating.

Thanks!

Reply | Quote

Windows 10 1909 Home and I’ve set the laptop to pause updates until Sept 2020, waiting on Aug/2020 DEFCON3, but I do not want 10/2004. So wushowhide is something that I’ll need to learn how to use. And does anyone have a link with instructions on how to download and Install/Extract this tool and use it to block any feature/other updates.

As is on my newest laptop, that’s running 10/1909 Home, I am rarely using that laptop currently and instead have been using my older Win 7(EOL)/Mint 20 and Windows 7(EOL)/Mint 19.3 dual boot laptops for daily online usage.

But as far as having my laptop force updated to 10/2004 is not what I want until closer to May 11, 2021 when 1909’s support ends.

Reply | Quote

Download wushowhide.diagcab from Microsoft.
Place it on your desktop.
Double click on it, click on “Advanced,” UNCHECK “make changes automatically.”
“Hide” will give you a list of the available updates you can hide BUT wushowhide uses the same Windows Update Service that Windows Update does. So if you have Paused updates so they don’t show up in Windows Update, they won’t show up in wushowhide either.
“Unhide” speaks for itself.

2 users thanked author for this post.

ve2mrx, woody

Reply | Quote

So will wushowhide show the 2004 feature update when my feature deferral period runs out? I’m on 1909, Pro, with group policy set to 2 and feature update deferred for 200 days. I don’t use metered connection or pause. I use wushowhide to hide quality and/or other updates when needed (KB4023057 showed up earlier this month and I hid it). For some reason I had thought that the feature update wouldn’t show up to be hidden in wushowhide.

Linux Mint Cinnamon 19.3
Group A:
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux, mostly offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro, mostly offline
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux

Reply | Quote

2004 has been out for about 95 days as of Aug 30. It should show up available in WU after 105 more days.

Reply | Quote

[jburk07]

Right, I understand that. I was wondering whether 2004 will show up in wushowhide *after* the 200-day deferral period is over. Assuming there are no other problems with my computer that might make it “unworthy.”

Linux Mint Cinnamon 19.3
Group A:
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux, mostly offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro, mostly offline
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux

• This reply was modified 2 years, 9 months ago by jburk07.

Reply | Quote

wushowhide and Wundows Update both use the same Windows Update Service to scan for updates. So they should both show the same thing (barring hidden updates) after WU rescans on its own.

2 users thanked author for this post.

Coldheart9020, jburk07

Reply | Quote

Thanks for this info, PKCano.

Just an fyi cross-reference to anyone who might be reading this later:

Note the additional information provided by abbodi86 in this exchange with KYKaren on another thread, in posts #2292596, #2292609, #2292935, #2293051, and #2293054.

Summary, as I understand it:
If Feature Update 2004 shows up in Windows Update with the Download and Install link, it apparently won’t show up in wushowhide (see posts #2292596 and #2292609).

However, if you set TargetReleaseVersion to 2004 (and possibly also if you’ve set the feature update deferral period and it has ended – not entirely clear), it will show up without the Download and Install link, and it *will* show up in wushowhide (see posts #2292935, #2293051, and #2293054).

Linux Mint Cinnamon 19.3
Group A:
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux, mostly offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro, mostly offline
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux

1 user thanked author for this post.

Reply | Quote

It’s an “Optional” update if you don’t ask for it. So it ends up in the “download and install now” section

If you ask for it (by ending Feature deferral, by choosing TargetVersion, or checking for updates”) it will show up in Windows Update for download/install.

2 users thanked author for this post.

jburk07

Reply | Quote

Ah, thanks for the clarification.

Linux Mint Cinnamon 19.3
Group A:
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux, mostly offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro, mostly offline
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux

1 user thanked author for this post.

Reply | Quote

On Windows Home you need to set your internet connection as “metered” to prevent auto download / install of updates. Then when you remove the pause wushowhide will be able to see available updates and you can hide if required.

Whatever you do, do not click “check for updates”. That will download and install everything regardless. Wait for Windows to perform a check on its own.

cheers, Paul

Reply | Quote

Having never encountered KB 4023057 on a particular PC, how to Pr-Emptively BLOCK it from ever getting installed.

WU Showhide will only show items already pending to be hidden.

 

Reply | Quote

I just started setting up a brand-new Dell Precision 3630 workstation and installed Windows 10 1903 Enterprise.  Regarding what the Patch Lady said, there’s lotsa space, networking is fine, nothing is corrupted.  Before connecting it to the network, I disabled Automatic Updates in the group policy, and enabled the TargetReleaseVersion hack in the registry.  I installed the PSWindowsUpdate module in PowerShell and ran a command to list what updates were waiting in the wings, and I saw KB4023057.  I ran a command to hide it and it completed successfully.

Reply | Quote

Okay I need some guidance please.

Just staring the AUG Updates per the Defcon and I’ve got very different results across the PCs I’m managing (relatives home PC all hand-built).

I have my own WinPro 1909 and never got the KB402 – imaged and updated using PcKano settings no issues. Target Release at 1909.

* WinPro 1903 Machine has been left on by user and not shutdown/restarted for a few days/weeks. Have PcKano settings and Target release 1909. 1909 Not offered yet.

* Used Wushowhide after image and KB402 avail so I hid it.

* BUT Settings-Windows Update is already showing Kb402 for download and install. Aug KB4565351/4569751 avail as normal.

I am hesitant to allow a normal Download with KB402 sitting there so I plan to do a manual update with the Aug KB instead.

Q. Will KB402 move to hidden after manual restarts for Aug KB? Or is it stuck there because I didn’t hide it soon enough as soon as it was released by MS.

Q. Any chance the 1903 (all 4 machines) is what is kicking the KB402 harder? Should I go ahead and get them all up to 1909 now in order to have TargetRelease hold off 2004 that much “stronger”?

Reply | Quote

darynman@gmail.com wrote:

* WinPro 1903 Machine has been left on by user and not shutdown/restarted for a few days/weeks. Have PcKano settings and Target release 1909. 1909 Not offered yet.

If you have Feature Deferral set at 365 days, you will not see 1909 until 365 days have passed. If you want 1909, set the Feature deferral to 200-250 days OR set the TargetReleaseVersion to 1909 – BUT NOT BOTH.

Yes, you should move all in your care to v1909. v1903 will be EOL on Dec 8.

darynman@gmail.com wrote:

Q. Will KB402 move to hidden after manual restarts for Aug KB? Or is it stuck there because I didn’t hide it soon enough as soon as it was released by MS.

If you hid KB 4023057 (please use the WHOLE KB number), it should be removed from the queue the next time WU scans for updates on it’s own. Use wushowhide to verify it is hidden.

1 user thanked author for this post.

Reply | Quote

Okay, Thanks,

For some reason it is only the one PC that popped the KB4023057 even though they all have the same upgrade settings.

I’ll get ready to push them all to 1909 using your notes.

 

• This reply was modified 2 years, 9 months ago by .

Reply | Quote

FYI it sneaks itself as “Windows Update Assistant” in Apps & Features, not Installed Updates! very very sneaky!

Reply | Quote

Save_Us_from_MS wrote:

FYI it sneaks itself as “Windows Update Assistant” in Apps & Features, not Installed Updates! very very sneaky!

I installed KB4023057 on 1909 Pro. I don’t have “Windows Update Assistant” in Apps & Features.
I have ‘Windows update for x64 KB4023057’ and ‘Microsoft Update Health Tools’ with no KB.

Reply | Quote

And now they’ve re-re-re-re-released it.  The current-version KB article is full of “and this update might also change THIS, if deemed necessary”.

Reply | Quote

For those curious about it, it will show up as “2021-05 Update for Windows 10 Version XXXX (where XXXX is your current version of Windows such as 2004 or 20H2) for x64 (or x86)-based systems (KB4023057)”.

So, if you’ve already hidden it since the end of May (and it’s titled as described above) then you’re all set for now. Otherwise, if the version of KB4023057 begins with “2021-03…”, then you might want to keep your eyes peeled for the 2021-05 version because it will be showing up on your machine for installation soon.

If you look in Windows Update under “View update history” and find it, you can then click on the blue link in the upper left corner of the window that says “Uninstall updates” to uninstall it if you didn’t want it installed in the first place. Please see @PKCano ‘s post right below this one.

If hiding updates is something you’d like to pursue, there are three candidates to consider for the task: wushowhide, which is again available from Microsoft after a brief absence, along with two third party tools, WUMgr and WUMiniTool (or WUMT for short). Which one you should use is a matter of personal preference.

Reply | Quote

KB4023057 installs as an App, “Microsoft Update Health Tools,” not as an Update.
It is not listed under “Installed Updates.”

To uninstall it, look in the Control Panel\Programs & Features or in the Settings App\Apps. Look for “Microsoft Update Health Tools,” right click, and uninstall.

1 user thanked author for this post.

Bob99

Reply | Quote

Thanks for the clarification! It’s been quite some time since I had to worry about it, so I was going off of memory from what I had to do to get rid of its first installation. Since the first installation and subsequent removal, I’ve successfully been hiding it for each quarterly or bi-monthly (in a couple of cases) appearance.

Reply | Quote

This seems like as good a place as any to ask the following question:

I wonder if MS will use KB4023057 itself, or if they’ll use another version of it, to grease the skids for those of us on the latest version of 10 (21H2 by then) to make the jump to 11?

I mentioned 21H2 because as of this writing, 11’s stated release is in time for the holiday season at year’s end, which sounds like it will be after 21H2’s release.

Please feel free to refresh my memory if I’m wrong, but wasn’t KB2952664 (IIRC) used for the same sort of purpose in Windows 7 that KB4023057 is currently being used in Windows 10?

Reply | Quote

If you read the MS Support Page for KB4023057, you can see exactly what it does. It basically prepares your computer for an upgrade.
Just like KB2952664 for Windows 7, it has been issued over and over. And each iteration, being a different version, is again offered through Windows Update, usually within a couple of months before a new version is released, but sometimes in between.

Reply | Quote

PKCano wrote:

If you read the MS Support Page for KB4023057, you can see exactly what it does. It basically prepares your computer for an upgrade.

When one is ready to install the next Feature Update, do you recommend letting KB4023057 go through?

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

Reply | Quote

I have never allowed it to install on my machines, although others have.
I want to know where my settings are. I don’t want MS changing things for me.

But the choice is yours. And others have different opinions.

1 user thanked author for this post.

Cybertooth

Reply | Quote

I always let KB4023057 through. But I also always take frequent system images so that an update that causes disruption can always be eliminated by rolling back to a previous image.

Windows 10 Pro 22H2

1 user thanked author for this post.

Cybertooth

Reply | Quote

Bob99 wrote:

I wonder if MS will use KB4023057 itself, or if they’ll use another version of it, to grease the skids for those of us on the latest version of 10 (21H2 by then) to make the jump to 11?

Set TVR (GP or registry hack) to 21H1 and don’t worry about W11.

Reply | Quote

PKCano wrote:

KB4023057 installs as an App, “Microsoft Update Health Tools,”

My notion of app is of a program that user executes.
Windows exposes no way to execute this.

Reply | Quote