Set up patch management for a group
Approve patches globally, then configure per-policy rollout rules for a Windows group.
Set up patch management for a group
Patch management in NetLock RMM is configured in two places, and patching works only when both are set up. The /patch-management page is the global approval queue: which patches are allowed on any device at all. The Policy Settings editor's Patch Management tab is the per-policy rollout: when and how these particular devices install the approved patches. This guide covers both, using a Windows group as the worked example.

Before you start
- A policy already exists and is routed to the target Windows group via an automation (see Guide H.4).
- At least one Windows device is online in that group.
- Patches have been detected and sit in the Pending state on the Patch Management page. If the list is empty, agents have not yet reported their update inventory; wait a sync cycle.
- Required permissions:
patch_management_enabledfor the approval page, pluspolicies_enabledand the policy edit flag for the rollout configuration.
Steps
Stage 1 — Approve patches globally
- Open
Patch Managementfrom the navigation. TheUpdate Approvaltab is the default. - Filter by
Windowsand browse the Pending patches. - Select a manageable first set. Critical security updates from the previous month are a safe start. Avoid bulk-approving every pending patch on day one.
- Click
Approve. The selected patches move into the Approved state. The server flags every device for a resync so agents pick up the updated approval list on their next poll.
Use the other actions as needed:
Reject: explicitly block a patch; devices never install it.Defer: postpone a patch for a number of days (default 7).Reset to Pending: revert any state decision back to pending for later review.
Approvals are global and apply to all devices. Scoping to devices and groups happens in stage 2.
Stage 2 — Configure the per-policy rollout
- Open
Policiesfrom the navigation and clickManageon the policy that routes to your Windows group. - Open the
Patch Managementtab in the Policy Settings editor. The tab is split intoGlobaland per-platform sub-tabs; pickWindows. - Under the Windows sub-tab, fill in at least these three sub-tabs for a minimal rollout:
General: enable patching for Windows and select which sources participate (at minimumOS-Mandatory, optionallyWingetandChocolatey).Schedule: pick the allowed patch days (default Monday to Friday) and a maintenance window. Outside the window the agent will not start an install; the one exception is the catch-up run described in Chapter 6.12, which runs the first check after the policy arrives, or after a missed window, right away.Reboot: decide whether the agent may reboot, whether it prompts the user, how long the prompt is visible, and what happens on a device where nobody is signed in. This is the only place in the product where reboot behaviour is configured.
- Optionally fill in
Approval & Filtering(narrow approved patches by severity or source),Deployment Rings(stage the rollout acrossPilot → Early → Broad),Notifications, andRetry. - Save the policy.
Verify it worked
- On the Patch Management page's
Update Approvaltab, the patches you approved show theApprovedstate and theInstalledandPendingcolumns begin moving as devices pick up the change. - On a target device's detail view in
Devices, the lineLast patch run: <time> – <outcome>appears after the first scheduled run that reached the install stage, and the device'sUpdatestab shows per update whether it was installed or why the last scheduled run held it back. Scheduled runs do not create entries inEvents; the only event a scheduled run writes is thePatch managementevent recorded once when an outstanding restart blocks the run. - The
Patch historytab on the Patch Management page and on the device lists each scheduled run of an agent 3.3.0.5 or later next to thePatch Nowjobs. Its details show per update whether it was installed, failed with the error Windows Update or the package manager reported, or was held back and why. - The
Update Historytab on the Patch Management page shows the install outcomes per patch per device.
Troubleshooting
-
Patches stay at 0 installed. Check that a policy with
Patch Management → Windows → Generalenabled is actually assigned to the device. If the device's detail view shows-as assigned policy, the automation is missing. On Linux, open the job or the scheduled run inPatch Management → Patch history: the item details and the note carry apt'sE:lines or dnf's error lines (No match for argument,Error:,Problem:), as does the agent'sError.txt. A package that apt keeps back because the upgrade would remove another package is listed asSkippedwith the packages a full upgrade would remove; enableAllow package removal (full upgrade)in the policy's Linux tab to install it. On Fedora and RHEL-based systems a package excluded byexcludepkgsindnf.conf, or a version the repository no longer offers, fails with dnf's message while the other approved packages are installed. -
Patches approved but devices ignore them. Check the policy's
Approval & Filteringsub-tab. A filter there can block a globally approved patch. -
My scheduled run never happens. First check where you are looking. With agent 3.3.0.5 or later, every scheduled run that reached the installation is an entry in the device's
Patch historytab and on thePatch historytab of the Patch Management page, with the result of each update and the reason an update was held back or failed (see Chapter 7.5). Runs skipped for disk space, informational mode, a disabled policy, missing patch settings or an incomplete maintenance window are listed there asSkipped.Waiting for an allowed day or for the maintenance window creates no entry; the
Scheduled patchingline in the device's detail view on/devicesshows it with the next possible run. Further traces are theLast patch runline, the chips on the device'sUpdatestab, and theLast scheduled runcolumn on theDevices Not Up To Datetab; with an older agent they are the only ones.The agent decides every five minutes whether a scheduled run may start and checks the following stages in this order. Go through them from the top; the first stage that fails is the reason. Agents 3.3.0.5 and later report the waiting stages in the
Scheduled patchingline.-
Patch settings on the device. The device has received the policy's patch settings. The detail view names the assigned policy (not
-) and theScheduled patchingline does not sayThe device has not received its patch management settings yet. Until the agent has reported anything, the detail view shows the schedule facts of the device's policy (mode, allowed days, window, catch-up), so you can compare them with what you expect. If the policy is missing, fix the automation and wait for the next sync. -
Platform mode is
Managed.Informationalonly reports:Last patch run: … – informational mode, nothing installed.Disabledskips without a run; theScheduled patchingline showsPatch management is disabled in the policy of this device. CheckPatch Management → Windows → Generalin the policy. -
Allowed patch day. The default is Monday to Friday. On an unticked day no scheduled run happens, not even as a catch-up run. The line shows
Waiting for an allowed patch daywith the next possible run. CheckSchedule → Allowed patch days. A typical example is a policy saved on Friday evening and checked on Saturday morning. -
Maintenance window or catch-up. Inside the window the run starts at the agent's next check. Outside the window a run starts only as a catch-up: the first check after the policy arrives on the device, or the first check after a missed window, runs right away even outside the window (
Catch up a missed maintenance windowon the platform'sSchedulesub-tab, on by default).Fromequal toTomeans no time restriction. The line showsWaiting for the maintenance windowwith the next possible run, orThe maintenance window of the policy is incomplete, no run is scheduledwhen it cannot read theFrom/Topair. Nothing runs until the window is corrected. -
One run per window occurrence. After a run the agent installs nothing more until the next window opens (once per day for a 24/7 window), whatever the outcome of that run was. The line shows
Already ran in the current maintenance windowwith the next possible run. If that run installed nothing, the reason is in one of the following stages. -
Free disk space. With
Check minimum free disk space before patchingon, a device below the threshold is skipped:Last patch run: … – skipped, insufficient disk space. This skip does not use up the window; the agent tries again at its next check. -
Windows: no outstanding restart. While a restart from an earlier update run is outstanding, a scheduled run installs no Windows updates:
Last patch run: … – restart pending, Windows updates held back. Winget and Chocolatey updates are still installed in such a run (agent 3.3.0.11 or later), and the tooltip of the line names how many of them were installed, failed or held back.The device shows the
Restart pending since …banner with the note that scheduled runs install no Windows updates until the device has restarted, together with the restart behaviour of its policy, and the blocked run is recorded once as an event of typePatch managementon the device.With
Ask usera device where nobody is signed in asks nobody; theIf nobody is signed inoption on theRebootsub-tab decides whether such a device restarts in the maintenance window, immediately, or not at all (the default). With the default the restart has to happen another way (a user or the Console restarts the device, or you change the option), and scheduled runs keep installing no Windows updates until then.Patch Nowstill installs Windows updates too. -
Windows Update query. The agent asks Windows Update for the available updates. When the query times out, fails or returns no result, the run is recorded as
completedand its note (the tooltip of theLast patch runline) says that the query for available updates failed and no update was installed. Windows Update itself, not the policy, is the place to look then. -
Per-update filters. The run happened (
completedornothing pending) but a specific update is still missing: open the device'sUpdatestab, where the chip on each update names the reason from the last scheduled run:Blocked by severity filter,Blocked by update type filter,Not approved,Deployment ring until …,Retry after …,Waiting for restart,Not offered in last run.nothing pendingmeans Windows Update offered nothing that the policy's sources cover. A deployment ring set toImmediateonly removes the waiting time after an update's release; the allowed days, the maintenance window and the one-run-per-window rule still apply. OnlyPatch Nowbypasses the schedule, the rings and the retry budget.
On the device itself, a 3.3.0.5 agent writes every change of its schedule decision and every run outcome to
Logs\Patch_Management.txtin the Comm Agent folder (C:\ProgramData\0x101 Cyber Security\NetLock RMM\Comm Agent\) without debug mode; state changes and outcomes only, so the file stays small. The full detail of every five-minute check needs debug mode: create an emptydebug.txtin the Comm Agent folder and restart the service, as described in Guide — Debug an agent. The agent's run bookkeeping lives inpatch_cycle_state.jsonunderC:\ProgramData\NetLock RMM\Agent\(Linux:/var/lib/netlock-rmm/); a missing or empty file means that no scheduled run has reached the install stage yet. -
-
Winget or Chocolatey updates are not installed by the scheduled run, although Patch Now installs them.
Patch Nowonly proves that the installer works on the device. The scheduled run has further places where it holds an application update back, and each one leaves a trace. Open the device'sPatch historytab, open the last scheduled runs with a double-click and check in this order:- The notice
Winget and Chocolatey updates were not checked in this run because Windows updates are waiting for a restart. The agent on the device is older than 3.3.0.11. Update the agent; until then, make sure the device restarts on the same day (Rebootsub-tab) or usePatch Now. - Items with source
WingetorChocolateyand the reasonRetry after …. The update failed in earlier runs and the retry budget is used up: after the policy'sRetry count(default 3) failed attempts the agent waits seven days before it tries again; the attempts are kept inpatch_retry.jsonunderC:\ProgramData\NetLock RMM\Agent\. TheFaileditems of the earlier runs carry the installer's result inDetails.Patch Nowignores the budget, and a successful installation resets it. - The note
The winget upgrade query failed, so application updates from winget were not attempted(or the same wording for Chocolatey). The package manager could not be queried when the run started, for example because winget is not usable from the agent's system account; the device then also carries the eventwinget is not usable from the agent's system account(see the entry below). TheUpdatestab keeps the rows of the last successful inventory, so the list looks current although the query fails. The rows of that source showPackage manager query failed in the last run(agent 3.3.0.11 or later).Patch NowwithPatch Allruns the same query and shows the failure in the job's note. - Items with the reason
Deferred to a later run.Install all pending patches before rebootingis off on theRebootsub-tab, so the run installs one update and the others follow in later runs. - No
WingetorChocolateyitems and no notice. The package manager reported nothing to upgrade when the run queried it, even if theUpdatestab lists updates from an earlier inventory. Such rows showNot offered in last run(agent 3.3.0.11 or later).
The
Last runchip on the device'sUpdatestab shows these decisions for Winget and Chocolatey updates as well (agent 3.3.0.11 or later), in the same way as for Windows updates; aRetry after …chip names the time of the next allowed attempt. The device's patch status is no indication either way: software updates only count toward it when the compliance scope on the Patch ManagementSettingstab includes theWingetandChocolateysources (see Chapter 7.4). - The notice
-
The device shows the event
winget is not usable from the agent's system account. The agent runs as the system account. There it uses winget through PowerShell 7 and Microsoft's moduleMicrosoft.WinGet.Client, andwinget.exewhen the module is not available. With agent 3.3.0.12 or later the event has the typePatch managementand is raised when neither of the two works. As long as that is the case, application updates from winget are not detected or installed on the device, and App Hub actions for winget apps withRequires Elevationfail. The event is raised once per cause, not repeatedly, however often the causes alternate. The same cause is reported again only after winget worked in between and at least a day has passed since its last event. Each event opens one alert, which ends when the event is read or hidden.The
Cause:line of the event names the step that failed, and thewinget.exe:line what the fallback did:Cause:begins withMeaning What to do PowerShell 7 install: … the download … failedThe device could not download the PowerShell 7 installer package from GitHub. Allow HTTPS from the device to raw.githubusercontent.com,github.comandrelease-assets.githubusercontent.com, or install PowerShell 7 on the device yourself (x64, ARM64 or x86 MSI from Microsoft, default location).PowerShell 7 install: … no Windows Installer package … could be downloadedNone of the PowerShell 7 releases the agent looked at offers an MSI for the device's architecture. Install PowerShell 7 on the device yourself. PowerShell 7 install: … does not carry a valid signatureThe downloaded package was not signed by Microsoft and was not installed. Check whether a proxy or a security product changes downloads on the way to the device; install PowerShell 7 yourself. PowerShell 7 install: … msiexec exit …Windows Installer did not install the package. Install the PowerShell 7 MSI by hand on the device to see the installer's own message. PowerShell 7: PowerShell 7 at … is not usedStandard users can write to the PowerShell 7 folder or to pwsh.exe, so the agent does not start it.Restore the default permissions of C:\Program Files\PowerShell\7, for example by reinstalling PowerShell 7.Microsoft.WinGet.Client module checkPowerShell 7 did not answer when the agent asked for the installed module. Start C:\Program Files\PowerShell\7\pwsh.exeon the device and check that it opens; repair or reinstall PowerShell 7 if it does not.Microsoft.WinGet.Client install from PSGalleryThe module could not be installed from the PowerShell Gallery. The cause names what each of the two installation commands reported ( Install-PSResource, thenInstall-Module).Allow HTTPS to www.powershellgallery.comandcdn.powershellgallery.com, or runInstall-PSResource -Name Microsoft.WinGet.Client -Repository PSGallery -Scope AllUsers -TrustRepositoryin an elevated PowerShell 7 on the device (Install-Module Microsoft.WinGet.Client -Scope AllUserson a PowerShell older than 7.4).…: PowerShell 7.x ended with a fatal error (exit …)after any of the stepspwsh.exeitself ended while the agent looked for, installed or loaded the module, for example with exit0xC0000005. This is not an error of the module or of the PowerShell Gallery. The cause carries the PowerShell version and the beginning of PowerShell's own error report; the complete output is inError.txtof the Comm Agent on the device.Repair or reinstall PowerShell 7 with Microsoft's MSI package and restart the device. Check whether a security product on the device interferes with pwsh.exe. Then run theInstall-PSResourcecommand of the row above in an elevated PowerShell 7 on the device. If PowerShell ends there as well, the Windows Application event log has the entriesApplication Errorand.NET Runtimeforpwsh.exe, which name the failing component.…: the check ended before winget ran, exit …or…: the check ended while the module was loaded, exit …The module is installed, but the check ended with exit 0xC0000409or0xC0000135. With the first text winget itself could not be started from the system account, which is a state of App Installer on the device, not of PowerShell. With the second text the process already ended while it loaded the module.Install the pending Windows updates and bring App Installer up to date (Microsoft Store, or Repair-WinGetPackageManager -AllUsersin an elevated PowerShell 7 window of an administrator). If the event stays, send its text to support.Microsoft.WinGet.Client module importorwinget source query (Get-WinGetSource)The module is installed but does not answer from the system account. The cause carries the error, the module version and the Windows build. Install the pending Windows updates and the current module version ( Install-Module Microsoft.WinGet.Client -Scope AllUsers -Force). If the event stays, send its text to support.The line
winget.exe: no usable answer for more than 24 hoursmeans thatwinget.exestarts on the device but, for longer than a day, has only run into its time limit or answered in a form the agent cannot read with certainty. Runwinget upgrade --source wingetin an administrator session on the device to see what it prints, and check the device's network path to the winget source.Windows Server and LTSC editions without App Installer. These editions come without App Installer, the package that contains
winget.exe; the event then showswinget.exe: not found on this device (App Installer is not installed). The agent does not install App Installer and does not repair its registration. Without it the updates inventory lists no winget updates for the device, and the agent has no fallback when the module cannot be used. To install or repair it, sign in as an administrator and run in an elevated PowerShell 7 window:Install-Module Microsoft.WinGet.Client -Scope AllUsers, thenRepair-WinGetPackageManager -AllUsers. Do not run this through a NetLock RMM job or the remote shell: both run as the system account, where Microsoft's cmdlet refuses-AllUsers.The agent tries again by itself 60 minutes after a failed attempt (6 hours after an attempt in which PowerShell 7 ended with a fatal error, because every such attempt leaves a crash entry in the Windows Application event log), and right away once PowerShell 7 exists at its default location; a service restart is not needed. It only uses PowerShell 7 from
C:\Program Files\PowerShell\7. An installation elsewhere (Microsoft Store, zip archive,dotnet tool) is neither used nor changed; the agent installs its own copy next to it. It installs the newest PowerShell 7 release Microsoft publishes as a Windows Installer package, at present the 7.6 LTS line. AMicrosoft.WinGet.Clientolder than 1.12.440 stays in place, and the agent installs the current version next to it.PowerShell 7 and the module are only installed on devices that use winget through the agent (agent 3.3.0.12 or later): the policy has
Install application patches (Winget)ticked inInformationalorManagedmode,Patch Nowruns with winget updates, a winget app withRequires Elevationis installed, updated or removed through App Hub or a software deployment, or such an app has automatic updates switched on. On every other device the updates inventory uses PowerShell 7 and the module if they are already there andwinget.exeotherwise. Wherewinget.exedoes not answer from the system account either, or answers in a form the agent cannot read with certainty, the winget rows on theUpdatestab stay as they are (none on a new device) until one of the conditions applies. Whenwinget.exereports nothing to upgrade, the rows are removed with the second sync in a row that says so.Agents up to 3.3.0.11 report the event with the type
joband repeat it every six hours. -
A Windows update is
Failedwith a time limit, orSkippedbecause Windows is still installing. An update has 6 hours for its download and installation, and a run starts no installation while Windows has another one in progress (agent 3.3.0.12 or later). Both, and the 60-minute limit of older agents, are described in Chapter 7.7. -
Reboots happen at unexpected times. Review
Patch Management → Windows → RebootandSchedulein the policy. Reboot prompts follow the schedule's maintenance window. -
SLA chips show
Overdue. Adjust the SLA thresholds on the Patch ManagementSettingstab if the defaults (7 / 15 / 30 / 60 days by severity) do not fit your environment.
Related
- Chapter 7 — Patch Management — the global approval queue, update history, and SLA settings.
- Chapter 6.12 — Patch Management tab — the complete per-policy rollout reference.
- Guide H.4 — Build and apply a policy — the prerequisite routing setup.