10586 CU (KB4048952) is applicable for Enterprise and Education only (and WinPE, Nanoserver) so the support is half ended
So, there are two updates but one (CU) is available in three formats (MSU, DELTA, CAB) and the other (Flash) is available in two (MSU, CAB) and therefore to integrate them I should only download 2 files and if so, which ones?
When integrating it's always best to start with an install.wim which wasn't updated before, delta's are dependent on previously integrated CU's so that's not the way to go, cab files are inside the .msu so both can be used. As you can see here, you only need the most current CU and Flash update for updating a clean 16299.15 install.wim.
@Enthousiast I'm currious, what this problem again.. to be inform.. pre-integrated CU winver 16299.64..and flash player old also security update flashplayer old before update flashplayer today Spoiler: Setting Code: ============================================================ 1. Target (x64): Current OS 2. Updates: "D:\Update Windows 10\W10UI_3.6" 3. DISM: "C:\Windows\system32\dism.exe" 4. Enable .NET 3.5: YES 5. Cleanup System Image: YES 6. Reset Image Base: NO ============================================================ 0. Start the process ============================================================ Change a menu option, press 0 to start, or 9 to exit: Spoiler: 16299.64 Code: ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/1: windows10.0-kb4049179-x64_1412087787b62de747da539e4d9397f0b5909713.cab ============================================================ Checking Updates... ============================================================ ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.64 Processing 1 of 1 - Adding package Package_for_KB4049179~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. ============================================================ Cleaning up OS image ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Error: 2 Unable to access the image. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ Press any key to exit. .
It means what it says "image path and the Windows directory for the image exist and you have Read permissions on the folder".
I also see this occur when something keeps a lock on the mount/temp folders used for the operation, which then kills the dism commit, or other ops. I always kill my explorer windows and any other apps open that might lock on any of the build folders while I build.
I know.. it in my windows not creating own iso.. it happen in enterprise.. in pro version dont like that
kb4049179 is superseeded by kb4048951 (released yesterday). What does this command reports (run in an elevated cmd): Code: Dism /Online /Cleanup-Image /StartComponentCleanup