no LOL ofc not... did you at any point saw few hundred hotfixes on WU ? They are from WU + support database + zukobonuses
Bunch of Office Hotfixes released today btw... "upgrades" most of office components on both platforms to build 14.0.5128.5000
Hmm... the last two builds & installs with latest updates integrated had some weird things: - I had a Windows.old folder on C:\ -- but I did not install over an existing Windows, only on formatted drive. - the latest out of the two installs, only 195 out of 361 updates were showing up under Programs & Features. Previously all updates would show up there. - but strangely enough, the build number is at 7600.20787... which is right and it only recently got up to that number as it had been at a lower number for a long time (20727?) So the win version number seems correct, but only a little over half of the integrated updates are showing under Programs & Features, were normally they all show up. Plus I've been having that Windows.old folder show up around this time as well. Any thoughts any one? Could it be any of the latest updates that could cause this? Thanks...
Well, firstly the Windows build number should be 20796 with the latest updates. Secondly, the build number doesn't reflect a combination of all updates, only the kernel updates. In fact, you could have build number 20796 with only one update installed, but it certainly won't be more up to date than a system with all new update except for the one which made it 20796 The reason why the build number is older is there must be an older update which updates the kernel to that number. That old update may cover more than just the kernel, or is required so the proper LDR version is installed later, so thats why it exists in the repository (assuming are up to date with the updates in the repository and have remove the old updates from your list). On a side note, remember there are a few updates in the additions folder which may be useful, such as kb917607 etc. The advantages of integrating updates is a little iffy. The main reason would be that post installation updating will be quicker since they are integrated, so you can get the system up and running much quicker than you would otherwise. Aside from that, there is no real benefit, there shouldn't even be a disk space utilised difference. If you integrate one update, and run that one update after Windows is installed, what is does to the add/remove programmes, winsxs folder etc should be the same. The disadvantage of not intergrating is post install updating. Basically, you can't install 350+ updates all at once and expect things to be speedy and possibly even work correctly! Its just too much for the system to handle. It may be the same reason with the integration, you're doing too much in one go!... Thats the main reason why I made the update installer listed earlier. If you break the updates in groups of around 50, then restart after each group, it will be faster than attempting them all at once, and the risk of an update error (which it looks like you've struck) is significantly reduced. In terms of updates that become superseded, the update uninstaller I made will remove them (although the update uninstaller relies on keeping the list.txt up to date, which it currently is.
Thanks for the reply, burfadel. A couple of things: - I generally don't include updates from the Additions folder, except recently the 958488 (which is now confirmed to let me install custom NET4 packs, btw). So which ones would you recommend besides KB917607? This may also explain my lower build number? - I've been pretty religious about keeping up with the updates, but I did not download the latest pack as I've been adding/deleting from the previous pack on. I'm sure I have not missed an update... - As for integration not being successful due to the large amounts of updates, personally I don't believe in that. The reason is, I've been making so many builds, and every time I checked it would show me, "359 updates installed", etc., so unless MS put the update limit at 360 (I had 361) -- which would be a very round number, wouldn't it -- I don't see a reason for that Now, if somehow an new update was breaking the sequence... that would be a different story, of course. - Just to be sure I'll try out your update uninstaller and see if my list is not up to date then I suspected this after I had that build number but only 195 of the updates were showing to be installed... Anyway, I'm gonna try another build using slightly different tools and hopefully I can confirm what's going on that way. Thanks!
Right now you get different build number on 32bit or 64bit Windows... this is because latest kernel update was avilable for Server R2 only and that is only 64bit but ofc it works on normal Win7 64bit as well. About additions i would say at least WAT and Ballout if you are in EU Im intergrating Ballout with to install DVD and then have registry script with Code: [HKEY_LOCAL_MACHINE\Software\BrowserChoice] "Enable"=dword:00000000 so it doesnt pop up im also integrating winhlp, update agent and IE9 beta.
Well, I guess its personal preference what you want to install from 'additions' the Windows update agent, kb982010, windows help 32-bit kb917607 (compatibility help for older programmes), kb943790 Windows File Management API (no doubt included with Sp1), #KB947821-v7 system update readiness tool, kb969168 Microsoft Agent (probably little use but doesn't harm installing it). #The tool is a checking tool, not an update even if it appears that way. Run after install, it fixes errors that occur due to problems with update tracking (probably an oversimplifcation). I notice when rebooting after installing kb976902 that under the windows logo it was update registry info, around 52,000 or so entry, at least that what it said... maybe it should be integrated last. Not sure if it affects already installed installations.
I noticed that too... Well, for my purposes I'm gonna kick that update out because if it can downdate my installation/build that bad I don't want anything to do with it. But yes, the only way to use is successfully (if possible) may be to install it post-install or otherwise put a "z" in front of it and have it integrate last (but I'm not trying it!). I figured MS would throw a trick/spook in there around Halloween time
I too had problems with KB976902, I wonder if it will hurt to integrate it last anyone give it a try yet?
Hi there Thank you very much for these updates. Sorry to be a pain, but is there any chance of a torrent download? The proxy server I have to use is an unforgiving bit**... Thank you all!