DISM Unable to Fix Corrupt Component Store After Installing Windows 11 26H2 CU November 10, 2026—KB5132061

Neil Hobbs 5 Reputation points
2026-11-11T17:12:39.7533333+00:00

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

Windows for home | Windows 11 | Windows update
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-11-11T17:13:49.4033333+00:00

    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^

    1. Back up important files as a precaution.
    2. Connect the PC to mains power and maintain its internet connection.
    3. Open Start > Settings > System > Recovery.
    4. Under Fix problems using Windows Update, select Reinstall now.
    5. Select OK and let Windows download and install the repair version.
    6. Restart when prompted. This operation reinstalls the same Windows version and preserves applications, files, and settings.^1^
    7. After restarting, open Terminal (Admin) and run:
    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.

    What error 0x800f0915 establishes

    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.

    If “Reinstall now” is missing or fails

    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:

    1. Obtain Windows 11 installation media matching Windows 11 26H2, architecture, language, and edition.
    2. From within the running Windows installation, mount the ISO and run setup.exe.
    3. Choose Keep personal files and apps.
    4. Complete Setup and rerun 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.

    Status of the November update

    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.log
    • C:\Windows\Logs\CBS\CBS.log
    • A screenshot or copy of the /ScanHealth result

    References

    1. Fix issues by reinstalling the current version of Windows | Microsoft Support
    2. Repair a Windows Image
    3. November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100 ...
    4. Configure a Windows Repair Source
    5. Windows 11, version 26H2 known issues and notifications
    6. June 9, 2026—KB5094126 (OS Builds 26200.8655 and 26100.8655 ...
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Ramesh 183.6K Reputation points Volunteer Moderator
    2026-11-11T17:28:20.0366667+00:00

    Hi Neil,

    Please share C:\Windows\Logs\CBS\CBS.log on OneDrive and post the link here.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.