@abbodi1406, If I put a generic mount folder in W10UI like .\Mount\Install\ and within this folder there are the mounting folders for specific indexes such as: .\Mount\Install\2 .\Mount\Install\3 .\Mount\Install\5 .\Mount\Install\6 .\Mount\Install\9 If I only put the main path ".\MNT\Install\" as a target, is there a way to make the script read these specific mount points to integrate the updates without having to modify the target in the ini file and run the script again for each index? This would be useful for indexes already mounted in the Toolkit or IMCK. I was thinking about something like inform the total number of indexes and using some code like: Code: set "MountDir=C:\TK\Mount\Install" set "ImageCount=11" if not exist "%MountDir%\Windows\" for /L %%i in (1 1 %ImageCount%) do ( if exists "%MountDir%\%%i\Windows\" ( call :IntegrateUpdates "%MountDir%\%%i" ) ) or informing the mounted indexes: Code: set "MountDir=C:\TK\Mount\Install" set "MountedIndexes=2,3,5,6,9" if not exist "%MountDir%\Windows\" for %%i in (%MountedIndexes%) do ( if exists "%MountDir%\%%i\Windows\" ( call :IntegrateUpdates "%MountDir%\%%i" ) ) Something like that. I don't know if this is already implemented in W10UI. If it already exists, is there any way to inform the indexes mounted in the ini file? Thank you!
@inTerActionVRI Code: call W10UI.cmd 1 "%MountDir%\%%i" "TmpFolder" TmpFolder must be created beforehand however, temporary extraced cab files (from msu files) will not be removed on the end
No problem, so I enter the path of the temporary folder, Toolkit or IMCK. What is 1 param, in "call W10UI.cmd 1"? Thnks, man!
TmpFolder should be empty it represent _CabDir for W10UI 1 = keep extracted updates (instead extracting the updates and remove them for each index)
No in this case, all Configuration options are detected from W10UI.ini except Target and _CabDir updates files location is based on "Repo" config (or place them next to W10UI) that's why you should specify empty existing folder for TmpFolder
@abbodi1406, I finished what I was doing. It's working fine, but for each index it's extracting all the files again. Remembering that for each index, I call the script again with parameter 1 activated. If I use the mount point path, the script hangs (pauses forever), does not extract anything to the temporary folder. This command simply stops execution (it looks like a pause, but there are no messages), but it does not break the script. Code: Start "" /wait /B cmd.exe /C call "!W10UIscript!" 1, "%InstallMount%\%%i", "%_TMP%\ExtractedUpdateFiles", "%InstallMedia%\sources" So I'm using the command with the empty second parameter. This one works, okay. Code: Start "" /wait /B cmd.exe /C call "!W10UIscript!" 1, "", "%_TMP%\ExtractedUpdateFiles", "%InstallMedia%\sources" I believe it is something related to %random% that continues to generate a new temporary folder instead of using the previously created empty folder. For each index a new ini file is generated replacing the previous one, I do this because it is only necessary to update the winre.wim of just one of the indexes, this winre.wim will be inserted in the other indexes later. Maybe creating a new ini causes the problem with random temporary folders, but in the ini, the same path to the folder is always entered. "B:\IMCK\TMP\ExtractedUpdateFiles" Spoiler: ini file Code: [W10UI-Configuration] Target =B:\IMCK\MNT\I\2 Repo =B:\IMCK_TOOLS\WHD\w11\x64\10.0.22621 DismRoot =B:\IMCK_TOOLS\Bin\x64\DISM10\Dism.exe Net35 =0 Net35Source = Cleanup =1 ResetBase =0 LCUwinre =1 WinRE =1 UpdtBootFiles =1 SkipEdge =0 UseWimlib =0 _CabDir =B:\IMCK\TMP\ExtractedUpdateFiles MountDir =B:\IMCK\MNT\I\2 WinreMount =B:\IMCK\MNT\WinRe wim2esd =0 wim2swm =0 ISO =0 ISODir = Delete_Source =0 AutoStart =1
Why the complication? Code: call "!W10UIscript!" 1 "%InstallMount%\%%i" "%_TMP%\ExtractedUpdateFiles" "%InstallMedia%\sources" or cmd.exe /C ""!W10UIscript!" 1 "%InstallMount%\%%i" "%_TMP%\ExtractedUpdateFiles" "%InstallMedia%\sources"" when you specify sources parameter, it will cause the script to process dynamic update each time _CabDir is not detected from the ini in this case
I tried these ways, I only ended the attempts when I removed the mount point. But when I removed the mount points I was with the command start "" /Wait ... In short, the eternal pause continues if I pass the mount point path for any of the below commands: Spoiler: commands and console log call "!W10UIscript!" 1 "%InstallMount%\%%i" "%_TMP%\ExtractedUpdateFiles" or cmd.exe /C ""!W10UIscript!" 1 "%InstallMount%\%%i" "%_TMP%\ExtractedUpdateFiles"" or Start "" /wait /B cmd.exe /C call "!W10UIscript!" 1 "%InstallMount%\%%i" "%_TMP%\ExtractedUpdateFiles" Code: =============================================================================== Integrate Update Files through W10UI =============================================================================== Image : install.wim Image Index : 1;2 Image Architecture : x64 Image Version : 10.0.22621.1.0 =============================================================================== [install.wim, Index : 1 - Edition : Core] =============================================================================== ------------------------------------------------------------------------------- Creating W10UI-Configuration .ini file ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Start Integrating Updates Process through W10UI Script ------------------------------------------------------------------------------- Ethernal pause here... Without the fourth parameter, still extracting at each index. Spoiler: command and complete console log Used command: call "!W10UIscript!" 1 "" "%_TMP%\ExtractedUpdateFiles" Code: =============================================================================== Integrate Update Files through W10UI =============================================================================== Image : install.wim Image Index : 1;2 Image Architecture : x64 Image Version : 10.0.22621.1.0 =============================================================================== [install.wim, Index : 1 - Edition : Core] =============================================================================== ------------------------------------------------------------------------------- Creating W10UI-Configuration .ini file ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Start Integrating Updates Process through W10UI Script ------------------------------------------------------------------------------- ============================================================ Running W10UI v10.35 ============================================================ ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/5: windows11.0-kb5027397-x64.cab [Enablement] 2/5: windows11.0-kb5029863-x64.cab [SafeOS DU] 3/5: Windows11.0-KB5030310-x64.cab [LCU] 4/5: windows11.0-kb5030327-x64.cab [Setup DU] 5/5: Windows11.0-KB5030508-x64.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2351~31bf3856ad364e35~amd64~~22621.2351.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2351 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_KB5027397~31bf3856ad364e35~amd64~~22621.2355.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.2361.1.13 [==========================100.0%==========================] The operation completed successfully. ============================================================ Cleaning up OS image... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22631.2361 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. ============================================================ Finished ============================================================ =============================================================================== [install.wim, Index : 2 - Edition : Professional] =============================================================================== ------------------------------------------------------------------------------- Creating W10UI-Configuration .ini file ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Start Integrating Updates Process through W10UI Script ------------------------------------------------------------------------------- ============================================================ Running W10UI v10.35 ============================================================ ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/5: windows11.0-kb5027397-x64.cab [Enablement] 2/5: windows11.0-kb5029863-x64.cab [SafeOS DU] 3/5: Windows11.0-KB5030310-x64.cab [LCU] 4/5: windows11.0-kb5030327-x64.cab [Setup DU] 5/5: Windows11.0-KB5030508-x64.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2351~31bf3856ad364e35~amd64~~22621.2351.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2351 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_KB5027397~31bf3856ad364e35~amd64~~22621.2355.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.2361.1.13 [==========================100.0%==========================] The operation completed successfully. ============================================================ Cleaning up OS image... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22631.2361 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. ============================================================ Finished ============================================================ =============================================================================== Finished Updates Integration through W10UI Script =============================================================================== =============================================================================== I do not know what is happening. Note: No variables are being sent empty. This has been checked. For the Pro I created the ini with the parameters to integrate with Winre, but I didn't see the winre update messages. Spoiler: ini file Code: [W10UI-Configuration] Target =B:\IMCK\MNT\I\2 Repo =B:\IMCK_TOOLS\WHD\w11\x64\10.0.22621 DismRoot =B:\IMCK_TOOLS\Bin\x64\DISM10\Dism.exe Net35 =0 Net35Source = Cleanup =1 ResetBase =0 LCUwinre =1 WinRE =1 UpdtBootFiles =1 SkipEdge =0 UseWimlib =0 _CabDir =B:\IMCK\TMP\ExtractedUpdateFiles MountDir =B:\IMCK\MNT\I\2 WinreMount =B:\IMCK\MNT\WinRe wim2esd =0 wim2swm =0 ISO =0 ISODir = Delete_Source =0 AutoStart =1 What could be wrong in the ini file?
@inTerActionVRI search for this line and remove it (2nd instance) Code: set "repo=!_work!" this shuould solve the Ethernal pause with the empty "" mount path, the script ignore the parameters and read the Target/_cabdir from ini file
Now, I'm discarding the changes and restarting the process to check the difference and see if the update in winre applies to the pro index. EDIT: Not integrated in winre mount dir. Should I call the script passing the winre mount point, to be able to update winre.wim? And, also make a call to each boot index to update boot.wim? I'm not doing that. Could this be what I'm doing wrong?
@inTerActionVRI No, this unattended mode will update the mounted directory as-is, regardless what's the source wim, and it will not updated inner winre.wim it's really ment as companion with W10MUI, and not used by itself
If I use it by placing the mount points for "%winremount%" and for "%bootmount%\1" and "%bootmount%\2", will it cause any problems? Or will W10UI identify the type of mount point and integrate the relevant updates?
Yes, the winremount will be commited, unmounted and placed in all indexes. And after the suggestion to comment the line to avoid the eternal pause. I added the fourth parameter and everything seems to have gone correctly. Spoiler: full console log progress Code: =============================================================================== Integrate Update Files through W10UI =============================================================================== Image : install.wim Image Index : 1;2 Image Architecture : x64 Image Version : 10.0.22621.1.0 =============================================================================== [install.wim, Index : 1 - Edition : Core] =============================================================================== ------------------------------------------------------------------------------- Creating W10UI-Configuration .ini file ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Start Integrating Updates Process through W10UI Script ------------------------------------------------------------------------------- ============================================================ Running W10UI v10.35f ============================================================ 1/5: windows11.0-kb5027397-x64.cab [Enablement] 2/5: windows11.0-kb5029863-x64.cab [SafeOS DU] 3/5: Windows11.0-KB5030310-x64.cab [LCU] 4/5: windows11.0-kb5030327-x64.cab [Setup DU] 5/5: Windows11.0-KB5030508-x64.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2351~31bf3856ad364e35~amd64~~22621.2351.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2351 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_KB5027397~31bf3856ad364e35~amd64~~22621.2355.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.2361.1.13 [==========================100.0%==========================] The operation completed successfully. ============================================================ Cleaning up OS image... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22631.2361 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. =============================================================================== [install.wim, Index : 2 - Edition : Professional] =============================================================================== ------------------------------------------------------------------------------- Creating W10UI-Configuration .ini file ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Start Integrating Updates Process through W10UI Script ------------------------------------------------------------------------------- ============================================================ Running W10UI v10.35f ============================================================ 1/5: windows11.0-kb5027397-x64.cab [Enablement] 2/5: windows11.0-kb5029863-x64.cab [SafeOS DU] 3/5: Windows11.0-KB5030310-x64.cab [LCU] 4/5: windows11.0-kb5030327-x64.cab [Setup DU] 5/5: Windows11.0-KB5030508-x64.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2351~31bf3856ad364e35~amd64~~22621.2351.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2351 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_KB5027397~31bf3856ad364e35~amd64~~22621.2355.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.2361.1.13 [==========================100.0%==========================] The operation completed successfully. ============================================================ Cleaning up OS image... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22631.2361 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. =============================================================================== [WinRe.wim] --> [install.wim, Index : 2 - Edition : Professional] =============================================================================== ------------------------------------------------------------------------------- Creating W10UI-Configuration .ini file ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Start Integrating Updates Process through W10UI Script ------------------------------------------------------------------------------- ============================================================ Running W10UI v10.35f ============================================================ 1/5: windows11.0-kb5027397-x64.cab [Enablement] 2/5: windows11.0-kb5029863-x64.cab [SafeOS DU] 3/5: Windows11.0-KB5030310-x64.cab [LCU] 4/5: windows11.0-kb5030327-x64.cab [Setup DU] 5/5: Windows11.0-KB5030508-x64.cab [SSU] Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2351~31bf3856ad364e35~amd64~~22621.2351.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2351 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_KB5029863~31bf3856ad364e35~amd64~~22621.2209.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1844 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.2361.1.13 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.2361 [=================== 33.6% ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.2361 [==========================100.0%==========================] The operation completed successfully. =============================================================================== [boot.wim, Index : 1] =============================================================================== ------------------------------------------------------------------------------- Creating W10UI-Configuration .ini file ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Start Integrating Updates Process through W10UI Script ------------------------------------------------------------------------------- ============================================================ Running W10UI v10.35f ============================================================ 1/5: windows11.0-kb5027397-x64.cab [Enablement] 2/5: windows11.0-kb5029863-x64.cab [SafeOS DU] 3/5: Windows11.0-KB5030310-x64.cab [LCU] 4/5: windows11.0-kb5030327-x64.cab [Setup DU] 5/5: Windows11.0-KB5030508-x64.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2351~31bf3856ad364e35~amd64~~22621.2351.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2351 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_KB5027397~31bf3856ad364e35~amd64~~22621.2355.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.2361.1.13 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting WinPE image base... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.2361 [=================== 33.6% ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.2361 [==========================100.0%==========================] The operation completed successfully. =============================================================================== [boot.wim, Index : 2] =============================================================================== ------------------------------------------------------------------------------- Creating W10UI-Configuration .ini file ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Start Integrating Updates Process through W10UI Script ------------------------------------------------------------------------------- ============================================================ Running W10UI v10.35f ============================================================ 1/5: windows11.0-kb5027397-x64.cab [Enablement] 2/5: windows11.0-kb5029863-x64.cab [SafeOS DU] 3/5: Windows11.0-KB5030310-x64.cab [LCU] 4/5: windows11.0-kb5030327-x64.cab [Setup DU] 5/5: Windows11.0-KB5030508-x64.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2351~31bf3856ad364e35~amd64~~22621.2351.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2351 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_KB5027397~31bf3856ad364e35~amd64~~22621.2355.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.2361.1.13 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting WinPE image base... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.2361 [=================== 33.6% ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25947.1000 Image Version: 10.0.22621.2361 [==========================100.0%==========================] The operation completed successfully. =============================================================================== Finished Update Files Integration through W10UI Script =============================================================================== =============================================================================== Press any key to continue . . . So, would there still be any contraindications about informing the path to sources? Thnks!
@abbodi1406, Can I ask for a detail for the next version of W10UI? If possible, add the option to configure the path to wimlib in the W10UI.ini settings.