@murphy78 If possible I want to ask you something, for example: I do a snapshot of the windows through a virtual machine, creating a custom iso only with integrated updates, but even I using an ESD iso and it is capturing the install.esd the same size of a install.wim with the same procedure. The command used for this capture is this: Code: cd sysprep sysprep dism /online /cleanup-image /startcomponentcleanup sysdm.cpl lusrmgr cleanmgr dism /capture-image /imagefile:<local which will save> /capturedir:<drive letter the VHD> /name:<description> /compress:max To some command that I can use so you can decrease the size of install.esd?
To my knowledge you can only capture as WIM file with these commands. Even if you name it ESD it's still a WIM file. You can convert the WIM to ESD afterwards. Code: dism /Export-Image /SourceImageFile:"path\to\install.wim" /SourceIndex:1 /DestinationImageFile:"path\to\new\install.esd" /Compress:recovery
@s1ave77 Thanks Bro! But the question I'm sorry, I did not understand much of it, following the procedure I use to capture the install.wim (or.esd), at what time I could use the command mentioned by you? I can replace the command I use for what you showed me? Code: dism /capture-image /imagefile:<local which will save> /capturedir:<drive letter the VHD> /name:<description> /compress:max for this Code: dism /Export-Image /SourceImageFile:"path\to\install.wim" /SourceIndex:1 /DestinationImageFile:"path\to\new\install.esd" /Compress:recovery
After the capture of the WIM you can convert it to ESD with that command. It will decrease size by ~25%.
i have a question: how to preinstalled some app and driver with winreducer? for example how to preinstalled nvidia and intel driver with program?
I think this will work... Code: dism /image:c:\mount /enable-feature /featurename:microsoft-hyper-v-all /all
There's a drivers addition section in winreducer. I don't really know beyond that. I'd prefer to stick to Microsoft methods.
did anyone try to integrate 2969339 in the ISOs with the update 1, that already have 2919442 integrated? from my observations, i saw that adding 2969339 before doing any other operation (like enabling NetFx3 or adding all the updates), that status of the update is Installed if 2969339 is added after enabling NetFx3 for example, it will have the status as "Install Pending" so i am wondering, which method is best to deal with this update offline, a) adding it before everything else, b) adding it before everything else and then cleanup the image with /resetbase, because there is no pending action, or c) adding it as any regular update in no particular order? i read a while ago a post made by murphy and he said that using /resetbase after adding a servicing stack update to install.wim could cause some issues, but can't find the post anymore it seems. i know that /resetbase is good for boot.wim and winre.wim as it cleans up the images, but i am mostly interested about install.wim
option c is good, or: d) adding it before everything else, without running /resetbase if one update triggers the Pending status, any update integrated after it will have the Pending status for now, those three updates doesn't trigger penging status 2969339, 2966870, 2959977 2934018 will trigger it, so leave it after them
thank you for the reply, your option D was my option A but i didn't make myself clear sorry and yes i know, even NetFx3 sets the Pending status to future updates, but i don't mind about the Pending flag to the other updates, was just interested about how to deal with the servicing stack update thank you for the answer
Once you trigger the pending status, everything installed past that point will also be added pending, whether or not it needs to.
When compressing wim files to esd files, DISM utility stops working with a dialog that says something went wrong bla bla bla. Any ideas? Sometimes works fine without issues so it's an intermittent fail. The problems shows up when export process goes at 1%, if by any lucky chance it surpasses 2% the thing finishes without issues. The problems seems to appear just when I start to export a new index, but not always, it's a random issue. Code: dism /export-image /sourceimagefile:W:\win81aio\esd\install.wim /sourceindex:1 /destinationimagefile:W:\win81aio\esd\install.esd /checkintegrity /compress:recovery I've already did the following recommended export commands prior the above one: Spoiler Code: dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:1 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:2 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:3 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:4 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:5 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:6 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:7 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:8 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:9 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:10 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\install.wim /sourceindex:11 /destinationimagefile:W:\win81aio\esd\install.wim /checkintegrity /compress:max All commands are made in an open command prompt, not a script.
Do you have at least 5 gigs of free memory? Hmm... You might check the dism log in the logs directory and see what error it kicks out at the end of the log where it fails.
That's exactly what I was suspicious of, the amount of RAM, but I needed an expert to confirm this. Oh my, I use a 32 bit Windows 8.1 with 4GB RAM so go figure Then I've got 3.21 GB usable RAM minus 600 MB used by OS, hahahaha. Now what the h... I'm going to do? It's a rhetorical question Just a suggestion: you could add this info at first post this way people would know what to expect when doing esd files. Thanks murphy once again.
So, which way you recommend? Enabling NetFx first and then adding updates and let them have Pending status OR Adding updates first and then enabling NetFx? Is it really important for packages to have Pending or Installed status? After successful installation of Windows, all of them will be "installed" at last. And another thing, Does ComponentCleanUp and /ResetBase recommended on install.wim at all? Imagine there is no pending.xml Like: Adding all updates, then ResetBase, NetFx.