Yeah, so far he never refused to help me when asked in a post or via several PMs . Believe me, some questions could be considered the opposite to qualified or sophisticated, to say it politely (or embarassingly stupid in clear text) .
Hi xinso, I'm trying to integrate some updates to Windows 8.1 with Update using the following command in a cmd prompt window, but it doesnt work: Code: for %%A in (W:\Upd_x86\KB\*.msu) do (cmd /c "dism /image:W:\win81aio\mount /Add-Package /PackagePath:%%A") It returns this error: %%A was unexpected at this time. Any help appreciated. When replied this post will be deleted
Try this: Code: for /R "W:\Upd_x86\KB" %%A in (*.msu) do (cmd /c "dism /image:W:\win81aio\mount /Add-Package /PackagePath:%%A") Or afaik better: Code: for /R "W:\Upd_x86\KB" %%A in (*.msu) do (dism /image:W:\win81aio\mount /Add-Package /PackagePath:%%A)
Updated dism.exe file was put manually into C:\Windows\System32. Then I open a cmd prompt as admin. change path to W:, run any other previous dism commands from that path (murphy's commands for offline integration) and everything went fine. It's just this loop I'm currently trying to execute. I'm working on Windows 8.1 with Update machine to do this job. Dism version: 6.3.9600.17031
Afaik you need the complete DISM folder (matching OS architecture), not only the single EXE . Better copy the whole folder to new location and place script there. Never faced that error with my tool and using several for-loops. The DISM part is started from inside the DISM files folder.
OK s1ave77, may I ask you a favor, could you upload a zipped file containing the folder/s to put it manually within System32 folder? Please.
I'm throtteled in bandwith so i can't. My JATD script from signature is shipped with x64 files in \files\adk\, simply delete the DISM.cmd .
It's only several MB large. I installed once and copied the folder. Now it works without installation .
Nope, this needs the adk files, either installed and used via adk own CMD or copied files and used by running best from inside the folder. That way it's nearly foolproof. The built-in DISM is mostly meant for /online maintenance on a running Windows but not for offline servicing of WIM files .
Thanks xinso, the only inconvenience I see, no offense, is that I want a loop for n updates. I guess this code is limited for the named KBs: Code: :Integrate DISM.exe /Mount-Wim /WimFile:install.wim /index:%~1 /MountDir:D:\mount for %%A in (KB2919442 KB2919355 KB2932046 KB2959977 KB2937592 KB2938439 KB2934018) do dir /b "msu" 2^>nul | findstr /i %%A >nul&&%INEL1% (Dism /Add-Package /PackagePath:"msu\%%A.msu" /Image:D:\mount) DISM.exe /Unmount-Wim /MountDir:D:\mount /commit
two of the baseline and Windows8.1-KB2934520-x86. These 3 KBs do need specific order. I have separate commands for them. As for the rest of KBs the order don't matter, here's where the loop comes into action.