Another complaint about KB 4023057

Topic

New Reply

Earlier today I had a tweet from Help4me who’s frustrated that we’re still stuck at MS-DEFCON 2: https://twitter.com/help4me666/status/958404040475455
[See the full post at: Another complaint about KB 4023057]

5 users thanked author for this post.

Elly, Tiernan, JDeC, SueW, WildBill

Reply | Quote

Replies

I thought I had this patch hidden on one of my 1703’s, but it showed again in WU. Used wushowhide to hide it again – no, it was still in WU. Repeated hidings didn’t work, it kept coming back in WU like a bad Penny (and this with WU set to notify download/install).

I think this is the sister to KB2952664 in Win7. How many versions have we seen?

3 users thanked author for this post.

Elly, woody, JDeC

Reply | Quote

On the occasion that you hide something with WUShowHide, sometimes it may still show but will silently fail to install for lack of existence. Recently I was able to reboot and the hidden update was removed from the ‘to download list’. I’m still using Windows 10, 1607 so you may have more trouble.

I forget how many revisions exist.

If there is newly appearing KB number for which you cannot download a file from the Update Catalog it is likely to be a feature update related thing or cause some other trouble.

Reply | Quote

If I remember well, KB4023057 was and still is one of the most weird and unexplained updates in the recent times. This update has never been offered to WSUS, but only to Windows Update. This would indicate that it meant for unmanaged end-users and unmanaged small business users.
My understanding was that it was meant to facilitate a smooth upgrade to 1703, but it is offered on Windows Update also to Windows 10 Enterprise LTSB version 1607 and Windows 2016 Server which is LTSB version 1607 as well, which are normally not upgraded to the next major version and an upgrade is not offered on any regular channel.
This patch may be harmless, but why it was released and where it actually applies, it is still a mystery. @abbodi86 is likely to have the right explanation, even if this covers only partially what this patch does.
https://support.microsoft.com/en-us/help/4023057/update-to-windows-10-versions-1507-1511-1607-and-1703-for-update-relia

2 users thanked author for this post.

Elly, AlexEiffel

Reply | Quote

An Anonymous poster reported KB4073543 showing up in Windows Update on Win10 1703. The patch was issued 1/29/2018. In conjunction with KB4023057 and considering the description, I wonder if it has anything to do with pushing 1703 to 1709 unbidden.

This update includes new stability improvements for the update components in Windows 10 Version 1703.

The update components include files and resources that work together with the servicing stack engine in Windows 10. These components make sure that quality updates are installed seamlessly and that they improve the reliability and security of Windows 10.

Only certain builds of Windows 10 Version 1703 require this update. Devices that are running those builds will automatically get the update downloaded and installed through Windows Update.

This update is also offered directly to Windows Update Client for some devices that do not have the most recent updates installed.

https://support.microsoft.com/en-us/help/4073543/updates-to-windows-10-version-1703-update-components-january-29-2018

2 users thanked author for this post.

Elly, RamRod

Reply | Quote

Still fat and sassy on 1511. But WU shows me 4023057 at least once per month. I talked about it here a while back. I use WUSHOWHIDE to hide it, it is hidden, until…it pops up again. I interpret this to MS’s way of forcing an upgrade. The info on the update says it is for update reliability. Them’s code words to me. Code that the enemy, my former ally, is storming my computing gates and wants to do nasty unbidden things to my computing experience. I continue to run WUSHOWHIDE daily blocking just about everything. I update Windows Defender manually everyday at the same time. Love/tolerate 1511. At least it’s a known for the time being. Will upgrade on my schedule unless MS does something really underhanded. Vigilance!

4 users thanked author for this post.

HiFlyer, Elly, SueW, Cybertooth

Reply | Quote

Thanks for the link to the Horowitz blog.

Sounds to me like a new Microsoft “Get GWX+” moment.

As Pink Floyd said, “Another Brink in the Wall” against Windows 10 for me. I keep hoping they will hear the voices of the users, but no. 2 Friends, one a senior, another in their 30s, just bought 12″ iPad Pros for their email and websearching. Why? Their Windows 10 PCs were too hard to keep running and kept changing (plus for serious work they have work provided and supported laptops).

