Mystery patch KB 4023057 reappears — a “reliability improvement” to some 1507, 1511, 1607, 1703, 1709 and 1803 machines

Topic

New Reply

Here we go again. KB 4023057 has been updated, with a lengthy KB article and very little substance that I can discern. We saw it on Sept. 9 and earlie
[See the full post at: Mystery patch KB 4023057 reappears — a “reliability improvement” to some 1507, 1511, 1607, 1703, 1709 and 1803 machines]

4 users thanked author for this post.

Elly, Fred, Microfix, ch100

Reply | Quote

Replies

I have had to rehide KB 4023057 every month (each time I update through WU) for a long time on just about every version of Win10 I’ve messed with. Statement excludes Win10 v1809 since I’ve only had it installed for one day at this point.

Reply | Quote

Can confirm that no such update has appeared for W10.1809 at any time since I installed its original release with subsequent updates to the current 17763.134 build. Seems to be prep work only for versions that may currently be subject to some major “feature” update.

Asus ROG Maximus XI Code board; Intel i9-9900K CPU; 32 GB DDR4-3600 RAM; Nvidia GTX1080 GPU; 2x512 GB Samsung 970 Pro M.2 NVMe; 2x2 TB Samsung 860 Pro SSDs; Windows 10.1809; Linux Mint 19.1; Terabyte Backup & Recovery

Reply | Quote

4023067 resets your machine in advance of updating to the current version of WinX. It is a Servicing Stack Update (SSU). It updates the WinX mechanism (Servicing Stack) to facilitate updating of Windows. It’s that simple. Of course it comes out in sync with new releases of WinX – MS wants/needs/forces the entire base to move along to the current version of WinX. It includes the dreaded Update Assistant and associated payload. It adds tasks in Task Scheduler to ensure that updating occurs – usually around 1 a.m. while you are peacefully snoozing.

I am still on 1511. If I ever do decide to move to the current version of WinX I will simply turn Windows Update Service on, and accept the 4023067 SSU. Then I will become a sucker…err – Seeker.

RamRod

2 users thanked author for this post.

radosuaf, jomargon

Reply | Quote

… which is why I find it so odd that MS releases it independently of the SSU updates.

Maybe there’s just too many of them.

1 user thanked author for this post.

RamRod

Reply | Quote

I suspect there are two sequences – first a monthly issuance, perhaps as a catchall; second synchronized with major version releases. A third sequence might coincide with specific changes internal to an update that requires special support or actions during or after the download of the update. Notice that it is for ‘some 1507, 1511, 1607, 1703, 1709 and 1803 machines’. Not all. Perhaps we should check the MS documentation to get to the truth of the matter.

Reply | Quote

KB4023057 is not an update and definitely not SSU

it’s indepentent MSI package

3 users thanked author for this post.

Fred, Wibbly, ch100

Reply | Quote

It is “fixit” tool 🙂

1 user thanked author for this post.

Wibbly

Reply | Quote

Notes about this update
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.

So why haven’t MS baked KB4023057 into the ISO or ‘feature Upgrade’ if it’s important during installation?

Windows - commercial by definition and now function...

1 user thanked author for this post.

Fred

Reply | Quote

Microfix wrote:

So why haven’t MS baked KB4023057 into the ISO or ‘feature Upgrade’ if it’s important during installation?

There are a whole bunch of “home remedies” out there on the Internet for solving various types of problems, including resetting the TCP/IP stack, deleting the local Windows Update catalog, restarting services, finding some extra disk space, etc.etc.  Microsoft figures that most of these could be done automatically instead — and they’re right.  Thing is, you can’t actually build that functionality into Windows Update itself, because if the problem is with a corrupted Windows Update….. well…. then what?

 

1 user thanked author for this post.

ch100

Reply | Quote

I think KB4023057 should enter Guinness World Records for how many versions it had 🙂

Reply | Quote

Can it beat KB2952664 (per Win10 version)? 🙂

