Why does the server 2019 iso download throw warnings that there is no digital signature?

Possibly you had a corrupt download of the ISO? Did you download the 64-bit English ISO?

If so, it is as follows:

17763.3650.221105-1748.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.ISO

Algorithm Hash

SHA256 6DAE072E7F78F4CCAB74A45341DE0D6E2D45C39BE25F1F5920A2AB4F51D7BCBB

If it matches, try another bootable media and make sure it boots off that media. If it does not, clear your web browser cache and redownload the file.

If you have access to another computer, try the bootable media and see if it works on that device or produces the same error.

"Possibly you had a corrupt download of the ISO? Did you download the 64-bit English ISO?

If so, it is as follows: 17763.3650.221105-1748.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.ISO

Algorithm Hash

SHA256 6DAE072E7F78F4CCAB74A45341DE0D6E2D45C39BE25F1F5920A2AB4F51D7BCBB"

Everything looks good up until now. But rufus throws the following error:

This seems to be the cause: https://www.neowin.net/news/rufus-fixes-windows-iso-crash-warns-for-vulnerable-uefi-bootloaders-adds-ffu-zip64/

"Due to changes to the Windows Boot Manager from CVE-2023-24932. Previously created boot media will no longer be able to boot once enforcement begins Q1 of 2024. If possible, detect this issue and provide a warning.

https://support.microsoft.com/en-us/topic/kb5025885-how-to-manage-the-windows-boot-manager-revocations-for-secure-boot-changes-associated-with-cve-2023-24932-41a975df-beb2-40c1-99a3-b3ff139f832d#avoidissues5025885" 

source: shttps://github.com/pbatard/rufus/issues/2244

:(

Since the current Windows Server 2019 ISO has yet to be updated with a non-revoked bootloader, your remaining option would be:

1. Create bootable media with the updated bootloader manually.
2. Use Windows Server 2022 evaluation bootable media
3. Temporarily disable Secure Boot to see if that will allow you to boot.

Hopefully, before any enforcement takes place an updated ISO will be released. The alternative may be to evaluate Windows Server 2022.

Thanks Techfreak_,

I did try a couple of those things and am now running Server 2022. Runs like a dream!

Here it is....

https://support.microsoft.com/en-au/topic/kb5025885-how-to-manage-the-windows-boot-manager-revocations-for-secure-boot-changes-associated-with-cve-2023-24932-41a975df-beb2-40c1-99a3-b3ff139f832d#updatebootable5025885