Reply | Quote

Resistance is futile.

1 user thanked author for this post.

ch100

Reply | Quote

I will not be assimilated!!!  😉

 

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

6 users thanked author for this post.

HiFlyer, Elly, Charlie, SueW, Ascaris, WildBill

Reply | Quote

In one sense resistance is futile – eventually my hardware will die and force replacement. That will usher in the latest version of WinX. Can’t take 1511 with me. Of course I know I can’t stay on 1511 forever – and I don’t want to. I’m merely trying to control my own computing experience. I’ll resist as long as it is profitable for me to do so. As my Dad always said – Anything taken to an extreme is ridiculous. That goes both ways MS.

Reply | Quote

RamRod wrote:

That will usher in the latest version of WinX.

As did my recent purchase of a cheap ultraportable laptop… but then I ushered it right back out again, just as I did with my other laptop when I bought it with Vista preinstalled in 2008.  One got Linux Mint, one XP, respectively (and I note that I am using the latter laptop now to write this, also under Linux).

I’ve never bought a desktop pre-assembled, so they never came with any OS.  The OS was just one of many components to be separately sourced and obtained.  I’d built many PCs, for myself and lots of others, before I ever bought my first laptop, which (due to its nature) has to be pre-assembled.  By then, the idea of the OS being distinct from the hardware was well-ingrained.  It’s nice if the OS it comes with is usable, but if not, it’s not the end of the world.

Now that I think about it, the laptop before the Vista one came with XP Home, and I put XP Pro on it, so that one didn’t keep its as-configured OS either.  The last one that I used with its preinstalled OS was a HP ZE4805, so old that it didn’t have USB 2 ports.  Must have been around 2003!

It might bother some people to have to pay the “Microsoft tax” twice, but really, it’s only once.  When Dell began offering one of their laptops with Linux instead of Windows, a lot of Linux fans were thrilled and couldn’t wait to get one… and they were shocked to find that they cost more than the Windows version of the same PC, not less.  It was only a slight premium, perhaps $20, but they had expected to pay less.  Dell, as the story goes, told them that the crapware (my term, not theirs) that comes with nearly every Windows PC subsidizes the Windows licensing cost.

I’m not sure how long 1511 will remain viable anyway.  Isn’t the MS policy to support a version of 10 for 18 months?  It should be well past its end of support date even now, unless you were fortunate enough to be able to get the LTSB edition that MS tells us is only for highly specialized applications like POS machines and ATMs; the rest of us can’t do without all these new “features” they keep forcung on us (even if we’d really, really rather do without them).

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, OpenSUSE Tumbleweed

1 user thanked author for this post.

Elly

Reply | Quote

Somehow I’ve managed to avoid updates beyond 1511. I use WUSHOWHIDE religiously. I keep my network connection set to metered. I use Spybot Anti-Beacon and shut down almost every option it presents. I understand that 1511 is out of support – so what?

Reply | Quote

RamRod wrote:

I understand that 1511 is out of support – so what?

The usual… security threats.  As risky as patching can be these days (with end users being the de facto beta testers now), it’s still something most of us recognize as a necessary evil, and the lack of such patches in the future for 7 and 8.1 is the primary reason those two versions of Windows are seen as being on borrowed time.  When people make references (within the context of operating systems) to 2020, they don’t even have to explain why that year… it’s the year that the most popular Windows version, Windows 7, stops being supported with security patches.  For most people, this means “end of the line” for 7.

I can understand wanting to join group “N,” as I think it is called, but to do so is to go in the opposite direction of Windows 10.  Windows 10 equals lots of updates, lots of change, with not much control over them.  Group N equals no updates, no change, thus total control.  The desire for that much control (which I understand; I desire it myself) means that the versions of Windows that didn’t attempt to usurp control from the owner (meaning anything prior to 10) are the much more typical choices for a group “N” approach.

That’s all… just an unusual choice.  It’s your computer; I am not one of those people who will try to tell you that you have a duty to keep it updated if you don’t want to.  If anything, I would blame Microsoft for making “group N” into the least-bad option for so many people.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, OpenSUSE Tumbleweed

