Forum Discussion
Hotpatch KB5132043 breaks print spooler - How do I disable hotpatch for a subset of systems
Hotpatch KB5132043 breaks print spooler due to our use of the ForcePoint client agent (per ForcePoint and Microsoft).
How do I disable hotpatching for a subset of systems and get WUFB to recognize the non hotpatch November 10, 2026—KB5132061 update??
Machines are Win 11 25H2 currently with October 13, 2026—KB5127648 (OS Builds 26200.9711) installed on them.
When I try to set a quality update policy to "block" HotPatch, it does not set the registry accordingly to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update\AllowRebootlessUpdates set to 0.
Thanks for any and all suggestions.
5 Replies
- IsabelleVandenHeuvelOccasional Reader
The solution is to exclude the affected machines from the Hotpatch policy and move them to the standard November cumulative update, KB5132061.
Recommended steps
1. In Intune, go to Devices → Windows updates → Quality updates.
2. Edit the existing Hotpatch-enabled policy and exclude the affected device group.
3. Create a separate Quality Update policy for that group, setting:
- When available, apply without restarting the device (Hotpatch): Block
4. Allow policy synchronization and verify the device receives the updated policy.
Important: Registry setting
Microsoft documents checking:
`HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\Update\AllowRebootlessUpdates`
Also check Event Viewer for `AllowRebootlessUpdates` to verify enrollment state. Don't rely solely on manually changing the registry; policy management can overwrite it.
Moving to KB5132061
For affected machines:
1. Uninstall KB5132043.
2. Run Windows Update scan.
3. Install standard November update KB5132061.
4. Restart and verify build 26200.9974.
Microsoft's guidance confirms that uninstalling the hotpatch and installing the standard LCU is the supported recovery route.
One additional point: This is not just anecdotal. Other administrators are reporting the same Forcepoint/print spooler problem and success after moving to KB5132061.
xxxx.9911
Reference: Microsoft – Configure Hotpatch with Windows Quality Updates - https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-hotpatch.
- JacquesHamianOccasional Reader
The recommended approach is to exclude the affected subset from Hotpatch and deploy the standard November LCU.
1. In Intune, go to Devices → Windows updates → Quality updates.
2. Exclude the affected device group from the Hotpatch-enabled policy.
3. Assign a separate quality update policy with Hotpatch set to Not allowed.
4. On pilot devices, uninstall KB5132043.
5. Run Windows Update and install standard KB5132061.
6. Reboot and verify build 26200.9974.
Important: Don't rely on manually setting `AllowRebootlessUpdates=0`; Intune policy management controls this setting. Check policy application and Event Viewer for `AllowRebootlessUpdates`.
Microsoft confirms that devices ineligible for Hotpatch receive the standard LCU instead.
My recommendation: Test this on one affected machine before rolling it out to the subset.
- maskwill53Tin Contributor
The key is to disable Hotpatch through policy, not by manually changing the registry.
For the affected Windows 11 25H2 devices:
- Create a separate Intune/WUfB device group for the affected machines.
- Apply a policy that disables rebootless updates (`AllowRebootlessUpdates = 0`).
- Verify that the policy is actually applied under `PolicyManager\current\device\Update`.
- Trigger a policy sync and Windows Update scan.
Important: Microsoft documents this setting through the Windows quality update policy, not as a registry setting you should manually enforce.
For your scenario:
- Create a separate quality update policy for the affected devices.
- Set When available, apply without restarting the device (Hotpatch) = Block.
- Assign it to the affected device group.
- Remove KB5132043 from a pilot machine.
- Run Windows Update and install standard cumulative update KB5132061.
- Restart and verify the print spooler.
Expected Windows 11 25H2 build: 26200.9974.
Microsoft documentation: Configure Hotpatch with Windows Quality Updates - https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-hotpatch
One caution: Check policy assignment conflicts and the Intune policy status before troubleshooting the registry.
- WinEndpointOpsIron Contributor
I have not tested this on a hotpatch tenant, so treat this as an order of checks rather than a confirmed fix.
- Check that the policy really targets those devices. Hotpatch is controlled from the quality update policy (Devices > Windows updates > Quality updates in the Intune admin center, or the Autopatch hotpatch setting if you manage it there). If a device is also in a group that has an Autopatch or another quality update policy with hotpatch allowed, the two can conflict. Look at the per-device status of the block policy for Conflict or Pending rather than Succeeded.
2. Give it time and a sync. The registry value you mention only appears after the device has checked in and applied the policy. Sync the device from Company Portal or Settings > Accounts > Access work or school > Info > Sync, reboot, then look at that AllowRebootlessUpdates value again. You can also see what the device received in the MDM diagnostics report (Settings > Accounts > Access work or school > Info > Create report).
3. Confirm the device is hotpatch eligible at all. As far as I know hotpatch needs Virtualization-based Security running and the right edition and baseline. If VBS is off on the machines that are not getting the non-hotpatch update, that could explain what you see, so check msinfo32 for "Virtualization-based security: Running".
4. As a stopgap while this is sorted, you could pause or defer the quality update for just that group with a separate update ring so the broken print spooler build does not land on the ForcePoint machines.
To narrow it down, can you say: which policy type you used (quality update policy, update ring or settings catalog), whether the devices are Autopatch registered, what the per-device policy status shows, and whether the registry key exists at all or just holds a different value?
- SCCOccasional Reader
at Tenant admin > Tenant management > hot patch is allowed
We use Update rings with different deferral and reboot criteria. I created my 1st and only Quality Update Policy (Devices > Windows >Windows Updates >Quality Updates) that would block hotpatching.I created a new Windows Update ring (unpaused) and applied this subset of machines to both the Quality Update policy as well as the new Update Ring.
have done multiple client syncs(Settings > Accounts > Access work or school > Info > Sync) and reboots but do not see indications in the MDM Diagnostics log or in registry that Hotpatch is disabled (0) (HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\Update\AllowRebootlessUpdates)
The keys exist but not what I would expect them to be. How long should this Intune change take to replicate to the device?My dilemma is when a hotpatch breaks something but the cumulative doesn't how can you easily move out of hotpatching and back to regular WUFB instead of waiting for the following month? Some articles indicate you may have to wait for next cumulative hotpatch baseline (next one in Jan 2027) to get squared away?