Windows 10.0.18362.145 KB4498523 - DISM fails offline /ResetBase (This was meant to have been fixed)

%3CLINGO-SUB%20id%3D%22lingo-sub-661335%22%20slang%3D%22en-US%22%3EWindows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fixed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-661335%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20previously%20posted%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWinHEC-Online%2FADK-18362-1-DISM-Fails-Offline-Install-for-kb4497936-kb4505057%2Fm-p%2F569470%3Fsearch-action-id%3D89024127053%26amp%3Bsearch-result-uid%3D569470%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWinHEC-Online%2FADK-18362-1-DISM-Fails-Offline-Install-for-kb4497936-kb4505057%2Fm-p%2F569470%3Fsearch-action-id%3D89024127053%26amp%3Bsearch-result-uid%3D569470%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKB44985263%20and%20KB4497935%20will%20successfully%20complete%20cleanup%20on%20Winre.wim.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EHowever%3C%2FSTRONG%3E%2C%20DISM%20ADK%2018362.1%20is%20failing%20SSU%20%3CSTRONG%3EKB4498523%3C%2FSTRONG%3E%20and%20LCU%20%3CSTRONG%3EKB4497935%3C%2FSTRONG%3E%20offline%20Component%20Cleanup%20and%20Reset%20Base.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20quoting%20the%20following%20from%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-au%2Fhelp%2F4498523%2Fwindows-10-update-kb4498523%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-au%2Fhelp%2F4498523%2Fwindows-10-update-kb4498523%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CH1%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%20id%3D%22toc-hId-1961185159%22%3EServicing%20stack%20update%20for%20Windows%2010%2C%20Version%201903%3A%20May%2029%2C%202019%3C%2FH1%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EAddresses%20an%20issue%20in%20which%20updates%20may%20fail%20to%20install%20after%20the%20%2F%3CSTRONG%3Eresetbase%3C%2FSTRONG%3E%20command%20in%20%3CSTRONG%3EDISM%3C%2FSTRONG%3E%20is%20run.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20image%20cleanup%20will%20fail%20with%20and%20without%20%2FResetBase%3C%2FP%3E%3CPRE%3EPS%20E%3A%5CWinROG%26gt%3B%20DISM%20%2FImage%3Amount%5COS%20%2FCleanup-Image%20%2FStartComponentCleanup%20%3CBR%20%2F%3EDeployment%20Image%20Servicing%20and%20Management%20tool%3CBR%20%2F%3EVersion%3A%2010.0.18362.1%3CBR%20%2F%3E%3CBR%20%2F%3EImage%20Version%3A%2010.0.18362.145%3CBR%20%2F%3E%3CBR%20%2F%3EError%3A%200x800f0806%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20operation%20could%20not%20be%20completed%20due%20to%20pending%20operations.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20DISM%20log%20file%20can%20be%20found%20at%20C%3A%5CWINDOWS%5CLogs%5CDISM%5Cdism.log%3CBR%20%2F%3EPS%20E%3A%5CWinROG%26gt%3B%20DISM%20%2FUnmount-Image%20%2FMountDir%3Amount%5COS%20%2FDISCARD%20%3CBR%20%2F%3EDeployment%20Image%20Servicing%20and%20Management%20tool%3CBR%20%2F%3EVersion%3A%2010.0.18362.1%3CBR%20%2F%3E%3CBR%20%2F%3EUnmounting%20image%3CBR%20%2F%3E%5B%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D100.0%25%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%5D%3CBR%20%2F%3EThe%20operation%20completed%20successfully.%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELog%3C%2FP%3E%3CPRE%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Build%3A%2018362.1.amd64fre.19h1_release.190318-1202%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Session%3A%2014376_34190296%20initialized%20by%20client%20DISM%20Package%20Manager%20Provider%2C%20external%20staging%20directory%3A%20(null)%2C%20external%20registry%20directory%3A%20(null)%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20No%20call%20is%20made%20on%20InitiateChanges%2C%20Synchronous%20Cleanup%20only.%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Maint%3A%20processing%20started.%20Client%3A%20DISM%20Package%20Manager%20Provider%2C%20Session%3A%2014376_34190296%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Maint%3A%20launch%20type%3A%20StartComponentCleanup%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Maint%3A%20Pending%20content%20found%2C%20aborting%20maintenance%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Maint%3A%20completed%2C%20interruptions%3A%200%2C%20(this%20pass%3A%20time%3A%200%20seconds%2C%20used%20space%20change%3A%200%20KB%2C%20hr%3A%200x800f0806%2C%20source%3A%20Other)%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20DISM%20DISM%20Package%20Manager%3A%20PID%3D14376%20TID%3D3112%20Error%20in%20operation%3A%20the%20operation%20could%20not%20be%20complete%20due%20to%20locked%20resources.%20(CBS%20HRESULT%3D0x800f0806)%20-%20CCbsConUIHandler%3A%3AError%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Maint%3A%20processing%20complete.%20Session%3A%2014376_34190296.%20%5BHRESULT%20%3D%200x800f0806%20-%20CBS_E_PENDING%5D%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Received%20notification%20that%20the%20operation%20is%20complete.%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20progress%20thread%20terminated%20normally%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Error%20CBS%20Session%3A%2014376_34190296%20failed%20to%20perform%20Synchronous%20Cleanup%20operation%20%5BHRESULT%20%3D%200x800f0806%20-%20CBS_E_PENDING%5D%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Info%20CBS%20Session%3A%2014376_34190296%20finalized.%20Reboot%20required%3A%20yes%20%5BHRESULT%20%3D%200x800f0806%20-%20CBS_E_PENDING%5D%3CBR%20%2F%3E2019-06-01%2002%3A43%3A23%2C%20Error%20DISM%20DISM%20Package%20Manager%3A%20PID%3D14376%20TID%3D3112%20Failed%20finalizing%20changes.%20-%20CDISMPackageManager%3A%3AInternal_Finalize(hr%3A0x800f0806)%3C%2FPRE%3E%3CP%3EThis%20should%20not%20be%20reading%20from%20Temporary%20AppData%3C%2FP%3E%3CPRE%3E2019-06-01%2002%3A43%3A20%2C%20Warning%20DISM%20DISM%20Provider%20Store%3A%20PID%3D14376%20TID%3D3112%20Failed%20to%20load%20the%20provider%3A%20C%3A%5CUsers%5CNeoBeum%5CAppData%5CLocal%5CTemp%5CD55E88EF-087D-4B12-BC86-AC00EDE638FB%5CPEProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_GetProvider(hr%3A0x8007007e)%3CBR%20%2F%3E2019-06-01%2002%3A43%3A22%2C%20Warning%20DISM%20DISM%20Provider%20Store%3A%20PID%3D14376%20TID%3D3112%20Failed%20to%20load%20the%20provider%3A%20C%3A%5CUsers%5CNeoBeum%5CAppData%5CLocal%5CTemp%5CD55E88EF-087D-4B12-BC86-AC00EDE638FB%5CEmbeddedProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_GetProvider(hr%3A0x8007007e)%3C%2FPRE%3E%3CH1%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%20id%3D%22toc-hId--590971802%22%3EThere%20may%20be%20an%20issue%20with%20ADK%2018362.1%3C%2FH1%3E%3CPRE%3E2019-06-01%2002%3A43%3A18%2C%20Warning%20DISM%20DISM%20Provider%20Store%3A%20PID%3D1632%20TID%3D14016%20Failed%20to%20load%20the%20provider%3A%20D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5CMetaDeployProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_GetProvider(hr%3A0x8007007e)%3C%2FPRE%3E%3CP%3EThis%20is%20something%20I%20have%20already%20complained%20about%20getting%20an%20Release%20Information%20page%20for%20Windows%2010%20ADK...%20here%20is%20a%20screenshot%20of%20a%20Virtual%20Machine%20with%20newly%20installed%20ADK%20WinPE.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F116781iB15D8430D2264757%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22FFS-IComplainedAboutADKUpdatesAlready.PNG%22%20title%3D%22FFS-IComplainedAboutADKUpdatesAlready.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E2019-06-01%2002%3A42%3A54%2C%20Error%20DISM%20DISM%20Package%20Manager%3A%20PID%3D8784%20TID%3D11168%20The%20operation%20could%20not%20be%20completed%20due%20to%20pending%20operations.%20-%20GetCbsErrorMsg%3CBR%20%2F%3E2019-06-01%2002%3A42%3A54%2C%20Error%20DISM%20DISM%20Package%20Manager%3A%20PID%3D8784%20TID%3D11168%20Failed%20processing%20package%20changes%20-%20CDISMPackageManager%3A%3AStartComponentCleanupEx(hr%3A0x800f0806)%3CBR%20%2F%3E2019-06-01%2002%3A42%3A54%2C%20Error%20DISM%20DISM%20Package%20Manager%3A%20PID%3D8784%20TID%3D11168%20The%20operation%20could%20not%20be%20completed%20due%20to%20pending%20operations.%20-%20GetCbsErrorMsg%3CBR%20%2F%3E2019-06-01%2002%3A42%3A54%2C%20Error%20DISM%20DISM%20Package%20Manager%3A%20PID%3D8784%20TID%3D11168%20Failed%20to%20start%20component%20cleanup.%20-%20CPackageManagerCLIHandler%3A%3AProcessCmdLine_CleanupImage(hr%3A0x800f0806)%3CBR%20%2F%3E2019-06-01%2002%3A42%3A54%2C%20Error%20DISM%20DISM%20Package%20Manager%3A%20PID%3D8784%20TID%3D11168%20Failed%20while%20processing%20command%20cleanup-image.%20-%20CPackageManagerCLIHandler%3A%3AExecuteCmdLine(hr%3A0x800f0806)%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20%26lt%3B-----%20Starting%20Dism.exe%20session%20-----%26gt%3B%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Host%20machine%20information%3A%20OS%20Version%3D10.0.18362%2C%20Running%20architecture%3Damd64%2C%20Number%20of%20processors%3D8%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Dism.exe%20version%3A%2010.0.18362.1%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Executing%20command%20line%3A%20%22D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5Cdism.exe%22%20%2FMount-Image%20%2FImageFile%3AE%3A%5CWinROG%5C18362-pro-au.wim%20%2FIndex%3A1%20%2FMountDir%3Amount%5COS%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Getting%20the%20collection%20of%20providers%20from%20a%20local%20provider%20store%20type.%20-%20CDISMProviderStore%3A%3AGetProviderCollection%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Connecting%20to%20the%20provider%20located%20at%20D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5CFolderProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_LoadProvider%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Connecting%20to%20the%20provider%20located%20at%20D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5CSiloedPackageProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_LoadProvider%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Connecting%20to%20the%20provider%20located%20at%20D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5CFfuProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_LoadProvider%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Connecting%20to%20the%20provider%20located%20at%20D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5CWimProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_LoadProvider%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Connecting%20to%20the%20provider%20located%20at%20D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5CVHDProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_LoadProvider%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Connecting%20to%20the%20provider%20located%20at%20D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5CImagingProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_LoadProvider%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Warning%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Failed%20to%20load%20the%20provider%3A%20D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%5CMetaDeployProvider.dll.%20-%20CDISMProviderStore%3A%3AInternal_GetProvider(hr%3A0x8007007e)%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Got%20the%20collection%20of%20providers.%20Now%20enumerating%20them%20to%20build%20the%20command%20table.%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Attempting%20to%20add%20the%20commands%20from%20provider%3A%20DISM%20Log%20Provider%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Attempting%20to%20add%20the%20commands%20from%20provider%3A%20FolderManager%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Attempting%20to%20add%20the%20commands%20from%20provider%3A%20SiloedPackageManager%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Succesfully%20registered%20commands%20for%20the%20provider%3A%20SiloedPackageManager.%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Attempting%20to%20add%20the%20commands%20from%20provider%3A%20FfuManager%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Succesfully%20registered%20commands%20for%20the%20provider%3A%20FfuManager.%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Attempting%20to%20add%20the%20commands%20from%20provider%3A%20WimManager%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Succesfully%20registered%20commands%20for%20the%20provider%3A%20WimManager.%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Attempting%20to%20add%20the%20commands%20from%20provider%3A%20VHDManager%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Attempting%20to%20add%20the%20commands%20from%20provider%3A%20GenericImagingManager%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM.EXE%3A%20Succesfully%20registered%20commands%20for%20the%20provider%3A%20GenericImagingManager.%3CBR%20%2F%3E2019-06-01%2002%3A40%3A33%2C%20Info%20DISM%20DISM%20Imaging%20Provider%3A%20PID%3D10592%20TID%3D12088%20WIM%20image%20specified%20-%20CGenericImagingManager%3A%3AGetImageInfoCollection%3CBR%20%2F%3E%5B10592%5D%20Mounting%20new%20image.%3CBR%20%2F%3EWim%3A%20%5BE%3A%5CWinROG%5C18362-pro-au.wim%5D%3CBR%20%2F%3EImage%20Index%3A%20%5B1%5D%3CBR%20%2F%3EMount%20Path%3A%20%5BE%3A%5CWinROG%5Cmount%5COS%5D%3CBR%20%2F%3E%5B10592%5D%20Wimserv%20process%20started%20for%20guid%20b1add07f-5c21-4e5f-8c5a-9579c8acf874.%20Id%20is%2014244%3CBR%20%2F%3E%5B14244%5D%20ImageUnmarshallHandle%3A%20Reconstituting%20wim%20at%20E%3A%5CWinROG%5C18362-pro-au.wim.%3CBR%20%2F%3E%5B14244%5D%20Mounted%20image%20at%20E%3A%5CWinROG%5Cmount%5COS.%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM.EXE%3A%20Image%20session%20has%20been%20closed.%20Reboot%20required%3Dno.%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM.EXE%3A%20%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM.EXE%3A%20%26lt%3B-----%20Ending%20Dism.exe%20session%20-----%26gt%3B%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM.EXE%3A%20%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Found%20the%20OSServices.%20Waiting%20to%20finalize%20it%20until%20all%20other%20providers%20are%20unloaded.%20-%20CDISMProviderStore%3A%3AFinal_OnDisconnect%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Disconnecting%20Provider%3A%20FolderManager%20-%20CDISMProviderStore%3A%3AInternal_DisconnectProvider%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Disconnecting%20Provider%3A%20SiloedPackageManager%20-%20CDISMProviderStore%3A%3AInternal_DisconnectProvider%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Disconnecting%20Provider%3A%20FfuManager%20-%20CDISMProviderStore%3A%3AInternal_DisconnectProvider%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Disconnecting%20Provider%3A%20WimManager%20-%20CDISMProviderStore%3A%3AInternal_DisconnectProvider%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Disconnecting%20Provider%3A%20VHDManager%20-%20CDISMProviderStore%3A%3AInternal_DisconnectProvider%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Disconnecting%20Provider%3A%20GenericImagingManager%20-%20CDISMProviderStore%3A%3AInternal_DisconnectProvider%3CBR%20%2F%3E2019-06-01%2002%3A42%3A27%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D10592%20TID%3D12088%20Releasing%20the%20local%20reference%20to%20DISMLogger.%20Stop%20logging.%20-%20CDISMProviderStore%3A%3AInternal_DisconnectProvider%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20PID%3D3704%20TID%3D15244%20Scratch%20directory%20set%20to%20'C%3A%5CUsers%5CNeoBeum%5CAppData%5CLocal%5CTemp%5C'.%20-%20CDISMManager%3A%3Aput_ScratchDir%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20PID%3D3704%20TID%3D15244%20DismCore.dll%20version%3A%2010.0.18362.1%20-%20CDISMManager%3A%3AFinalConstruct%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20Initialized%20Panther%20logging%20at%20C%3A%5CWINDOWS%5CLogs%5CDISM%5Cdism.log%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20PID%3D3704%20TID%3D15244%20Successfully%20loaded%20the%20ImageSession%20at%20%22D%3A%5CWindows%20Kits%5C10%5CAssessment%20and%20Deployment%20Kit%5CDeployment%20Tools%5CAMD64%5CDISM%22%20-%20CDISMManager%3A%3ALoadLocalImageSession%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20Initialized%20Panther%20logging%20at%20C%3A%5CWINDOWS%5CLogs%5CDISM%5Cdism.log%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D3704%20TID%3D15244%20Found%20and%20Initialized%20the%20DISM%20Logger.%20-%20CDISMProviderStore%3A%3AInternal_InitializeLogger%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D3704%20TID%3D15244%20Failed%20to%20get%20and%20initialize%20the%20PE%20Provider.%20Continuing%20by%20assuming%20that%20it%20is%20not%20a%20WinPE%20image.%20-%20CDISMProviderStore%3A%3AFinal_OnConnect%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20DISM%20Provider%20Store%3A%20PID%3D3704%20TID%3D15244%20Finished%20initializing%20the%20Provider%20Map.%20-%20CDISMProviderStore%3A%3AFinal_OnConnect%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20Initialized%20Panther%20logging%20at%20C%3A%5CWINDOWS%5CLogs%5CDISM%5Cdism.log%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20DISM%20Manager%3A%20PID%3D3704%20TID%3D15244%20Successfully%20created%20the%20local%20image%20session%20and%20provider%20store.%20-%20CDISMManager%3A%3ACreateLocalImageSession%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20DISM.EXE%3A%20%3CBR%20%2F%3E2019-06-01%2002%3A42%3A48%2C%20Info%20DISM%20DISM.EXE%3A%20%26lt%3B-----%20Starting%20Dism.exe%20session%20-----%26gt%3B%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-661335%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOperating%20System%20Deployment%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665329%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665329%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88946%22%20target%3D%22_blank%22%3E%40Neo%20Beum%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20don't%20have%20an%20answer%20here%20but%20would%20strongly%20suggest%20posting%20this%20in%20a%20Windows-centric%20forum%20as%20ConfigMgr%20plays%20no%20part%20in%20the%20this%20and%20this%20is%20completely%20Windows-centric.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-677234%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-677234%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F117994%22%20target%3D%22_blank%22%3E%40Jason%20Sandys%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EI'm%20pretty%20sure%20that%20that%20the%20Windows%20team%20has%20no%20idea%20about%20this%20either...%20I'm%20just%20going%20to%20spam%20everywhere%20until%20I%20get%20someone%20who%20knows%20something%20about%20where%20Servicing%20Stack%2C%20ADK%20and%20DISM%20actually%20belong.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-677503%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-677503%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88946%22%20target%3D%22_blank%22%3E%40Neo%20Beum%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EActually%2C%20the%20Windows%20team%20does%20in%20fact%20directly%20own%20this%20and%20this%20is%20definitely%20core%20Windows%20functionality.%20Ultimately%2C%20if%20you're%20not%20getting%20an%20answer%2C%20you%20will%20probably%20need%20to%20open%20a%20support%20case%20as%20deeper%20investigation%20is%20probably%20needed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESpamming%20forums%20may%2Fwill%20get%20you%20banned%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678681%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678681%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F117994%22%20target%3D%22_blank%22%3E%40Jason%20Sandys%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20going%20to%20give%20ADK%20a%20temporary%20home%20with%20MDT%2C%20until%20Microsoft%20give%20ADK%20a%20proper%20home.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-699676%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-699676%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88946%22%20target%3D%22_blank%22%3E%40Neo%20Beum%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20called%20out%2C%20it%20has%20a%20proper%20home%3A%20The%20Windows%20Setup%20team.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-710998%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-710998%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F117994%22%20target%3D%22_blank%22%3E%40Jason%20Sandys%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20a%20link%20for%20the%20subforum%2Fcategory%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-711033%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-711033%22%20slang%3D%22en-US%22%3E%3CP%3ETry%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-10-servicing%2Fbd-p%2FWindows10servicing%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-10-servicing%2Fbd-p%2FWindows10servicing%3C%2FA%3E%20or%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-10-deployment%2Fbd-p%2FWindows10deployment%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-10-deployment%2Fbd-p%2FWindows10deployment%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1066423%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010.0.18362.145%20KB4498523%20-%20DISM%20fails%20offline%20%2FResetBase%20(This%20was%20meant%20to%20have%20been%20fi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1066423%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88946%22%20target%3D%22_blank%22%3E%40Neo%20Beum%3C%2FA%3Eboot%20the%20windows%20into%20safemode%2C%26nbsp%3B%20mount%20wim%20file%20using%20dism%20%2C%20do%20changes%20apply%20updates%26nbsp%3B%20and%20then%20resetbase%20%2C%20unmount%20wim%20file%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

I've previously posted: https://techcommunity.microsoft.com/t5/WinHEC-Online/ADK-18362-1-DISM-Fails-Offline-Install-for-kb44...

 

KB44985263 and KB4497935 will successfully complete cleanup on Winre.wim.

 

However, DISM ADK 18362.1 is failing SSU KB4498523 and LCU KB4497935 offline Component Cleanup and Reset Base.

 

I am quoting the following from https://support.microsoft.com/en-au/help/4498523/windows-10-update-kb4498523

 

Servicing stack update for Windows 10, Version 1903: May 29, 2019

 

  • Addresses an issue in which updates may fail to install after the /resetbase command in DISM is run.

 

 

The image cleanup will fail with and without /ResetBase

PS E:\WinROG> DISM /Image:mount\OS /Cleanup-Image /StartComponentCleanup 
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.145

Error: 0x800f0806

The operation could not be completed due to pending operations.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
PS E:\WinROG> DISM /Unmount-Image /MountDir:mount\OS /DISCARD
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Unmounting image
[==========================100.0%==========================]
The operation completed successfully.

 

Log

2019-06-01 02:43:23, Info CBS Build: 18362.1.amd64fre.19h1_release.190318-1202
2019-06-01 02:43:23, Info CBS Session: 14376_34190296 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null)
2019-06-01 02:43:23, Info CBS No call is made on InitiateChanges, Synchronous Cleanup only.
2019-06-01 02:43:23, Info CBS Maint: processing started. Client: DISM Package Manager Provider, Session: 14376_34190296
2019-06-01 02:43:23, Info CBS Maint: launch type: StartComponentCleanup
2019-06-01 02:43:23, Info CBS Maint: Pending content found, aborting maintenance
2019-06-01 02:43:23, Info CBS Maint: completed, interruptions: 0, (this pass: time: 0 seconds, used space change: 0 KB, hr: 0x800f0806, source: Other)
2019-06-01 02:43:23, Info DISM DISM Package Manager: PID=14376 TID=3112 Error in operation: the operation could not be complete due to locked resources. (CBS HRESULT=0x800f0806) - CCbsConUIHandler::Error
2019-06-01 02:43:23, Info CBS Maint: processing complete. Session: 14376_34190296. [HRESULT = 0x800f0806 - CBS_E_PENDING]
2019-06-01 02:43:23, Info CBS Received notification that the operation is complete.
2019-06-01 02:43:23, Info CBS progress thread terminated normally
2019-06-01 02:43:23, Error CBS Session: 14376_34190296 failed to perform Synchronous Cleanup operation [HRESULT = 0x800f0806 - CBS_E_PENDING]
2019-06-01 02:43:23, Info CBS Session: 14376_34190296 finalized. Reboot required: yes [HRESULT = 0x800f0806 - CBS_E_PENDING]
2019-06-01 02:43:23, Error DISM DISM Package Manager: PID=14376 TID=3112 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0806)

