How to install Windows server with UEFI?Ubuntu 14.04 installation on Asrock H77M UEFI, dual boot with windows...

Why are special aircraft used for the carriers in the United States Navy?

How can I handle a player who pre-plans arguments about my rulings on RAW?

Has Wakanda ever accepted refugees?

How can I be pwned if I'm not registered on the compromised site?

How do you say “my friend is throwing a party, do you wanna come?” in german

Plagiarism of code by other PhD student

Can a Trickery Domain cleric cast a spell through the Invoke Duplicity clone while inside a Forcecage?

Specific Chinese carabiner QA?

GPL code private and stolen

Should we avoid writing fiction about historical events without extensive research?

How do we objectively assess if a dialogue sounds unnatural or cringy?

I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?

How to get the first element while continue streaming?

“I had a flat in the centre of town, but I didn’t like living there, so …”

Are small insurances worth it

Should I use HTTPS on a domain that will only be used for redirection?

When was drinking water recognized as crucial in marathon running?

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

PTIJ: Is all laundering forbidden during the 9 days?

How to kill a localhost:8080

Did Amazon pay $0 in taxes last year?

What can I do if someone tampers with my SSH public key?

How can I highlight parts in a screenshot

Why is it "take a leak?"



How to install Windows server with UEFI?


Ubuntu 14.04 installation on Asrock H77M UEFI, dual boot with windows 8.1 already installedInstalling Windows 7 onto Laptop in UEFIUnable to boot Windows 8.1 UEFI USB key on XPS 13 2015UEFI BIOS won't recognize USBWhen UEFI/(Motherboard Firmware), is set to UEFI(not legacy), USB is not detectedhow to install WIndows 8/10 on Dell Venue Pro (Uefi) after having damaged partitionsLinux Mint failed to install in UEFI modeWindows 10 won't boot via UEFI after fresh installHow to install Ubuntu on Odys Winbook 14 - USB booting via uefi not workingHow to install grub2 in windows 10/UEFI laptop













0















To install SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_-4_MLF_X19-82891 on to an RD230 [server][1] in UEFI mode secure boot must be enabled, correct?



The ISO was written to USB with Rufus with UEFI mode selected.



While I didn't capture the note, Rufus seemed to, as I recall, indicate that secure boot should be disabled. Surely secure boot should be enabled for UEFI.



--



reference:



https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface










share|improve this question

























  • This subject seems to be well covered: install windows server uefi. There's no sense in rehashing the steps that are all across the web. You should probably state a problem you are having so someone can field an answer.

    – jww
    yesterday








  • 1





    Windows Server 2012 R2 is based on Windows 8.1 not Windows 10

    – Ramhound
    yesterday











  • @Ramhound, why is it significant that Windows Server 2012 R2 is based on Windows 8.1 and not Windows 10?

    – Thufir
    yesterday











  • Because you provided a link about Windows 10/Server 2016. There are some significant differences between Windows 8.1 and Windows 10.

    – Ramhound
    yesterday











  • I see, okay. My fault then.

    – Thufir
    yesterday
















0















To install SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_-4_MLF_X19-82891 on to an RD230 [server][1] in UEFI mode secure boot must be enabled, correct?



The ISO was written to USB with Rufus with UEFI mode selected.



While I didn't capture the note, Rufus seemed to, as I recall, indicate that secure boot should be disabled. Surely secure boot should be enabled for UEFI.



--



reference:



https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface










share|improve this question

























  • This subject seems to be well covered: install windows server uefi. There's no sense in rehashing the steps that are all across the web. You should probably state a problem you are having so someone can field an answer.

    – jww
    yesterday








  • 1





    Windows Server 2012 R2 is based on Windows 8.1 not Windows 10

    – Ramhound
    yesterday











  • @Ramhound, why is it significant that Windows Server 2012 R2 is based on Windows 8.1 and not Windows 10?

    – Thufir
    yesterday











  • Because you provided a link about Windows 10/Server 2016. There are some significant differences between Windows 8.1 and Windows 10.

    – Ramhound
    yesterday











  • I see, okay. My fault then.

    – Thufir
    yesterday














