I am unable to install Windows 11 Insider Preview Experimental Build 28120.2912 over my current Build 28120.2630

Question

I am unable to install Windows 11 Insider Preview Experimental Build 28120.2912 over my current Build 28120.2630

Артур Гроховский 10

I am unable to install Windows 11 Insider Preview Experimental Build 28120.2912 over my current Build 28120.2630.

Windows Update repeatedly fails with the following message:

“Some update files are missing or have problems. We’ll try to download the update again later.”

Error code: 0x80073712

The failure is fully reproducible.

So far I have tried the following:

Restarted the PC and retried the update several times.
Ran: DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow

All of these commands completed successfully and reported no unresolved corruption.

Reset Windows Update components by stopping wuauserv, BITS and cryptsvc, renaming SoftwareDistribution and catroot2, restarting the services, rebooting, and downloading the update again.

The result was exactly the same: 0x80073712.

I then checked CBS.log. The failure appears to occur while servicing the Microsoft-Windows-WAB-App component during the transition from version 10.0.28000.2630 to 10.0.28000.2912.

The key lines are:

“Delta file missing on generating delta for: wab.exe”

followed by:

“Attempting to mark store corrupt with category: CorruptPayloadFile”

and then:

“STATUS_SXS_COMPONENT_STORE_CORRUPT”

The transaction subsequently fails with:

HRESULT_FROM_WIN32(ERROR_SXS_COMPONENT_STORE_CORRUPT) 0x80073712

I also checked the WinSxS component directories.

The current 28000.2630 component contains the full wab.exe file.

For 28000.2912, the component directory contains:

wabmig.exe
r\wabmig.exe
r\wab.exe

but there is no full wab.exe in the 28000.2912 component directory.

This seems to suggest that the failure occurs while Windows is reconstructing the new wab.exe from the differential update payload rather than because the currently installed wab.exe is missing.

Since DISM and SFC both report the component store as healthy, and resetting Windows Update and downloading the package again does not change the result, I am wondering whether this could be a problem with the differential servicing payload for Build 28120.2912, or specifically with the update path from 28120.2630 to 28120.2912.

Has anyone else encountered 0x80073712 with Build 28120.2912?

I can provide the full CBS.log and a filtered log containing the WAB-related failure if needed.I am unable to install Windows 11 Insider Preview Experimental Build 28120.2912 over my current Build 28120.2630.

Windows Update repeatedly fails with the following message:

“Some update files are missing or have problems. We’ll try to download the update again later.”

Error code: 0x80073712

The failure is fully reproducible.

So far I have tried the following:

Restarted the PC and retried the update several times.
Ran:
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

All of these commands completed successfully and reported no unresolved corruption.

Reset Windows Update components by stopping wuauserv, BITS and cryptsvc, renaming SoftwareDistribution and catroot2, restarting the services, rebooting, and downloading the update again.

The result was exactly the same: 0x80073712.

I then checked CBS.log. The failure appears to occur while servicing the Microsoft-Windows-WAB-App component during the transition from version 10.0.28000.2630 to 10.0.28000.2912.

The key lines are:

“Delta file missing on generating delta for: wab.exe”

followed by:

“Attempting to mark store corrupt with category: CorruptPayloadFile”

and then:

“STATUS_SXS_COMPONENT_STORE_CORRUPT”

The transaction subsequently fails with:

HRESULT_FROM_WIN32(ERROR_SXS_COMPONENT_STORE_CORRUPT)
0x80073712

I also checked the WinSxS component directories.

The current 28000.2630 component contains the full wab.exe file.

For 28000.2912, the component directory contains:

wabmig.exe
r\wabmig.exe
r\wab.exe

but there is no full wab.exe in the 28000.2912 component directory.

This seems to suggest that the failure occurs while Windows is reconstructing the new wab.exe from the differential update payload rather than because the currently installed wab.exe is missing.

Since DISM and SFC both report the component store as healthy, and resetting Windows Update and downloading the package again does not change the result, I am wondering whether this could be a problem with the differential servicing payload for Build 28120.2912, or specifically with the update path from 28120.2630 to 28120.2912.

Has anyone else encountered 0x80073712 with Build 28120.2912?

I can provide the full CBS.log and a filtered log containing the WAB-related failure if needed.

0 comments

2 answers

Your answer

Answer 1

Vikki-T 9,850 Microsoft External Staff Moderator

Hi Артур Гроховский,

Thank you for providing such a detailed investigation and for including the relevant CBS entries. Since DISM, SFC, and a Windows Update component reset have already completed successfully, repeating those standard repair steps is unlikely to provide additional information.

At this stage, I would suggest checking the release notes for this Insider build and submitting the issue through Feedback Hub under Install and update > Downloading, installing, and configuring Windows Update. Please attach the full CBS log, the filtered entries, the current and target build numbers, and the exact error code. You can open Feedback Hub by pressing Win + F.

If you decide to share the full CBS.log publicly, please review it first and redact any personal or device-specific information it may contain, such as your Windows account name, device name, or file paths containing your user profile folder.

If possible, please also share the Feedback Hub link here so that other Insiders who experience the same failure can upvote it and add diagnostic data. Since this is an Experimental Insider build and the usual servicing repairs have not resolved the failure, the Windows Insider engineering team would be best positioned to determine whether the differential update payload is affected.

In the meantime, check whether a newer build becomes available for the same channel. If the device remains unable to move forward, back up your important files before considering recovery or a clean installation of an available Insider build. Thank you so much for your understanding.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Артур Гроховский 10 Reputation points

2026-09-09T18:57:00.6166667+00:00

Hi Vicky

Thank you for the response.

I have already submitted the issue through Feedback Hub under the Windows Update installation category and attached the full CBS.log together with a filtered extract covering the failure.

The issue is still reproducible when updating from Build 28120.2630 to 28120.2912. Windows Update consistently fails with 0x80073712.

The standard servicing checks do not report unresolved corruption:

DISM /ScanHealth completes successfully

DISM /RestoreHealth completes successfully

sfc /scannow completes successfully

Windows Update components were reset and the update package was downloaded again

Despite this, CBS fails consistently during servicing of Microsoft-Windows-WAB-App. The relevant sequence is:

“Delta file missing on generating delta for: wab.exe”

followed by:

“Attempting to mark store corrupt with category: CorruptPayloadFile”

and then:

STATUS_SXS_COMPONENT_STORE_CORRUPT / 0x80073712

The failure occurs while transitioning the component from 10.0.28000.2630 to 10.0.28000.2912.

Since the existing 28000.2630 wab.exe payload is present in WinSxS, while the 28000.2912 component staging appears incomplete, the failure may be related to the differential servicing path or payload for this update rather than to a persistent component store corruption detectable by DISM or SFC.

At this point I will avoid further manual servicing changes and wait for either guidance from the Insider engineering team or a newer build in the same channel.

I post the Feedback Hub link here as well so that other affected Insiders can upvote the report and attach additional diagnostics: Thank you for the response.
Vikki-T 9,850 Reputation points Microsoft External Staff Moderator

2026-09-10T11:09:42.8866667+00:00

Hi Артур Гроховский,

Thank you so much for the update.

If you ever have any other questions or run into anything in the future, please feel free to post your question on the Microsoft Q&A Forum anytime. I’ll always be here and ready to assist you.

Wishing you a great experience ahead!
Артур Гроховский 10 Reputation points

2026-09-10T18:54:55.91+00:00

Hi Vicky

Thanks for the reply.

So far it looks like no one else has run into this exact error. That's a bit puzzling, especially since both DISM and SFC aren't finding any issues.

Should I just chalk this up to a problem specific to my particular hardware/software configuration, or is it still worth trying something like updating via an ISO built through UUP?
Vikki-T 9,850 Reputation points Microsoft External Staff Moderator

2026-09-11T09:23:34.96+00:00

Hi Артур Гроховский,

The fact that no one else has reported the exact same failure does not necessarily mean that it is specific to your hardware or software configuration.

I would be cautious about using an ISO created through UUP as a workaround. Because it is not an official Microsoft-provided installation image, a failed ISO upgrade could introduce additional variables and make the original servicing issue more difficult to diagnose.

Since you have already submitted the relevant logs through Feedback Hub, the safer approach would be to keep the current report available for additional diagnostics and check whether Microsoft releases a newer build for the same Insider channel. If Microsoft provides an official Insider ISO that matches an appropriate build and edition, that would be preferable to a manually created image.