4 users thanked author for this post.

HiFlyer, Cascadian, windows7forever, Elly

Reply | Quote

I saw this update today been installed for the 3d time in 3 weeks, seems to actually be something weekly. After every install, I get a series of events 7023 in the logs. Have the feeling Microsoft is completely lost in what it’s doing or trying to do. Happy my main production machine is not running on Windows anymore since a couple of weeks, it gives me badly needed rest.

4 users thanked author for this post.

HiFlyer, Elly, witp, Cybertooth

Reply | Quote

KB4023057 = Remediation Shell (known as WaaSMedic in version 1709)

fix and reset update-related parts to their “supported” configuration
i.e. restore registry settings, services status, schedule tasks, clear disk space, launch UpdateAssistant.exe if installed

mainly it’s ment to pave the way to receive the latest updates, whether quality updates, or feature update to latest Windows 10 version

it’s a msi package not a regular update, doesn’t require a reboot

it has more than 12 releases so far

———–

other updates also facilitate the upgrade in a way or another

KB4021701 (1507) KB4021702 (1511) – KB4049411 (1607) – KB4073543 (1703)
the update components (Windows Update Agent, Update Orchestrator, Delivery Optimization, BITS)

KB4033631
the Compatibility Appraiser (equivalent to the famous KB2952664/KB2976978)

KB4056254
OS Remediation System Service (OSRSS)

KB4023814
Update Assistant tool (aka Windows10Upgrader.exe)
equivalent to Media Creation Tool, which will download and prepare the ESD file for upgrade, in case you hid/block the upgrade through WU

———–

you do not need any of those updates if you intend to stay on your current Windows 10 version, or want to upgrade on your terms

14 users thanked author for this post.

anita.yk, Microfix, Seattle27, JDeC, Noel Carboni, HiFlyer, Elly, ch100, woody, dononline, RamRod, Cascadian, MrBrian, PKCano

Reply | Quote

It does not come on WSUS though. I am wondering why, if from a pure engineering point of view is such a desirable update.

Reply | Quote

Probably it will mess with WSUS policy settings

and as you described it, it’s for unmanaged users whom “mess” with their update settings 😀

2 users thanked author for this post.

Elly, ch100

Reply | Quote

I got this one instead
https://support.microsoft.com/en-us/help/4074608/servicing-stack-update-for-windows-10-version-1709-january-30-2018
which is on WSUS but not on WU, although according to the KB it should be.
The documentation says: “This update doesn’t replace a previously released update”, while WSUS supersedence metadata indicates that KB4074608 supersedes KB4058702 and KB4054022.

2 users thanked author for this post.

PKCano, woody

Reply | Quote

We already clarified that SSU is bundled with CU in version 1709 🙂

you may notice that 1709 SSU has a distinguished version (i.e. 16299.122.1.0), not the generic version like other updates before (i.e. 10.0.1.2)

it won’t listed in WU history, but you can find it in Installed Updates

KB articles are mostly geberic regarding the replacement

3 users thanked author for this post.

ch100, woody, PKCano

Reply | Quote

I have a question.  When one looks at the 1709 updates on the Catalog site, SSU is classified as a “Critical Update,” but the CU is classified as a just an “Update.”

If in 1709 SSU is bundled with CU, shouldn’t the classification of the SSU supersede that of the CU thus making both the SSU and CU “Critical Updates?”

Reply | Quote

“KB4023057 = Remediation Shell (known as WaaSMedic in version 1709)”

What is this WaasMedic? and Why it required to connect internet and make changes on MY COMPUTER?

3 users thanked author for this post.

Elly, woody, ch100

Reply | Quote

As if the Spectre/Meltdown nightmare wasn’t enough to deal with …

I want to thank the author also for this excellent post re: the WUP ‘enhancements’ that M$ won’t divulge any details about. This is the first post I have found that explains the recent flood of KBs with Remediation, new Service ‘osrss’, etc.