0












0








0








To install SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_-4_MLF_X19-82891 on to an RD230 [server][1] in UEFI mode secure boot must be enabled, correct?



The ISO was written to USB with Rufus with UEFI mode selected.



While I didn't capture the note, Rufus seemed to, as I recall, indicate that secure boot should be disabled. Surely secure boot should be enabled for UEFI.



--



reference:



https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface










share|improve this question
















To install SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_-4_MLF_X19-82891 on to an RD230 [server][1] in UEFI mode secure boot must be enabled, correct?



The ISO was written to USB with Rufus with UEFI mode selected.



While I didn't capture the note, Rufus seemed to, as I recall, indicate that secure boot should be disabled. Surely secure boot should be enabled for UEFI.



--



reference:



https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface







boot usb uefi windows-server-2012-r2 bootmgr






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday







Thufir

















asked yesterday









ThufirThufir

47211024




47211024













  • This subject seems to be well covered: install windows server uefi. There's no sense in rehashing the steps that are all across the web. You should probably state a problem you are having so someone can field an answer.

    – jww
    yesterday








  • 1





    Windows Server 2012 R2 is based on Windows 8.1 not Windows 10

    – Ramhound
    yesterday











  • @Ramhound, why is it significant that Windows Server 2012 R2 is based on Windows 8.1 and not Windows 10?

    – Thufir
    yesterday











  • Because you provided a link about Windows 10/Server 2016. There are some significant differences between Windows 8.1 and Windows 10.

    – Ramhound
    yesterday











  • I see, okay. My fault then.

    – Thufir
    yesterday



















  • This subject seems to be well covered: install windows server uefi. There's no sense in rehashing the steps that are all across the web. You should probably state a problem you are having so someone can field an answer.

    – jww
    yesterday








  • 1





    Windows Server 2012 R2 is based on Windows 8.1 not Windows 10

    – Ramhound
    yesterday











  • @Ramhound, why is it significant that Windows Server 2012 R2 is based on Windows 8.1 and not Windows 10?

    – Thufir
    yesterday











  • Because you provided a link about Windows 10/Server 2016. There are some significant differences between Windows 8.1 and Windows 10.

    – Ramhound
    yesterday











  • I see, okay. My fault then.

    – Thufir
    yesterday

















This subject seems to be well covered: install windows server uefi. There's no sense in rehashing the steps that are all across the web. You should probably state a problem you are having so someone can field an answer.

– jww
yesterday







This subject seems to be well covered: install windows server uefi. There's no sense in rehashing the steps that are all across the web. You should probably state a problem you are having so someone can field an answer.

– jww
yesterday






1




1





Windows Server 2012 R2 is based on Windows 8.1 not Windows 10

– Ramhound
yesterday





Windows Server 2012 R2 is based on Windows 8.1 not Windows 10

– Ramhound
yesterday













@Ramhound, why is it significant that Windows Server 2012 R2 is based on Windows 8.1 and not Windows 10?

– Thufir
yesterday





@Ramhound, why is it significant that Windows Server 2012 R2 is based on Windows 8.1 and not Windows 10?

– Thufir
yesterday













Because you provided a link about Windows 10/Server 2016. There are some significant differences between Windows 8.1 and Windows 10.

– Ramhound
yesterday





Because you provided a link about Windows 10/Server 2016. There are some significant differences between Windows 8.1 and Windows 10.

– Ramhound
yesterday













I see, okay. My fault then.

– Thufir
yesterday





I see, okay. My fault then.

– Thufir
yesterday










1 Answer
1






active

oldest

votes


















1















Surely secure boot should be enabled for UEFI




