Win Update KB5053598 Windows 11 Cumulative Update build 26100.3476 (24H2) - March 11

fg2001gf11F · Mar 16, 2025

Mitch said:
@fg2001gf11F . Yes I noticed the "MS Store Is UpTo Date" message was missing on all our devices. There was an update to the MS Store app yesterday which showed in Reliability Monitor as "failed to install " again on all devices, although MS Store seems to be working. I thought the up to date part was related to that?

This is the latest version of MS Store installed on my Public Build 26100.3476. It was updated on March 14, 2025.
I don't see any failed to install in the reliability monitor.

fg2001gf11F · Mar 16, 2025

khanmein said:
@hader Thanks for your explanation and as for the /RestoreHealth stuck at 62.3% for a period of time also I think is a common thing. While I saw @Ghot ==100%== the operation completed successfully.

/RESTOREHEALTH can go quickly to 100% if /SCANHEALTH did not find anything repairable.
If it found repairable components, the /RESTOREHEALTH will pause at 62.3% for a period of time while repairing and then jump up to 100% when it is finally done.

I had 2 machines without any repairable components, and 3 other machines that required /RESTOREHEALTH to repair and eventually completed successfully on those too.

Quagmire · Mar 16, 2025

Way to go Microsoft, you made a right mess of my system this month :eyeroll:

wordsworth · Mar 16, 2025

Of my three machines, the System 3 in my specs went to a green screen after restarting during this Update and I had to do a Restore to solve it. After the Restore, Updating the second time installed without trouble. So far in all the Updates since 24 H2 the machine giving no problems is the unsupported machine, LOL. Go figure.

fg2001gf11F · Mar 16, 2025

Quagmire said:
Way to go Microsoft, you made a right mess of my system this month

You may have to try reinstalling using the recovery repair version, it worked for me when I had a similar problem.

Quagmire · Mar 16, 2025

fg2001gf11F said:
You may have to try reinstalling using the recovery repair version, it worked for me when I had a similar problem.

View attachment 128398

Thanks. I tried that and got this error code:

Rebooted and now just I get this:

fg2001gf11F · Mar 16, 2025

Quagmire said:
Thanks. I tried that and got this error code:

View attachment 128405

Rebooted and now just I get this:

View attachment 128406

Weird,
The only alternative would be an ISO download from UUPDump.

Any third-party software that may be in the way?

How to fix windows 11 update error 0x8000ffff for update 2023-09 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5030219) - Microsoft Q&A

Hi, I've been having some problems with windows update, after having fixed a previous error code this one has now appeared. Thank you in advance for your help.

learn.microsoft.com

Your original issue:

Configure a Windows Repair Source

learn.microsoft.com

Quagmire · Mar 16, 2025

fg2001gf11F said:
Weird,
The only alternative would be an ISO download from UUPDump.

Sounds fun.

fg2001gf11F said:
Any third-party software that may be in the way?

How to fix windows 11 update error 0x8000ffff for update 2023-09 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5030219) - Microsoft Q&A

Hi, I've been having some problems with windows update, after having fixed a previous error code this one has now appeared. Thank you in advance for your help.

learn.microsoft.com

Nope, pretty clean install and no 3rd party AV that's for sure.

So what are the implications of just leaving the component store in its corrupted state? The bloody thing seems to prefer being broken anyway judging by how many of us run these DISM checks each month after MS updates. My machine seems to be operating fine as far as I can tell.

fg2001gf11F · Mar 16, 2025

Quagmire said:
Sounds fun.

Nope, pretty clean install and no 3rd party AV that's for sure.

So what are the implications of just leaving the component store in its corrupted state? The bloody thing seems to prefer being broken anyway judging by how many of us run these DISM checks each month after MS updates. My machine seems to be operating fine as far as I can tell.

There are other ways to use a repair source as explained in the link below.
Or you can wait for the next windows update.

Configure a Windows Repair Source

learn.microsoft.com

hader · Monday at 5:54 AM

fg2001gf11F said:
....
The CBS log is the one used for SFC /SCANNOW run and not for the DISM runs.
There are 2 completely separate logs, CBS.log and dism.log for the 2 different processes and should not be confused.
See in the 2 folders below for the 2 different files. CBS.log is in the CBS folder, dism.log is in the DISM folder.
.....

The Component-Based Servicing stack (CBS for short) is also involved with the SFC and DISM commands. See. Servicing stack updates

Inside the DISM.log you will see a part of the DISM process. But the DISM process calls CBS processes many times and outputs it into the CBS.log.
And it is these processes who are visible inside the CBS.log during that "Stuck at 62,3%" part.
You claim that the CBS.log is only used by the SFC. Yes of course because SFC is not a DISM command. But it's also used (indirectly) by the DISM process.

