Before we sysprep and collect an image we make sure that all updates are installed on the pc used for collection, this includes office updates as well. Upon finishing the deployment of the image 36 updates are required to be installed most of these are for office. At first we thought it may have been sysprep getting rid of these updates but ruled that out when we started up the computer we collected from after sysprep and it had all the updates still installed. Anyone have any idea as to why these updates are not being collected with the rest of the image. This happens with both a kimage and a wim-image.
3 Comments   [ - ] Hide Comments


  • Is Office a post install task, or included in your image?
    • we included it in the image and installed the updates for it before collecting the image
  • we included it in the image and installed the updates for it before collecting the image
  • are you using wsus?
    • We are not currently, we have a test instance of WSUS that we are planning on using in the near future, and we know that we wont be able to get all updates with a image because of the speed at which Microsoft releases updates, however all current updates should be on the collected image, at least the ones that were on the pc we collected from but on deployment they are not
      • They should be. I have run inot this once

        That is why I asked about wsus, if you are pointed at it when you sysprep. when it comes out of sysprep it goes to MS. And it will find updates not approved by wsus and get them. (Not your problem)

        What is the update that is trying to install?

        Did you hide any updates on the master?
    • We did not hide any updates on the master, the 36 updates that it claims it needs are for office 2013. there is one for silverlight and a couple windows security updates, I will need to apply another image to get the exact ones for you.
      • no need, just wondered if it was .net or VS type of updates, those are main stream updates you mentioned

        Prior to syspreping, when you go to control panel - windows update, does it say check online for "windows update" or "microsoft updates". needs to be Microsoft updates.
    • it was set to "Microsoft Update"
      • sounds like you have everything correct. Only thought is to try to clear the updates on the master so it looks at all of them again.

        On the master:
        Go to C:\Windows\SoftwareDistribution\Download and delete every file and folder in there. Then go to C:\Windows\SoftwareDistribution\DataStore and delete the datastore.edb file. If you have any trouble deleting the files, stop B.I.T.S. and windows update services.

        Reboot and check for updates again.
    • I will try this and get back with you thank you
Please log in to comment

Answer this question or Comment on this question for clarity



It is not documented, but Sysprep does clear the Windows Update history.  So the next question is why do only some updates get re-installed while others do not?  The answer is it depends (got to love it).

Windows updates check for updates in several ways.  One is through checking files directly and another is through installed programs that you can see under Add Removed programs and another is via the Windows Update History.  The 36 patches that you see may be checking if they were installed only by checking the success/fail from the Windows Update history and now that it is gone the patches redeploy.

Now the next question is how do I get an image that has every patch available up to this second?  I do not have an answer, just advice - Don't kill yourself trying because it probably is not going to happen.


Answered 07/15/2014 by: JordanNolan
Fifth Degree Black Belt

  • if this was the case wouldn't the original pc, the one we captured the image from and performed sysprep on, be missing the 36 updates as well after we turn the pc back on? Because even after we sysprep that pc still has all the updates.
Please log in to comment
You could of course try capturing the installation of updates so that you can determine where the update history is held. Then take a backup of it, sysprep, and have a first run setting that puts the update history back. Have never tried this but there should be some way of cranking this. Alternatively, don't bother installing all the updates - just let it happen post deployment.
Answered 07/16/2014 by: EdT
Red Belt

Please log in to comment