Hi Neil,
Please share C:\Windows\Logs\CBS\CBS.log on OneDrive and post the link here.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have just installed the Windows 11 26H2 CU November 10, 2026—KB5132061 and as usual, it has corrupted the Component Store. So I have ran the following command as an Admin;
dism /online /cleanup-image /restorehealth
The process got to 65% and then ended with the following error message;
C:\Windows\System32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.26100.9549
Image Version: 10.0.26300.9974
[==========================100.0%==========================]
Error: 0x800f0915
The repair content could not be found anywhere.
Check the internet connectivity or use the "Source" option to specify the location of the files that are required to restore the image. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Can someone advise on how to fix this issue and when the issues with the November 2026 CU will be resolved?
Many thanks in advance,
Kind regards
Neil
Hi Neil,
Please share C:\Windows\Logs\CBS\CBS.log on OneDrive and post the link here.
AI answer
Use Settings > System > Recovery > Fix problems using Windows Update > Reinstall now to reinstall the current Windows 11 26H2 build and rebuild its system files and components without removing apps, files, or settings.^1^
DISM /Online /Cleanup-Image /ScanHealth
sfc /scannow
The expected result is that DISM reports no component-store corruption and SFC reports no integrity violations or successfully repairs affected files.
0x800f0915 means DISM could not obtain the required repair content. By itself, it does not prove that KB5132061 corrupted the component store. /ScanHealth is the appropriate check for whether corruption exists; /RestoreHealth then attempts a repair if the image is repairable.^2^
Your version lines are expected for this release family: KB5132061 brings Windows 11 26H2 to OS build 26300.9974, while servicing components can retain a 26100 version line.^3^ The differing DISM and image version numbers therefore do not, on their own, establish an incompatible DISM installation.
That option can be unavailable on work- or school-managed PCs, devices governed by certain Windows Update policies, or unsupported older configurations.^1^
In that case, use an in-place repair installation:
setup.exe.DISM /Online /Cleanup-Image /ScanHealth.A manually supplied DISM source is another option only when the source contains the files required by the installed system. Microsoft notes that a source below the target’s cumulative-update level can fail because it lacks the newer files.^4^ Consequently, an older 26H2 ISO may produce the same error and should not be treated as a definitive test.
Microsoft’s KB5132061 page currently says it is not aware of any issues with this update.^3^ The Windows 11 26H2 release-health page also does not list DISM error 0x800f0915 as an open KB5132061 issue.^5^
Therefore, Microsoft has not published a resolution date for this specific KB5132061/26H2 symptom. An earlier update fixed the same error on some Windows 11 24H2 devices, but that statement does not establish that the November 26H2 case has the same cause.^6^
If the repair reinstall fails, preserve these files before contacting Microsoft through Get Help:
C:\Windows\Logs\DISM\dism.logC:\Windows\Logs\CBS\CBS.log/ScanHealth resultReferences