You can install them both offline, but 2821895 has to be last since it is servicing stack stuff. The problem is that it overwrites some of the 2855336 update. If you could integrate it before 2855336 it wouldn't really be a problem. *edit: it could also be that the 2855336 msu file has old components and the windows update version has newer ones... they might v2 it..
Murphy78 I would like to know what the method that you use to integrate the kbs in your iso,you use the audit method by sysprep and capture or you integrates by dism? Thank you
Please, could you tell me, which updates are required to be installed at clean W8 Ent x32 b9200-16384 so KB2855336 could be installed (or offered by Windows Update)...? In other words, on which updates is KB2855336 dependent? Thanks...
Thanks to komm for info on the following changes. And thanks to McRip for info on KB2870270 Repo updated: Added: KB2862073 KB2864629 KB2869923 KB2870270 Removed: KB2830615 (superseded by KB2855336) KB2846618 (replaced by KB2870270) KB2848344 (superseded by KB2870270) ------------ Note: for those having problems with KB2855336, try integrating KB2862073 & KB2864629 to see if things are fixed.
I thought I'd give Win8 a try again. I got the upgrade iso with .esd inside (rather than .wim) but I have converted it several times before (via sysprep). Anyway, I was going to install the esd version again, as before, install all current updates, and sysprep it again to get an updated iso. Well, I don't know what on earth is going on but I have a huge number of updates failing. I mean, crazy. I have about 25 failing (and I'm not done yet), several 'not applicable' and it's just a general mess. This is a clean install in a VM, no problems with the install. Just the updates fail all over the place. I did use Burf's v28 script to try to install updates in LDR, etc., but mostly had to revert to installing each update at a time, many of which are still failing then. I just did that so I won't constantly get the 'failure to configure' error and it has to roll back everything, etc. Gawd, what an awful experience! I had some problems months ago when using Win8 and making the sysprep'd install, but nothing like this. What could be causing all these update errors? No programs are installed, no AV's, just the plain Win8 Pro x64 image. Last night I downloaded the Win8 x64 updates through Alphawaves' tool, so the updates are recent. And they are all Main update, not Additional ones. I have never had problems like this with Win7.
Hmm...had no problems yesterday. Installed .Net and then did a first Update run, were about 750 MB to install, after Reboot did the second run with about 350 MB to install. Not a single one refused to install on Win 8 Pro WMC (installed from self-made Pro-WMC-ISO).
When you say 'update run' do you mean you used WU? I used the .msu updates from the McRip/PointZero repo.
I think my problems had something to do with installing straight from the .esd based iso. Now that I'm using a previously sysprep'd image (based on that original .esd image, but converted to have an install.wim) all updates are applying without a problem so far. Weird... Honestly I can't remember what I had to do to get that esd image converted back late last year. I know how to do the sysprep process, but perhaps I can't apply updates in the Administrator mode on the install from esd and it has to be converted to install.wim image first? Wish I had kept some notes back then because I forgot everything EDIT: Yes, no problems at all with this VM install. All updates applied without failing using Burf's script. Win8 images sure get big fast when updating images, much more so than Win7 in my experience. I never had a Win7 image bigger than little more then 4gb for x64, but with Win8 I get over 5gb either using offline integration or sysprep method of installing updates followed by a capture.
I use sysprep when I have to install something you can't install offline, such as Office. It's really a lot faster, but harder to work with a sysprepped image. I personally never experience problems working with sysprep captures, but some of the ppl that download my stuff have complained that they cannot use stuff like rt7lite to go back and remove features or something... That's referring to win7. There's not really anything preventing me from doing sysprep captures for win8 without office, but since there's not really much of a speed increase, there's almost no incentive for me to do it. If I wanted to sysprep a bunch of custom drivers and programs, it would be perfect. You could, say, Install WinRaR, Office2013, KMS server service, DamnNFO viewer, hashtab, AMD Display drivers, etc. Then when you are happy with it, just don't generalize when you shut down. For sysprep on win8 I do an extra cleanupcomponents pass since it's available and I delete the windows update download folder, but there isn't really much junk beyond that. Obviously there is some dism log stuff, windows update log stuff, etc. I kind-of am reluctant to delete those. They don't seem to be harmful in any way, and for the really nerdy people, they can see if a certain KB file was installed, or if there were errors. Ahh.. you got me going off on a tangent... Easy to do I'm afraid, since it's my hobby... feel free to PM me if yer looking for pointers or wondering why I do things a certain way.