In your case, operating Windows Server 2019 under the Legacy BIOS architecture dictates that this platform entirely lacks the integration of a cryptographic signature database, as well as the firmware communication functions required to activate the Secure Boot feature.
To verify this on your server, the Windows operating system manages the state of the Secure Boot feature through the registry key located at the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\State. On a Legacy BIOS system, the UEFISecureBootEnabled value at this directory will be either unavailable or unreadable, because the underlying hardware lacks an NVRAM chip to store such certificates. Strictly due to this architectural framework, when Windows updates related to Secure Boot certificates are executed on your server, the system will automatically detect the hardware incompatibility and bypass the procedure. It avoids forcing an installation that would otherwise generate boot denial error codes or update failures (such as error code 0x800f0922, commonly observed on misconfigured UEFI machines).
The expiration of the Secure Boot certificate presents no physical or logical vectors of impact on your current server environment. Therefore, your system is completely immune to this issue, and the deployment of the Secure Boot certificate update patch is unnecessary.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN