HELLO! DISM Health-Check Failure (0x800f0915) After W10UI Update Integration on IoT Enterprise LTSC 26100.1742 → 26200.8968 Code: DISM Health-Check Failure (0x800f0915) After W10UI Update Integration on IoT Enterprise LTSC 26100.1742 → 26200.8968 TL;DR After integrating a July 2026 LCU + Enablement Package + Defender update into an IoT Enterprise LTSC base image via W10UI v10.62, a post-build DISM /Cleanup-Image /ScanHealth on the finished install.wim reports 196 corrupt payload files across 76 unrelated components, and /RestoreHealth fails with 0x800f0915 (CBS_E_REPAIR_CONTENT_MISSING). This exact workflow has been run successfully many times before; this is the first failure. Suspected cause: the UseWimlib export option breaking WinSxS hardlink integrity during the final install.wim rebuild, combined with /ResetBase having already stripped superseded payloads that DISM would normally use to self-repair. Environment Item Detail Base image Windows 11 IoT Enterprise LTSC, build 26100.1742 Tool W10UI v10.62 W10UI options LCUmsuExpand 1, Cleanup, ResetBase, UseWimlib, WinRE, ISO, Delete_Source Packages integrated LCU: Windows11.0-KB5101684-x64.msu (Combined UUP) — RollupFix 26100.8968.1.30 Enablement: Windows11.0-KB5054156-x64.cab — 26100.6717.1.4 Defender: defender-dism-x64.cab SSU: Windows11.0-KB5101711-x64_inout.cab — auto-extracted by W10UI from the Combined UUP .msu (not added manually) — Package_for_ServicingStack_8962 (26100.8962.1.12) Resulting build 26200.8968.260717-1759.25H2_GE_RELEASE_SVC_PROD3_CLIENT_X64FRE_EN-US (the 26100→26200 jump is the expected effect of the Enablement Package, not a version mismatch) Baseline (Before Updates) A full SFC (System File Checker) scan was run on the base ISO (26100.1742) before any package integration, and no errors were detected. This confirms the starting point is clean and the issue is introduced during the integration/rebuild process, not in the original image. Workflow (All Steps Succeed) Mount sources\install.wim (index 1/1) — native DISM. Install servicing stack update (26100.8962) — succeeds. Install KB5054156 (Enablement) and RollupFix KB5101684 (26100.8968) — both succeed. Run /ResetBase on the OS image — succeeds. Add Defender update, update winre.wim — succeeds. Unmount and save install.wim — succeeds. Rebuild/re-export sources\install.wim via W10UI's UseWimlib option (wimlib-imagex instead of native wimgapi) — completes without reported error. Same servicing stack sequence repeated for boot.wim indexes 1/2 and 2/2 — all succeed. ISO created via oscdimg — succeeds. Every step in the build log (W10UI_RUN.txt) reports The operation completed successfully. There is no error anywhere in the build itself. Symptom Running the post-build image-cleanup tool (LIMPIEZA_Y_REPARACION_RUN.txt) against the finished, already-built install.wim (mounted offline to C:\TEMP): Command Result [1] CheckHealth No component store corruption detected. [2] ScanHealth Diagnóstico: DAÑADA (Reparable) [3] RestoreHealth Fails with: Error: 0x800f0915 — The repair content could not be found anywhere. dism.log shows the deep scan detecting: text Corruption detection complete. numCorruptions = 196, Disp = 1. Key detail: The corruptions are exclusively payloads: text CSI Payload Corrupt: 196 CSI Manifest Corruption: 0 This means manifests (metadata) are intact, but physical files are "disconnected" — exactly what you'd expect from broken hardlinks. The 196 corrupt payload entries span 76 completely unrelated component families — NFS admin/client tools, IIS (w3svc), DirectX (direct3d10, directinput), TV tuner filter drivers, ACM audio codecs, com-complus-runtime, AzMan, logman/relog/diskperf, WebView2, AppV, HostGuardianClient, NetAdapterCim, etc. — with version tags ranging across the entire build's component set, from the base 10.0.26100.1882 through the latest-installed 10.0.26100.8968. There is no thematic or version-band clustering that would point to a single bad package. What Was Ruled Out ❌ SSU/LCU version mismatch The SSU (26100.8962) having a lower build number than the LCU (26100.8968) is normal — SSUs and LCUs are versioned on independent tracks and are not required to align. The SSU was also not added manually; it was auto-extracted by W10UI from the Combined UUP .msu, exactly as intended. ❌ Branch/channel incompatibility The 26100.x → 26200.x jump is the documented, expected behavior of the Enablement Package (KB5054156), not evidence of mixing release branches. Final ISO name (25H2_GE_RELEASE) confirms a single consistent branch. ❌ CBS "Virtual Edition" mapping line The IoTEnterpriseSEdition → EnterpriseSEdition mapping is routine and appears identically during phases that completed without error — not diagnostic of the failure. ❌ Package application failure Ruled out because every package installation step in W10UI_RUN.txt completes successfully with no CBS/DISM errors during application. A genuine SSU/LCU incompatibility would be expected to fail at package-apply time, not silently pass and only surface on a later full-store deep scan. Working Theory The corruption signature — broad, cross-component, cross-version, unrelated to the specific KBs applied — is not consistent with damage introduced by the LCU/Enablement/Defender packages themselves. It is consistent with broken WinSxS hardlink groups introduced during the install.wim re-export step. This run used UseWimlib (wimlib-imagex) instead of native wimgapi/DISM export. wimlib rebuilds hardlink groups independently by matching payload content/attributes during capture, and does not always reproduce the exact hardlink table DISM/CBS expects for the component store. Files that should share a single payload can end up detached, which CSI's deep scan then reports as "Payload Corrupt" even though the underlying data isn't necessarily damaged. Because /ResetBase ran before this re-export (in the same session), the superseded package payloads that RestoreHealth would normally pull from to self-repair had already been purged — leaving no local source and producing 0x800f0915. This is the first run using UseWimlib that failed, after previously identical workflows (without this option, or on earlier W10UI versions) succeeded — consistent with the export step being the point of introduction. Diagnostic Tests in Progress Test Description A Re-run the identical workflow with UseWimlib disabled, letting W10UI use the native DISM exporter, and compare results. B Run DISM /Image:C:\TEMP /Cleanup-Image /ScanHealth immediately after the mount/update/unmount cycle, before the install.wim rebuild step, to confirm the image is clean at that point and isolate whether the wimlib re-export is where the corruption is introduced. C Re-run with UseWimlib enabled but without /ResetBase, to determine if the issue is wimlib alone or the combination of wimlib + ResetBase. Question for the Community Has anyone else seen UseWimlib in W10UI introduce WinSxS payload corruption on export, specifically on IoT Enterprise LTSC bases combined with /ResetBase? Looking for confirmation this is a known wimlib/hardlink limitation versus something specific to this build combination. Any insights, workarounds, or suggestions would be greatly appreciated. dism.log — Detailed CBS/CSI corruption report
Missing the point, LTSC never will get the 25H2 EKB offered, that is by design because LTSC never will get feature ugrades, The stuff about W10UI i leave to @abbodi1406
I understand that, but I tested it using the direct ISO from UUP dump (Windows 11 Pro), and after running the test, it also says it's corrupted; that means the problem lies directly with the update. The UUPdump ISO is a completely standard retail build, not LTSC, and not modified by me in any way. Since it shows the exact same DISM error, the issue is clearly with the build itself, not with the integration process or the edition The idea here was to look for answers regarding this.
Yes, I tried it with wimlib 0 and without `/ResetBase`, but I still got an error when verifying the image integrity. I also tried the version directly from UUPdump without any modifications, and that one is corrupted too. Then I tried the previous update (26200.8894), and that one has no errors. Code: ======================================================= Image Cleanup Tools ======================================================= [1] Quick Health Check (DISM /CheckHealth) [2] Advanced Scan (Slow) (DISM /ScanHealth) [3] Repair Image (DISM /RestoreHealth) [4] SFC Repair (Offline) (SFC /Scannow /OffWindir) [5] Analyze Component Store (DISM /AnalyzeComponentStore) [6] Clean Up Components (DISM /StartComponentCleanup) [7] Run ALL (1-6) ------------------------------------------------------- [V] Back Select an option: 7 Before starting: Do you want to include the /ResetBase parameter in the final cleanup? [WARNING] This will prevent uninstalling previous updates (Y/N): Y [1/5] Quick health check (CheckHealth)... Deployment Image Servicing and Management tool Version: 10.0.26100.8737 Image Version: 10.0.26200.8894 No component store corruption detected. The operation completed successfully. [2/5] Running full scan (ScanHealth)... Diagnosis: HEALTHY (No repair required) [3/5] Repairing image... >>> SKIPPED: Image is already healthy. [4/5] Verifying files (SFC)... Beginning system scan. This process will take some time. Windows Resource Protection did not find any integrity violations. [5/5] Analyzing/Cleaning up components... Proceeding with cleanup... Deployment Image Servicing and Management tool Version: 10.0.26100.8737 Image Version: 10.0.26200.8894 [===========================70.0%======== ] The operation completed successfully. [OK] Sequence completed. Press Enter to continue...:
26200.8968 gives SFC.exe scan errors? or only Dism /Restore-Health? if update integrtion completed sucessfully, then we have nothing to change or fix
Yes, it seems the update has that issue; the last test I haven't run yet is creating it from the instance installed on the host itself, just in case the DISM version is causing this.
It seems to be related to the DISM version; when installing the resulting ISO and running the repair tool, it reports that the system is healthy. I'm just sharing this in case anyone else has the same problem. Code: ============================================================ Image Cleanup Tools ============================================================ Mode : ONLINE [ASUSROGSTRIX | 10.0.26200.0] ============================================================ [1] Check Health (Quick) (DISM /CheckHealth) [2] Advanced Scan (Slow) (DISM /ScanHealth) [3] Repair Image (DISM /RestoreHealth) [4] SFC Repair (SFC /Scannow) [5] Analyze Component Store (DISM /AnalyzeComponentStore) [6] Clean Up Components (DISM /StartComponentCleanup) [7] Run ALL (1-6) ------------------------------------------------------------ [B] Back to main menu [AUTO] Seleccionando opcion [7] Run ALL... Do you want to include /ResetBase in the final cleanup (step 5/5)? [WARNING] Prevents uninstalling previous updates. [AUTO] Include /ResetBase? -> Y (automatico) ------------------------------------------------------------ [1/5] Checking quick health (CheckHealth)... ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.26100.8968 Image Version: 10.0.26200.8968 No component store corruption detected. The operation completed successfully. ------------------------------------------------------------ [2/5] Performing deep scan (ScanHealth)... ------------------------------------------------------------ Diagnosis: HEALTHY - No repair required. ------------------------------------------------------------ [3/5] Repairing image (RestoreHealth)... ------------------------------------------------------------ >>> SKIPPED: The image is already healthy. ------------------------------------------------------------ [4/5] Verifying system files (SFC)... ------------------------------------------------------------ Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. [OK] SFC: No integrity violations found. ------------------------------------------------------------ [5/5] Analyzing and cleaning component store... ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.26100.8968 Image Version: 10.0.26200.8968 [======== 14.9% ] [========== 18.2% ] [========== 18.2% ] [=========== 19.5% ] [================= 29.9% ] [======================= 41.0% ] [===========================53.5% ] [===========================60.0%== ] [===========================82.3%=============== ] [===========================97.7%======================== ] [===========================97.7%======================== ] [==========================100.0%==========================] Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store : 10.05 GB Actual Size of Component Store : 9.95 GB Shared with Windows : 6.81 GB Backups and Disabled Features : 2.95 GB Cache and Temporary Data : 188.18 MB Date of Last Cleanup : 2026-07-22 23:23:57 Number of Reclaimable Packages : 2 Component Store Cleanup Recommended : Yes The operation completed successfully. Component cleanup recommended. Proceeding... Deployment Image Servicing and Management tool Version: 10.0.26100.8968 Image Version: 10.0.26200.8968 [===========================70.0%======== ] The operation completed successfully. ============================================================ [OK] Full sequence completed successfully. ============================================================ Press Enter to continue...:
Code: ====================== W10UI v10.62 ======================= [1] Target (x64): "E:\W10UI_28000\28000.1450_Work_NL" [2] Updates: "E:\W10UI_28000\Updates" [3] DISM: "Windows NT 10.0 ADK" [4] Enable .NET 3.5: NO [5] Cleanup System Image: YES [6] Reset Image Base: YES / Extra [7] Update WinRE.wim: YES [8] install.wim selected indexes: 4 / [K] Keep indexes: Selected [M] Mount Directory: "c:\W10UImount_3193" [E] Extraction Directory: "c:\W10UItemp_*****" ============================================================ Change a menu option, press 0 to start the process, or 9 to exit: Code: ============================================================ Running W10UI v10.62 ============================================================ ============================================================ Configured Options... ============================================================ LCUmsuExpand 1 Cleanup ResetBase UpdtBootFiles WinRE ISO ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting UpdateCompression.dll file... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/1: windows11.0-kb5101681-x64_LCU_2608.1.29.msu [Combined UUP] ============================================================ Extracting files from update containers (cab/wim)... *** This will require some disk space, please be patient *** ============================================================ 1/9: defender-dism-x64_steven4554_July_21_2026.cab 2/9: Windows11.0-KB5077868-x64.cab [SSU] 3/9: Windows11.0-KB5081921-x64_Critical_OOBE_1701.1.1.cab [OOBE] 4/9: windows11.0-kb5082960-x64_OOBE_1706.1.3.cab 5/9: Windows11.0-KB5101002-x64-NDP481_CU_9340.3.cab [NetFx] 6/9: windows11.0-kb5101718-x64_DU_SafeOS_2605.1.9.cab [SafeOS DU] 7/9: windows11.0-kb5106083-x64_DU_Sources_2605.cab [Setup DU] 8/9: Windows11.0-KB5101747-x64_inout.cab [SSU] 9/9: Windows11.0-KB5101681-x64.wim [LCU] ============================================================ Mounting sources\install.wim - index 4/8 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Processing 1 of 1 - Adding package Package_for_ServicingStack_2602~31bf3856ad364e35~amd64~~28000.2602.1.2 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2602 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Processing 1 of 3 - Adding package Package_for_KB5081921~31bf3856ad364e35~amd64~~28000.1701.1.1 [==========================100.0%==========================] Processing 2 of 3 - Adding package Package_for_KB5082960~31bf3856ad364e35~amd64~~28000.1706.1.3 [==========================100.0%==========================] Processing 3 of 3 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9340.3 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~28000.2608.1.29 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting OS image base... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.2608 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.2608 [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding Defender update... ============================================================ Platform : 4.18.26060.3008 Engine : 1.1.26060.3008 Signatures: 1.455.259.0 ============================================================ Updating winre.wim ... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2602~31bf3856ad364e35~amd64~~28000.2602.1.2 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2602 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1 Processing 1 of 1 - Adding package Package_for_SafeOSDU~31bf3856ad364e35~amd64~~28000.2605.1.9 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.2605 [===========================71.8%========= ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.2605 [===========================70.0%======== ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image File : E:\W10UI_28000\winre.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding updated winre.wim ... ============================================================ 1 file(s) copied. ============================================================ Unmounting sources\install.wim - index 4/8 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image File : E:\W10UI_28000\28000.1450_Work_NL\sources\install.wim Image Index : 4 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Rebuilding sources\install.wim ... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Mounting sources\boot.wim - index 1/2 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Processing 1 of 1 - Adding package Package_for_ServicingStack_2602~31bf3856ad364e35~amd64~~28000.2602.1.2 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2602 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~28000.2608.1.29 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting WinPE image base... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.2608 [===========================70.0%======== ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.2608 [===========================70.0%======== ] The operation completed successfully. ============================================================ Unmounting sources\boot.wim - index 1/2 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image File : E:\W10UI_28000\28000.1450_Work_NL\sources\boot.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Mounting sources\boot.wim - index 2/2 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Processing 1 of 1 - Adding package Package_for_ServicingStack_2602~31bf3856ad364e35~amd64~~28000.2602.1.2 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2602 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~28000.2608.1.29 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting WinPE image base... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.2608 [===========================70.0%======== ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.2608 [===========================70.0%======== ] The operation completed successfully. ============================================================ Unmounting sources\boot.wim - index 2/2 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image File : E:\W10UI_28000\28000.1450_Work_NL\sources\boot.wim Image Index : 2 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Rebuilding sources\boot.wim ... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Exporting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding setup dynamic update(s)... ============================================================ windows11.0-kb5106083-x64_DU_Sources_2605.cab ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Creating updated ISO file... ============================================================ ISO Location: "E:\W10UI_28000" OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (1000 files in 93 directories) Scanning source tree complete (1060 files in 97 directories) Computing directory information complete Image file is 8214052864 bytes (before optimization) Writing 1060 files in 97 directories to 28000.2608.260724-1812.BR_RELEASE_SVC_PROD3_CLIENT_X64FRE_NL-NL.iso 100% complete Storage optimization saved 69 files, 15642624 bytes (1% of image) After optimization, image file is 8200921088 bytes Space saved because of embedding, sparseness or optimization = 15642624 Done. ============================================================ Finished ============================================================ Press 9 or q to exit. Updated: https://forums.mydigitallife.net/posts/1895887