This should not be reading from Temporary AppData

2019-06-01 02:43:20, Warning DISM DISM Provider Store: PID=14376 TID=3112 Failed to load the provider: C:\Users\NeoBeum\AppData\Local\Temp\D55E88EF-087D-4B12-BC86-AC00EDE638FB\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-06-01 02:43:22, Warning DISM DISM Provider Store: PID=14376 TID=3112 Failed to load the provider: C:\Users\NeoBeum\AppData\Local\Temp\D55E88EF-087D-4B12-BC86-AC00EDE638FB\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

There may be an issue with ADK 18362.1

2019-06-01 02:43:18, Warning DISM DISM Provider Store: PID=1632 TID=14016 Failed to load the provider: D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

This is something I have already complained about getting an Release Information page for Windows 10 ADK... here is a screenshot of a Virtual Machine with newly installed ADK WinPE.

FFS-IComplainedAboutADKUpdatesAlready.PNG

 

 

2019-06-01 02:42:54, Error DISM DISM Package Manager: PID=8784 TID=11168 The operation could not be completed due to pending operations. - GetCbsErrorMsg
2019-06-01 02:42:54, Error DISM DISM Package Manager: PID=8784 TID=11168 Failed processing package changes - CDISMPackageManager::StartComponentCleanupEx(hr:0x800f0806)
2019-06-01 02:42:54, Error DISM DISM Package Manager: PID=8784 TID=11168 The operation could not be completed due to pending operations. - GetCbsErrorMsg
2019-06-01 02:42:54, Error DISM DISM Package Manager: PID=8784 TID=11168 Failed to start component cleanup. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f0806)
2019-06-01 02:42:54, Error DISM DISM Package Manager: PID=8784 TID=11168 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0806)

 

