also when you delete this both wims you have more than 4.6 GB?? hmm i have one AIO iso with all version also with WMC ( without integrated updates) and iso has 3.85GB
Just wanted to let everybody know that I followed the same procedure I used for Windows 8, this time for Windows 7. Install w7 (clean MSDN sp1u) with JFX's WinNTSetup, use alternate unattend.xml with the Audit setting, get updates with Windows Update (not the PC-specific ones), generalize, shutdown, DISM capture-image. Then tested the new updated w7.wim with (again) WinNTSetup, with my normal autounattend.xml (for full unattended setup). OK, for you experts this is all very normal stuff, but for me this is a very special christmas gift. Two new .wim files on my USB, with w7 and w8 fully up-to-date, ready for clean setups. Amazing stuff, thanks to everyone who helped me with this. Still too bad for SukInSin, but USB is the way to go...
i dont know what i doing wrong with wind i download integrator all was OK atari can you upload your wim for win 8 ? usb ?
This won't matter for WinNTSetup, but you can also put Windows 7 and Windows 8 in one .wim and use the Windows 8 setup files to install. The difference is that Windows 7 setup creates a 100 MB boot partition, and Windows 8 setup creates a 350 MB one (which, if you're going to use BitLocker, is better anyway because it's usable for WinRE).
Thanks 100, I might try that as well. I don't use the 100mb/350mb reserved partitions now, but I like to try things out, so... After the successful w8/w7 audit experiments, I'm curious about XP, but I guess this works quite differently. Any pointers/ links?
so 64x updates not work for me but x86 i have windows 8 pro x86 windows 8 ent x86 and integration worked ok for both (34 updates) now my wim finally has 2.80GB i hope that is OK now.
I see your are running the files from your desktop. move all updates and install.wim to your c: drive and run from there.....
Well, isn't this all a lot of fun For my last test, this is what I did: (1) Install Windows 8 64-bit with an "Audit mode" xml. (2) After setup, let Windows Update do all updates (except PC-specific ones). (3) DISM cleanup (nothing to do) (4) Let Sysprep generalize and shutdown. (5) WinPE4: Capture wim with DISM. (6) To test, use new wim to setup a new Windows 8 64bit. (7) Check Windows update (hoped to see "no updates needed"). Instead, there's 2756872 (169mb), 2770917 (142mb), 2779768 (61mb). Now I know these are discussed elsewhere, but still I'm disappointed. It all seems too much work to create an up-to-date wim, even though I would really like to have one of these! Of course, I could do another run in Audit mode, or try to inject the offline updates into the wim, etc., but who's to say that in a month or two, there'll be more stubborn updates that can't be easily integrated into the wim? Oh well, I expected a bit too much maybe....
Same happens to me too... First i tried to install those manually but message appeared that "already installed". I already integrate those updates in wim but after install, window was showing again those updates (Not exactly the same as mentioned by you) in list. But after two three restarts & recheck with widdows update those number gone without reinstall.
Thanks rrohela!!! I will try a few reboots, and then maybe I'll keep the new .wim after all!! and all work was *not* a waste of time after all Thanks! Maybe if I'll try a little harder, I (we) will find a secret setting somewhere that prevents those updates from appearing in the list without a reason. At least you saved me the trouble of testing to inject those updates in the wim, when there's no reason to. So thanks again!!!!
wooork it has been hidden i must click installed updates so installed 33 so 1 missing when i click check updates it show me only 9 updates Microsoft Windows [Version 6.2.9200] (c) 2012 Microsoft Corporation. All rights reserved. C:\Windows\system32>dism /online /get-packages Deployment Image Servicing and Management tool Version: 6.2.9200.16384 Image Version: 6.2.9200.16384 Packages listing: Package Identity : Microsoft-Windows-CameraCodec-Package~31bf3856ad364e35 .2.9200.16464 State : Installed Release Type : Update Install Time : 12/23/2012 8:30 AM Package Identity : Microsoft-Windows-Client-LanguagePack-Package~31bf3856 5~x86~en-US~6.2.9200.16384 State : Installed Release Type : Language Pack Install Time : 7/26/2012 6:47 AM Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~ 2.9200.16384 State : Installed Release Type : Foundation Install Time : 7/26/2012 6:03 AM Package Identity : Microsoft-Windows-Winhelp-Update-Client-TopLevel~31bf3 4e35~x86~~6.2.0.1 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2727528~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Security Update Install Time : 12/23/2012 8:30 AM Package Identity : Package_for_KB2746119~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Hotfix Install Time : 12/23/2012 8:30 AM Package Identity : Package_for_KB2753842~31bf3856ad364e35~x86~~6.2.2.0 State : Installed Release Type : Security Update Install Time : 12/23/2012 8:30 AM Package Identity : Package_for_KB2756872~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2758246~31bf3856ad364e35~x86~~6.2.2.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2761094~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2763342~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Hotfix Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2764870~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2768703~31bf3856ad364e35~x86~~6.2.1.1 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2769034~31bf3856ad364e35~x86~~6.2.1.1 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2769165~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2769674~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Hotfix Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2770660~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Security Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2770816~31bf3856ad364e35~x86~~6.2.1.1 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2771821~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2777166~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2777294~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2779562~31bf3856ad364e35~x86~~6.2.1.1 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2779768~31bf3856ad364e35~x86~~6.2.1.1 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2780541~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2781498~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Hotfix Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2782419~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2782560~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Hotfix Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2782826~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Hotfix Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2783251~31bf3856ad364e35~x86~~6.2.1.1 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2784153~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Hotfix Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2784160~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2785605~31bf3856ad364e35~x86~~6.2.1.2 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2788261~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2792463~31bf3856ad364e35~x86~~6.2.1.0 State : Installed Release Type : Hotfix Install Time : 12/23/2012 8:56 PM Package Identity : Package_for_KB2792476~31bf3856ad364e35~x86~~6.2.1.2 State : Installed Release Type : Update Install Time : 12/23/2012 8:56 PM The operation completed successfully. hmm but why on X64 wims it show me always errors ? maybe that i run on X86 system ?
100, I think I might test that next week, but do you think/know that there's any "overlap" in w7.wim and w8.wim? Or will the new wim size be just w7+w8? So if w7.wim = 2gb, w8.wim = 2gb, will w7andw8.wim be smaller than 4gb?
I see you got 2756872 and 2779768 in there, congrats! In my version, they're not present. I think I might give the whole Audit cycle another go, and do more checks if everything's installed... Maybe do some manual updating. But that will be my last try!