The author says “you do not need any of those updates if you intend to stay on your current Windows 10 version, or want to upgrade on your terms.” Be warned that if you install KB4023057 and KB4056254 you won’t be able to uninstall them. At least, I have not found a way.

 

Reply | Quote

For the sake of completeness, there is also KB4021702.

Here are links to all of these update KB articles:

https://support.microsoft.com/en-us/help/4021701/
https://support.microsoft.com/en-us/help/4021702/
https://support.microsoft.com/en-us/help/4049411/
https://support.microsoft.com/en-us/help/4073543/
https://support.microsoft.com/en-us/help/4033631/windows-10-update-kb4033631
https://support.microsoft.com/en-us/help/4056254/windows-10-update-facilitation-service
https://support.microsoft.com/en-us/help/4023057/update-to-windows-10-versions-1507-1511-1607-and-1703-for-update-relia
https://support.microsoft.com/en-us/help/4023814/some-versions-of-windows-10-display-a-notification-to-install-the-late

1 user thanked author for this post.

abbodi86

Reply | Quote

@PKCano: Yes, I do believe you are correct if you are wedded to the Windows universe.

But there are other Borgs out there for individual users, some orderly and controlled, others more open (or chaotic depending on personal tastes and definitions).

I am using a Windows 10 laptop in Airplane Mode (all connectivity turned off) for organizational productivity work that does not require online access, but does require absolute reliability with existing peripherals. I find it fine for that work. It is only when you try to change settings (like to truely turn off when you shut down) that I have to search and use in internal help feature. I have gotten in the habit of removing the battery to prevent it from being 100% drained by a feature.

1 user thanked author for this post.

Elly

Reply | Quote

Don’t know what to trust anymore.

Really?

Well, then there’s no help for you! (see what I did there? 😀 )

But seriously, just follow the Defcon system. Skim the posts, follow Woody and gang’s recommendations and you’re safe.

Trust me, you’re in both good and caring hands.

But really…

Woody’s recommendations versus Microsoft’s recommendated updates?
And who to trust?

If you’ve been around since the happy GWX days and has followed the fantastic festival of pacthes since then, it really should be easy to pick side…

Otoh, if you have doubt in Woody, why not just press “Update now”?
I dare you! 😀

9 users thanked author for this post.

HiFlyer, Elly, Charlie, SueW, Tiernan, JDeC, WildBill, Cascadian

Reply | Quote

You wrote that so well, with just the right cadence. I stifled a shiver on your last line.

1 user thanked author for this post.

HiFlyer

Reply | Quote

Don’t be cruel. Things move plenty fast in the Windows world and it’s not easy to keep up. Trust is necessary, yet hard to generate let alone maintain. Everyone simply wants a good computing experience – for the computer and OS to recede and information to flow.

1 user thanked author for this post.

HiFlyer

Reply | Quote

From a comment at Windows 10: What is REMSH.exe for?: ‘The ETL files in the log folder for REMSH are readable by “Microsoft Message Analyzer” and show information like this […]’

Reply | Quote

The description at the end of Born’s article for KB4023057 is the same as I posted above for KB4073543

Me thinks more forced upgrades are in the offing!!!

Reply | Quote

That’s what I suspect too. I’m staying on 1511 as an experiment – to see if MS will actually force an upgrade. First they will demonstrate that they have the capability. Second the will. Third they will demonstrate the contempt they have for this virtual customer (virtual customers are users of their software wherein no transfer of $ occurs in the procurement or maintenance of said software). Ain’t science great!

Reply | Quote

anonymous wrote:

I have a question. When one looks at the 1709 updates on the Catalog site, SSU is classified as a “Critical Update,” but the CU is classified as a just an “Update.”

If in 1709 SSU is bundled with CU, shouldn’t the classification of the SSU supersede that of the CU thus making both the SSU and CU “Critical Updates?”

SSU is a companion update in the terms of UUP delivery mechanism in 1709, it’s not actually bundled or part of CU, they are completely separated updates

i believe all SSUs are classified “Critical Update” due to their nature (the engine that process all other updates)
whereas CUs are classified based on the most recent fixes, security fix “Security Update”, or quality fixes “Updates”

