When UEFI/(Motherboard Firmware), is set to UEFI(not legacy), USB is not detected












5














When UEFI/(Motherboard Firmware), is set to UEFI(not legacy), USB is not detected



When set to legacy, it is detected.



It goes without saying that I can't boot from it when the UEFI is in UEFI mode. The USB is not even detected.



Here are some pics.



The hard drive has no partitions now (since I removed them with partition wizard), but it did have windows 8.



enter image description here



enter image description here



Note- This is not the same as this question
Windows to go usb 3.0 booting problems . Because my one fails for USB 3.0 and the USB 2.0 ports. Any USB port doesn't work. And the accepted answer on that one suggests that another port would work. I notice though, as I comment, that My USB 2.0 stick works, in any port even in my USB 3 port. So the issue I have is USB 3 sticks. But then the problem I have, is , besides using USB 2 sticks only. How can I get USB 3 support, is it possible to.



Further additional note - The USB2 stick I had tried, had the latest Macrium reflect on there. I just tried a USB 3 stick with Windows 10 ISO on there, (made with rufus. GPT,FAT32) and it got detected under UEFI. The same model stick out the pack, isn't detected under UEFI. And when I made a Windows 7 ISO with that USB 3 stick, in rufus even with GPT,FAT32, it wasn't detected in UEFI So maybe it has to be Win10.. or the latest macrium reflect, for UEFI to be supported by the USB as far as even being getting detected. Also, for the purposes of seeing when it is detected, I see there's no need to switch from UEFI set to UEFI, vs UEFI set to legacy, to see if a USB has been detected by UEFI, as it will be listed under EFI either way. And if legacy is set it will list it there too.



And updated note
It seems as long if it's formatted GPT,FAT32 and has the EFI folder on there, then it works. The file it needs for the BIOS to see it is efibootbootx64.efi The filename might suggest 64bit only. If you tell rufus to make a usb GPT,FAT32, then it won't have the file yet but if you download the file or copy it from a win7 64bit then it will work. So that's a quick way of testing and narrows it down...It seems for win7 32bit, rufus defaults to ntfs, and won't let "GPT with UEFI" be chosen. Also, while ISO is a file system, I suppose it isn't when writing to USB 'cos file systems on USB are e.g. FAT32 and NTFS.



The win7 32bit does have an EFI folder. so I guess rufus is wrong when it says it's not an EFI image



enter image description here



So maybe the win7 download tool is the thing to use for that.. Or, just formatting it with rufus and copying the files over. Though my laptop is 64bit.. so perhaps no use testing a 32bit ISO../ no point.



https://technet.microsoft.com/en-au/library/hh824898.aspx "While in UEFI mode, the Windows version must match the PC architecture. A 64-bit UEFI PC can only boot 64-bit versions of Windows. A 32-bit PC can only boot 32-bit versions of Windows. In some cases, while in legacy BIOS mode, you may be able to run 32-bit Windows on a 64-bit PC, assuming the manufacturer supports 32-bit legacy BIOS mode on the PC. Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2"



Though my issue is not how many bit windows is.. it's just the detection.. but to avoid further problems, I see it's worth using 64bit windows on a 64bit laptop










share|improve this question





























    5














    When UEFI/(Motherboard Firmware), is set to UEFI(not legacy), USB is not detected



    When set to legacy, it is detected.



    It goes without saying that I can't boot from it when the UEFI is in UEFI mode. The USB is not even detected.



    Here are some pics.



    The hard drive has no partitions now (since I removed them with partition wizard), but it did have windows 8.



    enter image description here



    enter image description here



    Note- This is not the same as this question
    Windows to go usb 3.0 booting problems . Because my one fails for USB 3.0 and the USB 2.0 ports. Any USB port doesn't work. And the accepted answer on that one suggests that another port would work. I notice though, as I comment, that My USB 2.0 stick works, in any port even in my USB 3 port. So the issue I have is USB 3 sticks. But then the problem I have, is , besides using USB 2 sticks only. How can I get USB 3 support, is it possible to.



    Further additional note - The USB2 stick I had tried, had the latest Macrium reflect on there. I just tried a USB 3 stick with Windows 10 ISO on there, (made with rufus. GPT,FAT32) and it got detected under UEFI. The same model stick out the pack, isn't detected under UEFI. And when I made a Windows 7 ISO with that USB 3 stick, in rufus even with GPT,FAT32, it wasn't detected in UEFI So maybe it has to be Win10.. or the latest macrium reflect, for UEFI to be supported by the USB as far as even being getting detected. Also, for the purposes of seeing when it is detected, I see there's no need to switch from UEFI set to UEFI, vs UEFI set to legacy, to see if a USB has been detected by UEFI, as it will be listed under EFI either way. And if legacy is set it will list it there too.



    And updated note
    It seems as long if it's formatted GPT,FAT32 and has the EFI folder on there, then it works. The file it needs for the BIOS to see it is efibootbootx64.efi The filename might suggest 64bit only. If you tell rufus to make a usb GPT,FAT32, then it won't have the file yet but if you download the file or copy it from a win7 64bit then it will work. So that's a quick way of testing and narrows it down...It seems for win7 32bit, rufus defaults to ntfs, and won't let "GPT with UEFI" be chosen. Also, while ISO is a file system, I suppose it isn't when writing to USB 'cos file systems on USB are e.g. FAT32 and NTFS.



    The win7 32bit does have an EFI folder. so I guess rufus is wrong when it says it's not an EFI image



    enter image description here



    So maybe the win7 download tool is the thing to use for that.. Or, just formatting it with rufus and copying the files over. Though my laptop is 64bit.. so perhaps no use testing a 32bit ISO../ no point.



    https://technet.microsoft.com/en-au/library/hh824898.aspx "While in UEFI mode, the Windows version must match the PC architecture. A 64-bit UEFI PC can only boot 64-bit versions of Windows. A 32-bit PC can only boot 32-bit versions of Windows. In some cases, while in legacy BIOS mode, you may be able to run 32-bit Windows on a 64-bit PC, assuming the manufacturer supports 32-bit legacy BIOS mode on the PC. Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2"



    Though my issue is not how many bit windows is.. it's just the detection.. but to avoid further problems, I see it's worth using 64bit windows on a 64bit laptop










    share|improve this question



























      5












      5








      5


      7





      When UEFI/(Motherboard Firmware), is set to UEFI(not legacy), USB is not detected



      When set to legacy, it is detected.



      It goes without saying that I can't boot from it when the UEFI is in UEFI mode. The USB is not even detected.



      Here are some pics.



      The hard drive has no partitions now (since I removed them with partition wizard), but it did have windows 8.



      enter image description here



      enter image description here



      Note- This is not the same as this question
      Windows to go usb 3.0 booting problems . Because my one fails for USB 3.0 and the USB 2.0 ports. Any USB port doesn't work. And the accepted answer on that one suggests that another port would work. I notice though, as I comment, that My USB 2.0 stick works, in any port even in my USB 3 port. So the issue I have is USB 3 sticks. But then the problem I have, is , besides using USB 2 sticks only. How can I get USB 3 support, is it possible to.



      Further additional note - The USB2 stick I had tried, had the latest Macrium reflect on there. I just tried a USB 3 stick with Windows 10 ISO on there, (made with rufus. GPT,FAT32) and it got detected under UEFI. The same model stick out the pack, isn't detected under UEFI. And when I made a Windows 7 ISO with that USB 3 stick, in rufus even with GPT,FAT32, it wasn't detected in UEFI So maybe it has to be Win10.. or the latest macrium reflect, for UEFI to be supported by the USB as far as even being getting detected. Also, for the purposes of seeing when it is detected, I see there's no need to switch from UEFI set to UEFI, vs UEFI set to legacy, to see if a USB has been detected by UEFI, as it will be listed under EFI either way. And if legacy is set it will list it there too.



      And updated note
      It seems as long if it's formatted GPT,FAT32 and has the EFI folder on there, then it works. The file it needs for the BIOS to see it is efibootbootx64.efi The filename might suggest 64bit only. If you tell rufus to make a usb GPT,FAT32, then it won't have the file yet but if you download the file or copy it from a win7 64bit then it will work. So that's a quick way of testing and narrows it down...It seems for win7 32bit, rufus defaults to ntfs, and won't let "GPT with UEFI" be chosen. Also, while ISO is a file system, I suppose it isn't when writing to USB 'cos file systems on USB are e.g. FAT32 and NTFS.



      The win7 32bit does have an EFI folder. so I guess rufus is wrong when it says it's not an EFI image



      enter image description here



      So maybe the win7 download tool is the thing to use for that.. Or, just formatting it with rufus and copying the files over. Though my laptop is 64bit.. so perhaps no use testing a 32bit ISO../ no point.



      https://technet.microsoft.com/en-au/library/hh824898.aspx "While in UEFI mode, the Windows version must match the PC architecture. A 64-bit UEFI PC can only boot 64-bit versions of Windows. A 32-bit PC can only boot 32-bit versions of Windows. In some cases, while in legacy BIOS mode, you may be able to run 32-bit Windows on a 64-bit PC, assuming the manufacturer supports 32-bit legacy BIOS mode on the PC. Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2"



      Though my issue is not how many bit windows is.. it's just the detection.. but to avoid further problems, I see it's worth using 64bit windows on a 64bit laptop










      share|improve this question















      When UEFI/(Motherboard Firmware), is set to UEFI(not legacy), USB is not detected



      When set to legacy, it is detected.



      It goes without saying that I can't boot from it when the UEFI is in UEFI mode. The USB is not even detected.



      Here are some pics.



      The hard drive has no partitions now (since I removed them with partition wizard), but it did have windows 8.



      enter image description here



      enter image description here



      Note- This is not the same as this question
      Windows to go usb 3.0 booting problems . Because my one fails for USB 3.0 and the USB 2.0 ports. Any USB port doesn't work. And the accepted answer on that one suggests that another port would work. I notice though, as I comment, that My USB 2.0 stick works, in any port even in my USB 3 port. So the issue I have is USB 3 sticks. But then the problem I have, is , besides using USB 2 sticks only. How can I get USB 3 support, is it possible to.



      Further additional note - The USB2 stick I had tried, had the latest Macrium reflect on there. I just tried a USB 3 stick with Windows 10 ISO on there, (made with rufus. GPT,FAT32) and it got detected under UEFI. The same model stick out the pack, isn't detected under UEFI. And when I made a Windows 7 ISO with that USB 3 stick, in rufus even with GPT,FAT32, it wasn't detected in UEFI So maybe it has to be Win10.. or the latest macrium reflect, for UEFI to be supported by the USB as far as even being getting detected. Also, for the purposes of seeing when it is detected, I see there's no need to switch from UEFI set to UEFI, vs UEFI set to legacy, to see if a USB has been detected by UEFI, as it will be listed under EFI either way. And if legacy is set it will list it there too.



      And updated note
      It seems as long if it's formatted GPT,FAT32 and has the EFI folder on there, then it works. The file it needs for the BIOS to see it is efibootbootx64.efi The filename might suggest 64bit only. If you tell rufus to make a usb GPT,FAT32, then it won't have the file yet but if you download the file or copy it from a win7 64bit then it will work. So that's a quick way of testing and narrows it down...It seems for win7 32bit, rufus defaults to ntfs, and won't let "GPT with UEFI" be chosen. Also, while ISO is a file system, I suppose it isn't when writing to USB 'cos file systems on USB are e.g. FAT32 and NTFS.



      The win7 32bit does have an EFI folder. so I guess rufus is wrong when it says it's not an EFI image



      enter image description here



      So maybe the win7 download tool is the thing to use for that.. Or, just formatting it with rufus and copying the files over. Though my laptop is 64bit.. so perhaps no use testing a 32bit ISO../ no point.



      https://technet.microsoft.com/en-au/library/hh824898.aspx "While in UEFI mode, the Windows version must match the PC architecture. A 64-bit UEFI PC can only boot 64-bit versions of Windows. A 32-bit PC can only boot 32-bit versions of Windows. In some cases, while in legacy BIOS mode, you may be able to run 32-bit Windows on a 64-bit PC, assuming the manufacturer supports 32-bit legacy BIOS mode on the PC. Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2"



      Though my issue is not how many bit windows is.. it's just the detection.. but to avoid further problems, I see it's worth using 64bit windows on a 64bit laptop







      usb uefi gpt






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 24 '17 at 10:21









      Pierre.Vriens

      1,23561218




      1,23561218










      asked Dec 2 '15 at 15:19









      barlopbarlop

      15.4k2287145




      15.4k2287145






















          2 Answers
          2






          active

          oldest

          votes


















          3














          It turns out that .. first of all, what mode the UEFI is in doesn't matter as regards detection. So, a USB that is detected under EFI will show under EFI, and if Legacy is chosen then on restart, the USB will show under both EFI and Legacy.



          But to be listed under EFI, the USB must be appropriately set up for EFI.



          The question, is how to set up a USB so it shows under EFI, (you then have a chance of booting off of it when it's not in legacy mode, i.e. when the UEFI is in UEFI mode). Below is the answer of how to make a USB stick show under EFI.



          Rufus offers a number of options



          enter image description here



          Note- the general term for MBR and GPT, are "partition formats".



          It may be that all 3 options could work, where they have UEFI in there.. They all work for me. These instructions http://www.eightforums.com/tutorials/15458-uefi-bootable-usb-flash-drive-create-windows.html say you should choose "GPT with UEFI"



          For file system.. apparently UEFI is required to support FAT32, and not necessarily NTFS. So, best option here is FAT32



          There is one more thing that is needed though. A "bootloader file" in a particular folder, typically efiboot



          This page about Debian mentions the names of these files. But it's still relevant to Windows, because for example, Windows 7 64bit uses the path and filename of EFIbootbootx64.efi



          https://wiki.debian.org/UEFI



          amd64 EFIbootbootx64.efi



          i386 EFIbootbootia32.efi



          arm64 EFIbootbootaa64.efi



          I find testing on a 64bit laptop.. If I have the bootia32.efi file on the usb, then it won't be detected(perhaps because the laptop is 64bit), but with bootx64.efi file it will, even if there's junk in the file and it's not a proper bootloader. Sure no doubt it won't boot properly or won't boot far. But my point is that to be detected you need that file. Detection is a precondition for booting. If it's the proper file then it will boot too. I could troubleshoot the issue much faster when I found that I didn't have to burn a whole windows ISO onto the USB to test this/that.



          The win7 32bit ISO i've looked at has the EFI folder The win7 64bit ISO has an EFI folder too. I'm not sure about defaults but it looks like the USB might not be EFI , it has an EFI directory but not EFIboot and so not bootx64.efi and the UEFI motherboard firmware on my laptop isn't seeing it as EFI either, so it's not just Rufus that sees it as not EFI, but the UEFI on my laptop too doesn't see Win7 (even 64bit), as EFI.



          While the filename in efiboot isn't OS specific, the contents of the file is most likely OS specific. This link for example http://www.nextofwindows.com/how-to-make-uefi-bootable-usb-flash-drive-to-install-windows-8 offers a download to the file and says "if you are preparing for a 64-bit version of installation. You will need to copy a file called bootmgfw.efi from inside install.wim file at sources folder to efiboot folder on USB flash drive, and rename it to bootx64.efi...[or]... you can simply download this file (http://www.nextofwindows.com/download/bootx64.efi) and copy to your efiboot folder. " And there may be some supporting files too for proper bootup.



          So you should check




          • Partition Format


          • File System


          • EFI folder existing with the relevant file (these are also going to be in any OS ISO that is meant to be booted from a UEFI set to UEFI - as opposed an OS designed to be booted from a BIOS or a UEFI set to legacy)



          The EFI folder is a necessity. but don't write the folder manually unless you're experimenting or know what you're doing. It's going to be with the OS ISO.



          Apparently Win7 has some issues with USB3 though that wasn't the issue here. That'd cause other symptoms.



          Windows 10 can also be made by the windows 10 "media creation tool" instead of rufus though rufus I have found to be ok. And the reason why Macrium reflect booted, was that the current one is based on WinPE 10 64bit which is the WinPE for Windows 10. Windows 10 64bit, has the EFI folder. (I can't comment on windows 10 32bit) And when the Macrium program makes the USB it must be it gives it a partition format that supports UEFI e.g. GPT or a form of MBR that supports UEFI, and the USB would have the EFI folder.






          share|improve this answer































            0














            If changing a bios setting from legacy to UEFI changes your result, it is (almost) certainly not a driver issue.



            Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet.



            If any boot disk (USB or not) is not detected when the motherboard firmware is set to UEFI instead of legacy mode, this is a partition table issue. Note I say partition table, not partition.



            The partition table contains partitions, and it is entirely possible you've deleted all the partitions on the USB device, leaving an effectively empty partition table. The partition table is still going to be there however, and if it is an MBR (Master Boot Record) partition table, then you need to replace it with a GPT (GUID Partition Table) partition table.



            An MBR partition table is a legacy format partition table that you computer will just not see unless the firmware has legacy support enabled.



            Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue.



            More info:



            GPT: https://en.wikipedia.org/wiki/GUID_Partition_Table



            MBR: https://en.wikipedia.org/wiki/Master_boot_record



            Using Microsoft's approach to convert an MBR disk to GPT:



            https://technet.microsoft.com/en-gb/library/dn336946.aspx



            There is some technically incorrect (though very common) usage of terms in the MS page, but that may help if that's your background. Feel free to use comments to ask for details if needed



            note added by barlop



            There were some good corrections to the ms link, david posted the corrections in comment, unfortunately a moderator deleted them rather than moving them into a chat link. I'll include here what I recall from memory what I recall David saying.



            The MS link uses the term partition style, the correct term is partition format.



            The MS link states that MBR has a 4TB limit, this is incorrect as there is a way to go beyond that with MBR. Perhaps David can edit some details back in, but I see some discussion here https://serverfault.com/questions/590524/why-are-there-only-four-primary-partitions-on-an-mbr-disk The MS link also says it's difficult to go beyond 4 partitions, that's not correct. You can have multiple logical partitions(as another Ms link says clearly and as is well known). The MBR limit is 4 primary partitions as that serverfault link says.



            There may have been other things he mentioned but I don't recall..






            share|improve this answer























            • You write "If changing a bios setting from legacy to UEFI " <-- I think that technically, that thing is the UEFI, either set to UEFI mode or to legacy/bios mode. But even in legacy mode it's not called a BIOS. It's a UEFI behaving in a way compatible with a BIOS.
              – barlop
              Dec 2 '15 at 22:44










            • You write "Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet." <--- Not really. In fact if i'd have chosen NTFS then it wouldn't work. Not all UEFIs support NTFS, mine doesn't. And also, the requirement of the EFI folder with the file, that's higher level than the file system, and was a necessity for detection.
              – barlop
              Dec 2 '15 at 22:47










            • You write "Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue." <--- The particular OS is actually NOT really an issue, to something more low level like why a USB is or isn't detected.. The OSs with the EFI folder are. But you can get detection with an EFI folder even if you delete the OS.
              – barlop
              Dec 2 '15 at 22:49











            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%2f1008125%2fwhen-uefi-motherboard-firmware-is-set-to-uefinot-legacy-usb-is-not-detecte%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            It turns out that .. first of all, what mode the UEFI is in doesn't matter as regards detection. So, a USB that is detected under EFI will show under EFI, and if Legacy is chosen then on restart, the USB will show under both EFI and Legacy.



            But to be listed under EFI, the USB must be appropriately set up for EFI.



            The question, is how to set up a USB so it shows under EFI, (you then have a chance of booting off of it when it's not in legacy mode, i.e. when the UEFI is in UEFI mode). Below is the answer of how to make a USB stick show under EFI.



            Rufus offers a number of options



            enter image description here



            Note- the general term for MBR and GPT, are "partition formats".



            It may be that all 3 options could work, where they have UEFI in there.. They all work for me. These instructions http://www.eightforums.com/tutorials/15458-uefi-bootable-usb-flash-drive-create-windows.html say you should choose "GPT with UEFI"



            For file system.. apparently UEFI is required to support FAT32, and not necessarily NTFS. So, best option here is FAT32



            There is one more thing that is needed though. A "bootloader file" in a particular folder, typically efiboot



            This page about Debian mentions the names of these files. But it's still relevant to Windows, because for example, Windows 7 64bit uses the path and filename of EFIbootbootx64.efi



            https://wiki.debian.org/UEFI



            amd64 EFIbootbootx64.efi



            i386 EFIbootbootia32.efi



            arm64 EFIbootbootaa64.efi



            I find testing on a 64bit laptop.. If I have the bootia32.efi file on the usb, then it won't be detected(perhaps because the laptop is 64bit), but with bootx64.efi file it will, even if there's junk in the file and it's not a proper bootloader. Sure no doubt it won't boot properly or won't boot far. But my point is that to be detected you need that file. Detection is a precondition for booting. If it's the proper file then it will boot too. I could troubleshoot the issue much faster when I found that I didn't have to burn a whole windows ISO onto the USB to test this/that.



            The win7 32bit ISO i've looked at has the EFI folder The win7 64bit ISO has an EFI folder too. I'm not sure about defaults but it looks like the USB might not be EFI , it has an EFI directory but not EFIboot and so not bootx64.efi and the UEFI motherboard firmware on my laptop isn't seeing it as EFI either, so it's not just Rufus that sees it as not EFI, but the UEFI on my laptop too doesn't see Win7 (even 64bit), as EFI.



            While the filename in efiboot isn't OS specific, the contents of the file is most likely OS specific. This link for example http://www.nextofwindows.com/how-to-make-uefi-bootable-usb-flash-drive-to-install-windows-8 offers a download to the file and says "if you are preparing for a 64-bit version of installation. You will need to copy a file called bootmgfw.efi from inside install.wim file at sources folder to efiboot folder on USB flash drive, and rename it to bootx64.efi...[or]... you can simply download this file (http://www.nextofwindows.com/download/bootx64.efi) and copy to your efiboot folder. " And there may be some supporting files too for proper bootup.



            So you should check




            • Partition Format


            • File System


            • EFI folder existing with the relevant file (these are also going to be in any OS ISO that is meant to be booted from a UEFI set to UEFI - as opposed an OS designed to be booted from a BIOS or a UEFI set to legacy)



            The EFI folder is a necessity. but don't write the folder manually unless you're experimenting or know what you're doing. It's going to be with the OS ISO.



            Apparently Win7 has some issues with USB3 though that wasn't the issue here. That'd cause other symptoms.



            Windows 10 can also be made by the windows 10 "media creation tool" instead of rufus though rufus I have found to be ok. And the reason why Macrium reflect booted, was that the current one is based on WinPE 10 64bit which is the WinPE for Windows 10. Windows 10 64bit, has the EFI folder. (I can't comment on windows 10 32bit) And when the Macrium program makes the USB it must be it gives it a partition format that supports UEFI e.g. GPT or a form of MBR that supports UEFI, and the USB would have the EFI folder.






            share|improve this answer




























              3














              It turns out that .. first of all, what mode the UEFI is in doesn't matter as regards detection. So, a USB that is detected under EFI will show under EFI, and if Legacy is chosen then on restart, the USB will show under both EFI and Legacy.



              But to be listed under EFI, the USB must be appropriately set up for EFI.



              The question, is how to set up a USB so it shows under EFI, (you then have a chance of booting off of it when it's not in legacy mode, i.e. when the UEFI is in UEFI mode). Below is the answer of how to make a USB stick show under EFI.



              Rufus offers a number of options



              enter image description here



              Note- the general term for MBR and GPT, are "partition formats".



              It may be that all 3 options could work, where they have UEFI in there.. They all work for me. These instructions http://www.eightforums.com/tutorials/15458-uefi-bootable-usb-flash-drive-create-windows.html say you should choose "GPT with UEFI"



              For file system.. apparently UEFI is required to support FAT32, and not necessarily NTFS. So, best option here is FAT32



              There is one more thing that is needed though. A "bootloader file" in a particular folder, typically efiboot



              This page about Debian mentions the names of these files. But it's still relevant to Windows, because for example, Windows 7 64bit uses the path and filename of EFIbootbootx64.efi



              https://wiki.debian.org/UEFI



              amd64 EFIbootbootx64.efi



              i386 EFIbootbootia32.efi



              arm64 EFIbootbootaa64.efi



              I find testing on a 64bit laptop.. If I have the bootia32.efi file on the usb, then it won't be detected(perhaps because the laptop is 64bit), but with bootx64.efi file it will, even if there's junk in the file and it's not a proper bootloader. Sure no doubt it won't boot properly or won't boot far. But my point is that to be detected you need that file. Detection is a precondition for booting. If it's the proper file then it will boot too. I could troubleshoot the issue much faster when I found that I didn't have to burn a whole windows ISO onto the USB to test this/that.



              The win7 32bit ISO i've looked at has the EFI folder The win7 64bit ISO has an EFI folder too. I'm not sure about defaults but it looks like the USB might not be EFI , it has an EFI directory but not EFIboot and so not bootx64.efi and the UEFI motherboard firmware on my laptop isn't seeing it as EFI either, so it's not just Rufus that sees it as not EFI, but the UEFI on my laptop too doesn't see Win7 (even 64bit), as EFI.



              While the filename in efiboot isn't OS specific, the contents of the file is most likely OS specific. This link for example http://www.nextofwindows.com/how-to-make-uefi-bootable-usb-flash-drive-to-install-windows-8 offers a download to the file and says "if you are preparing for a 64-bit version of installation. You will need to copy a file called bootmgfw.efi from inside install.wim file at sources folder to efiboot folder on USB flash drive, and rename it to bootx64.efi...[or]... you can simply download this file (http://www.nextofwindows.com/download/bootx64.efi) and copy to your efiboot folder. " And there may be some supporting files too for proper bootup.



              So you should check




              • Partition Format


              • File System


              • EFI folder existing with the relevant file (these are also going to be in any OS ISO that is meant to be booted from a UEFI set to UEFI - as opposed an OS designed to be booted from a BIOS or a UEFI set to legacy)



              The EFI folder is a necessity. but don't write the folder manually unless you're experimenting or know what you're doing. It's going to be with the OS ISO.



              Apparently Win7 has some issues with USB3 though that wasn't the issue here. That'd cause other symptoms.



              Windows 10 can also be made by the windows 10 "media creation tool" instead of rufus though rufus I have found to be ok. And the reason why Macrium reflect booted, was that the current one is based on WinPE 10 64bit which is the WinPE for Windows 10. Windows 10 64bit, has the EFI folder. (I can't comment on windows 10 32bit) And when the Macrium program makes the USB it must be it gives it a partition format that supports UEFI e.g. GPT or a form of MBR that supports UEFI, and the USB would have the EFI folder.






              share|improve this answer


























                3












                3








                3






                It turns out that .. first of all, what mode the UEFI is in doesn't matter as regards detection. So, a USB that is detected under EFI will show under EFI, and if Legacy is chosen then on restart, the USB will show under both EFI and Legacy.



                But to be listed under EFI, the USB must be appropriately set up for EFI.



                The question, is how to set up a USB so it shows under EFI, (you then have a chance of booting off of it when it's not in legacy mode, i.e. when the UEFI is in UEFI mode). Below is the answer of how to make a USB stick show under EFI.



                Rufus offers a number of options



                enter image description here



                Note- the general term for MBR and GPT, are "partition formats".



                It may be that all 3 options could work, where they have UEFI in there.. They all work for me. These instructions http://www.eightforums.com/tutorials/15458-uefi-bootable-usb-flash-drive-create-windows.html say you should choose "GPT with UEFI"



                For file system.. apparently UEFI is required to support FAT32, and not necessarily NTFS. So, best option here is FAT32



                There is one more thing that is needed though. A "bootloader file" in a particular folder, typically efiboot



                This page about Debian mentions the names of these files. But it's still relevant to Windows, because for example, Windows 7 64bit uses the path and filename of EFIbootbootx64.efi



                https://wiki.debian.org/UEFI



                amd64 EFIbootbootx64.efi



                i386 EFIbootbootia32.efi



                arm64 EFIbootbootaa64.efi



                I find testing on a 64bit laptop.. If I have the bootia32.efi file on the usb, then it won't be detected(perhaps because the laptop is 64bit), but with bootx64.efi file it will, even if there's junk in the file and it's not a proper bootloader. Sure no doubt it won't boot properly or won't boot far. But my point is that to be detected you need that file. Detection is a precondition for booting. If it's the proper file then it will boot too. I could troubleshoot the issue much faster when I found that I didn't have to burn a whole windows ISO onto the USB to test this/that.



                The win7 32bit ISO i've looked at has the EFI folder The win7 64bit ISO has an EFI folder too. I'm not sure about defaults but it looks like the USB might not be EFI , it has an EFI directory but not EFIboot and so not bootx64.efi and the UEFI motherboard firmware on my laptop isn't seeing it as EFI either, so it's not just Rufus that sees it as not EFI, but the UEFI on my laptop too doesn't see Win7 (even 64bit), as EFI.



                While the filename in efiboot isn't OS specific, the contents of the file is most likely OS specific. This link for example http://www.nextofwindows.com/how-to-make-uefi-bootable-usb-flash-drive-to-install-windows-8 offers a download to the file and says "if you are preparing for a 64-bit version of installation. You will need to copy a file called bootmgfw.efi from inside install.wim file at sources folder to efiboot folder on USB flash drive, and rename it to bootx64.efi...[or]... you can simply download this file (http://www.nextofwindows.com/download/bootx64.efi) and copy to your efiboot folder. " And there may be some supporting files too for proper bootup.



                So you should check




                • Partition Format


                • File System


                • EFI folder existing with the relevant file (these are also going to be in any OS ISO that is meant to be booted from a UEFI set to UEFI - as opposed an OS designed to be booted from a BIOS or a UEFI set to legacy)



                The EFI folder is a necessity. but don't write the folder manually unless you're experimenting or know what you're doing. It's going to be with the OS ISO.



                Apparently Win7 has some issues with USB3 though that wasn't the issue here. That'd cause other symptoms.



                Windows 10 can also be made by the windows 10 "media creation tool" instead of rufus though rufus I have found to be ok. And the reason why Macrium reflect booted, was that the current one is based on WinPE 10 64bit which is the WinPE for Windows 10. Windows 10 64bit, has the EFI folder. (I can't comment on windows 10 32bit) And when the Macrium program makes the USB it must be it gives it a partition format that supports UEFI e.g. GPT or a form of MBR that supports UEFI, and the USB would have the EFI folder.






                share|improve this answer














                It turns out that .. first of all, what mode the UEFI is in doesn't matter as regards detection. So, a USB that is detected under EFI will show under EFI, and if Legacy is chosen then on restart, the USB will show under both EFI and Legacy.



                But to be listed under EFI, the USB must be appropriately set up for EFI.



                The question, is how to set up a USB so it shows under EFI, (you then have a chance of booting off of it when it's not in legacy mode, i.e. when the UEFI is in UEFI mode). Below is the answer of how to make a USB stick show under EFI.



                Rufus offers a number of options



                enter image description here



                Note- the general term for MBR and GPT, are "partition formats".



                It may be that all 3 options could work, where they have UEFI in there.. They all work for me. These instructions http://www.eightforums.com/tutorials/15458-uefi-bootable-usb-flash-drive-create-windows.html say you should choose "GPT with UEFI"



                For file system.. apparently UEFI is required to support FAT32, and not necessarily NTFS. So, best option here is FAT32



                There is one more thing that is needed though. A "bootloader file" in a particular folder, typically efiboot



                This page about Debian mentions the names of these files. But it's still relevant to Windows, because for example, Windows 7 64bit uses the path and filename of EFIbootbootx64.efi



                https://wiki.debian.org/UEFI



                amd64 EFIbootbootx64.efi



                i386 EFIbootbootia32.efi



                arm64 EFIbootbootaa64.efi



                I find testing on a 64bit laptop.. If I have the bootia32.efi file on the usb, then it won't be detected(perhaps because the laptop is 64bit), but with bootx64.efi file it will, even if there's junk in the file and it's not a proper bootloader. Sure no doubt it won't boot properly or won't boot far. But my point is that to be detected you need that file. Detection is a precondition for booting. If it's the proper file then it will boot too. I could troubleshoot the issue much faster when I found that I didn't have to burn a whole windows ISO onto the USB to test this/that.



                The win7 32bit ISO i've looked at has the EFI folder The win7 64bit ISO has an EFI folder too. I'm not sure about defaults but it looks like the USB might not be EFI , it has an EFI directory but not EFIboot and so not bootx64.efi and the UEFI motherboard firmware on my laptop isn't seeing it as EFI either, so it's not just Rufus that sees it as not EFI, but the UEFI on my laptop too doesn't see Win7 (even 64bit), as EFI.



                While the filename in efiboot isn't OS specific, the contents of the file is most likely OS specific. This link for example http://www.nextofwindows.com/how-to-make-uefi-bootable-usb-flash-drive-to-install-windows-8 offers a download to the file and says "if you are preparing for a 64-bit version of installation. You will need to copy a file called bootmgfw.efi from inside install.wim file at sources folder to efiboot folder on USB flash drive, and rename it to bootx64.efi...[or]... you can simply download this file (http://www.nextofwindows.com/download/bootx64.efi) and copy to your efiboot folder. " And there may be some supporting files too for proper bootup.



                So you should check




                • Partition Format


                • File System


                • EFI folder existing with the relevant file (these are also going to be in any OS ISO that is meant to be booted from a UEFI set to UEFI - as opposed an OS designed to be booted from a BIOS or a UEFI set to legacy)



                The EFI folder is a necessity. but don't write the folder manually unless you're experimenting or know what you're doing. It's going to be with the OS ISO.



                Apparently Win7 has some issues with USB3 though that wasn't the issue here. That'd cause other symptoms.



                Windows 10 can also be made by the windows 10 "media creation tool" instead of rufus though rufus I have found to be ok. And the reason why Macrium reflect booted, was that the current one is based on WinPE 10 64bit which is the WinPE for Windows 10. Windows 10 64bit, has the EFI folder. (I can't comment on windows 10 32bit) And when the Macrium program makes the USB it must be it gives it a partition format that supports UEFI e.g. GPT or a form of MBR that supports UEFI, and the USB would have the EFI folder.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 4 '15 at 14:46

























                answered Dec 2 '15 at 22:24









                barlopbarlop

                15.4k2287145




                15.4k2287145

























                    0














                    If changing a bios setting from legacy to UEFI changes your result, it is (almost) certainly not a driver issue.



                    Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet.



                    If any boot disk (USB or not) is not detected when the motherboard firmware is set to UEFI instead of legacy mode, this is a partition table issue. Note I say partition table, not partition.



                    The partition table contains partitions, and it is entirely possible you've deleted all the partitions on the USB device, leaving an effectively empty partition table. The partition table is still going to be there however, and if it is an MBR (Master Boot Record) partition table, then you need to replace it with a GPT (GUID Partition Table) partition table.



                    An MBR partition table is a legacy format partition table that you computer will just not see unless the firmware has legacy support enabled.



                    Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue.



                    More info:



                    GPT: https://en.wikipedia.org/wiki/GUID_Partition_Table



                    MBR: https://en.wikipedia.org/wiki/Master_boot_record



                    Using Microsoft's approach to convert an MBR disk to GPT:



                    https://technet.microsoft.com/en-gb/library/dn336946.aspx



                    There is some technically incorrect (though very common) usage of terms in the MS page, but that may help if that's your background. Feel free to use comments to ask for details if needed



                    note added by barlop



                    There were some good corrections to the ms link, david posted the corrections in comment, unfortunately a moderator deleted them rather than moving them into a chat link. I'll include here what I recall from memory what I recall David saying.



                    The MS link uses the term partition style, the correct term is partition format.



                    The MS link states that MBR has a 4TB limit, this is incorrect as there is a way to go beyond that with MBR. Perhaps David can edit some details back in, but I see some discussion here https://serverfault.com/questions/590524/why-are-there-only-four-primary-partitions-on-an-mbr-disk The MS link also says it's difficult to go beyond 4 partitions, that's not correct. You can have multiple logical partitions(as another Ms link says clearly and as is well known). The MBR limit is 4 primary partitions as that serverfault link says.



                    There may have been other things he mentioned but I don't recall..






                    share|improve this answer























                    • You write "If changing a bios setting from legacy to UEFI " <-- I think that technically, that thing is the UEFI, either set to UEFI mode or to legacy/bios mode. But even in legacy mode it's not called a BIOS. It's a UEFI behaving in a way compatible with a BIOS.
                      – barlop
                      Dec 2 '15 at 22:44










                    • You write "Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet." <--- Not really. In fact if i'd have chosen NTFS then it wouldn't work. Not all UEFIs support NTFS, mine doesn't. And also, the requirement of the EFI folder with the file, that's higher level than the file system, and was a necessity for detection.
                      – barlop
                      Dec 2 '15 at 22:47










                    • You write "Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue." <--- The particular OS is actually NOT really an issue, to something more low level like why a USB is or isn't detected.. The OSs with the EFI folder are. But you can get detection with an EFI folder even if you delete the OS.
                      – barlop
                      Dec 2 '15 at 22:49
















                    0














                    If changing a bios setting from legacy to UEFI changes your result, it is (almost) certainly not a driver issue.



                    Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet.



                    If any boot disk (USB or not) is not detected when the motherboard firmware is set to UEFI instead of legacy mode, this is a partition table issue. Note I say partition table, not partition.



                    The partition table contains partitions, and it is entirely possible you've deleted all the partitions on the USB device, leaving an effectively empty partition table. The partition table is still going to be there however, and if it is an MBR (Master Boot Record) partition table, then you need to replace it with a GPT (GUID Partition Table) partition table.



                    An MBR partition table is a legacy format partition table that you computer will just not see unless the firmware has legacy support enabled.



                    Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue.



                    More info:



                    GPT: https://en.wikipedia.org/wiki/GUID_Partition_Table



                    MBR: https://en.wikipedia.org/wiki/Master_boot_record



                    Using Microsoft's approach to convert an MBR disk to GPT:



                    https://technet.microsoft.com/en-gb/library/dn336946.aspx



                    There is some technically incorrect (though very common) usage of terms in the MS page, but that may help if that's your background. Feel free to use comments to ask for details if needed



                    note added by barlop



                    There were some good corrections to the ms link, david posted the corrections in comment, unfortunately a moderator deleted them rather than moving them into a chat link. I'll include here what I recall from memory what I recall David saying.



                    The MS link uses the term partition style, the correct term is partition format.



                    The MS link states that MBR has a 4TB limit, this is incorrect as there is a way to go beyond that with MBR. Perhaps David can edit some details back in, but I see some discussion here https://serverfault.com/questions/590524/why-are-there-only-four-primary-partitions-on-an-mbr-disk The MS link also says it's difficult to go beyond 4 partitions, that's not correct. You can have multiple logical partitions(as another Ms link says clearly and as is well known). The MBR limit is 4 primary partitions as that serverfault link says.



                    There may have been other things he mentioned but I don't recall..






                    share|improve this answer























                    • You write "If changing a bios setting from legacy to UEFI " <-- I think that technically, that thing is the UEFI, either set to UEFI mode or to legacy/bios mode. But even in legacy mode it's not called a BIOS. It's a UEFI behaving in a way compatible with a BIOS.
                      – barlop
                      Dec 2 '15 at 22:44










                    • You write "Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet." <--- Not really. In fact if i'd have chosen NTFS then it wouldn't work. Not all UEFIs support NTFS, mine doesn't. And also, the requirement of the EFI folder with the file, that's higher level than the file system, and was a necessity for detection.
                      – barlop
                      Dec 2 '15 at 22:47










                    • You write "Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue." <--- The particular OS is actually NOT really an issue, to something more low level like why a USB is or isn't detected.. The OSs with the EFI folder are. But you can get detection with an EFI folder even if you delete the OS.
                      – barlop
                      Dec 2 '15 at 22:49














                    0












                    0








                    0






                    If changing a bios setting from legacy to UEFI changes your result, it is (almost) certainly not a driver issue.



                    Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet.



                    If any boot disk (USB or not) is not detected when the motherboard firmware is set to UEFI instead of legacy mode, this is a partition table issue. Note I say partition table, not partition.



                    The partition table contains partitions, and it is entirely possible you've deleted all the partitions on the USB device, leaving an effectively empty partition table. The partition table is still going to be there however, and if it is an MBR (Master Boot Record) partition table, then you need to replace it with a GPT (GUID Partition Table) partition table.



                    An MBR partition table is a legacy format partition table that you computer will just not see unless the firmware has legacy support enabled.



                    Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue.



                    More info:



                    GPT: https://en.wikipedia.org/wiki/GUID_Partition_Table



                    MBR: https://en.wikipedia.org/wiki/Master_boot_record



                    Using Microsoft's approach to convert an MBR disk to GPT:



                    https://technet.microsoft.com/en-gb/library/dn336946.aspx



                    There is some technically incorrect (though very common) usage of terms in the MS page, but that may help if that's your background. Feel free to use comments to ask for details if needed



                    note added by barlop



                    There were some good corrections to the ms link, david posted the corrections in comment, unfortunately a moderator deleted them rather than moving them into a chat link. I'll include here what I recall from memory what I recall David saying.



                    The MS link uses the term partition style, the correct term is partition format.



                    The MS link states that MBR has a 4TB limit, this is incorrect as there is a way to go beyond that with MBR. Perhaps David can edit some details back in, but I see some discussion here https://serverfault.com/questions/590524/why-are-there-only-four-primary-partitions-on-an-mbr-disk The MS link also says it's difficult to go beyond 4 partitions, that's not correct. You can have multiple logical partitions(as another Ms link says clearly and as is well known). The MBR limit is 4 primary partitions as that serverfault link says.



                    There may have been other things he mentioned but I don't recall..






                    share|improve this answer














                    If changing a bios setting from legacy to UEFI changes your result, it is (almost) certainly not a driver issue.



                    Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet.



                    If any boot disk (USB or not) is not detected when the motherboard firmware is set to UEFI instead of legacy mode, this is a partition table issue. Note I say partition table, not partition.



                    The partition table contains partitions, and it is entirely possible you've deleted all the partitions on the USB device, leaving an effectively empty partition table. The partition table is still going to be there however, and if it is an MBR (Master Boot Record) partition table, then you need to replace it with a GPT (GUID Partition Table) partition table.



                    An MBR partition table is a legacy format partition table that you computer will just not see unless the firmware has legacy support enabled.



                    Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue.



                    More info:



                    GPT: https://en.wikipedia.org/wiki/GUID_Partition_Table



                    MBR: https://en.wikipedia.org/wiki/Master_boot_record



                    Using Microsoft's approach to convert an MBR disk to GPT:



                    https://technet.microsoft.com/en-gb/library/dn336946.aspx



                    There is some technically incorrect (though very common) usage of terms in the MS page, but that may help if that's your background. Feel free to use comments to ask for details if needed



                    note added by barlop



                    There were some good corrections to the ms link, david posted the corrections in comment, unfortunately a moderator deleted them rather than moving them into a chat link. I'll include here what I recall from memory what I recall David saying.



                    The MS link uses the term partition style, the correct term is partition format.



                    The MS link states that MBR has a 4TB limit, this is incorrect as there is a way to go beyond that with MBR. Perhaps David can edit some details back in, but I see some discussion here https://serverfault.com/questions/590524/why-are-there-only-four-primary-partitions-on-an-mbr-disk The MS link also says it's difficult to go beyond 4 partitions, that's not correct. You can have multiple logical partitions(as another Ms link says clearly and as is well known). The MBR limit is 4 primary partitions as that serverfault link says.



                    There may have been other things he mentioned but I don't recall..







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Apr 13 '17 at 12:14









                    Community

                    1




                    1










                    answered Dec 2 '15 at 16:38









                    David VernonDavid Vernon

                    779310




                    779310












                    • You write "If changing a bios setting from legacy to UEFI " <-- I think that technically, that thing is the UEFI, either set to UEFI mode or to legacy/bios mode. But even in legacy mode it's not called a BIOS. It's a UEFI behaving in a way compatible with a BIOS.
                      – barlop
                      Dec 2 '15 at 22:44










                    • You write "Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet." <--- Not really. In fact if i'd have chosen NTFS then it wouldn't work. Not all UEFIs support NTFS, mine doesn't. And also, the requirement of the EFI folder with the file, that's higher level than the file system, and was a necessity for detection.
                      – barlop
                      Dec 2 '15 at 22:47










                    • You write "Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue." <--- The particular OS is actually NOT really an issue, to something more low level like why a USB is or isn't detected.. The OSs with the EFI folder are. But you can get detection with an EFI folder even if you delete the OS.
                      – barlop
                      Dec 2 '15 at 22:49


















                    • You write "If changing a bios setting from legacy to UEFI " <-- I think that technically, that thing is the UEFI, either set to UEFI mode or to legacy/bios mode. But even in legacy mode it's not called a BIOS. It's a UEFI behaving in a way compatible with a BIOS.
                      – barlop
                      Dec 2 '15 at 22:44










                    • You write "Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet." <--- Not really. In fact if i'd have chosen NTFS then it wouldn't work. Not all UEFIs support NTFS, mine doesn't. And also, the requirement of the EFI folder with the file, that's higher level than the file system, and was a necessity for detection.
                      – barlop
                      Dec 2 '15 at 22:47










                    • You write "Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue." <--- The particular OS is actually NOT really an issue, to something more low level like why a USB is or isn't detected.. The OSs with the EFI folder are. But you can get detection with an EFI folder even if you delete the OS.
                      – barlop
                      Dec 2 '15 at 22:49
















                    You write "If changing a bios setting from legacy to UEFI " <-- I think that technically, that thing is the UEFI, either set to UEFI mode or to legacy/bios mode. But even in legacy mode it's not called a BIOS. It's a UEFI behaving in a way compatible with a BIOS.
                    – barlop
                    Dec 2 '15 at 22:44




                    You write "If changing a bios setting from legacy to UEFI " <-- I think that technically, that thing is the UEFI, either set to UEFI mode or to legacy/bios mode. But even in legacy mode it's not called a BIOS. It's a UEFI behaving in a way compatible with a BIOS.
                    – barlop
                    Dec 2 '15 at 22:44












                    You write "Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet." <--- Not really. In fact if i'd have chosen NTFS then it wouldn't work. Not all UEFIs support NTFS, mine doesn't. And also, the requirement of the EFI folder with the file, that's higher level than the file system, and was a necessity for detection.
                    – barlop
                    Dec 2 '15 at 22:47




                    You write "Filesystems like NTFS / FAT / HFS sit at a higher level than you need to troubleshoot just yet." <--- Not really. In fact if i'd have chosen NTFS then it wouldn't work. Not all UEFIs support NTFS, mine doesn't. And also, the requirement of the EFI folder with the file, that's higher level than the file system, and was a necessity for detection.
                    – barlop
                    Dec 2 '15 at 22:47












                    You write "Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue." <--- The particular OS is actually NOT really an issue, to something more low level like why a USB is or isn't detected.. The OSs with the EFI folder are. But you can get detection with an EFI folder even if you delete the OS.
                    – barlop
                    Dec 2 '15 at 22:49




                    You write "Legacy OSs require legacy partition table formats, but you mention Windows 8, which has full UEFI / GPT support, so this shouldn't be an issue." <--- The particular OS is actually NOT really an issue, to something more low level like why a USB is or isn't detected.. The OSs with the EFI folder are. But you can get detection with an EFI folder even if you delete the OS.
                    – barlop
                    Dec 2 '15 at 22:49


















                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f1008125%2fwhen-uefi-motherboard-firmware-is-set-to-uefinot-legacy-usb-is-not-detecte%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

                    How to make a Squid Proxy server?

                    Is this a new Fibonacci Identity?

                    19世紀