Doesn't work for me. I run the script and the windows folder named Documents opens and that is it??? Maybe step 3?? What index number would I want? How do I do this step? Other than that I did as instructed.
Figured it out. I named the initial folder W8 Folder instead of W8 as the path you list is C:\W8 Folder. I'm good now. Thanks.
Ok I can see where I won't be able to use this. The new file size is 4.46GB. I install using USB and GPT UEFI Boot so the USB has to be formatted Fat32. Fat 32 only goes to 4GB in size so I'm licked.
Does this script not perform the resetbase against the mounted .wim ? Is that why the size is so much larger. Code: dism /Image:c:\w8\mount\install /cleanup-image /startcomponentcleanup /resetbase #
where in the script can i put dism /Image:c:\w8\mount\install /cleanup-image /startcomponentcleanup /resetbase #
Not sure, the workflow is hinkey with all the batch 'functions', so MSMG would be the one to ask. For know I would test my theory by mounting the file (after using MSMG's script), run the resetbase, commit wim, then export the image into a new .wim container. (pick any name you want) Or maybe it cannot be done until after installation.
Unless I misremember, I think I tried that. As I recall, it refused because there were pending updates.
You cannot because most of the updates trigger pending status. What you can do, and what I plan on starting to do come this next patch date is make a setupcomplete.cmd with the resetbase line Make folder structure: $oem$\$$\Setup\Scripts\ Then inside the scripts\ folder, make setupcomplete.cmd with the following: dism /online /cleanup-image /startcomponentcleanup /resetbase Save the file and copy the entire $oem$ folder to the \sources\ folder of the iso.
In light of that, then the next steps after the batch would be to install the iso, sysprep, resetbase (or vice versa) and recapture the new GA wim with fully integrated updates. Then you might get an under 4GB install.wim.
Update Windows 8.1 Enterprise Evaluation with: KB2894179 KB2883200 KB2894029 Using MGMG Toolkit, Updated fine, Thanks ace2 .
Already done that. A better solution would be to figure out a way to extract the install.esd files though... Even if you delete the administrator folder before capturing, it still generates a decent amount unique data. We really need to get an install.esd extraction method down solid. I have the prowmc install.esd files, but I don't have Pro, Core, Pro N, Core N, or Core SL en-us versions