Win Update KB5127648 Windows 11 Cumulative Update build 26100.9711 (24H2), 26200.9711 (25H2), 26300.9711 (26H2) - Oct. 13

fg2001gf11F · 2026-10-22T20:23:23-0400

garlin said:
This is an often misunderstood topic.

SFC only has one job: To confirm if the correct Windows files are present in their right locations. SFC compares what is listed in the Component Store vs. what is found in the \Windows and \Program Files folders. If any file is missing or "corrupted" (ie. different) then it's replaced by a new hardlink back to the Component Store. SFC presumes the Component Store is healthy and correct.

DISM health checks don't assume the Component Store is intact, and try to use metadata or a reference image source (local image or via network access) to confirm if any WinSxS files are missing or corrupted.

Neither process affects the other. Running SFC doesn't affect the DISM status.

But if you have recently DISM repaired the Component Store, then it may be useful to run SFC again, because SFC was dependent on what the Component Store said was "correct" when it last ran.

I see several cases when SFC /SCANNOW finds corrupted components and also fixes them on the same tun.
DISM /SCANHEALTH only checks for components that need to be repaired. /RESTOREHEALTH tries to fix what needs to be fixed.
I usually run SFC /SCANNOW before and after the DISM commands.

garlin · 2026-10-22T20:31:38-0400

What files do you see repaired in the SFC logs? If it corrects anything at the \Windows, \Windows\System32, \Program Files* level – those are not component files.

The component folders live under \Windows\WinSxS, with some package data in \Windows\Servicing.

Chestnut · 2026-10-22T20:36:03-0400

Zardoc said:
You're right, but if you run SFC again it gives a clean bill of health so there is or must be a bug in the restorehealth option with a specific setting or a removed key or something else because not everyone sees that error. I have that error but everything runs fine although I did disable a bunch of stuff. So, you play, you pay (in my case).

I've been having this dism /restorehealth "cannot find source ..." 0x800f0915 issue for months now, sfc always ends clean though. No major problems with this comp in general. Yet, I have an elephant in the room: I belong to those people that removed the 2 "unreclaimable packages" (un-removable?) that were always left over after a dism /startcomponentcleanup. There was this thread with a super enthusiastic onset I found at the time (the mood quickly changed 3-4 pages into that thread, but I did not read that far - tl;dr, my mistake).

From what I eyeballed on this forum, my impression was/is that there might be no relation between (a) removal of them packages and (b) the dism "cannot find source ... " error. So, I'd like to ask if anybody who has the current dism error 0x800f0915 did not remove those 2 componentstore packages? Then I can send the elephant away.

Maybe, when I've summoned up the courage, I'll try the windows update repair option. On the other hand, a windows registry error was somewhere said to be involved, might as well wait untill and if µSoft fixes it. It's not a biggy. Anyway, looks like computers are like people: quite similar on the outside but no two are the same.

Antrox41 · 2026-10-22T20:52:39-0400

Chestnut said:
I've been having this dism /restorehealth "cannot find source ..." 0x800f0915 issue for months now, sfc always ends clean though. No major problems with this comp in general. Yet, I have an elephant in the room: I belong to those people that removed the 2 "unreclaimable packages" (un-removable?) that were always left over after a dism /startcomponentcleanup. There was this thread with a super enthusiastic onset I found at the time (the mood quickly changed 3-4 pages into that thread, but I did not read that far - tl;dr, my mistake).

From what I eyeballed on this forum, my impression was/is that there might be no relation between (a) removal of them packages and (b) the dism "cannot find source ... " error. So, I'd like to ask if anybody who has the current dism error 0x800f0915 did not remove those 2 componentstore packages? Then I can send the elephant away.

Maybe, when I've summoned up the courage, I'll try the windows update repair option. On the other hand, a windows registry error was somewhere said to be involved, might as well wait untill and if µSoft fixes it. It's not a biggy. Anyway, looks like computers are like people: quite similar on the outside but no two are the same.

My logs said 242 file flags detected 193 repaired (flagged endlessly on each reboot). The unrepairable 49 were clustered at .8972 (25 files) and .9278 (17), with a few at .5074, .9168, .8737, .7705 and .1882. Components involved: FSRM, WPD shell extension, App-V, webcam UI host, event aggregation, filter manager utils, host guardian client, ICM UI, tethering, Explorer ADMX resources. All the same result with the 0x800f0915 source error. The scan was repeated several times over weeks of updates same end result different number of flagged files.

