huh? do you mean they didn't installed, or did install?... KB947821 is a tool, not an update, and can be run as many times as the user wants (not that there would be any need). The others should have installed fine. The behaviour of updates seems to have changed, if you install an LDR version, and then try and run an update again (which used to install the GDR version), it no longer does this (comes up already installed/not applicable), at least that is what I have found. Not sure what updates have done this, although I suspect its possibly one of those relating in some way to Windows 8 (KB2506143 (build 195), KB999158, KB999159). If so, it shows a possible change in the way Windows 8 updates work. Its not a bad change ... Please explain the issues you are having with the above updates and I'll let you know if there is an issue
I've seen that also. My guess would be kb2663352, since it's an installer engine update and was just added a couple weeks ago. ---------------- "the devil pulled me poke pens" -that would make a good title for a song
I have not done any offline integration of the new updates/hotfixes yet, but I did manually install all updates one by one in VirtualBox vm (Win7 x64) and found the following update failed until I had done a reboot: KB2646060-v3-x64. After the reboot, I was able to install it just fine. I don't think that particular one will give any problems during offline integration, though. Reason I installed all new updates one by one was to figure out which updates were applicable to my latest lite build of Win7 x64 using vLite. vLite actually works really well (much better and much faster than RT7Lite), but you cannot use it with Win7 SP1 as integrated by MS. Having messed with this quite a bit lately I'd say that MS did not do a very good job with their Win7 SP1 integrated iso release. If you capture a vm Win7 SP0 install on which you've installed SP1 and perform a generalized sysprep and subsequent SP cleanup via DISM, you end up with a Win7 SP1 iso that is 100mb smaller than MS' release -- and one that you can use with vLite. Not only that, the MS versions contains hundreds (yes, hundreds) more registry errors than the result you can achieve making your own image. Further, if you transplant the install.wim into an extracted SP1 original iso and rebuild it, you can actually have SP1 integrated install.wim that will work with vLite but at the same time have all the newer auxilliary files on the iso (such as setup.exe, etc.), making it as close to SP1 integrated iso as can be. The slimming results of vLite are quite a bit better than RT7Lite. I made a Win7 SP1 x64 vLited build from which I removed Accessibility, Speech, Natural Languages, Tablet PC and some other, more minor things (compatibility and full Win7 experience above all!!), and ended up with a Win7 Sp1 x64 iso 1gb smaller (2.07gb) than the rtm version of the same (which is 3.09gb), without any limitations to my personal computing needs. (RT7Lite using MS Win7 SP1 iso: 2.47 with same removal scheme.) I can install Office 2010 and IE9 works completely (as was not the case with some people trying vLite on Win7 SP1). Anyway, a buddy of mine had been messing with Win SP1 vLite builds and got it down to a science, and after he recently showed me how to do this it got pretty exciting to mess with as most people had given up on vLite altogether as an option to customize Win7 SP1. Anyway, so basically all the updates so far are integratable, except the PowerShell update, correct? (KB999158 and KB999159 are fine?)
I think the best advice with my installer is to run option 2 (or 1, or 3 etc...), reboot, and run again with option 2 (to cover updates possibly missed)... the missed updates seems to be a result of Windows, and not the installer. For other installers the same applies, in that you install, reboot, and re-run the install, although it may take a bit (maybe a significant bit!) longer. It does go to prove on thing though... bring on SP2 (which quite possibly won't be until after Windows 8 is released).
Someone recently showed me a chart stating support for Win7 until 2020, which I thought was good so that all desktop users can let Vista SP4... ahem... I mean Windows 8 and it stupid interface... blow over like it never happened.
I have seen that also, I believe its because of Server 2008 R2... however I also believe that it may be just security and other critical support options, and not hotfixes like we currently have. There may be the occasional hotfix, but the target will definitely be Windows 8 after the initial support for Windows 7 is done (2014? probably start slowing down after Windows 8 is released and through 2013).
I'm able to integrate all except those flagged in the repo' as Not integratable to Offline image and KB2506143 Windows Management Framework 3.0 CTP-absolutely everythimg else integrates without issue to a sysprepped image where I install KB2652029, KB2603229 and KB2533552 during sysprep and capture the result as my base image. For me anyways, KB2506143 is trouble....causes some wierd anomolies; like resource exhaustion errors I do not experience without it installed. Trust me on this, my PC does not run out of anything-it's a power house beast. On another note, I have never liked the idea of RT7Lite and after nhui quit supporting nlite/vlite then so would my use of them. One can do most of what they do right in the answer file/config file or using DISM/imagex which are the only tools I am comfortable with anymore....no incompatabilities, unexpected errors due to inappropriate component removal etc.; everything seems to go just a whole lot smoother. The automated tools M$ has provided for multiple/mass deployment are really quite good...just my 2 cents.
Yes, you are probably right about the hotfixes situation. Then again, with just about every software company on rapid-release schedule we are probably on Windows 12 by the time it's 2020 Yeah, when I upgraded a little while ago from my old e8500 8gb ddr2 800 system running RAID0 with HDD's, to a 2500k at 4.5ghz, DDR3 2133mhz Z68 system with a Sata3 SSD, things just started going a lot smoother for me I agree with you about MS' deployment tools and have personally not gotten into the creation of answer files yet (but this did peak my interest) but this would be the next step, and the more apt one at that. I do find that a lot of the examples I was able to find online toward usage of the deployment tools centered around what IT pros would do with these (quite naturally ) and I therefore found it a bit hard to find examples of the specific uses I was looking for. But I'm sure over time I can get a grasp on this stuff a bit better. What I have found in the vLite vs RT7Lite situation is that vLite, although never released as a Windows 7 tool, actually does a better job than RT7Lite does, which was released (albeit in beta form only) for Win 7.
I think it is tripping up on the cause of this (this if from your log): Code: 2012-03-04 01:25:18, Info DISM DISM Package Manager: PID=2880 DISM has detected a DISM component change. Requesting a shutdown. - CDISMPackageManager::Internal_Finalize 2012-03-04 01:25:18, Info DISM DISM Image Session: PID=2880 The image session needs to be closed and re-opened before any servicing operations can be performed. - CDISMImageSession::put_ImageState So whatever caused that is the cause of this issue, or another issue...! Did you install KB2533552 like the installer asks (or should ask!), and reboot before using the option 3?...
KB2652029, KB2603229 and KB2533552 were installed during sysprep and the captured image shows them installed; this captured image is my default base image. One annoyance; whenever I create a new sysprepped image, I have to capture the first one and then reinstall to VM and sysprep again with no changes other than to recapture a second time before I am able to integrate updates. Otherwise, half the updates will not slipstream because a pending service is not completed. That all is good after the second capture though and I have been using this default image for quite a while now-problem free other than I can't get option 3 to work in your script. I'll see if Google can help with those lines. But, really, I have no idea; DISM runs fine otherwise and I can do with it anything I want that it supports without issue. Go figure....... That cmd is run before anything else is done to the fresh install. It's also wierd that it starts with KB2276594 and not KB949843-v2-which is 11 hotfixes it skips over.
me too they have been integrated, and they are in the list of updates (after installation) the files of 999158 have been updated, for KB999159, I don't know where are the files
And here's another. Correct, if it is not, but the Old Update Remover removes KB2647841 without the bit of update, although only supersedes x64.
Fixed locally. I'll upload after SoLoR's Sunday scan is uploaded, assuming he still does a weekly scan like clockwork on Sunday
I just did an offline image update w/ KB999158 and KB999159 & there were no problems. Shon3 was right, you could not integrate kb2506143 whether it's the old version or the latest one to offline image.