@abboddi1406 1. Why KB2746119 for x64 isn't downloaded by WHD? 2. Please also look into 2483564 and 2492386 - do they belong in ''main'' folder (for x64)? Thanks
1. It's downloading here, but latest WHD build has a bug and it deletes first downloaded update 2. 2492386 is a Compatibility Update, it's "almost' superseded, but it has one active valid component for x64 client 2483564 is a regular hotfix and after checking, it's superseded by 2799925-v2 + 2813430 (if installed in LDR) so i think it's safe to remove it
Maybe that's the point, maybe there's no reason to keep that ''one active valid component'', as three similar app compatibility updates, all say in their article they've replaced / superseded 2492386. The three updates are 2820331, 2762895 and 2791765. So if you ask me, I think it's safe to also delete this one, but you know better. Also, abbodi, I have a (hopefully) small request: can you please move 2857650 from main folder to RDP / RDC 8.1? There are four reasons behind: 1. It may still (like other RDP 8.0 / 8.1 updates) generate issues with Win Toolkit (when integrated); 2. It's mainly RDP related, although can also be considered valid for ''normal'' windows components; 3. It was retracted by Microsoft; 4. Issue and Error are the most used words in its KB article
What's the recommended order of offline integration? general > additional > security > hotfixes > ie11 ?
I dont think order matters much. You cant get everything right on first pass anyway. I suggest two passes. On first pass possible prerequisites are integrated but certain hotfixes will surely fail. On second pass any missed ones should also integrate since prerequisites should be in place. Just make sure to do a unmount and commit between passes to solidify changes.
That's interesting to know, all along, -each time there's a new update list-... i would grab a clean vanilla sp1 install.wim and just integrate them following numerical order.. with ie11 last. so are you strongly suggesting that i now repeat the exact same thing twice? Would anyone like to share a second opinion on this?
This is my order.... Code: Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp00.WUClient" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp01.General" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp02.Security" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp03.Hotfix" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp04.Platform" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp05.PlatformUpdates" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp06.WindowsMediaCenter" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp07.WinHelp" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp08.NFS" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp09.WAT" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp010.IE11Prerequisites" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp011.IE11CABs" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp012.IE11Updates
For me All hotfixes (LDR) Windows6.1-KB2685811-x64 and Windows6.1-KB2685813-x64 (GDR) IE cabs IE Updates
This is exactly why sysprep is becoming the way to go for Windows 7. Less problems, you can use WU, even, and no pending updates, etc. Offline integration is inferior to me now, for Windows 7 and its ton of updates especially.
My script generates something like this Code: /packagepath:"Z:\solor\tmp\_x_\22Windows6.1-KB2545698-x64.cab\update.mum" /packagepath:"Z:\solor\tmp\_x_\22Windows6.1-KB2545698-x64.cab\update-bf.mum" /packagepath:"Z:\solor\tmp\_x_\22Windows6.1-KB2547666-x64.cab\update.mum" /packagepath:"Z:\solor\tmp\_x_\22Windows6.1-KB2547666-x64.cab\update-bf.mum" and so on... it's very big Which way do you recommend? to integrate from KB9x to KB2x ALL update-bf.mum that exist and then update.mum starting from KB9 to 2x again?? or to integrate update.mum & update-bf.mum for each KB before moving on to the next? I may have been doing this wrong all along oh dear. What I currently do is integrate update.mum first and then update-bf.mum (if existant) from kb9x to kb2x sequentially.
Well, after further check, 2492386 has two non-superseded components: msimain.sdb, pcamain.sdb (both can be found in Windows\AppPatch) so i take this update as not superseded It's a regular update, why would it generate issue? i can verify that it gets integrated without an issue here nevertheless, i will remove it from General category (it's already found in RDC 8.1 Prerequisites )
Yeah im using a sysprepped image as a base image with NET 4.5 integrated (4.5.1 was not out at that time). That way i can integreate WPF 4.0 without the installation failing ( i need Powershell v3). Atleast sysprep works on Win7. It fails utterly and miserably on Win8 even with slightest changes.