I have the same problem. Downloaded the November 8th x86 zipped file and integrated its updates in a windows 7 ISO.
this type of errors usually happen when wim doesnt write correctly and things like that... try to integrate once more and try it in VM first before burning it to DVD...
I haven't got any error with a fresh build today (latest SP0 from 8 november, with LDR files also). However, KB2556532 seems to be the most stuborn update in Microsoft history - it really doesn't care it was superseded It was the only update ''missing''
Ah, OK, I have never integrated KB2506143 into an image so I cannot confirm the problems with this. Unless you really need it, why integrate? This is of course for personal use, but I only integrate the main update folder and the updates inside the LDR folder, besides that nothing (well, IE9 and its updates are the exception). @RicaNeaga: you are using Win7 SP0??? KB2603229: At first I put this in my integration update folder as it didn't give an error according to SoLoR during integration, but then I decided to not integrate it but made a dual-arch silent installer out of the updates (x86 and x64) that runs right at first desktop upon fresh install.
Sorry, I got confused as I updated the silent installer for the KB2533552 (which is for both archs) at the same time, using your little SilentSwitchMaker package this time around. But yes, 2603229 is x64 only
Nobody knows which of the updates improves update installation performance? Reason for my thoughts on this is installing say, 10 updates on a fresh installation can take some time, but installation 10 updates (that haven't been installed before) on an otherwise updated system installs considerably quicker. When installing 240+ updates on a fresh installation it still takes some time even with the fast script, due to DISM being a bit slow. Finding this update (or updates, but I presume its just one) I could set the script up so it installs it first if present, like the servicing stack update (which I originally thought was a contributor) first, which means after reboot the reset of the process can proceed quite quickly. These changes won't affect adding integration seeing its a subset. A subset can also be added just for integration for updates that don't like integration If nobody knows of this update its ok, just a though I had a look myself, I believe its an update from earlier on... (however, this may have been replaced by a more recent update)... Also, has anyone tried integrating all the updates to the boot.wim file? of course many of the updates aren't applicable, but it can be done. It may or may not provide improvements to the installation speed?...
A bunch of new updates are out. Sorry, I still can't post direct links. Usbaudio.sys: hxxp://support.microsoft.com/kb/2619331 Gpapi.dll & Gpsvc.dll: hxxp://support.microsoft.com/kb/2581608 Rdbss.sys: hxxp://support.microsoft.com/kb/2622136 Windowscodecs.dll: hxxp://support.microsoft.com/kb/2619291 Spoolsv.exe: hxxp://support.microsoft.com/kb/2532459 Ndisuio.sys: hxxp://support.microsoft.com/kb/976373 Raspptp.sys (64-bit): hxxp://support.microsoft.com/kb/2625737 System.management.automation.dll: hxxp://support.microsoft.com/kb/2552055 Xpsgdiconverter.dll: hxxp://support.microsoft.com/kb/2584449 Certenroll.dll: hxxp://support.microsoft.com/kb/2625430 Microsoft.activedirectory.management.dll (server only?): hxxp://support.microsoft.com/kb/2577917 Dns.exe (server only): hxxp://support.microsoft.com/kb/2586946 Ntdsai.dll (server only): hxxp://support.microsoft.com/kb/2616886
Sometimes you may need to try twice or more on the same link before it works. This seems to be the case sometimes with these request links. I believe it may error due to there being spaces in the links (spaces are actually filled with '%20'), and the servers handling of them? this is just a guess, but in general its not good practice to create weblinks with spaces, and instead create them with, for example, '_'.