Rufus only asks you to temporarily disable Secure Boot, and the reason it needs to do that is because, if your ISO contains a file that is larger than 4GB, then you cannot use FAT32 to write it but have to use NTFS (as FAT32 cannot accommodate files that are larger than 4GB, a technical limitation of that file system). But this means that you also need an NTFS UEFI driver & bootloader to boot that drive in UEFI mode.



Rufus can and does install those files for you. However, because of Microsoft's arbitrary decisions (point 4 here) with regards to what can and cannot be signed for Secure Boot, the files that Rufus uses, which are licensed under the GPLv3, cannot be signed for Secure Boot, which means that Secure Boot must be TEMPORARILY disabled for the first boot where the NTFS bootloader has to be used. But of course you can reenable it afterwards, and you should understand that, because Rufus is itself digitally signed and if you have validated the SHA-1 of the Windows ISO you used, temporarily disabling Secure Boot is not as great a security risk as people tend to believe (in other words it's not because it's called "Secured Something" that it should never be disabled, ever).



For more information on this, you can read this entry from the Rufus FAQ.



But again, the message you have gotten for Rufus did mention very explicitly (I know, because I'm the one who wrote that message) that the disabling of Secure Boot was only to be temporary. Oh, and I also made sure that, besides that message, there was a direct link to the FAQ entry I pointed above, that user can consult if they need more info about why Rufus asks them to temporarily disable Secure Boot. So please try to also pay attention to what the application tells you, as it might answer your questions...






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1411606%2fhow-to-install-windows-server-with-uefi%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1















    Surely secure boot should be enabled for UEFI




    Rufus only asks you to temporarily disable Secure Boot, and the reason it needs to do that is because, if your ISO contains a file that is larger than 4GB, then you cannot use FAT32 to write it but have to use NTFS (as FAT32 cannot accommodate files that are larger than 4GB, a technical limitation of that file system). But this means that you also need an NTFS UEFI driver & bootloader to boot that drive in UEFI mode.



    Rufus can and does install those files for you. However, because of Microsoft's arbitrary decisions (point 4 here) with regards to what can and cannot be signed for Secure Boot, the files that Rufus uses, which are licensed under the GPLv3, cannot be signed for Secure Boot, which means that Secure Boot must be TEMPORARILY disabled for the first boot where the NTFS bootloader has to be used. But of course you can reenable it afterwards, and you should understand that, because Rufus is itself digitally signed and if you have validated the SHA-1 of the Windows ISO you used, temporarily disabling Secure Boot is not as great a security risk as people tend to believe (in other words it's not because it's called "Secured Something" that it should never be disabled, ever).



    For more information on this, you can read this entry from the Rufus FAQ.



    But again, the message you have gotten for Rufus did mention very explicitly (I know, because I'm the one who wrote that message) that the disabling of Secure Boot was only to be temporary. Oh, and I also made sure that, besides that message, there was a direct link to the FAQ entry I pointed above, that user can consult if they need more info about why Rufus asks them to temporarily disable Secure Boot. So please try to also pay attention to what the application tells you, as it might answer your questions...






    share|improve this answer




























      1















      Surely secure boot should be enabled for UEFI




      Rufus only asks you to temporarily disable Secure Boot, and the reason it needs to do that is because, if your ISO contains a file that is larger than 4GB, then you cannot use FAT32 to write it but have to use NTFS (as FAT32 cannot accommodate files that are larger than 4GB, a technical limitation of that file system). But this means that you also need an NTFS UEFI driver & bootloader to boot that drive in UEFI mode.



      Rufus can and does install those files for you. However, because of Microsoft's arbitrary decisions (point 4 here) with regards to what can and cannot be signed for Secure Boot, the files that Rufus uses, which are licensed under the GPLv3, cannot be signed for Secure Boot, which means that Secure Boot must be TEMPORARILY disabled for the first boot where the NTFS bootloader has to be used. But of course you can reenable it afterwards, and you should understand that, because Rufus is itself digitally signed and if you have validated the SHA-1 of the Windows ISO you used, temporarily disabling Secure Boot is not as great a security risk as people tend to believe (in other words it's not because it's called "Secured Something" that it should never be disabled, ever).



      For more information on this, you can read this entry from the Rufus FAQ.



      But again, the message you have gotten for Rufus did mention very explicitly (I know, because I'm the one who wrote that message) that the disabling of Secure Boot was only to be temporary. Oh, and I also made sure that, besides that message, there was a direct link to the FAQ entry I pointed above, that user can consult if they need more info about why Rufus asks them to temporarily disable Secure Boot. So please try to also pay attention to what the application tells you, as it might answer your questions...






      share|improve this answer


























        1












        1








        1








        Surely secure boot should be enabled for UEFI




        Rufus only asks you to temporarily disable Secure Boot, and the reason it needs to do that is because, if your ISO contains a file that is larger than 4GB, then you cannot use FAT32 to write it but have to use NTFS (as FAT32 cannot accommodate files that are larger than 4GB, a technical limitation of that file system). But this means that you also need an NTFS UEFI driver & bootloader to boot that drive in UEFI mode.



        Rufus can and does install those files for you. However, because of Microsoft's arbitrary decisions (point 4 here) with regards to what can and cannot be signed for Secure Boot, the files that Rufus uses, which are licensed under the GPLv3, cannot be signed for Secure Boot, which means that Secure Boot must be TEMPORARILY disabled for the first boot where the NTFS bootloader has to be used. But of course you can reenable it afterwards, and you should understand that, because Rufus is itself digitally signed and if you have validated the SHA-1 of the Windows ISO you used, temporarily disabling Secure Boot is not as great a security risk as people tend to believe (in other words it's not because it's called "Secured Something" that it should never be disabled, ever).



        For more information on this, you can read this entry from the Rufus FAQ.



        But again, the message you have gotten for Rufus did mention very explicitly (I know, because I'm the one who wrote that message) that the disabling of Secure Boot was only to be temporary. Oh, and I also made sure that, besides that message, there was a direct link to the FAQ entry I pointed above, that user can consult if they need more info about why Rufus asks them to temporarily disable Secure Boot. So please try to also pay attention to what the application tells you, as it might answer your questions...






        share|improve this answer














        Surely secure boot should be enabled for UEFI




        Rufus only asks you to temporarily disable Secure Boot, and the reason it needs to do that is because, if your ISO contains a file that is larger than 4GB, then you cannot use FAT32 to write it but have to use NTFS (as FAT32 cannot accommodate files that are larger than 4GB, a technical limitation of that file system). But this means that you also need an NTFS UEFI driver & bootloader to boot that drive in UEFI mode.



        Rufus can and does install those files for you. However, because of Microsoft's arbitrary decisions (point 4 here) with regards to what can and cannot be signed for Secure Boot, the files that Rufus uses, which are licensed under the GPLv3, cannot be signed for Secure Boot, which means that Secure Boot must be TEMPORARILY disabled for the first boot where the NTFS bootloader has to be used. But of course you can reenable it afterwards, and you should understand that, because Rufus is itself digitally signed and if you have validated the SHA-1 of the Windows ISO you used, temporarily disabling Secure Boot is not as great a security risk as people tend to believe (in other words it's not because it's called "Secured Something" that it should never be disabled, ever).



        For more information on this, you can read this entry from the Rufus FAQ.



        But again, the message you have gotten for Rufus did mention very explicitly (I know, because I'm the one who wrote that message) that the disabling of Secure Boot was only to be temporary. Oh, and I also made sure that, besides that message, there was a direct link to the FAQ entry I pointed above, that user can consult if they need more info about why Rufus asks them to temporarily disable Secure Boot. So please try to also pay attention to what the application tells you, as it might answer your questions...







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 20 hours ago









        AkeoAkeo

        2,61011219




        2,61011219






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1411606%2fhow-to-install-windows-server-with-uefi%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

            Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

            looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...