Is it possible to create an install wim the same way an install wim gets created by Microsoft? For example, the wim for update3 for win 8.1 is about 3.6 Gig in size. It has about 20 updates that have been superseded and can't be removed from the image. I'd like to create an install wim without those updates. I tried using Update1 as the base and installed the still valid u3 updates, but the install wim is 1GB bigger than the original U3 wim. Resetbase doesn't work because the U3 updates are flagged as pending. Anyone know of an alternative method to do what I want or know how MS creates their install wims with no pending flags and the reduced size? I've read about sysprep and generalize, but it seems there are restrictions (KB828287) that apply which don't seem to apply to the install wims created by MS. I may be wrong though. Thanks for any infos.
I'd be interested in the method MS uses. My results are a bit different. This is what I tried: Used a U1 wim and included the still valid U3 fixes Spoiler Code: Current Edition : ProfessionalWMC Deployment Image Servicing and Management tool Version: 6.3.9600.17031 Image Version: 6.3.9600.17031 Packages listing: ----------------------------------------------------------------------------------------- | --------------- | --------------- | ---------------- Package Identity | State | Release Type | Install Time ----------------------------------------------------------------------------------------- | --------------- | --------------- | ---------------- Microsoft-Hyper-V-Integration-Services-Package-2~31bf3856ad364e35~amd64~~6.3.9600.18792 | Install Pending | Update | 12/27/2017 22:09 Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384 | Installed | Language Pack | 3/18/2014 09:32 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 | Installed | Foundation | 8/22/2013 14:46 Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14 | Installed | Update | 3/18/2014 10:39 Package_for_KB2919442~31bf3856ad364e35~amd64~~6.3.1.8 | Installed | Update | 3/18/2014 09:58 Package_for_KB2932046~31bf3856ad364e35~amd64~~6.3.1.5 | Installed | Feature Pack | 3/18/2014 10:39 Package_for_KB2934018~31bf3856ad364e35~amd64~~6.3.1.5 | Install Pending | Feature Pack | 12/27/2017 21:52 Package_for_KB2937220~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 3/18/2014 10:39 Package_for_KB2937592~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Feature Pack | 3/18/2014 10:39 Package_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Feature Pack | 3/18/2014 10:39 Package_for_KB2938772~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 3/18/2014 10:39 Package_for_KB2939471~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 3/18/2014 10:39 Package_for_KB2949621~31bf3856ad364e35~amd64~~6.3.2.0 | Installed | Hotfix | 3/18/2014 10:39 Package_for_KB2954879~31bf3856ad364e35~amd64~~6.3.2.0 | Install Pending | Update | 12/27/2017 21:52 Package_for_KB2967917~31bf3856ad364e35~amd64~~6.3.1.2 | Install Pending | Update | 12/27/2017 21:52 Package_for_KB2968599~31bf3856ad364e35~amd64~~6.3.1.1 | Install Pending | Update | 12/27/2017 21:52 Package_for_KB2973351~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Security Update | 12/27/2017 21:52 Package_for_KB2978002~31bf3856ad364e35~amd64~~6.3.1.1 | Install Pending | Update | 12/27/2017 21:52 Package_for_KB2978742~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Security Update | 12/27/2017 21:53 Package_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8 | Install Pending | Update | 12/27/2017 22:03 Package_for_KB3003057~31bf3856ad364e35~amd64~~6.3.1.6 | Install Pending | Security Update | 12/27/2017 22:04 Package_for_KB3014442~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Update | 12/27/2017 22:05 Package_for_KB3022776~31bf3856ad364e35~amd64~~6.3.3.0 | Install Pending | Hotfix | 12/27/2017 22:05 Package_for_KB3088956~31bf3856ad364e35~amd64~~6.3.1.24 | Install Pending | Hotfix | 12/27/2017 22:06 Package_for_KB3133690~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Update | 12/27/2017 22:06 Package_for_KB3173424~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Update | 12/27/2017 22:06 The operation completed successfully. After the install 1. ran dism /Online /Cleanup-Image /StartComponentCleanup /Resetbase 2. ran sysprep /generalize /shutdown /oobe 3 from w10, ran Code: dism /Capture-Image /ImageFile:d:\W81Pro$WMC++.wim /CaptureDir:e:\ /Name:"Windows 8.1.1 Pro with Media Center" /compress:max The resulting wim showed all the packages flagged as installed and the image was about 3.8gig compared to the 3.6gig original u3 My install with the captured image did not run the same way as with an MS install.wim, because the userid that I created during the installation to do the sysprep was still part of the image after the capture. Generalize doesn't seem to get rid of it for a clean install. There a probably other things left behind too that don't get included with the MS images. What did I do wrong?
Did you install in Audit mode? and you need to use wimscript.ini to exclude some redundant files from capture Spoiler Code: [ExclusionList] \hiberfil.sys \pagefile.sys \swapfile.sys \System Volume Information \$Recycle.Bin\* \Recycler \Recycled \Windows\CSC \winpepge.sys \$windows.~ls \$windows.~bt \Boot \Recovery \Recovery.txt \bootsect.bak \ProgramData\Microsoft\Network\Downloader\* \ProgramData\Microsoft\Windows\SQM \Users\*\NTUSER.DAT*.TM.blf \Users\*\NTUSER.DAT*.regtrans-ms \Users\*\NTUSER.DAT*.log* \Users\*\AppData\Local\Microsoft\Windows\INetCache\IE\* \Users\*\AppData\Local\Microsoft\Terminal Server Client\Cache\* \Users\*\AppData\Local\Opera\Opera\cache\* \Users\Administrator \Windows\AppCompat\Programs\Amcache.hve*.TM.blf \Windows\AppCompat\Programs\Amcache.hve*.regtrans-ms \Windows\AppCompat\Programs\Amcache.hve*.log* \Windows\CSC \Windows\Debug\* \Windows\inf\*.etl \Windows\inf\*.ev* \Windows\inf\*.log \Windows\Logs\CBS\* \Windows\Logs\DISM \Windows\Logs\DPX \Windows\Logs\dosvc\* \Windows\Logs\WindowsUpdate\* \Windows\Logs\PBR \Windows\Logs\*.log \Windows\Panther\*.etl \Windows\Panther\*.log \Windows\Panther\FastCleanup \Windows\Panther\img \Windows\Panther\Licenses \Windows\Panther\MigLog*.xml \Windows\Panther\Resources \Windows\Panther\Rollback \Windows\Panther\Setup* \Windows\Panther\UnattendGC \Windows\Panther\upgradematrix \Windows\Prefetch\* \Windows\security\database\*.chk \Windows\security\database\*.log \Windows\security\database\*.jrs \Windows\ServiceProfiles\LocalService\AppData\Local\FontCache-S-1-5-21-*.dat \Windows\ServiceProfiles\LocalService\NTUSER.DAT*.TM.blf \Windows\ServiceProfiles\LocalService\NTUSER.DAT*.regtrans-ms \Windows\ServiceProfiles\LocalService\NTUSER.DAT*.log* \Windows\ServiceProfiles\NetworkService\NTUSER.DAT*.TM.blf \Windows\ServiceProfiles\NetworkService\NTUSER.DAT*.regtrans-ms \Windows\ServiceProfiles\NetworkService\NTUSER.DAT*.log* \Windows\servicing\Sessions\*_*.xml \Windows\servicing\Sessions\Sessions.back.xml \Windows\SoftwareDistribution\Download\* \Windows\System32\catroot2\*.chk \Windows\System32\catroot2\*.log \Windows\System32\catroot2\*.jrs \Windows\System32\config\RegBack\* \Windows\System32\config\*.TM.blf \Windows\System32\config\*.regtrans-ms \Windows\System32\config\*.log* \Windows\System32\CodeIntegrity\bootcat.cache \Windows\System32\SMI\Store\Machine\SCHEMA.DAT*.TM.blf \Windows\System32\SMI\Store\Machine\SCHEMA.DAT*.regtrans-ms \Windows\System32\SMI\Store\Machine\SCHEMA.DAT*.log* \Windows\System32\Sysprep\Panther \Windows\System32\Sysprep\Sysprep_succeeded.tag \Windows\System32\wdi\LogFiles\* \Windows\System32\winevt\Logs\* \Windows\System32\winevt\TraceFormat\* \Windows\Temp\* \Windows\WinSxS\ManifestCache\* \Windows\WinSxS\Temp\* \Windows\*.log [CompressionExclusionList] *.mp3 *.zip *.cab *.wmv *.wma *.wim *.swm *.dvr-ms \windows\inf\*.pnf *.rar *.7z
Nice, I will try audit mode and then the capture with the wimscript.ini. I haven't used any of these functions before, so I really appreciate the help.
Here is a useful thread about the subject: https://forums.mydigitallife.net/th...etupcomplete-firstlogon-silent-install.73131/
Audit Mode and wimscript.ini did the trick. I now have a clean refeshed u3 wim which ended up being 3.5 gig and slightly smaller than the original. If the trend stays with the monthly rollups, would it be advisable to create a refresh with the additional 237 or so W8.1 fixes excluding the rollup? That would pretty much give me an updated install.wim that might only require new rollups or SSUs to be applied, or am I missing some important facts that would make this a not so good of an idea?