@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
I think resolve now.. ty. Spoiler Code: Microsoft Windows [Version 10.0.16299.19] (c) 2017 Microsoft Corporation. All rights reserved. C:\Windows\system32>Dism /online /Cleanup-Image /AnalyzeComponentStore Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.19 [==========================100.0%==========================] Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store : 7.21 GB Actual Size of Component Store : 6.96 GB Shared with Windows : 6.02 GB Backups and Disabled Features : 833.35 MB Cache and Temporary Data : 114.76 MB Date of Last Cleanup : 2017-09-29 21:15:26 Number of Reclaimable Packages : 0 Component Store Cleanup Recommended : Yes The operation completed successfully. C:\Windows\system32>Dism.exe /online /Cleanup-Image /StartComponentCleanup Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.19 [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32> then I'll try update tuesday patch now using w10ui_3.7
When launching Windows update after a clean install with a pre-updated 1709 ISO i get offered the latest cumulative update again. Is that normal? I used W10UI_3.7 to integrate the updates + Net 3.5. I also chose Cleanup system image and Reset image base.
I just ran the script with the updates in the same folder and toggled to enable net 3.5, figured the script did everything.
Interesting, then i have no idea why it happend for me. Thanks for trying it out and showing me your results.