2 users thanked author for this post.

Elly, RTEsysadmin

Reply | Quote

26th re-release for KB4023057

Windows - commercial by definition and now function...

1 user thanked author for this post.

RTEsysadmin

Reply | Quote

I’m pretty sure it’s reached 40 😀

3 users thanked author for this post.

flackcatcher, ch100, woody

Reply | Quote

This update was downloaded and installed on my HP Omen 7th generation core i7 7700 laptop with 8 Gb RAM and a 128 Gb SanDisk SSD running Windows 10 1803 build xxxxx.407 last week, a laptop that I only use for a couple hours every other day in the evening hours. I have not been offered (if you can call it that) the upgrade to version 1809 yet. This is the first time I have seen this update in the almost a year that I’ve had that laptop, which came with version 1709. The odd thing to me at least is that KB4023057 is the only KB that has ever appeared on the Programs and Features page and been listed as an installed software program or application like the VLC media player or some/any other downloaded and installed software package or application. It is right there listed as downloaded and installed software. But it is not listed as a program on the start menu under any Windows or Microsoft heading. Odd. I am assuming now that I will be upgrading to version 1809 soon (I have Windows 10 Home), probably Tuesday, whether I want it or not (since having a Windows 10 OS presumably means that my ownership of this one thousand dollar device is by definition shared with Microsoft). <smh>

 

2 users thanked author for this post.

RTEsysadmin, Fred

Reply | Quote

anonymous wrote:

KB4023057

@anonymous : Exactly the same here with this “update”, it was installed on my HP Pavilion 6th generation core i7 6500 laptop with 8 Gb RAM and a 128 Gb SanDisk SSD running Windows 10 1803 build xxxxx.407
I noticed 3 “flashes” of my screen, looked like a popping up of a Command-window;  this update KB4023057 is in the software installation list too, NOT in the historylist of the “Quality Updates”
=> noticed that my Prefetcher settings in the registry was set to “applications+boot” files (before it was set to “bootfiles only”, so it is back again right now, manualy set again)…

Some unexplained magic here for me

* _ ... _ *

Reply | Quote

KB4023057 is mainly to unblock blocked or disabled Windows Update, so that M$ can force the Win 10 1809 auto-upgrade onto all Win 10 Home & Pro computers. Eg some Win 10 Home users might have blocked/disabled Windows Update’s forced auto-updates/upgrades through a Registry setting or Component Services setting or etc.

Reply | Quote

When I was still using win10 1709, KB4023057 would get pushed every month after 1803 was released. Microsoft apparently can’t understand why someone wouldn’t want their twice-yearly computer-breaking updates, so they push out KB4023057 to re-enable all the Windows Update stuff. I had my fill after the first couple attempts, so I did this:

1. Uninstall it in Control Panel\Programs and Features. It’s not in the list of updates.

2. Make a C:\Program Files\rempl folder. If it’s already there, delete it and then make it yourself so you have ownership from the get-go.

3. Deny all accounts but administrators all access to the rempl folder. You can do this through the permissions dialog or with icacls in an administator command prompt. You will probably have to take ownership first if you didn’t make the folder.

This way, if you forget to run wushowhide (what an awful tool btw) in time, the installation of KB4023057 will just fail and your Windows Update disabling trickery will survive. Windows Update will keep trying to install it though, so you should still wushowhide it when you remember to do it.

Reply | Quote

I have managed to keep control of updates by setting:
1. gpedit.msc : Computer Configuration – Administrative Templates – Windows Components – Windows Update – Configure Windows Updates: 2 – Notify for download and auto install.
2. Settings – Update & Security – Windows Update – Advanced Options – Choose when updates are installed – Feature updates = 365 days.

Does anybody know if these settings are reset by KB4023057?
thanks,
Clark.

Reply | Quote

After posting, I had a look at the Windows update history on my main computer, Previous versions of KB4023057 have been installed and my settings were not effected.

1 user thanked author for this post.

woody

Reply | Quote