WinRE KB5057589 fake out

Topic

New Reply

PK noted this behavior the other day (if I am recalling correctly) where the installation of the KB5057589 patch looks like it failed, but it really d
[See the full post at: WinRE KB5057589 fake out]

Susan Bradley Patch Lady/Prudent patcher

5 users thanked author for this post.

dataman1701, lmacri, katiedid, Cybertooth, Great Lake Bunyip

Reply | Quote

Replies

I’ve seen this ‘fake out’ behavior in the past with other patches.  My rule of thumb since then has been : ONE Patch at a Time.  Takes a bit longer but reduces the headache factor!

1 user thanked author for this post.

dataman1701

Reply | Quote

My experience with this phenomenon is recorded in #2761751 and #2761854.
Note the difference with the third install of Win10.

1 user thanked author for this post.

dataman1701

Reply | Quote

Microsoft is flooding Windows 10 and 11 with WinRE and Dynamic updates :

https://www.neowin.net/news/windows-10-kb5057589-kb5055674-kb5056474-kb5055769-kb5055768-kb5055770-updates-released/

Last week, Microsoft released Patch Tuesday updates for Windows 11 and Windows 10 under KB5055523/ KB5055528 and KB5055518, KB5055519/ KB5055521/ KB5055547, respectively. Following that, Microsoft also released out-of-band updates under KB5058919 / KB5058922 / KB5058921 for both Windows versions in order to fix a Group Policy-related bug for enterprises.

The tech giant also published Dynamic updates for all supported Windows 11 versions, namely 24H2, 23H2, and 22H2. They also apply to Windows Server 2025. You can find them under KB5055671 and KB5056789.

Alongside them, Microsoft has also published dynamic updates for all supported Windows 10 versions as well as for Windows Servers…

Reply | Quote

FWIW – The out of band updates in Alex5723’s quote of a neowin article are all non-security updates available through the MS Catalog only. That’s according to the MS support pages for the updates.

1 user thanked author for this post.

Alex5723

Reply | Quote

KB5058919 / KB5058922 / KB5058921

The ones released Patch Tues. are 555, the ones with 589 are OOB released on 4/11/25 instead of 4/8/25

2 users thanked author for this post.

Alex5723, DrBonzo

Reply | Quote

Roger that, and it’s the OOB/589 updates that I was referring to as being non-security, catalog only updates.

Reply | Quote

Also, according to Microsoft’s catalog, the Windows 10 OOB updates only apply to 1607 & 1809.

KB5058921 = 1607

KB5058922 = 1809

There was no OOB for Windows 10 22H2!

1 user thanked author for this post.

DrBonzo

Reply | Quote

KB5058919 (the other OOB) was for Win11 21H2 and 22H2.

 

Reply | Quote

And this is EXACTLY why I follow Susan’s advice on patch day and defer. This stuff nearly ALWAYS happens.

Reply | Quote

My problem with KB5057589 is that every day since April 8, the last Patch Tuesday, it has been showing up anew in the Reliability Monitor as “Installation Successful”. One might suppose that a single successful installation would be enough, so this suggests to me that something is broken.
Any ideas?

Reply | Quote

Are you running update every day or is it stuck in an installation loop?

Try uninstalling it and rebooting.

cheers, Paul

Reply | Quote

I’m not running Windows Update per se; they’re arriving with the usual antivirus definition files I normally see a handful of each day, along with the infrequent .NET and mysterious WINDOWSSTORE updates.  No looping involved, except that KB5057589 comes in every day.

Anyhow, I’ll try uninstalling and rebooting.  Thanks!

 

Reply | Quote

That is the Windows recovery environment patch. We know it’s rubbish – I’d hide it.

cheers, Paul

Reply | Quote

Alas, I didn’t find it listed among my uninstallable updates.  (Its latest “successful” arrival, from today, was listed in the Update History, at least.)  So much for uninstalling it … unless there’s another approach?

Mainly, though, I’m just curious about why I’m receiving daily “successful’ updates with KB5057589!  I suppose the short answer is “another Microsoft bug”.

Reply | Quote

I have it installed and all is well on a Gen12 W11 23H2 device AND also on a W11 installation using what microsoft published then removed, to install on under-the-bar devices using rufus procedures.

The patch works fine here, so here it shall stay as intended by MSFT

Windows - commercial by definition and now function...

Reply | Quote

The WinRE updater has installed successfully on all my Win10/Win11 installations. The WinRE was updated with the April updates in this manner:
Win10 22H2 from Build 5363 to Build 5728
Win11 23H2 from Build 4890 to Build 5184
Win11 24H2 from Build 3321 to Build 3762

To see if your WinRE is being updated, in an elevated Command Prompt (replace the * in the second command with the partition number from the first command)

reagentc /info

Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition*\Recovery\WindowsRE\winre.wim /index:1

1 user thanked author for this post.

SteveIT

Reply | Quote