yes you can. after mounting each index of the wim file you can use this command to add updates package; type the following command to add a specific package to each index of the image. You can add multiple packages on one command line as I did below. They will be installed in the order listed in the command line. the follwoing updates are for my system on win8.1 64bits, if you have diiferent updates for your system then just add them like below. each color shows addition of different updates for your easy understanding. path is same as posted in the first post of this thread. Code: [FONT=&]Dism /Image:C:\win81\mount /Add-Package /PackagePath:C:\win81\packages\Windows8.1-KB2894179-x64.msu [/FONT][FONT=&]/PackagePath:C:\win81\packages\Windows8.1-KB2883200-x64.msu [/FONT][FONT=&]/PackagePath:C:\win81\packages\Windows8.1-KB2894029-x64.msu [/FONT][FONT=&]/PackagePath:C:\win81\packages\Windows8.1-KB2901549-x64.msu [/FONT][FONT=&][/FONT][FONT=&]and so on[/FONT][FONT=&] [/FONT] You can add the drivers too. [please extract all drivers of your system to their specific folders and put these folders to a folder named drivers. suppose your driver folders is here: C:\win81\drivers Code: [FONT=&]Dism /Image:C:\win81\mount /Add-Driver /Driver:c:\win81\drivers /Recurse [/FONT] after doing all add and removal activity unmount the index to save the changes.
How to rebuild .WIM ??? I've integrated updates to my Win8.1 Pro ISO but it's size increased to 4GB, that's crazy. I want to know how to rebuild .wim with the maximum compression, please help me
You cannot rebuild wim to increase the compression because all of that extra information is uniquely identified. It can only store the exact same files, regardless of most of the content of the files. The way you can reduce the size when you add tons of updates is to export to install.esd recovery compression format and delete the install.wim file. It requires a multiple export-step method though... Basically what you do when you integrate is roughly like this: Code: @echo off if not exist c:\temp mkdir c:\temp if not exist c:\mount mkdir c:\mount if not exist c:\win81 exit for /l %%x in (1, 1, 20) do ( dism /mount-wim /wimfile:c:\win81\sources\install.wim /index:%%x /mountdir:c:\mount dism /image:c:\mount /add-package /packagepath:c:\msufiles\ dism /unmount-wim /mountdir:c:\mount /commit dism /export-image /sourceimagefile:c:\win81\sources\install.wim /sourceindex:%%x /destinationfilename:c:\temp\install.wim /compress:maximum /checkintegrity ) for /l %%x in (1, 1, 20) do ( dism /export-image /sourceimagefile:c:\temp\install.wim /sourceindex:%%x /destinationfilename:c:\win81\sources\install.esd /compress:recovery /checkintegrity ) del /q /s c:\win81\sources\install.wim oscdimg -u1 etc... Obviously that is for 20 indexes... If you have less indexes, make the loops for the appropriate amount of indexes. I personally use a copy/paste method on my own personal scripts, but the loop method is easier to work with. The reason I use a double export method instead of exporting straight from the c:\win81\sources\install.wim to c:\win81\sources\install.esd is that for some reason when you do that it has weird errors during setup. It seems to get worse the more information you add to your index, but exporting first to a different temporary install.wim seems to fix the issue.
Thanks But, isn't .esd format is uneditable? I've looked at WinToolkit, there's an option to rebuild WIM which it says that will reduce the size of install.wim, but i want to know what kind of code to rebuild the WIM just like WinToolkit do
Code: imagex /compress maximum /export X:\win81\sources\install.wim * X:\temp\install.wim move /y X:\temp\install.wim X:\win81\sources\ Just replace X to your WIM file location..
Ahh, well... you can slightly re-compress the wim file by re-exporting it, but it doesn't compress it nearly as much as the esd file. As far as being uneditable, you can save the temporary install.wim from the first export and simply use that later if you wish.
Ok I'm having trouble with an automated cmd script copying the data.dat file the tokens.dat copies over fine. Data.dat requires admin privileges to overwrite, how do it set this in my cmd script? please note the I am already running the script with admin privileges Code: @Rem "Inserting Wmc Tokens" xcopy /s /h /y /k /g /c "I:\Apps\Wmc Builder\Wmc 8.1 Patcher\Data\x64\data.dat" "D:\Win81\mount\Windows\System32\spp\store\2.0.\" xcopy /s /h /y /k /g /c "I:\Apps\Wmc Builder\Wmc 8.1 Patcher\Data\x64\tokens.dat" "D:\Win81\mount\Windows\System32\spp\store\2.0.\" "I:\Apps\GetWaikTools\x64\Dism\Dism.exe" /Commit-Image /mountdir:D:\Win81\mount Edit: i assume i have something like this before it? Takeown /F "D:\Win81\mount\Windows\System32\spp\store\2.0.\data.dat" Icacls "D:\Win81\mount\Windows\System32\spp\store\2.0.\data.dat" /grant administrators:F
Code: Echo "Inserting Wmc Tokens" Takeown /F "D:\Win81\mount\Windows\System32\spp\store\2.0.\data.dat" Icacls "D:\Win81\mount\Windows\System32\spp\store\2.0.\data.dat" /grant administrators:F xcopy /s /h /y /k /g /c "I:\Apps\Wmc Builder\Wmc 8.1 Patcher\Data\x64\data.dat" "D:\Win81\mount\Windows\System32\spp\store\2.0.\" xcopy /s /h /y /k /g /c "I:\Apps\Wmc Builder\Wmc 8.1 Patcher\Data\x64\tokens.dat" "D:\Win81\mount\Windows\System32\spp\store\2.0.\" "I:\Apps\GetWaikTools\x64\Dism\Dism.exe" /Commit-Image /mountdir:D:\Win81\mount Ok i tried taking ownership but I still get access denied, other than manually copying it each time and approving the overwrite anyone else got any other ways to automate it? Edit nvm figured it out need a /r D:\>xcopy /r /s /h /y /k /g /c "I:\Apps\Wmc Builder\Wmc 8.1 Patcher\Data\x64\data.dat" "D:\Win81\Mount\Windows\System32\spp\store\2.0" I:\Apps\Wmc Builder\Wmc 8.1 Patcher\Data\x64\data.dat 1 File(s) copied
thank you , worked like a charm, now i have winblues14 with media center fully activated and permanent, also have the iso that can upgrade but has my personal Windows center activation that i cannot share, once installed it is already activated, good thanks for the explination
Hello guys I've been trying to make an AIO out of my Windows 8.1 Pro VL 32/64bit iso's. I've done everything stated in the OP (but I skipped the ''step to convert to ProfessionalWMC") but when I boot to my flash drive (Sandisk Cruzer Force 8gb) I get a BSOD. Do any of you guys know what I've done wrong? I'm not entirely new to this boot to usb thingy as I installed my current os (Win 8.1 Pro 64bit) directly from the same flash drive so I'm quite confused on what I did wrong. If anyone has done this with just the VL editions of Win 8.1 Pro please give me some advice on how to get it done right.
Is there any way using this integration system that I can make separate ISOs of all versions of x86 and all versions of x64, Windows 8.1.
Yeah...but murphy78 is a nice (and very skilled in that field ) guy and will answer questions, i would optimistically guess . For the Record: Still don´t get the point of AIOs. They are the ultimate Nightmare when it comes to maintaining all those countless indices afterwards, and fun when trying to install them in UEFI . To carry updated and correctly tweaked ISOs, i love my Easy2Boot stick, where i simply switch out ISO files and boot directly from them .
I have tried the links for the x86 and x64 bit Enterprise non-N editions but there are no seeders on the torrents. Does anyone know where else I can get them Thanks