Disabled Server Still Received Windows Updates

[Graceyin39]

Hello,

We have a Windows Server 2022 system that was disabled in BatchPatch, but Windows updates were still installed and the server rebooted afterward at the original scheduled time.

Could you please help us understand why a disabled server would still receive update installations? Also, is there a way to verify that BatchPatch will not trigger future update installations or reboots for this server?

Thank you for your assistance.

Best regards,
Grace

[doug]

Realistically, there isn’t a way that the software could have executed a Windows Update action on a row in the grid where that row is disabled. We have reviewed the code to confirm that this is the case. Therefore, I think there is likely another explanation for what you observed. For example, is the server listed multiple times in the grid but only disabled in one of the rows and not all rows? Or is there another instance of BP or another grid that contains the server? Did the Windows Update action actually get triggered by BatchPatch or was it really triggered by something else? If you contact us directly, we can get logs from you to review the possibilities. We’ll want to see an HTML grid export (sanitized) of the grid in question so that we can start by reviewing what you’re seeing. While it’s conceivable that there could be some unknown bug in the app that made this somehow possible, our review of the code did not uncover any such possibility, and no other customer has ever reported such an event occurring, so we’ll really need to see the grid where you observed this so that we have a starting point to evaluate what actually happened or if there is, indeed, a bug in the app that somehow allowed this occur. Thanks.

[Author]

Posts