I will add KB2853772 install support in the updated installer (not ready yet). Not only does it make no sense that if you install the update directly, or via the cab, that it isn't really installed, but the fact that there are both GDR and LDR manifest versions of the update, even though they serve no function! Even if it is to say that it is installed, only one branch is required.
Burf: Yes, it's weird that MS would include an LDR branch for an update like KB2853772 (which doesn't need it), but not include an LDR branch for one that really does need it, like KB2800033. ------------- Asim Omer: I have the list but will need to post it later when I have more time.
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.