2 users thanked author for this post.

ch100, woody

Reply | Quote

The CU in question is an “Update” because it should be seen as a “Preview Update” to use the language known from Windows 7 and Windows 8.x.
Any Windows 10 released out of band and available in the Catalog only is the equivalent of a Preview Update and this is what most people participating here do not understand. The Catalog is not for those who are looking for in detail advice here, but it is useful at the informational level for everyone. Those who are technical enough to understand and use the Catalog effectively are only a few here and it is very obvious who they are. Everyone else should use only Windows Update as this is the only mechanism available to end users which takes care of supersedence and the correct order of installation of the updates.

1 user thanked author for this post.

PKCano

Reply | Quote

I’ve had update off on my Win 10 box over 1 month.

Using Windows Update Blocker, Windows update service is switched off and the off state is protected (verified just now). Windows update is saying it is having problems updating the machine. Despite that, KB 4023057 installed this morning (and did not manage to start the update service).

Presumably, the update is squirreled away somewhere on the hard drive for occasions when Windows cannot make update do its thing.  That’s probably good for Fred Average who never looks at update and trusts Microsoft via default.

 

Group A (but Telemetry disabled Tasks and Registry)
Win 7 64 Pro desktop
Win 10 64 Home portable

Reply | Quote

KB4023057 appeared yesterday ( Jan22-2019) at one of my machines  W10Home.1803.V17134.556
Weird, must be all that testing that Micro$0ft is doing these days   :-S

* _ the metaverse is poisonous _ *

Reply | Quote

Microsoft is set on pushing upgrades (obviously). They continue to change/modify/update that push. KB4023057 is like KB2952664 on Win7 and KB2976978 on Win8.1 were. Each issue is a revision, new version, but with the same KB number. So it appears as if they are reissuing the same patch again when it’s actually not exactly the same.

But the PURPOSE  is the same.
A Carrion Flower by any other name is still a carrion flower.
HIDE IT.

Reply | Quote

Well, kb4023057 appeared by magic today here (win10 pro x64, on the laptop). And it’s failing to install ( by what I’m reading, I should not cry about it ).
For the sake of discussion, is this going to cause failures to other things updating ( like defender ) or just show the annoying message ?

Reply | Quote

Hide it. It should cause not problem to do so. I have updated and upgraded without ever installing that one. (See reply directly above.)

Reply | Quote

First thing I did after posting 😛
Funny thing is that this kb first caused an october update to show up ( and install ), after the first reboot

Reply | Quote

KB4023057 is published to Update Catalog for the first time
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4023057

1 user thanked author for this post.

woody

Reply | Quote

Hah!, Am I blowing this out of proportion but this seems to be a big deal and they have released packages for almost all the versions. 1809 (really 1901) does not need this er remediation tool?

Reply | Quote

KB4023057 is ment to “facilitate” the upgrade, 1809 don’t have new version to upgrade to yet 🙂

besides, 1809 already has most of KB4023057 functions inbox
but probably when 1903 upgrade become broad, it will get updated version of it

Reply | Quote

Okay that would make sense to for Microsoft to bake that Windows, and also to meet a set target to boast about later. (If I’m wrong about this future projection fine, Microsoft might choose to do another adoption rate marketing campaign later this year.)

All of these 4023057’s in the catalog now after these many years may also be another method for Microsoft to ‘encourage’ upgrading Windows 10, now confirmed by reading the Overview tab and the repetitively familiar help article.

Yes that appears to be why they were added to the catalog, somewhat less likely the 4023057’s have themselves have serious vulnerabilities.

1 user thanked author for this post.

woody

Reply | Quote

anonymous wrote:

All of these 4023057’s in the catalog now after these many years may also be another method for Microsoft to ‘encourage’ upgrading Windows 10…

Perhaps more accurately… its another method to discourage ‘fiddlers’ trying to stop Windows 10 self-updating…

It’s quite a long read but I like Michael Horowitz’ take on the whole ‘updating’ saga and note his conclusion:

Outside of large companies, I don’t think anyone should use Windows. Certainly, non techies should not use Windows.

