Hi all,

So each month I update our Office 2010 package with the latest updates from Microsoft Update. I do this according to Microsoft's supported method of putting the MSP files into the Updates folder within the Office 2010 package.

This month, out of the blue, these latest MSP update cause the PC to restart after installing Office 2010, which makes the overall build fail because my answer file is not designed to have a restart there.

I rolled back to last months Office package and the build once again completes successfully, so it's confirmed to be the cause.

My question is for anyone who knows a bit more about these MSP updates that go into Office packages. Why would suddenly after doing so many before, would they now cause the PC to restart? And how can I identify the culprit update?


Answer Summary:
2 Comments   [ + ] Show Comments


  • Why is it interfering with your answer file? If you set "autologon" to infinite by not specifying a reboot count, you shouldn't have a problem. Otherwise you will have to check each .msp and see which one requires a reboot.
  • Hi nlieschke,

    Thanks for responding but in the meantime it's no longer happening. I duplicated my post-install task in KACE and replaced the Office file there with the new one and it doesn't reboot.

    So yeah, thanks for replying but all good.
Please log in to comment



Duplicated the post-install task and replaced the office file there and the PC no longer restarts during deployment.

Answered 05/28/2014 by: twit
Fourth Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity