W10UI_6.2 can't update the 18362.30 winpe images (boot.wim and winre.wim). The test is with W10UI_6.3 and the winpe images.
I downloaded clean 10.0.18362.30 iso but i can not integrate the new CU kb4495666 to the image.. It say it is not applicable.. Does anybody have a solution for this ?
Did you provide the correct architecture CU for the wim? And how did you do it? Have the progress of the cmd?
Code: dism.exe /image:"c:\mount" /Add-Package /PackagePath:"j:\W10UI\18362.1_Updates_x86\CU" Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.18362.30 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~x86~~18362.53.1.5 [==========================100.0%==========================] The operation completed successfully.
Here is the progress enthousiast Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.30 Processing 1 of 1 - Adding package E:\SYSTEM\Windows10\1903_18362.30_ENTERPRISE\packages\cumulative\windows10.0-kb4495666-x64_9a38cfd2baecbf99be7ce4348d9bf866d7ea9eeb.msu [==========================100.0%==========================] E:\SYSTEM\Windows10\1903_18362.30_ENTERPRISE\packages\cumulative\windows10.0-kb4495666-x64_9a38cfd2baecbf99be7ce4348d9bf866d7ea9eeb.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x800f081f Error: 0x800f081f DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Can you reduce the path lengths? Maybe that's what's causing the error. Code: dism.exe /image:"c:\mount" /Add-Package /PackagePath:"j:\W10UI\18362.1_Updates_x86\CU" Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.18362.30 Processing 1 of 1 - Adding package j:\W10UI\18362.1_Updates_x86\CU\windows10.0-kb4495666-x86_abdd6d1073e568d4f104a04e268375b25f4368f1.msu [==========================100.0%==========================] The operation completed successfully.
No change dear enthousiast , the result is the same C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>Dism /Mount-Image /ImageFile:C:\Win10\sources\install.wim /index:1 /MountDir:C:\Mount Deployment Image Servicing and Management tool Version: 10.0.17763.1 Mounting image [==========================100.0%==========================] The operation completed successfully. C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>Dism /image:C:\Mount /Add-Package /PackagePath:C:\Cumulative Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.18362.30 Processing 1 of 1 - Adding package C:\Cumulative\windows10.0-kb4495666-x64.msu [==========================100.0%==========================] C:\Cumulative\windows10.0-kb4495666-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x800f081f Error: 0x800f081f DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>
@abbodi1406 No Abbodi , host operating system is Windows 10.0.18362.30. I have found the source of problem. I trimmed the original 18362.30.iso for removing some components with MSMG toolkit. Trimmed iso gave error when integrating cumulative update I tried the original iso for integration and it all went well Thanks Abbodi and Enthousiast
People want a clean system which is free of unwanted or unneeded components. MSMG Toolkit is a project of this forum and thousands of people are using it to butcher their systems So , if you want a system that is full of bloatware then it is your decision but you do not have right to blame people for using MSMG Toolkit if they want a clean system I could not integrate the last cumulative update and i asked experienced people to help me Moreover i am a member of this forum and i can ask any question and i can request help from other members I hope you will think twice for not typing a useless comment from now on I do not think i am wasting people's time buddy.. I faced a problem and i asked it to specialized people in the forum and later on i found the source of problem by myself so what is wrong with you ?
Maybe next time mention upfront that it's a chopped wim, that would have been enough for the helpers to warn that it's probably the cause of your problems. Once we had a chopper of windows 7, he couldn't get it activated, didn't mention to daz that it was heavily chopped, daz was trying to get it fixed for a week, when i noticed an earlier post by the chopper, about what he all did to the install, all was solved in a second