Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Multiple computers reboot after patching one computer

Multiple computers reboot after patching one computer

Updated November 30, 2017


When you run the Update Management Wizard to apply a patch to a single computer, all managed computers are rebooted in the management group.


  1. Log in to the Patch Manager Administrator Console.
  2. Locate and select a computer to update.
  3. In the Actions pane, click Update Management Wizard. 
  4. Select Download and install all needed approved updates, and click Next.
  5. Delete all default rules, select Load Template to load an existing template, and click Next.
    The Task Options Wizard screen displays, allowing you to select computers for your patches. 
    if a different Task Options Wizard screen displays (as shown below), the rule template may have been modified. 


  • All Patch Manager versions
  • Microsoft® Windows Server® 2012


The rule template used in the Update Management Wizard was modified. 


Verify that you are using the correct rule template. If the template is correct, do one of the following: 

  • Use the Update Management task instead of the Update Management Wizard.
  • Replace the current rule template with a new template. Use this template for all subsequent procedures. 


Last modified