Win Update KB5058411 Windows 11 Cumulative Update build 26100.4061 (24H2) - May 13

Garrett · May 28, 2025

Installed fine no errors but noticed that system decided to rebuild the index after this update without any input from me. Previously around 270000 files were indexed, ( I check it ) now it's says indexing complete with only 76129 items! I wonder what triggered this automatic rebuild? Rebooted and indexing has resumed. Not from paused but from stated completed status.

Ghot · May 28, 2025

Garrett said:
I wonder what triggered this automatic rebuild?

It's a mystery. But here's ten points for filling out your computer specs.

antspants · May 28, 2025

Garrett said:
Installed fine no errors but noticed that system decided to rebuild the index after this update without any input from me. Previously around 270000 files were indexed, ( I check it ) now it's says indexing complete with only 76129 items! I wonder what triggered this automatic rebuild? Rebooted and indexing has resumed. Not from paused but from stated completed status.

Maybe it’s indexing just the new or changed files as a result of the update? Hence the low count.

Garrett · May 29, 2025

antspants said:
Maybe it’s indexing just the new or changed files as a result of the update? Hence the low count.

I forced a rebuild and now back over 270000 items. I always check the index after updates just out of curiosity to see roughly how many new files have been added. I've never seen less before!

hader · May 29, 2025

Damn! The capacity of the MS download servers sucks big time. They knew that bringing out a new update that many people are updating their system. So extra capacity of the download farm is needed. I am waiting (WULib DownloadProgress) on part 50 (out of 100) for 15 minutes now.

Levitate11 · May 29, 2025

hader said:
Damn! The capacity of the MS download servers sucks big time. They knew that bringing out a new update that many people are updating their system. So extra capacity of the download farm is needed. I am waiting (WULib DownloadProgress) on part 50 (out of 100) for 15 minutes now.

They did state that it's a gradual rollout to avoid overload. But, all the media channels start talking about it as soon as it hits the streets, and all the nerds (like us) jump to download it whether it's offered or not.

hader · May 30, 2025

Levitate11 said:
They did state that it's a gradual rollout to avoid overload. But, all the media channels start talking about it as soon as it hits the streets, and all the nerds (like us) jump to download it whether it's offered or not.

It was offered....
A real nightmare. This update went wrong. Again. I suspect that removing one 1742 package (The one caused 2 un-reclaimable packages) is the perpetrator. During the update you can see that it's examine the baseline version 1742. Now I did a In-Place install of 1742 and the update went quick and was OK. Had troubles with the last 2 updates. So I just leave those 1742 packages alone. 2 unreclaimable packages... So be it.

Scott · May 30, 2025

hader said:
I suspect that removing one 1742 package (The one caused 2 un-reclaimable packages) is the perpetrator.

So strange...you and I have very similar computers, right down to the same BIOS version.
Why yours wouldn't update w/o those 2 packages is a mystery, as mine does fine w/o them.

hader · May 30, 2025

Scott said:
So strange...you and I have very similar computers, right down to the same BIOS version.
Why yours wouldn't update w/o those 2 packages is a mystery, as mine does fine w/o them.

I believe you. In my opinion it should not matter. The only difference I can think off; With 4061 I did an In-Place install from a MVP ISO that was a little bit adjusted so that it could be installed on non-certified hardware. My hardware is certified. Maybe it done something that it wasn't supposed to do. I thought I did a normal install. I leave those MVP ISO alone from now on. If I have to do a In-place install I will use the official 1742 version. Updating it is straight forward. In just applies the latest patch and done with it. You can't get any cleaner than this. It dumps the complete old version in the Windows.old directory.

Birk · Jun 10, 2025

So I waited until KB5060842 came out (today) and tried it. Needless to say it failed. So I'll be doing a Repair Install later today.

During my hiatus from updates I discovered several interesting things:

sfc /scannow found some errors but corrected them all. After that dism said my component store was repairable. But all the dism repair options failed. I looked at the log files but they were not helpful :

Error CBS FC: CFCAcquirerWUClient:

ownload(141): Result = 0x800F095

I found a utility called SFCFix.exe that said it could fix DISM errors that were otherwise unfixable. Except it couldn't. So a Repair Install is my last resort. I have done that before with good results - so here's hoping that scenario will continue.

Hopefully my next post in this thread will be mu last.

hsehestedt · Jun 10, 2025

I know that this may be a wildly unpopular opinion for some, but I simply don't even bother sfc /scannow or related options. Maybe I run it once a year (that's being generous). The only extremely rare exception is if I run into some odd issue that I simply cannot explain by user settings, configuration, etc.

FrancoDT · Jun 10, 2025

hsehestedt said:
I know that this may be a wildly unpopular opinion for some, but I simply don't even bother sfc /scannow or related options. Maybe I run it once a year (that's being generous). The only extremely rare exception is if I run into some odd issue that I simply cannot explain by user settings, configuration, etc.

I'll be honest I didn't use to run DISM and SFC /scannow except when I had a known problem but after everyone here started running them after every update I started as well lol. I find errors about 50% of the time but I honestly don't know if they present any real issue or not.

Birk · Jun 10, 2025

I decided not to wait until after dinner to do the reinstall. It worked. The process is a bit time consuming, and there are periods when it seems like nothing is happening. But it completed OK. Windows Update says I am up to date, so I guess I'll have to wait another month to see if new updates install OK.

I was happy to see that the update did not lose a couple of my custom Junction Links, my additional animated cursors, my wireless keyboard/USB dongle and BlueTooth trackball, and the fact that I've got 2 4K monitors, with one of them in portrait mode.

My boot drive went from 62GB to nearly 80 GB, but that's mostly dues to the Windows.old directory showing as 35 GB, but I'll get that back when I delete it.

hader · Jun 11, 2025

Birk said:
I decided not to wait until after dinner to do the reinstall. It worked. The process is a bit time consuming, and there are periods when it seems like nothing is happening. But it completed OK. Windows Update says I am up to date, so I guess I'll have to wait another month to see if new updates install OK.
.....

If you are wondering what your system is doing than use the following tip;

Start Powershell as admin. Issue the following command; Get-Content C:\Windows\Logs\CBS\CBS.log -tail 10 -wait
It may look if your system is doing nothing but in reality it's quiet busy. Checking, downloading, applying etc. Errors will also logged. Look for results line [HRESULT = 0x00000000 - S_OK] to see it has done something with succes. Others like [HRESULT = 0x800f0991 - - PSFX_E_MISSING_PAYLOAD_FILE] means error. This errorcode (0x800f0991) will also be seen inside the Windows Update screen of Settings.

Anything will scroll by. It's is a view inside the CBS engine. Every DISM command and even sfc it's progress will be logged in the CBS.log file. At the end of the action The TrustedInstaller Service (Windows Modules Installer) will automatically shutdown due to a timeout. (Nothing to do..) This line will be visible in the log; Ending TrustedInstaller finalization. If you see this info on a regulair basis you are getting a feeling what it's doing. During every upgrade it will follow the same path each time.

Win Update KB5058411 Windows 11 Cumulative Update build 26100.4061 (24H2) - May 13

May 13, 2025 - KB5058411 (OS Build 26100.4061)​

Highlights​

Improvements​

Well-known member

My Computer

Well-known member

My Computers

Like a rolling drone.

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Similar threads

May 13, 2025 - KB5058411 (OS Build 26100.4061)

Highlights

Improvements