none
Continuous "Restart Required" Prompt after Windows Updates applied RRS feed

  • Question

  • Before I begin my rant, I'll point out that I've read as many relevant blogs as I can find, but nothing really seems to fix the continuous restart (Green square with starburst) prompt on my machines. I've tried the script that deletes the %windir%\SoftwareDisribution store etc. I've kicked off Update Scan Cycle and Update Evaluation Cycles on clients to see if they would "report" that everything is installed and maybe the icon would go away.

    Here is what I see - the clients want a reboot to "complete" installation, but it already shows up as installed updates. No matter how many times we reboot, it appears again.

    I feel like we didn't have this issue when we used to utilize the option to install/restart outside of maintenance window when deadline is reached, but we were in our early stages of use and I could be wrong because we weren't using that method for long (angry users :\)

    The setup now is:

    -Maintenance Window daily from 8pm-6am

    -Deployment is required; User notifications=Display in Software Center and show all notifications (changing to "only show restart notifications does not seem to make a difference) -- we choose to display so that users have the option of seeing and installing updates earlier than the deadline

    -Deadline is usually 9pm or 10pm and nothing is allowed to update/reboote outside of the MW in Deadline Behavior

    -Reboots are NOT suppressed on client machines (and they do reboot overnight to complete installation)

     

    If anyone has anything else to offer, I would forever be grateful! If more info is needed please let me know.

    Thursday, August 7, 2014 4:26 PM

Answers

  • Microsoft has designated this a bug that they have seen in very few places. So far, a process consisting of running ccmclean and reinstalling the client seems to resolve the issue, but doing so on thousands of computers isn't really my first option for a resolution, so I am awaiting a response still.

    Thanks again everyone for the support.

    Monday, August 25, 2014 1:43 PM

All replies

  • Is this happening on all systems for all updates?

    Jason | http://blog.configmgrftw.com

    Thursday, August 7, 2014 5:42 PM
  • Hi Jason, 

    Thanks for your response. Yes, as far as I know it seems to be on all workstations right now. Curious though, that mine does not. I am sort of anal about installing updates so I do them right away. We had a deadline expire last night, so today everyone is seeing those notifications. (Perhaps it's punishment for waiting until the deadline!?)

    *Rarely* I will be able to manually run those 2 Software Update Scan Cycles and have it disappear later, after a reboot. The other 99% of machines, this has no effect. 

    While on the subject, I would assume a similar (if not the same) scan takes place AFTER updates are installed in order to notify the server that they are no longer needed, but it sure seems that isn't the case if we are having to manually run scans to make this go away. Is that not the case? Granted, if that's how it works, these icons/prompts *may* go away every few days when the software updates evaluation cycle runs again, but the helpdesk gets calls about "those annoying prompts" which then make their way to me.

    Thursday, August 7, 2014 6:17 PM
  • Does this still happens after system updates?
    Thursday, August 7, 2014 6:28 PM
  • If I'm understanding your question correctly - Yes - the initial deployment installs updates and reboots to apply. The updates show up in Programs & Features > Installed Updates as installed, but the ConfigMgr Software Center still wants to reboot. 
    Thursday, August 7, 2014 6:32 PM
  • Update for this morning-

    My test machine, along with a few others that I've seen (potentially many more) now have nothing listed in the Software Center under the Installation Status tab, but still have the notification icon. Machines also restarted again last night, presumably to "complete" the installation that had already been done.

    Edit: Another update - it looks like it might be the same few updates giving each machine problems, and those updates have been in the Windows image for some time now (1 update in particular was installed 12/15/2013 according to Installed Updates applet)

    I may try removing those few updates from the Software Update Group and waiting to see if the prompts go away...but I'm concerned that this could happen down the road again for any other update - seems like client scans aren't reporting updates as installed, and therefore will reboot indefinitely until the advertisement is deleted.

    • Edited by Paul_131 Friday, August 8, 2014 1:30 PM More info
    Friday, August 8, 2014 1:19 PM
  • Have you reviewed the logs? Specifically rebootcoordinator.log on the client?

    Jason | http://blog.configmgrftw.com

    Friday, August 8, 2014 3:02 PM
  • Yes, and it basically looks like it would during a normal deployment - maintenance window opens, it detects the "pending restart" and restarts. The particular log I'm looking at rebooted twice last night, once at 9:50pm and again at 4:25am. The MW for this collection is 8pm-6am, so it is within the allowable window, it just wasn't supposed to install anything since they are already installed.

    Also in the log, when the computer comes back up I still see:

    Entered ScheduleRebootImpl - requested from 'UpdatesDeploymentAgent'. set Rebootby = 0. set NotifyUI = True. set PreferredRebootWindowType = 4 RebootCoordinator 8/8/2014 8:21:25 AM 884 (0x0374)

    Scheduled non mandatory reboot from agent UpdatesDeploymentAgent RebootCoordinator 8/8/2014 8:21:25 AM 884 (0x0374)

    User S-1-5-21-1130838179-498391445-2376766145-1446 is getting pending reboot information... RebootCoordinator 8/8/2014 8:21:48 AM 5444 (0x1544)

    CRebootCoordinator::GetPendingRebootInfo, Get NotifyUI = True RebootCoordinator 8/8/2014 8:21:48 AM 5444 (0x1544)

    CRebootRequest::GetPendingRebootInfo, Get NotifyUI = True RebootCoordinator 8/8/2014 8:21:48 AM 5444 (0x1544)

    User S-1-5-21-1130838179-498391445-2376766145-1446 is getting pending reboot information... RebootCoordinator 8/8/2014 8:21:48 AM 5444 (0x1544)

    and this repeats util they restart, then starts all over again once they log in.

     
    Friday, August 8, 2014 3:13 PM
  • I wanted to update since today is Patch Tuesday-

    I deployed some updates to a small group of computers; they will apply tonight and suppress restarts. I applied them to mine early (3-4 of them required a restart) and performed a restart. Without running any "fixes" such as clearing folders or kicking off any scans, the restart prompt did disappear, but only after 3 restarts.

    Now, I thought that CM "shared" reboots? That is, if 5 updates require a restart, it will wait until the final update is installed and restart ONE time. Is this not the case? The only other thing I can think of would be Update X depends on Update Y to be installed, and Y requires a reboot. After that reboot, X installs but it ALSO needed a reboot. They all install at the same time according to the software center, but what's with the multiple reboots needed to clear the notification?

    Tuesday, August 12, 2014 10:11 PM
  • Another update-

    I made a deployment to a test collection that suppressed all notifications in an attempt to just make it invisible to the user that this bug is occurring. The updates installed at the deadline and prompted for a reboot with a 90min countdown which is normal. I performed the restart and now the Software Center is empty on the test machine, but the notification for a reboot still persists. I ran a compliance report against that collection/software update group and it says it is 100% compliant - yet the reboot prompt remains.

    Looks like I may be opening a ticket with Microsoft since this issue seems to have no resolution.

    Wednesday, August 13, 2014 2:35 PM
  • I would definitely do that, as this is not something I've ever experienced, and obviously no one else has, or they'd have responded with help for you by now.

    Wally Mead

    Wednesday, August 13, 2014 3:55 PM
  • Thanks Wally (and everyone else that has replied.) I've opened a ticket with Microsoft support. Unless this thread gets closed I'll update with any results I have.
    Friday, August 15, 2014 7:21 PM
  • Microsoft has designated this a bug that they have seen in very few places. So far, a process consisting of running ccmclean and reinstalling the client seems to resolve the issue, but doing so on thousands of computers isn't really my first option for a resolution, so I am awaiting a response still.

    Thanks again everyone for the support.

    Monday, August 25, 2014 1:43 PM
  • Well, if it is a bug, they might request a hotfix (you can ask them to). However the team has to decide if it is a risky fix to make, whether or not it is worthwhile to make, how many others are experiencing the same problem, etc. If there is a workaround, even if it involves reinstalling each client, they may decide not to create a hotfix.

    Wally Mead

    Monday, August 25, 2014 9:42 PM
  • Paul I know its been a long time since you reported this issue here. Did Microsoft ever come up with a fix for this issue?
    Wednesday, April 6, 2016 7:58 AM
  • Hi Laurence, After working with the sccm team, the Windows update team, and then an escalated sccm engineer, we were all unable to determine the exact cause. In the end, ccmclean temporarily fixes the issue until the next round of updates.
    Wednesday, April 6, 2016 12:31 PM
  • My problem is a continuous request for restart for update.  After I comply the PC restarts and goes thru the routine of restarting and updating and eventually it comes back with the very same request to restart only other option is to set a day and time for automatic  restart, this also ends up with the request to do it all over again.
    Monday, September 9, 2019 5:09 PM