[Feature]: [Feature]: Improve Windows update and reboot detection

What is the installation method of your PatchMon server?

Docker

What is the version of your PatchMon server?

2.02

Briefly describe the feature

Improve Windows update compliance detection for Windows hosts by handling Microsoft Defender Security Intelligence updates and reboot detection more intelligently.

Detailed description

After testing PatchMon with several Windows Server 2019 systems, I noticed two situations that generate false-positive compliance information.

1. Microsoft Defender Security Intelligence Updates (KB2267602)

Microsoft Defender updates its signatures automatically, but Windows Update frequently reports a new KB2267602 update shortly afterwards.

This causes PatchMon to report a pending update even though Defender is already up to date, resulting in Windows hosts appearing permanently non-compliant.

Possible solutions:

• Allow ignoring specific Windows KBs (e.g. KB2267602)
• Allow excluding updates by title or regex
• Optionally ignore Defender Security Intelligence Updates completely

1. Reboot detection

PatchMon reports "Needs Reboot" when only PendingFileRenameOperations exist.

In my case these entries are created by the Windows Print Spooler (V4Dirs / printer driver cleanup) after an RDP session with printer redirection.

Windows itself does not report Windows Update reboot pending, but PatchMon still reports the host as requiring a reboot.

It would be useful if PatchMon distinguished between:

• Windows Update reboot required
• Component Based Servicing reboot required
• PendingFileRenameOperations only

or at least made the reboot reason visible in the UI.

Why is this useful?

This would significantly reduce false positives on Windows servers.

Currently Windows hosts can appear permanently non-compliant because of Defender signature updates or harmless PendingFileRenameOperations, making it difficult to identify systems that actually require administrator action.