This is the summary of my log^^

This has been explained before so I will just repeat and quote what was said as to why the source error is happening.

"Many continue to get this issue even on the just released latest builds because the needed repair files are now stored in the cloud and many systems can no longer find the correct matching files from the cloud that are needed. Because Microsoft now forces Windows to rely heavily on dynamic cloud payloads for servicing, the Microsoft cloud servers contain severe file mismatches compared to what is actually running on users' machines."

fg2001gf11F · 2026-10-22T20:54:19-0400

garlin said:
What files do you see repaired in the SFC logs? If it corrects anything at the \Windows, \Windows\System32, \Program Files* level – those are not component files.

The component folders live under \Windows\WinSxS, with some package data in \Windows\Servicing.

It’s a known Windows issue — SFC often repairs Bluetooth driver files like BthHfEnum.sys after updates, even if the hardware works fine, and it’s not always a sign of a deeper problem.

I have never seen SFC results change after /RESTOREHEALTH on any of my machines.

garlin · 2026-10-22T21:03:48-0400

fg2001gf11F said:
It’s a known Windows issue — SFC often repairs Bluetooth driver files like BthHfEnum.sys after updates, even if the hardware works fine, and it’s not always a sign of a deeper problem.

The CU currently includes "BthHfEnum.sys" as part of the update.

But... users have been complaining about SFC repairing the BT drivers as far back as 4 years ago (way before the current round of DISM complaints).

https://www.reddit.com/r/Windows11/comments/urflz8/anyone_knows_why_my_system_has_found_corrupted

Bree · 2026-10-22T21:04:29-0400

fg2001gf11F said:
I see several cases when SFC /SCANNOW finds corrupted components and also fixes them on the same tun.

There are two types of errors that SFC reports that it has found and corrected. One is major, the other trivial.
The major error is a corrupt file that has been fixed with a good copy from the component store.
The trivial one is that ownership or security permissions have been set twice on a system file. It's trivial because both settings are the same and it has no effect at all on the running of Windows.

Both are reported at the command line with the same wording though. The only way to find which type was found/fixed is to read the log file C:\Windows\Logs\CBS\CBS.log

There's a lot in CBS.log besides SFC's reports. You need to filter it first, Option Three in Brink's tutorial.

When SFC runs from within Windows, it logs its actions into the C:\Windows\Logs\CBS\CBS.log file with [SR] tags.

This option creates a sfcdetails.txt file on your desktop that shows you only the specific SFC details from the huge CBS.log.

Use System File Checker (SFC) to Repair System Files in Windows 11

The trivial one does not have the [SR] tag, you'll need to search for the word 'twice' to find it. It's most commonly seen in Windows 10.

Bree said:
...the one thing SFC can find and fix that does not get the [SR] tag, that seems to only be used for corrupt files that need to be replaced. If it's just permissions/ownership then the file itself is not corrupt.

This seems to be found most often after installing a Preview cumulative update, the Patch Tuesday CUs seldom show this.

The error itself is trivial and would have no effect if left unfixed. If you run SFC /ScanNow to fix the permissions, you should find in CBS.log that the previous owner and the new owner are the same.

Code:

2022-03-23 14:29:03, Info CSI 0000007e Warning: Overlap: Directory \??\C:\WINDOWS\Logs\CBS\ is owned twice or has its security set twice Original owner: Microsoft-Windows-ServicingStack, version 10.0.19041.1613, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} New owner: Microsoft-Windows-ServicingStack, version 10.0.19041.1613, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} 2022-03-23 14:29:03, Info CSI 0000007f Warning: Overlap: Directory \??\C:\WINDOWS\Servicing\ is owned twice or has its security set twice Original owner: Microsoft-Windows-ServicingStack, version 10.0.19041.1613, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} New owner: Microsoft-Windows-ServicingStack, version 10.0.19041.1613, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} 2022-03-23 14:29:03, Info CSI 00000080 Warning: Overlap: Directory \??\C:\WINDOWS\Servicing\Packages\ is owned twice or has its security set twice Original owner: Microsoft-Windows-ServicingStack, version 10.0.19041.1613, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} New owner: Microsoft-Windows-ServicingStack, version 10.0.19041.1613, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

Ten Forums | SFC found integrity violations, how to check before fixing? - post #5

fg2001gf11F · 2026-10-22T21:13:13-0400

