Cumulative Update requires a restart after SP1 install - by AaronBertrand

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 774111 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/12/2012 4:51:32 AM
Access Restriction Public


I have complained in the past about SP1 setup showing confusing things about services and applications that might cause a restart to be required:

And other users have complained about this reboot in general:

It seems that both of these problems have been "fixed" by hiding the services and applications that are found in the "Check Files In Use" step of SP1 setup. Does this really fix the problem?

After installing SP1, I went to install SP1 CU1 (since I still have to do this in two steps if the instance already exists), and the Rule "Restart computer" failed. So, it seems that after SP1 is installed, even though "Check Files In Use" indicated that no reboot-causing files were actually in use, I still have to restart the computer before installing CU1.

It isn't quite clear during SP1 setup if or why a reboot will be required after installing SP1; in this case, the engine seems to be patched correctly. But I found this in Detail.txt for SP1:

(07) 2012-12-12 06:46:38 Slp: Rule 'RebootRequiredCheck' results: IsRebootNotRequired=True

And then for CU1, run only a few minutes after SP1 was complete, I see:

(07) 2012-12-12 06:53:38 Slp: Windows Update requires a reboot
(07) 2012-12-12 06:53:38 Slp: Rule 'RebootRequiredCheck' results: IsRebootNotRequired=False

So something happened during the SP1 install that set a flag with Windows Update that a restart would be required before performing any more installations.

In addition I've blogged about these issues:
Sign in to post a comment.
Posted by Microsoft on 1/11/2013 at 10:36 AM
For the specific reboot issue that Aaron has reported, I have worked with Aaron and found out that it was Microsoft Update which downloaded and installed various updates and set the pending reboot flag in Aaron's machine. About at the same time that Windows Update was running, Aaron was installing SQL Server 2012 SP1 and CU1 patches. That was the reason CU1 captured the reboot required flag and reported in the rule check.

For customers who are installing new instance of SQL, you can use Product Update feature of /UpdateSource and point the install to the single installation folder of SP1 and CU1. For customers who are on existing SQL instance, I see that this feature was being considered for the next major release based on feedback in this connect request
Posted by Nancy Hidy Wilson1 on 12/12/2012 at 1:55 PM
Totally agree that we need the ability to slipstream a new SP/CU combination onto an existing instance. This is where it would be of most value as SLAs are impacted by having to do 2 installs with potentially 2 reboots when patching.