This months cumulative update still updates the latest installer to the LDR branch if you force install the LDR branch, or have an update that initiates the branch change, but it won't show in WU if the GDR branch (the new IE9 installer) is installed and no preceding updates are installed.
Im not sure if I understand what u just said. So I integrated the new IE9 installer along with other updates in LDR/QFE mode to offline image, but when I install win, WU shows IE9 for installation. That wasnt happening with the previous IE9 installer. What should I do ?
IE 9 is installed properly. Just hide the entry from WU on Windows 7. Microsoft will never make it to handle this shi* properly.
Its possibly a service store (on your computer) misconfiguration... something that KB947821 deals with. KB947821 probably needs a new version to be of any use in this case though. I should point out the IE9 needs to be installed before the cumulative update patch, but the cumulative update patch may be tried to integrate first if the program you are using to do it tries to do it by alphabetical order, since the cumulative updates start with IE9. Also note the correct name for the IE installer is Windows6.1-KB982861-x86.msu (or Windows 6.1-KB982861-x64.msu). Realistically they should just release it as such (Windows 6.1-KB982861-x64.msu) but with a version number like other updates... Are you sure IE9 is properly installed, and that you installed the x64 version on x64, x86 on x86 etc? the download for the new installer won't say in the filename if its x86 and x64.
@ burf I have just tested this scenario on my machines with the same results. All is installed properly. All files are installed properly. You have just to hide it from WU. That's it.
I use WinKit, thus IE9 is integrated first, because it counts as prequisity. All other updates integrate after this. You dont integrate/install cumulative patch when u use fresh IE9 installer, because it already contains latest cumulative patch, just like the pevious one already contained previous cumulative update. So if I use the new IE9 installer, cumulative update is no use. Yes correct name is 982861, but I integrated several times the previous installer with the name of IE9-win7.msu, and it was working fine, never shown in WU. Anyway, I integrated x64 version of course, x64 versions are the bigger ones, because they contain both x86 and x64. It works fine, it just shows in WU... Never happened with previous IE9 installer which is still in SoLoR´s repo.
well I integrate with LDR/QFE mode but IE9 always gets integrated as GDR, according to "integrated" window in WinKit edit: nevermind
Thanks, I also use firstlogon cmd and some other methods. What I did with the sysprepped image is install KB2533552 and KB2603229 (it's a x64 image) and turned off UAC and set Power Options and some other minor things (used VirtualBox, made VM as VHD from the get-go so easy for capture). But like you I ran into the pending updates problem. But, seems like an easy enough fix, just install this image in vm again and sysprep it, I'm going to try this and report back.
McRip, can you please update your 7z files in your's homeserver? SoLoR didn't update yet. Thanks for your work!
I have also sysprepped my image with KB2533552 and KB2603229 and I also need to capture twice or I will run into pending updates problem. Also my recent tests lead me to believe that KB2603229 should be installed via setupcomplete.cmd after oobe otherwise the registry entries mentioned in the knowledge base article does not get updated as it should.
The runtimes are updated and 7-zipped; the uncompressed update repo-both x86/x64-are uptodate as of April 10 with all from M$ update in addition to those extra's posted here. McRip's server is basically a mirror of SoLoR's to alleviate bandwidth use-spread it out if you will. The x86/x64 updates will be 7z when SoLoR does his. There is just not enough volume since the last 7z to warrant the time to upload a new 7z for each architecture. Added to this is the fact we are just hitting the "boat load" of unofficial updates/hotfixes this month. When they are checked/sorted/included will be the time for a new 7z.
In the new bunch, KB2642947 is old, and is already part of the repository. It is superseded by KB2642947-V3 also in the pack. KB2665347 and KB2673007 are Server updates? might be why they are x64 only. In any case, they aren't applicable to me, and the files they replace aren't present.
I installed all the updates, and the two above (so had KB2680906-v2 installed as well as KB2646535-v4 that supersedes it, as I had already installed it). When it booted back into Windows and was completing the update, it got to 32 percent, spent maybe a minute doing something?, got up to 70 or so percent, Windows rebooted again, completed to 100 percent, and when the desktop was meant to show got a BSOD in tunnel.sys. When the computer rebooted, everything is fine now. The Windows Network Security, NetTCPip inf, Network Location Awareness, Kerberos (security), Netlogon, TCP-IP binaries, and MSMQ Queuemanager, all being network related, are updated in the latest bunch of updates, so is possibly related to the installation of one of these... if anyone else finds peculiarities with the installation post it, as one of the updates may have to be installed separately?
I have just installed all the updates and nothing of your description occured to my machine. Everything went fine.
I think it might have been just in my situation, just thought I'd better mention it just in case tunnel.sys is the IPV6 to IPV4 function (which some people disable), and I do share out media stuff to other computers in the household, so might have something to do with that... or it could be that I installed the update to daemon-tools at the same time as the updates (which probably wasn't the best thing to do!) In any case, done a full sfc check (no issues) etc, and there hasn't been any issues since, even after multiple restarts etc.