1 user thanked author for this post.

woody

Reply | Quote

The long term servicing branch might be better for non-techy people or as I have seen in the past customized all-in-one computers aimed for the Senior population which had a highly customized GNU/Linux based operating system.

Reply | Quote

anonymous wrote:

The long term servicing branch might be better for non-techy people

Isn’t LTSB only available within the Enterprise channel?

(I accept that this may be a stupid question but I don’t actually keep up.

I made my Win 10  ‘updating/upgrading’ decisions some time so – thank goodness – have been able to ignore most of the angst discussed here on AskWoody… until KB4023057 found its way through my defences. So, my interest in Win 10 patching/updating/upgrading/whatever is now [temporarily] aroused.)

Reply | Quote

Yes, it is only available for Enterprise market and costs a business very much money.

(I accept that this may be a stupid question but I don’t actually keep up.)

Not a stupid question, you may also have some more free time…

…I made my Win 10 ‘updating/upgrading’ decisions some time so…

…and enjoyed piece of mind. 😉

I hope you were able to successfully get rid of 4023057?

Reply | Quote

anonymous wrote:

I hope you were able to successfully get rid of 4023057?

Not yet. Uninstall via ‘Control Panel > Programs and Features’ did nothing. Uninstall using elevated VBS/WMI did nothing. Uninstall via 2 elevated PowerShell methods did nothing. There are times when you think… “Microsoft, now you’re just trying my patience… :)”

Whilst I’ve certainly enjoyed peace of mind for a long, long, long time, it’s disconcerting how this KB4023057 malware slipped by… and, apparently, some time ago. I hadn’t been checking… ‘cos this is my only Win 10 PC and just used as a dumb network storage device (my other Win 10 devices are laptops, frequently re-imaged). I reverted my main PC back from Win 10 to Win 7 nearly 3 years ago.

My fault for not paying attention to this dumb Win 10 pseudo-NAS for a long time (just checked and it’s still on Win 10 1709 16299.248).

It’ll be a time-consuming pain but if KB4023057 results in a forced feature update to this 1709 device then I’ll just wipe its current Win 10 SSD OS drive and re-implement as Linux with its multiple internal drives shared via Samba. It’ll be a pain but… since Win 10, I’ve become used to fighting MS instead of working in collaboration.

Thanks Win 10 for practically ‘strong arming’ me into looking at alternative OS’ in my wish to retain some semblance of control over how I choose to work.

2 users thanked author for this post.

woody, Lars220

Reply | Quote

Hey it is Windows 10… that pesky Ninja Cat riding upon a Unicorn delivered it to your computer. 😉

Back to the topic, were any of these methods you tried trying to take ownership targeting the rempl folder to delete it, and stopping services?

(https://www.askvg.com/how-to-remove-or-disable-windows-setup-remediations-service-in-windows-10/)

Can you find a way keep that particular machine away from an outgoing internet connection, like using a firewall?

Reply | Quote

Just now got my New/Improved 4023057. I got it on 2/21/19 and a new one this afternoon 3/1/19. Guess I better check Grp Policy to see if they changed anything there.

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

Reply | Quote

Adding to strange behaviour:

Endeavouring to fix a ‘freeze every 15-20 minutes issue’ yesterday I eventually ran the dreaded ‘check for updates’ then WUMT to get the rest when the system became stable. Having worked on the problem all day, by  11:30PM my level of normal update caution was at an incredibly low ebb. Deciding my new laptop will arrived within a week or two I decided “just let it all in”, planning to review and remove unwanted updates today.

The strange part is WUMT says it downloaded and installed KB4023057. Control Panel’s Add Remove Programs does not list it. Everything (search utility) locates the cab file and nothing more.

In and not removable or the system decided it wasn’t needed? Either way, I presume the next feature update will roll in and Demons it includes  so it’s probably not worth the fight.

THE GOOD: Despite my lack of caution Winver tells me 1803.

Reply | Quote

Interesting that it doesn’t show up in Progs&Features, it always has on mine.

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

1 user thanked author for this post.

Lars220

Reply | Quote