Share via

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

Anonymous
2024-01-19T14:35:12+00:00

I downloaded it from here: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2019

which takes you to this URL: https://info.microsoft.com/ww-landing-windows-server-2019.html to register and then back to the previous page to download the iso.

The download causes Rufus and Windows to throw a warning about no digital signature (See below). Thanks a bunch!

Windows for business | Windows Server | Networking | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-19T22:13:41+00:00

    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.

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-01-22T17:05:47+00:00

    "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

    :(

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-01-22T21:19:21+00:00
    0 comments
  4. Anonymous
    2024-01-24T06:03:48+00:00

    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.

    0 comments
  5. Anonymous
    2024-01-25T15:55:05+00:00

    Thanks Techfreak_,

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

    0 comments