In the meantime, I would also avoid manually replacing wab.exe or modifying the WinSxS component folders, as those changes could further affect the servicing state. Please continue to back up any important files while monitoring the Feedback Hub report and Windows Update. Thank you so much for your cooperation.
Артур Гроховский 10 Reputation points

2026-09-11T19:57:55.4233333+00:00

Hi Vicky

An update on this issue:

A newer Experimental flight, Build 28120.3002 (KB5124112), has now become available. Unfortunately, it fails to install with exactly the same 0x80073712 error.

I checked CBS.log again, and the failure is effectively identical to the one seen with Build 28120.2912.

The relevant sequence is again:

“Delta file missing on generating delta for: wab.exe”

followed by:

“Attempting to mark store corrupt with category: CorruptPayloadFile”

and:

STATUS_SXS_COMPONENT_STORE_CORRUPT

CBS again identifies the failing component transition as:

Microsoft-Windows-WAB-App 10.0.28000.2630 -> 10.0.28000.2912

The new cumulative package itself is:

Package_for_RollupFix~31bf3856ad364e35~amd64~~28000.3002.1.0

Identifier: KB5124112

So although the target flight is now 28120.3002, servicing still fails while attempting to bring Microsoft-Windows-WAB-App through the 28000.2912 component state.

This makes it much less likely that the original failure was specific only to the 28120.2912 update package. It now appears more likely that there is a persistent servicing/differential payload problem affecting this particular component on my current 28120.2630 installation.

DISM /ScanHealth, DISM /RestoreHealth, and sfc /scannow still do not report unresolved corruption.

At this point I am going to try the supported “Fix problems using Windows Update > Reinstall now” repair installation of the current Windows version, which should preserve files, applications, and settings.

After that completes, I will retry Build 28120.3002 and report whether the same WAB servicing failure still occurs.
Артур Гроховский 10 Reputation points

2026-09-12T00:25:54.6266667+00:00

Hi Vicky

Resolved.

I performed the supported repair reinstall using:

Settings → System → Recovery → Fix problems using Windows Update → Reinstall now

The repair installation completed successfully and preserved my applications, files, and settings.

After the repair, Windows 11 Insider Preview Build 28120.3002 installed successfully. winver confirms that the system is now running Build 28120.3002.

I then ran:

DISM /Online /Cleanup-Image /ScanHealth

and DISM reported:

“No component store corruption detected. The operation completed successfully.”

Before the repair reinstall, both Builds 28120.2912 and 28120.3002 had repeatedly failed with 0x80073712, and CBS.log consistently showed the same failure while servicing Microsoft-Windows-WAB-App:

Delta file missing on generating delta for: wab.exe

followed by CorruptPayloadFile and STATUS_SXS_COMPONENT_STORE_CORRUPT.

Since Build 28120.3002 installed successfully immediately after the repair reinstall, this strongly suggests that the problem was caused by a persistent local servicing/component-store state that was not detected or corrected by DISM, SFC, or resetting Windows Update components alone.

In my case, Fix problems using Windows Update → Reinstall now was the effective solution.

Thank you for the assistance.

Answer 2

Error 0x80073712 maps to component store corruption. The CBS entries cited (STATUS_SXS_COMPONENT_STORE_CORRUPT, missing delta payload, and CorruptPayloadFile) are consistent with that condition even when DISM /RestoreHealth and sfc /scannow do not report unresolved corruption.

Since the standard repair steps were already completed and the failure is reproducible, the supported next actions are:

Inspect C:\Windows\Logs\CBS\CBS.log for the exact failing package or component.
- Search for Error, CORRUPT, MISSING, or HRESULT.
- The package name in the failing entry identifies the corrupted update/component.
If the specific corrupted package can be identified, try removing that package and then repairing the image:

DISM.exe /Online /Remove-Package /PackageName:<package-name-from-log>
DISM.exe /Online /Cleanup-Image /RestoreHealth

If /RestoreHealth is not sufficient, run DISM with a known-good Windows installation source that matches the installed OS version and build:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess
sfc /scannow

Retry Windows Update after the repair completes.
If the update still fails, perform a repair reinstall of the current Windows version using the built-in recovery path:
- Settings > System > Recovery
- Under Fix problems using Windows Update, select Reinstall now
- This repair installation keeps files, apps, and settings.

Important: do not manually delete files from WinSxS. Some files in that folder are required for boot and servicing, and deleting them can severely damage the system.

References: