I can understand that, fully. Just saying why don't start another parallel solution along Simplix Pack.
It would be correct if I add links after some checking and edits, I think. If everybody make additions there would be no reason for this topic to exist. Main post updated with version UpdatePack7R2 version 15.1.20
@ gamazet: Thank you for your heads up in your pm. I couldn't answer that because I didn't have 5 posts til now. Anyway it's sorted out now.
There are already other paths similar to this - i.e. WUD (the windows update downloader) that uses a list of patches to download them from MS into a directory. From there, you can use NTLite (or other tools) to integrate them. In fact, the SIMPLEX approach uses DISM to integrate the patches, and that could also be done with some scripting. So for now, unless you have a real urge to make another "wheel", there really isn't anything "magic" going on here, and I (for one) am happy to let Simplex do his thing!
Sorry but i didn't say start a parallel solution but what i wanna say that group is better than a single person contribution.. simplix has his own life own things to do so if we start as a group than some small small contribution make a huge difference and we make a good app. he also told that he don't have time for windows 8.1 may be we can build ... it just a my opinion guys sorry if someone is feeling bad. thnx
I am quite impressed with the Simplix Updater. I applied it to a Win7 iso, and did a fresh install and it reduced the install footprint by ~10GB, compared to a fresh install of Win7 then updating. After I installed from Updated iso I only had *9 updates to d/l via Windows Update, besides 5 updated drivers.
I agree! Long live Mr Simplix's work Here is a script I used before I found SIMPLIX, you will still need to compress your WIM file after and I have posted this elsewhere on the forum. Hardest issue faced is that if you download all updates posted since SP1, then you have 100+ but you need to delete some as they are superceeded by new patches and this is where Mr Simplix has done his homework well. This script needs to be placed in same location as your install.wim and you need a sub-folder called x86 just for all the 32-bit updates. Code: MD %~dp0MOUNT Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:1 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:2 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:3 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:4 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:5 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Pause After you would then run another command, or in same batch file to compress the install.wim Code: @Echo off :: Rename the install.wim to source.wim :: This way you have backup, and you can compare before/after size REN install.wim source.wim dism /Export-Image /SourceImageFile:source.wim /SourceIndex:1 /DestinationImageFile:install.wim /Compress:Max /DestinationName:"Windows 7 Starter x86" dism /Export-Image /SourceImageFile:source.wim /SourceIndex:2 /DestinationImageFile:install.wim /Compress:Max /DestinationName:"Windows 7 HomeBasic x86" dism /Export-Image /SourceImageFile:source.wim /SourceIndex:3 /DestinationImageFile:install.wim /Compress:Max /DestinationName:"Windows 7 HomePremium x86" dism /Export-Image /SourceImageFile:source.wim /SourceIndex:4 /DestinationImageFile:install.wim /Compress:Max /DestinationName:"Windows 7 Professional x86" dism /Export-Image /SourceImageFile:source.wim /SourceIndex:5 /DestinationImageFile:install.wim /Compress:Max /DestinationName:"Windows 7 Ultimate x86" Pause Overall, I find the Simplix method much cleaner and easier to use, but fear not at least you can use batch file and DISM yourselves if he decided to quit.
Just to double check, there is no reason this wouldn't work on an AIO that includes both 32 and 64 bit right? Also, is there something similar for Vista and 8.1? I had a quick look but I'm an internet person and therefore lazy... obviously. /s Oh, and also, would this work on ThinPC?
There would be no problem if you integrate updates first in all indexes of x86 image than in x64. How you will create AIO afterwards depends on you. Lot of ppl here are making AIOs so I know it is possible. There is no Simplix Pack for Vista and Windows 8.1. If the updates are the same for ThinPC as for non-stripped down windows 7, than there should be no problem. But I doubt that they are the same. Anyway Simplix Pack will report eventual error.
There are just a few simple rules to follow: 1. Always use a "Virgin" install.wim (SP1) to update from. If you apply the updates say to an install.wim you updated to last month, then the size will be bigger than one you update from "Virgin" SP1 file. 2. You can update an AIO install.wim (Windows 7 32+64-bit = 9 indices) again providing you apply to an AIO that is just SP1 (no updates applied) 3. You can update 32-bit install.wim, then update 64-bit install.wim... then combine AFTER updating both sepertate install.wim 4. Remember you final AIO install.wim will most likely be bigger than 4GB! So if you wantto use this to boot later you may need DVD9 or USB stick formatted so it can handle 4GB+ files. All of this can be done by batch file if need be, and left to run over night. You have the bones of the batch file above to add updates from a folder to a 32-bit install.wim, you can simply expand this to make a 64-bit updated install.wim after you can use DISM again to combine both install.wim's into a single AIO
Well, I've got it running on my AIO image now. Told it to do all indexes and it seems to be working it's way through them correctly. I've also now noticed the Windows Download Integrator, but it's discontinued. I'll give that a shot tho first.
What's the difference between installing the pack the first time with ie11 vs installing it without ie11 and then re-running the pack with ie11? The first post says it's recommended to run the pack twice for ie11; but I had already ran the pack the first time with ie11; was wondering if I needed to redo the install? I did silent and reboot options, so when the pack was done with the 100 updates, it rebooted, and upon logging in, the pack installer reappeared with 90 updates; is this because of me doing ie11 first?
That advice is just for those with problems installing IE11, or just to be sure that everything will go well. Usually nothing is wrong when installing Pack at once. In your case too much updates reappeared. I don't know why, but it's certainly not the case because of doing whole pack at once. When updating, Pack should run on clean fresh installed system.
i integrate the update in index:1 ( starter) i delete other image's and i show this error View attachment 33386
DISM error code 769 means compression is disabled on volume Type on CMD prompt c:\>fsutil behavior query disablecompression If the value is 1 than you should change it Run regedit and look for HKLM\System\CurrentControlSet\Policies ---If you see Value NtfsDisableCompression Deactivate this and restart Than, type on CMD prompt c:\>fsutil behavior query disablecompression to see the status. If it is 0 should be OK