2019-06-01 02:40:33, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2019-06-01 02:40:33, Info DISM DISM.EXE:
2019-06-01 02:40:33, Info DISM DISM.EXE: Host machine information: OS Version=10.0.18362, Running architecture=amd64, Number of processors=8
2019-06-01 02:40:33, Info DISM DISM.EXE: Dism.exe version: 10.0.18362.1
2019-06-01 02:40:33, Info DISM DISM.EXE: Executing command line: "D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\dism.exe" /Mount-Image /ImageFile:E:\WinROG\18362-pro-au.wim /Index:1 /MountDir:mount\OS
2019-06-01 02:40:33, Info DISM DISM Provider Store: PID=10592 TID=12088 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2019-06-01 02:40:33, Info DISM DISM Provider Store: PID=10592 TID=12088 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-01 02:40:33, Info DISM DISM Provider Store: PID=10592 TID=12088 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-01 02:40:33, Info DISM DISM Provider Store: PID=10592 TID=12088 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-01 02:40:33, Info DISM DISM Provider Store: PID=10592 TID=12088 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-01 02:40:33, Info DISM DISM Provider Store: PID=10592 TID=12088 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-01 02:40:33, Info DISM DISM Provider Store: PID=10592 TID=12088 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-01 02:40:33, Warning DISM DISM Provider Store: PID=10592 TID=12088 Failed to load the provider: D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-06-01 02:40:33, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2019-06-01 02:40:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2019-06-01 02:40:33, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2019-06-01 02:40:33, Info DISM DISM.EXE: Attempting to add the commands from provider: SiloedPackageManager
2019-06-01 02:40:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: SiloedPackageManager.
2019-06-01 02:40:33, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager
2019-06-01 02:40:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.
2019-06-01 02:40:33, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
2019-06-01 02:40:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
2019-06-01 02:40:33, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager
2019-06-01 02:40:33, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2019-06-01 02:40:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2019-06-01 02:40:33, Info DISM DISM Imaging Provider: PID=10592 TID=12088 WIM image specified - CGenericImagingManager::GetImageInfoCollection
[10592] Mounting new image.
Wim: [E:\WinROG\18362-pro-au.wim]
Image Index: [1]
Mount Path: [E:\WinROG\mount\OS]
[10592] Wimserv process started for guid b1add07f-5c21-4e5f-8c5a-9579c8acf874. Id is 14244
[14244] ImageUnmarshallHandle: Reconstituting wim at E:\WinROG\18362-pro-au.wim.
[14244] Mounted image at E:\WinROG\mount\OS.
2019-06-01 02:42:27, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2019-06-01 02:42:27, Info DISM DISM.EXE:
2019-06-01 02:42:27, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2019-06-01 02:42:27, Info DISM DISM.EXE:
2019-06-01 02:42:27, Info DISM DISM Provider Store: PID=10592 TID=12088 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-06-01 02:42:27, Info DISM DISM Provider Store: PID=10592 TID=12088 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-01 02:42:27, Info DISM DISM Provider Store: PID=10592 TID=12088 Disconnecting Provider: SiloedPackageManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-01 02:42:27, Info DISM DISM Provider Store: PID=10592 TID=12088 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-01 02:42:27, Info DISM DISM Provider Store: PID=10592 TID=12088 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-01 02:42:27, Info DISM DISM Provider Store: PID=10592 TID=12088 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-01 02:42:27, Info DISM DISM Provider Store: PID=10592 TID=12088 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-01 02:42:27, Info DISM DISM Provider Store: PID=10592 TID=12088 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2019-06-01 02:42:48, Info DISM PID=3704 TID=15244 Scratch directory set to 'C:\Users\NeoBeum\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2019-06-01 02:42:48, Info DISM PID=3704 TID=15244 DismCore.dll version: 10.0.18362.1 - CDISMManager::FinalConstruct
2019-06-01 02:42:48, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-01 02:42:48, Info DISM PID=3704 TID=15244 Successfully loaded the ImageSession at "D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM" - CDISMManager::LoadLocalImageSession
2019-06-01 02:42:48, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-01 02:42:48, Info DISM DISM Provider Store: PID=3704 TID=15244 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2019-06-01 02:42:48, Info DISM DISM Provider Store: PID=3704 TID=15244 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2019-06-01 02:42:48, Info DISM DISM Provider Store: PID=3704 TID=15244 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2019-06-01 02:42:48, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-01 02:42:48, Info DISM DISM Manager: PID=3704 TID=15244 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2019-06-01 02:42:48, Info DISM DISM.EXE:
2019-06-01 02:42:48, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

 

 

 

8 Replies
Highlighted

@Neo Beum 

I don't have an answer here but would strongly suggest posting this in a Windows-centric forum as ConfigMgr plays no part in the this and this is completely Windows-centric.

Highlighted

@Jason Sandys 

 

Thanks,

I'm pretty sure that that the Windows team has no idea about this either... I'm just going to spam everywhere until I get someone who knows something about where Servicing Stack, ADK and DISM actually belong.

Highlighted

@Neo Beum 

Actually, the Windows team does in fact directly own this and this is definitely core Windows functionality. Ultimately, if you're not getting an answer, you will probably need to open a support case as deeper investigation is probably needed.

 

Spamming forums may/will get you banned as well.

Highlighted

@Jason Sandys 

 

I'm going to give ADK a temporary home with MDT, until Microsoft give ADK a proper home.

 

Highlighted

@Neo Beum 

As called out, it has a proper home: The Windows Setup team.

Highlighted

@Jason Sandys 

 

Do you have a link for the subforum/category?

Thanks

Highlighted

@Neo Beumboot the windows into safemode,  mount wim file using dism , do changes apply updates  and then resetbase , unmount wim file