You can extract them manually (starting with older), or put them with other updates and W10UI takes care of that
I found the cause of the problem I installed my customized version in Vmware virtual machine and tried to update KB3200970 and it was working without any errors. Then i started to applying some other tweaks that i have on my windows to virtual machine and I got same error as on my real Windows. The cause of the problem was disabled "App readiness" service,changed it back to default(Manual) on my real Windows and installation of KB3200970 passed without any problems
Dear abbodi1406, I used to delete boot.wim's index 1, so the script gives some errors, because you don't check index number for boot.wim (for install.wim, you check index number, so if I delete index 1 or 2, there's no error). Can I just substitute if %dvd%==1 (set imgcount=2&call :mount "%target%\sources\boot.wim") with if %dvd%==1 (set imgcount=1&call :mount "%target%\sources\boot.wim") ? So the script copy the files of DU IM KB3203338 in sources folder? It doesn't seem so, but maybe because of boot.wim's errors. Please, let me know. Thanks
Error: 0x800f0922 when integrating CU for Windows 10 (KB3205436) to Windows 10 Enterprise 2015 LTSB using DISM The last CU that can be integrated sucessfully was CU for Windows 10 (KB3186987) from August, any CU after that will give the same error. Has anyone have the same error? ------------------------------------------------------------------------------------------------------------------- C:\Windows\system32>dism /mount-wim /wimfile:\Win10\sources\x86\install.wim /index:1 /mountdir:\Win10\mount\x86 Deployment Image Servicing and Management tool Version: 10.0.14393.0 Mounting image [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>dism /image:\Win10\mount\x86 /add-package /packagepath:\Win10\kbfiles\x86 Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.10240.16384 Processing 1 of 7 - Adding package Package_for_KB3151900~31bf3856ad364e35~x86~~10.0.1.581 [==========================100.0%==========================] Processing 2 of 7 - Adding package d:\Win10\kbfiles\x86\Windows10.0-KB3125217-x86.msu [==========================100.0%==========================] Processing 3 of 7 - Adding package d:\Win10\kbfiles\x86\windows10.0-kb3161102-x86_fd60ede9f566cd7f14a8e5f68bb58c22905e7de6.msu [==========================100.0%==========================] Processing 4 of 7 - Adding package d:\Win10\kbfiles\x86\windows10.0-kb3172729-x86_2ccd3af51d198b548c849226f66c81174303aaa3.msu [==========================100.0%==========================] Processing 5 of 7 - Adding package d:\Win10\kbfiles\x86\Windows10.0-KB3173427-x86.msu [==========================100.0%==========================] Processing 6 of 7 - Adding package d:\Win10\kbfiles\x86\windows10.0-kb3202790-x86_96a49918ef109be2b99def3c1c929736203c7fc0.msu [==========================100.0%==========================] Processing 7 of 7 - Adding package d:\Win10\kbfiles\x86\windows10.0-kb3205436-x86_14970e4a7ab0a967c3799afd4b59c3d17ea9340e.msu [==========================100.0%==========================] Error: 0x800f0922 Package d:\Win10\kbfiles\x86\windows10.0-kb3205436-x86_14970e4a7ab0a967c3799afd4b59c3d17ea9340e.msu may have failed due to pending updates to servicing components in the image. Try the command again.The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log C:\Windows\system32>dism /unmount-wim /mountdir:\Win10\mount\x86 /commit Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image File : d:\Win10\sources\x86\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32> -----------------------------------------------------------------------------------------------------------------
Hi, Enthousiast, I did as what you said: exclude KB3125217 & integrate sstack (KB3173427) first still end up with same error with the CU patch (and with ANY CU after (KB3186987) from August. We might need a new sstack? -------------------------------------------------------------------------------------------------- C:\Windows\system32>dism /image:\Win10\mount\x86 /add-package /packagepath:\Win10\kbfiles\x86 Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.10240.16384 Processing 1 of 1 - Adding package d:\Win10\kbfiles\x86\Windows10.0-KB3173427-x86.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>dism /image:\Win10\mount\x86 /add-package /packagepath:\Win10\kbfiles\x86 Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.10240.16384 Processing 1 of 5 - Adding package Package_for_KB3151900~31bf3856ad364e35~x86~~10.0.1.581 [==========================100.0%==========================] Processing 2 of 5 - Adding package d:\Win10\kbfiles\x86\windows10.0-kb3161102-x86_fd60ede9f566cd7f14a8e5f68bb58c22905e7de6.msu [==========================100.0%==========================] Processing 3 of 5 - Adding package d:\Win10\kbfiles\x86\windows10.0-kb3172729-x86_2ccd3af51d198b548c849226f66c81174303aaa3.msu [==========================100.0%==========================] Processing 4 of 5 - Adding package d:\Win10\kbfiles\x86\windows10.0-kb3202790-x86_96a49918ef109be2b99def3c1c929736203c7fc0.msu [==========================100.0%==========================] Processing 5 of 5 - Adding package d:\Win10\kbfiles\x86\windows10.0-kb3205436-x86_14970e4a7ab0a967c3799afd4b59c3d17ea9340e.msu [==========================100.0%==========================] Error: 0x800f0922 Package d:\Win10\kbfiles\x86\windows10.0-kb3205436-x86_14970e4a7ab0a967c3799afd4b59c3d17ea9340e.msu may have failed due to pending updates to servicing components in the image. Try the command again.The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log -----------------------------------------------------------------------------------------------------------
Yes, i can confirm this status this is due an updated component for SSShim.dll (PackageManager) for some reason the servicing stack mistakenly maps the Host OS path not the Mount directory path when it tries to replace the new component Code: Error STATUS_CANNOT_DELETE while executing operation HardLinkFile on [l:326{163}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-packagemanager_31bf3856ad364e35_10.0.10240.17113_none_f4cc02dc8dfac900\SSShim.dll, \??\C:\Windows\System32\SSShim.dll" until they fix that (new servicing stack update), the only workaround is to install the CU on live running 10240 OS
I can confirm that it tries to change something outsite of the mounted files, i had some problems discarding the mount
He's been notified but the new runtimes is branded for now as Microsoft Visual C++ 15, so it may cause confusion i would prefer to wait for RTM