Easy to see it for yourself;
Start a 1st PowerShell box as admin; Paste this command: Get-Content C:\Windows\Logs\CBS\CBS.log -tail 10 -wait <Enter>
Start a 2nd PowerShell box as admin; Paste this command: Get-Content C:\Windows\Logs\DISM\DISM.log -tail 10 -wait <Enter>
Start a 1st command or a 3rd PowerShell box as admin and use the command; DISM /Online /Cleanup-Image /RestoreHealth
Let the DISM command run and watch both .log windows.

You can clearly see that DISM starts CBS processes. The DISM.log goes silent but the CBS.log shows a lot of activity that shows people what your system is doing while DISM is "Stuck at 62,3%". DISM is using CBS processes and waits for it to end before it continues.
While the CBS process (and others) logs into CBS.log and shows a lot of info about what your system is doing. Very insightful....

Pirilampo2 · Monday at 6:55 AM

Updated with no incidents to report so far.

steveg · Monday at 7:45 AM

I believe Open-Shell caused my taskbar and start menu to disappear after the update. Got everything working eventually. Will be sure to uninstall it before doing future updates. Hindsight is 20/20.

fg2001gf11F · Tuesday at 1:15 AM

hader said:
The Component-Based Servicing stack (CBS for short) is also involved with the SFC and DISM commands. See. Servicing stack updates

Inside the DISM.log you will see a part of the DISM process. But the DISM process calls CBS processes many times and outputs it into the CBS.log.
And it is these processes who are visible inside the CBS.log during that "Stuck at 62,3%" part.
You claim that the CBS.log is only used by the SFC. Yes of course because SFC is not a DISM command. But it's also used (indirectly) by the DISM process.

Easy to see it for yourself;
Start a 1st PowerShell box as admin; Paste this command: Get-Content C:\Windows\Logs\CBS\CBS.log -tail 10 -wait <Enter>
Start a 2nd PowerShell box as admin; Paste this command: Get-Content C:\Windows\Logs\DISM\DISM.log -tail 10 -wait <Enter>
Start a 1st command or a 3rd PowerShell box as admin and use the command; DISM /Online /Cleanup-Image /RestoreHealth
Let the DISM command run and watch both .log windows.

You can clearly see that DISM starts CBS processes. The DISM.log goes silent but the CBS.log shows a lot of activity that shows people what your system is doing while DISM is "Stuck at 62,3%". DISM is using CBS processes and waits for it to end before it continues.
While the CBS process (and others) logs into CBS.log and shows a lot of info about what your system is doing. Very insightful....

Now I see what you explained earlier. Thanks for the clarification.
This is a sample of the CBS log while repairing components with DISM /Online /Cleanup-Image /RestoreHealth.
I see it doing a lot of downloading. I guess that is why it takes so long stuck at 62.3%.

pietcorus2 · Tuesday at 5:48 AM

HOW(??) to clean this up ??

C:\Users\Piet>Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.3476

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 10.92 GB

Actual Size of Component Store : 10.63 GB

Shared with Windows : 7.00 GB
Backups and Disabled Features : 2.97 GB
Cache and Temporary Data : 656.64 MB

Date of Last Cleanup : 2025-03-18 10:37:48

Number of Reclaimable Packages : 2
Component Store Cleanup Recommended : Yes

The operation completed successfully.

gtspeck · Tuesday at 7:16 AM

pietcorus2 said:
HOW(??) to clean this up ??

C:\Users\Piet>Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.3476

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 10.92 GB

Actual Size of Component Store : 10.63 GB

Shared with Windows : 7.00 GB
Backups and Disabled Features : 2.97 GB
Cache and Temporary Data : 656.64 MB

Date of Last Cleanup : 2025-03-18 10:37:48

Number of Reclaimable Packages : 2
Component Store Cleanup Recommended : Yes

The operation completed successfully.

I have the same issue, it seems to be a problem with MS.

hader · Tuesday at 7:20 AM

pietcorus2 said:
HOW(??) to clean this up ??

You can't. Those 2 packages will remain there till the end of life of 24H2. (Or when MS decides to exclude them out of this DISM check) Those 2 packages are a part of the base-build 26100.1742. Inside the store there are many duplicate packages; Ones with Build 26100.1742 and those of the latest Build. (and some others) in your case mainly 26100.3470 & a few 26100.3476. They can not be removed. (Your Windows would go corrupt if you do!)

See those packages for yourself with DISM /ONLINE /GET-PACKAGES /FORMAT:TABLE > C:\users\<Username>\downloads\packages.txt.
Open packages.txt and you can see what I mean.

Open the C:\Windows\Logs\CBS\CBS.log file and search for; "is a top-level package and is deeply superseded"

You will find 2 hits; Those are those 2 unreclaimable packages.
1) [Microsoft-Windows-FodMetadataServicing-Desktop-Metadata-Package~31bf3856ad364e35~amd64~~10.0.26100.1742]
2) [Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10]
Both has the status: "is a top-level package and is deeply superseded"

Bree · Tuesday at 7:38 AM

hader said:
They can not be removed. (Your Windows would go corrupt if you do!)

Actually, mine didn't. I removed one of the packages long ago, but hader's post helped me identify and remove the last one ....

hader · Tuesday at 7:40 AM

fg2001gf11F said:
Now I see what you explained earlier. Thanks for the clarification.
This is a sample of the CBS log while repairing components with DISM /Online /Cleanup-Image /RestoreHealth.
I see it doing a lot of downloading. I guess that is why it takes so long stuck at 62.3%.

Yes. I came to the same conclusion. Now I understand why it took me some 15-20 min while others are busy for hours...

It all depends on how fast your CPU, Disks, Connection is. I have a very fast system and a very fast connection. (But that depends also how busy the MS download Farm is aka time of day) Image how long it would take with a slower laptop?

I would watch TV for the rest of the evening

....

hader · Tuesday at 8:21 AM

Bree said:
Actually, mine didn't.....

Daredevil you....

And those are only 2 out of the 60 ish.... Now the rest.....

For now.... Wait until you update your system. I hope you made a backup beforehand. In a VM environment; I removed all 1742 packages. System had no problem and said it was still at the latest build. Everything SFC and DISM checked out OK. But by removing a 1742 package that had something to do with Ethernet stuff: that went up in smoke. Broken. No ethernet card and no connection, could not update anymore. Tried to find a driver for it. Failed because this was a simulated VMwareNAT Ethernet Card. And during this time the same package of the latest build was still there. Well we'll soon see if your system continues without any problems or it can't be updated anymore. (and that is not because your ethernet card is gone. That is still there. But CBS will complain and can't update anymore. That's the theory... I didn't had the changes to do this. (never came up in my mind) and now we have a volunteer! You!

)

Send us a conclusion after the next update..... so we all can learn if this is possible thing to try. I tried together with Microsoft many solutions. They absolutely don't want to go there for this question. (removing 1742....) They said; Don't do it! In my case they were right. So I would also advise: Don't do this.
I know the reason why those 2 are unreclaimable and that's fine with me. There are some 58 other 1742 packages in your store now at this moment. (take a look....) So what's next? Remove them also? If you do.... I predicted it. And this time it will be true for sure. But hey feel free to try it.

.....

Those developers are not stupid. They have their reasons why that old stuff is still there. I believe them; I am not a MS developer.

Bree · Tuesday at 10:44 AM

hader said:
Daredevil you.... And those are only 2 out of the 60 ish.... Now the rest.....

For now.... Wait until you update your system. I hope you made a backup beforehand.....

I routinely make Macrium Reflect images, and keep several previous ones too....

hader said:
Send us a conclusion after the next update..... so we all can learn if this is possible thing to try.

No need to wait, I can boot an older image of 26100.2894 as a VM using Macrium viBoot to test this.

I've done so, then removed the Package_for_RollupFix~31bf3856ad364e35~amd64 ~~ 26100.1742.1.10
(it's the only one you need to remove, doing so removes both (un)reclaimable packages).

Then I cleaned up and checked for updates. That installed the latest Patch Tuesday CU, KB5053598.

.

The CU added one new reclaimable package, but it is one that could be cleaned up by normal methods.

Certainly looks like a permanent fix to me....

Win Update KB5053598 Windows 11 Cumulative Update build 26100.3476 (24H2) - March 11

March 11, 2025 - KB5053598 (OS Build 26100.3476)​

Highlights​

Improvements​

Windows 11 servicing stack update (KB5052915)- 26100.3321​

Known issues in this update​

How to get this update​

Well-known member

My Computer

Well-known member

My Computer

New member

My Computers

Well-known member

My Computers

Well-known member

My Computer

New member

My Computers

Well-known member

My Computer

New member

My Computers

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Active member

My Computer

Well-known member

My Computers

Similar threads

March 11, 2025 - KB5053598 (OS Build 26100.3476)

Highlights

Improvements

Windows 11 servicing stack update (KB5052915)- 26100.3321

Known issues in this update

How to get this update