Bree said:
There are two types of errors that SFC reports that it has found and corrected. One is major, the other trivial.
The major error is a corrupt file that has been fixed with a good copy from the component store.
The trivial one is that ownership or security permissions have been set twice on a system file. It's trivial because both settings are the same and it has no effect at all on the running of Windows.

Both are reported at the command line with the same wording though. The only way to find which type was found/fixed is to read the log file C:\Windows\Logs\CBS\CBS.log

There's a lot in CBS.log besides SFC's reports. You need to filter it first, Option Three in Brink's tutorial.

Use System File Checker (SFC) to Repair System Files in Windows 11

The trivial one does not have the [SR] tag, you'll need to search for the word 'twice' to find it. It's most commonly seen in Windows 10.

Ten Forums | SFC found integrity violations, how to check before fixing? - post #5

I usually attach the CBS logs to the FBH reports if I see anything unusual. Those files are way too long to show them in here.

Nothing wrong currently on this build.

Microsoft Windows [Version 10.0.26300.9711]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH

Deployment Image Servicing and Management tool
Version: 10.0.26100.9549

Image Version: 10.0.26300.9711

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\System32>

fg2001gf11F · 2026-10-22T21:59:12-0400

Antrox41 said:
This is the summary of my log^^

This has been explained before so I will just repeat and quote what was said as to why the source error is happening.

"Many continue to get this issue even on the just released latest builds because the needed repair files are now stored in the cloud and many systems can no longer find the correct matching files from the cloud that are needed. Because Microsoft now forces Windows to rely heavily on dynamic cloud payloads for servicing, the Microsoft cloud servers contain severe file mismatches compared to what is actually running on users' machines."

Where did you find that comment about the cloud.
I don't have any issue on my machines, and I don't rely on the cloud at all.

0x800f0915 DISM Error

Hello, Today I updated my computer to the latest version, 25H2. So the current build is 26200.8524, but even though I performed a clean installation using the original ISO, the DISM tool keeps progressing but gives a 0x800f0915 error when it reaches the end. I can't figure out how to fix this...

www.elevenforum.com

JGToy · 2026-10-22T22:13:29-0400

neldog said:
This worked for me when my power plan got off track one time.

powercfg -restoredefaultschemes

Restart computer.

JGToy said:
I didn't know that! I will definitely going to try it.

The idea didn't worked for me, but I kept it on my annotations since I did not know it.
But, after several days fighting with it, today, came to my mind: CMOS, so I did it... Problem solved!
Thank you for your input.

Zardoc · 2026-10-22T22:40:50-0400

This how I go about. This time, all is clean.

Antrox41 · 2026-10-23T00:18:59-0400

fg2001gf11F said:
Where did you find that comment about the cloud.
I don't have any issue on my machines, and I don't rely on the cloud at all.

0x800f0915 DISM Error

Hello, Today I updated my computer to the latest version, 25H2. So the current build is 26200.8524, but even though I performed a clean installation using the original ISO, the DISM tool keeps progressing but gives a 0x800f0915 error when it reaches the end. I can't figure out how to fix this...

www.elevenforum.com

Was posted on another thread. What do you mean you don't rely on the cloud? DISM and the Restore Health function literally pull from it now if you don't point to a source, so does the WUS.

Another theory here also mentioned

Windows 11 Error with DISM RestoreHealth

If SFC works, and the system is running well (and repair installs are not failing), I personally wouldn't worrry about DISM. As always, YMMV I haven't elevated this one to "worry".

www.elevenforum.com

Anyway, i am done trying to solve this as its still clearly a microsoft related issue despite some people not having it.

Available	Next Step
	This update downloads and installs automatically from Windows Update and Microsoft Update.
	To install this update, download the standalone package(s) for this update from the Microsoft Update Catalog. This update contains MSU files that require installation in a specific order. Follow the Arm64 installation instructions or x64 installation instructions, as appropriate.

Win Update KB5127648 Windows 11 Cumulative Update build 26100.9711 (24H2), 26200.9711 (25H2), 26300.9711 (26H2) - Oct. 13

Announcements and messages​

Improvements​

Components updates​

Known issues in this update​

How to get this update​

Deployment​

Install this update​

File information​

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Active member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Too young to know

My Computer My Computer

At a glance

Dazed & Confused

My Computer My Computer

At a glance

Active member

My Computer My Computer

At a glance

Similar threads

Announcements and messages

Improvements

Components updates

Known issues in this update

How to get this update

Deployment

Install this update

File information

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computers

My Computer

My Computer

My Computer

My Computer

My Computer