Forum Discussion
Hotpatch KB5132043 breaks print spooler - How do I disable hotpatch for a subset of systems
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?
- SCCNov 20, 2026Occasional 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?