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

That is super helpful, Jody. Thanks a bunch!

I don't know if this will help you or not...... I encountered the same issue. It happened after I set the bios to legacy mode. I was looking up the issue and saw someone commenting about changing your HDD to GPT and I thought it was odd. But it put me on the right path.

I was able to overcome it by simply telling Rufus to make the USB with MBR instead of GPT. Booted right up and runs beautifully.

Hope this helps.

"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

:(

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.

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