How to do UEFI+GPT with a iso file greater than 4GB
As I understand the only way I can reformat my laptop which is gpt+uefi by default is if I crate a bootable usb that is also gpt+uefi. However the image file that I have is greater than 4GB and RUFUS says that it cannot be burned to a fat32 usb. I realize that fat32 cannot hold anything larger than 4gb, however I do not intent to put the iso in there as a whole, isn't it supposed to extract it into the usb?
I think it HAS TO be fat32 to work with gpt. Is there anything else I can do other than finding an image file smaller than 4gb?
edit: I found an image file smaller than 4gb it worked fine
uefi gpt fat32
asked Jan 8 '16 at 1:57
grdgfgr
2951717
add a comment |
As I understand the only way I can reformat my laptop which is gpt+uefi by default is if I crate a bootable usb that is also gpt+uefi. However the image file that I have is greater than 4GB and RUFUS says that it cannot be burned to a fat32 usb. I realize that fat32 cannot hold anything larger than 4gb, however I do not intent to put the iso in there as a whole, isn't it supposed to extract it into the usb?
I think it HAS TO be fat32 to work with gpt. Is there anything else I can do other than finding an image file smaller than 4gb?
edit: I found an image file smaller than 4gb it worked fine
uefi gpt fat32
asked Jan 8 '16 at 1:57
grdgfgr
2951717
What you would extract is larger then 4GB currently. What specifically are you trying to burn?
– Ramhound
Jan 8 '16 at 2:01
Rufus is not the only tool for creating a bootable USB drive. Most distributions support writing the.isofile to a USB flash drive viadd, as indd if=imagefile.iso of=/dev/sdc. There are also other tools, like Unetbootin, that might work. One more point: The partition table type (MBR vs. GPT) of the installation medium is mostly irrelevant, so don't worry about that unless your computer won't boot from your medium. (Some are finicky.) The boot mode (BIOS vs. EFI) is important when you're installing, though.
– Rod Smith
Jan 8 '16 at 20:35
1
"I think it HAS TO be fat32 to work with gpt." That's a common misconception, and it is WRONG. Rufus will happily create an UEFI bootable NTFS drive (through UEFI:NTFS). You should try formatting your drive in NTFS in Rufus and see if that works. Rufus will detect if an ISO contains a >4GB file and set all the options you need to be able to boot it from UEFI for you.
– Akeo
Jan 12 '16 at 11:33
There are several workarounds. Basically it's just about creating a small FAT32 partition for UEFI and a big NTFS/ext4/whatever file system for big files. See UEFI Boot a NTFS Drive
– phuclv
Apr 17 '17 at 8:33
add a comment |
As I understand the only way I can reformat my laptop which is gpt+uefi by default is if I crate a bootable usb that is also gpt+uefi. However the image file that I have is greater than 4GB and RUFUS says that it cannot be burned to a fat32 usb. I realize that fat32 cannot hold anything larger than 4gb, however I do not intent to put the iso in there as a whole, isn't it supposed to extract it into the usb?
I think it HAS TO be fat32 to work with gpt. Is there anything else I can do other than finding an image file smaller than 4gb?
edit: I found an image file smaller than 4gb it worked fine
uefi gpt fat32
asked Jan 8 '16 at 1:57
grdgfgr
2951717
As I understand the only way I can reformat my laptop which is gpt+uefi by default is if I crate a bootable usb that is also gpt+uefi. However the image file that I have is greater than 4GB and RUFUS says that it cannot be burned to a fat32 usb. I realize that fat32 cannot hold anything larger than 4gb, however I do not intent to put the iso in there as a whole, isn't it supposed to extract it into the usb?
I think it HAS TO be fat32 to work with gpt. Is there anything else I can do other than finding an image file smaller than 4gb?
edit: I found an image file smaller than 4gb it worked fine
uefi gpt fat32
uefi gpt fat32
asked Jan 8 '16 at 1:57
grdgfgr
2951717
asked Jan 8 '16 at 1:57
grdgfgr
2951717
edited Jan 8 '16 at 8:25
asked Jan 8 '16 at 1:57
grdgfgr
2951717
asked Jan 8 '16 at 1:57
grdgfgr
2951717
asked Jan 8 '16 at 1:57
grdgfgr
2951717
2951717
What you would extract is larger then 4GB currently. What specifically are you trying to burn?
– Ramhound
Jan 8 '16 at 2:01
Rufus is not the only tool for creating a bootable USB drive. Most distributions support writing the.isofile to a USB flash drive viadd, as indd if=imagefile.iso of=/dev/sdc. There are also other tools, like Unetbootin, that might work. One more point: The partition table type (MBR vs. GPT) of the installation medium is mostly irrelevant, so don't worry about that unless your computer won't boot from your medium. (Some are finicky.) The boot mode (BIOS vs. EFI) is important when you're installing, though.
– Rod Smith
Jan 8 '16 at 20:35
1
"I think it HAS TO be fat32 to work with gpt." That's a common misconception, and it is WRONG. Rufus will happily create an UEFI bootable NTFS drive (through UEFI:NTFS). You should try formatting your drive in NTFS in Rufus and see if that works. Rufus will detect if an ISO contains a >4GB file and set all the options you need to be able to boot it from UEFI for you.
– Akeo
Jan 12 '16 at 11:33
There are several workarounds. Basically it's just about creating a small FAT32 partition for UEFI and a big NTFS/ext4/whatever file system for big files. See UEFI Boot a NTFS Drive
– phuclv
Apr 17 '17 at 8:33
add a comment |
What you would extract is larger then 4GB currently. What specifically are you trying to burn?
– Ramhound
Jan 8 '16 at 2:01
Rufus is not the only tool for creating a bootable USB drive. Most distributions support writing the.isofile to a USB flash drive viadd, as indd if=imagefile.iso of=/dev/sdc. There are also other tools, like Unetbootin, that might work. One more point: The partition table type (MBR vs. GPT) of the installation medium is mostly irrelevant, so don't worry about that unless your computer won't boot from your medium. (Some are finicky.) The boot mode (BIOS vs. EFI) is important when you're installing, though.
– Rod Smith
Jan 8 '16 at 20:35
1
"I think it HAS TO be fat32 to work with gpt." That's a common misconception, and it is WRONG. Rufus will happily create an UEFI bootable NTFS drive (through UEFI:NTFS). You should try formatting your drive in NTFS in Rufus and see if that works. Rufus will detect if an ISO contains a >4GB file and set all the options you need to be able to boot it from UEFI for you.
– Akeo
Jan 12 '16 at 11:33
There are several workarounds. Basically it's just about creating a small FAT32 partition for UEFI and a big NTFS/ext4/whatever file system for big files. See UEFI Boot a NTFS Drive
– phuclv
Apr 17 '17 at 8:33
What you would extract is larger then 4GB currently. What specifically are you trying to burn?
– Ramhound
Jan 8 '16 at 2:01
What you would extract is larger then 4GB currently. What specifically are you trying to burn?
– Ramhound
Jan 8 '16 at 2:01
Rufus is not the only tool for creating a bootable USB drive. Most distributions support writing the
.iso file to a USB flash drive via dd, as in dd if=imagefile.iso of=/dev/sdc. There are also other tools, like Unetbootin, that might work. One more point: The partition table type (MBR vs. GPT) of the installation medium is mostly irrelevant, so don't worry about that unless your computer won't boot from your medium. (Some are finicky.) The boot mode (BIOS vs. EFI) is important when you're installing, though.– Rod Smith
Jan 8 '16 at 20:35
Rufus is not the only tool for creating a bootable USB drive. Most distributions support writing the
.iso file to a USB flash drive via dd, as in dd if=imagefile.iso of=/dev/sdc. There are also other tools, like Unetbootin, that might work. One more point: The partition table type (MBR vs. GPT) of the installation medium is mostly irrelevant, so don't worry about that unless your computer won't boot from your medium. (Some are finicky.) The boot mode (BIOS vs. EFI) is important when you're installing, though.– Rod Smith
Jan 8 '16 at 20:35
1
1
"I think it HAS TO be fat32 to work with gpt." That's a common misconception, and it is WRONG. Rufus will happily create an UEFI bootable NTFS drive (through UEFI:NTFS). You should try formatting your drive in NTFS in Rufus and see if that works. Rufus will detect if an ISO contains a >4GB file and set all the options you need to be able to boot it from UEFI for you.
– Akeo
Jan 12 '16 at 11:33
"I think it HAS TO be fat32 to work with gpt." That's a common misconception, and it is WRONG. Rufus will happily create an UEFI bootable NTFS drive (through UEFI:NTFS). You should try formatting your drive in NTFS in Rufus and see if that works. Rufus will detect if an ISO contains a >4GB file and set all the options you need to be able to boot it from UEFI for you.
– Akeo
Jan 12 '16 at 11:33
There are several workarounds. Basically it's just about creating a small FAT32 partition for UEFI and a big NTFS/ext4/whatever file system for big files. See UEFI Boot a NTFS Drive
– phuclv
Apr 17 '17 at 8:33
There are several workarounds. Basically it's just about creating a small FAT32 partition for UEFI and a big NTFS/ext4/whatever file system for big files. See UEFI Boot a NTFS Drive
– phuclv
Apr 17 '17 at 8:33
add a comment |
4 Answers
4
active
oldest
votes
Rufus developer here. I'm going to try to add a proper answer since there seems to be a lot of misconception about the whole thing. Hopefully, this will help others.
RUFUS says that it cannot be burned to a fat32 usb.
Yes, but if you tried NTFS in Rufus, you would have seen that it does allow you to use that file system, even for GPT/UEFI boot, in which case the issue about the >4GB install.wim goes away.
This is because Rufus relies on an advanced feature, called UEFI:NTFS, precisely to work around this kind of situation. With UEFI:NTFS, Rufus does allow seamless boot of an NTFS partition from a pure UEFI system.
In other words, despite what you may have heard, you are NOT limited to only using FAT32 when booting UEFI. If needed, you can actually boot from NTFS (at least, if you created the drive using Rufus). Plus, Rufus does have logic to detect the presence of a >4GB file in an ISO, and select NTFS by default as the file system when that is the case. So, all you had to do was rely on Rufus to pick the best set of options for you, and just give it a try.
I think it HAS TO be fat32 to work with gpt.
I think you mean UEFI rather than GPT, but, regardless, that's actually a very damaging misconception that is still being very erroneously propagated to this day. I really can't stress this enough: There is absolutely nothing in the UEFI specs that says that it HAS TO boot from FAT32.
As a matter of fact, if you want you can go and purchase any NUC system from intel (as well some systems from other manufacturers), and you'll find that its UEFI firmware will happily boot, in pure UEFI mode, straight from an NTFS partition. So, NO, UEFI does not require FAT32 to work.
The only thing the UEFI specs say is that, at the very least, FAT32 should be supported for boot, but that doesn't preclude other file systems from also being bootable, or utilities, such as Rufus, to work around the possibility that the UEFI firmware's default only includes support for FAT32, and expand on the capabilities of that firmware by adding runtime support for NTFS boot if that is missing.
For more on this, you may be interested in the relevant entry from the Rufus FAQ.
So, to summarize, be mindful about what you hear on the internet about FAT32 and UEFI. Instead, it might be worth to give a little credit to utilities that have been designed, from the ground up, to work around any potential limitations, by testing whether the default configuration they advise you to use might work.
answered Jan 26 '18 at 14:06
Akeo
2,55611219
The thing is, I am not a partition mastermind or anything. Even though I am somewhat tech literate, all of this looks somewhat of a battle of the alphabet with UEFI NTFS GPT FAT32 etc. Essentially what I am saying is that you should make the program more foolproof. I tried to use a windows10 image that was larger than 4GB a year ago numerous times and I couldnt get it to work.
– grdgfgr
Feb 8 '18 at 3:18
Did you try to pick NTFS then? If you do and select GPT for UEFI (rather than MBR for BIOS or UEFI-CSM) in Rufus, then I can guarantee that, if your UEFI options are properly configured, and if your firmware does comply with the UEFI specifications, you will be able to boot that drive, even though it contains a >4GBinstall.wim. Now, one thing you may have to temporarily do is disable Secure Boot.
– Akeo
Feb 8 '18 at 14:02
With regards to your other point, unfortunately, holding the hand of users with regards to this whole process is not something that is feasible: People are already mostly ignoring the DD vs ISO prompt, which is is very straightforward ("Try ISO mode, but if that doesn't work, remember to also try DD mode") and only there to help them, and the main issue here is that there are parameters that the application can simply not guess for you, or even guide you on how to guess them, as they are system dependent. There's too much information that can not be summarized in easily digestible bites here.
– Akeo
Feb 8 '18 at 14:11
add a comment |
The issue for Rufus, and for other burners, isn't that the ISO is bigger than 4 GB typically but a file is bigger than 4 GB in the ISO.
In particular you need to find the install.wim files from the sources directory and then use DISM to chop it up. You then don't even need to use Rufus.
It took me a while to work this out and there are a few steps so I've put the full details at http://blog.next-genit.co.uk/2018/01/how-to-burn-usb-stick-for-uefi-windows.html
NB My advice about Rufus is wrong according to developer so please ignore that part. My way of creating ISOs does work though and FAT32 does have a 4GB limit, but Rufus can work around they say.
answered Jan 26 '18 at 9:28
Ian McDonald
1092
1
"The issue for Rufus (is that it contains) a file is bigger than 4 GB in the ISO". Rufus developer here: that is actually not an issue, since Rufus includes UEFI:NTFS, which allows it to seamlessly handle >4GB files (such asinstall.wim) in pure UEFI mode. Please look into UEFI:NTFS or simply select NTFS as the file system in Rufus, and try.
– Akeo
Jan 26 '18 at 13:35
Interesting - I agree Rufus has worked for me in the past automatically but having consistent failures on Windows 10 FCU ISO, latest Rufus and Surface Pro 4. I'll put edit on above comment and need to explore some more in Rufus.
– Ian McDonald
Jan 26 '18 at 14:28
add a comment |
UEFI only reads FAT/FAT32 and those do not allow a single file to be larger than 4GB. The solution is to split the large file or to prepare the USB stick with a small FAT32 partition that UEFI recognises and then a larger partition with the installation files. Many ways to do this but here are som explanations:
https://blogs.technet.microsoft.com/askcore/2013/03/20/creating-bootable-usb-drive-for-uefi-computers/
answered Dec 27 '17 at 9:50
Yooakim
1526
add a comment |
simply format your boot USB Stick with exFAT which can handle >4GB files fine and will be recognized by UEFI (and BIOS)
answered Oct 2 '16 at 18:30
Falco Alexander
5182721
3
I don't think exFAT will be recognizable by UEFI. If yes then it's a non-standard UEFI implementaion
– phuclv
Apr 17 '17 at 2:52
2
yeah of course, EFI is not UEFI. "Note that a standard EFI can read FAT, but cannot read NTFS, ext2/3/4fs, HFS+, or any other filesystem. (Apple's EFI can read HFS+, and so can read its boot loader from a Mac OS X root partition rather than from the ESP, but Apple's EFI is the exception rather than the rule. A few EFIs also have ISO-9660 filesystem drivers -- but again, they're exceptions to the rule.)"
– phuclv
Apr 17 '17 at 8:25
2
UEFI exFAT partition? "EFI isn't compatible with exFAT and exFAT isn't backwards-compatible with FAT32"
– phuclv
Apr 17 '17 at 8:27
2
No, it won't work in the real world except some minorities. People have tested it if you have read the links above
– phuclv
Apr 18 '17 at 0:05
1
There's no theory about it. This is not a universal solution nor applicable. UEFI has a set standard and does not support what you're talking about outside Apple's custom EFI environment. EFI is an app/OS that boots from UEFI. Look at a lot of the firmware updaters bootable tools out there, they all have a .efi file. (Windows uses boot.wim and install.wim on the Windows ISO file). That Mac EFI "OS" is what you're talking about, not UEFI.
– PeterFnet
Dec 6 '17 at 0:43
|
show 2 more comments
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1023290%2fhow-to-do-uefigpt-with-a-iso-file-greater-than-4gb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Rufus developer here. I'm going to try to add a proper answer since there seems to be a lot of misconception about the whole thing. Hopefully, this will help others.
RUFUS says that it cannot be burned to a fat32 usb.
Yes, but if you tried NTFS in Rufus, you would have seen that it does allow you to use that file system, even for GPT/UEFI boot, in which case the issue about the >4GB install.wim goes away.
This is because Rufus relies on an advanced feature, called UEFI:NTFS, precisely to work around this kind of situation. With UEFI:NTFS, Rufus does allow seamless boot of an NTFS partition from a pure UEFI system.
In other words, despite what you may have heard, you are NOT limited to only using FAT32 when booting UEFI. If needed, you can actually boot from NTFS (at least, if you created the drive using Rufus). Plus, Rufus does have logic to detect the presence of a >4GB file in an ISO, and select NTFS by default as the file system when that is the case. So, all you had to do was rely on Rufus to pick the best set of options for you, and just give it a try.
I think it HAS TO be fat32 to work with gpt.
I think you mean UEFI rather than GPT, but, regardless, that's actually a very damaging misconception that is still being very erroneously propagated to this day. I really can't stress this enough: There is absolutely nothing in the UEFI specs that says that it HAS TO boot from FAT32.
As a matter of fact, if you want you can go and purchase any NUC system from intel (as well some systems from other manufacturers), and you'll find that its UEFI firmware will happily boot, in pure UEFI mode, straight from an NTFS partition. So, NO, UEFI does not require FAT32 to work.
The only thing the UEFI specs say is that, at the very least, FAT32 should be supported for boot, but that doesn't preclude other file systems from also being bootable, or utilities, such as Rufus, to work around the possibility that the UEFI firmware's default only includes support for FAT32, and expand on the capabilities of that firmware by adding runtime support for NTFS boot if that is missing.
For more on this, you may be interested in the relevant entry from the Rufus FAQ.
So, to summarize, be mindful about what you hear on the internet about FAT32 and UEFI. Instead, it might be worth to give a little credit to utilities that have been designed, from the ground up, to work around any potential limitations, by testing whether the default configuration they advise you to use might work.
answered Jan 26 '18 at 14:06
Akeo
2,55611219
The thing is, I am not a partition mastermind or anything. Even though I am somewhat tech literate, all of this looks somewhat of a battle of the alphabet with UEFI NTFS GPT FAT32 etc. Essentially what I am saying is that you should make the program more foolproof. I tried to use a windows10 image that was larger than 4GB a year ago numerous times and I couldnt get it to work.
– grdgfgr
Feb 8 '18 at 3:18
Did you try to pick NTFS then? If you do and select GPT for UEFI (rather than MBR for BIOS or UEFI-CSM) in Rufus, then I can guarantee that, if your UEFI options are properly configured, and if your firmware does comply with the UEFI specifications, you will be able to boot that drive, even though it contains a >4GBinstall.wim. Now, one thing you may have to temporarily do is disable Secure Boot.
– Akeo
Feb 8 '18 at 14:02
With regards to your other point, unfortunately, holding the hand of users with regards to this whole process is not something that is feasible: People are already mostly ignoring the DD vs ISO prompt, which is is very straightforward ("Try ISO mode, but if that doesn't work, remember to also try DD mode") and only there to help them, and the main issue here is that there are parameters that the application can simply not guess for you, or even guide you on how to guess them, as they are system dependent. There's too much information that can not be summarized in easily digestible bites here.
– Akeo
Feb 8 '18 at 14:11
add a comment |
Rufus developer here. I'm going to try to add a proper answer since there seems to be a lot of misconception about the whole thing. Hopefully, this will help others.
RUFUS says that it cannot be burned to a fat32 usb.
Yes, but if you tried NTFS in Rufus, you would have seen that it does allow you to use that file system, even for GPT/UEFI boot, in which case the issue about the >4GB install.wim goes away.
This is because Rufus relies on an advanced feature, called UEFI:NTFS, precisely to work around this kind of situation. With UEFI:NTFS, Rufus does allow seamless boot of an NTFS partition from a pure UEFI system.
In other words, despite what you may have heard, you are NOT limited to only using FAT32 when booting UEFI. If needed, you can actually boot from NTFS (at least, if you created the drive using Rufus). Plus, Rufus does have logic to detect the presence of a >4GB file in an ISO, and select NTFS by default as the file system when that is the case. So, all you had to do was rely on Rufus to pick the best set of options for you, and just give it a try.
I think it HAS TO be fat32 to work with gpt.
I think you mean UEFI rather than GPT, but, regardless, that's actually a very damaging misconception that is still being very erroneously propagated to this day. I really can't stress this enough: There is absolutely nothing in the UEFI specs that says that it HAS TO boot from FAT32.
As a matter of fact, if you want you can go and purchase any NUC system from intel (as well some systems from other manufacturers), and you'll find that its UEFI firmware will happily boot, in pure UEFI mode, straight from an NTFS partition. So, NO, UEFI does not require FAT32 to work.
The only thing the UEFI specs say is that, at the very least, FAT32 should be supported for boot, but that doesn't preclude other file systems from also being bootable, or utilities, such as Rufus, to work around the possibility that the UEFI firmware's default only includes support for FAT32, and expand on the capabilities of that firmware by adding runtime support for NTFS boot if that is missing.
For more on this, you may be interested in the relevant entry from the Rufus FAQ.
So, to summarize, be mindful about what you hear on the internet about FAT32 and UEFI. Instead, it might be worth to give a little credit to utilities that have been designed, from the ground up, to work around any potential limitations, by testing whether the default configuration they advise you to use might work.
answered Jan 26 '18 at 14:06
Akeo
2,55611219
The thing is, I am not a partition mastermind or anything. Even though I am somewhat tech literate, all of this looks somewhat of a battle of the alphabet with UEFI NTFS GPT FAT32 etc. Essentially what I am saying is that you should make the program more foolproof. I tried to use a windows10 image that was larger than 4GB a year ago numerous times and I couldnt get it to work.
– grdgfgr
Feb 8 '18 at 3:18
Did you try to pick NTFS then? If you do and select GPT for UEFI (rather than MBR for BIOS or UEFI-CSM) in Rufus, then I can guarantee that, if your UEFI options are properly configured, and if your firmware does comply with the UEFI specifications, you will be able to boot that drive, even though it contains a >4GBinstall.wim. Now, one thing you may have to temporarily do is disable Secure Boot.
– Akeo
Feb 8 '18 at 14:02
With regards to your other point, unfortunately, holding the hand of users with regards to this whole process is not something that is feasible: People are already mostly ignoring the DD vs ISO prompt, which is is very straightforward ("Try ISO mode, but if that doesn't work, remember to also try DD mode") and only there to help them, and the main issue here is that there are parameters that the application can simply not guess for you, or even guide you on how to guess them, as they are system dependent. There's too much information that can not be summarized in easily digestible bites here.
– Akeo
Feb 8 '18 at 14:11
add a comment |
Rufus developer here. I'm going to try to add a proper answer since there seems to be a lot of misconception about the whole thing. Hopefully, this will help others.
RUFUS says that it cannot be burned to a fat32 usb.
Yes, but if you tried NTFS in Rufus, you would have seen that it does allow you to use that file system, even for GPT/UEFI boot, in which case the issue about the >4GB install.wim goes away.
This is because Rufus relies on an advanced feature, called UEFI:NTFS, precisely to work around this kind of situation. With UEFI:NTFS, Rufus does allow seamless boot of an NTFS partition from a pure UEFI system.
In other words, despite what you may have heard, you are NOT limited to only using FAT32 when booting UEFI. If needed, you can actually boot from NTFS (at least, if you created the drive using Rufus). Plus, Rufus does have logic to detect the presence of a >4GB file in an ISO, and select NTFS by default as the file system when that is the case. So, all you had to do was rely on Rufus to pick the best set of options for you, and just give it a try.
I think it HAS TO be fat32 to work with gpt.
I think you mean UEFI rather than GPT, but, regardless, that's actually a very damaging misconception that is still being very erroneously propagated to this day. I really can't stress this enough: There is absolutely nothing in the UEFI specs that says that it HAS TO boot from FAT32.
As a matter of fact, if you want you can go and purchase any NUC system from intel (as well some systems from other manufacturers), and you'll find that its UEFI firmware will happily boot, in pure UEFI mode, straight from an NTFS partition. So, NO, UEFI does not require FAT32 to work.
The only thing the UEFI specs say is that, at the very least, FAT32 should be supported for boot, but that doesn't preclude other file systems from also being bootable, or utilities, such as Rufus, to work around the possibility that the UEFI firmware's default only includes support for FAT32, and expand on the capabilities of that firmware by adding runtime support for NTFS boot if that is missing.
For more on this, you may be interested in the relevant entry from the Rufus FAQ.
So, to summarize, be mindful about what you hear on the internet about FAT32 and UEFI. Instead, it might be worth to give a little credit to utilities that have been designed, from the ground up, to work around any potential limitations, by testing whether the default configuration they advise you to use might work.
answered Jan 26 '18 at 14:06
Akeo
2,55611219
Rufus developer here. I'm going to try to add a proper answer since there seems to be a lot of misconception about the whole thing. Hopefully, this will help others.
RUFUS says that it cannot be burned to a fat32 usb.
Yes, but if you tried NTFS in Rufus, you would have seen that it does allow you to use that file system, even for GPT/UEFI boot, in which case the issue about the >4GB install.wim goes away.
This is because Rufus relies on an advanced feature, called UEFI:NTFS, precisely to work around this kind of situation. With UEFI:NTFS, Rufus does allow seamless boot of an NTFS partition from a pure UEFI system.
In other words, despite what you may have heard, you are NOT limited to only using FAT32 when booting UEFI. If needed, you can actually boot from NTFS (at least, if you created the drive using Rufus). Plus, Rufus does have logic to detect the presence of a >4GB file in an ISO, and select NTFS by default as the file system when that is the case. So, all you had to do was rely on Rufus to pick the best set of options for you, and just give it a try.
I think it HAS TO be fat32 to work with gpt.
I think you mean UEFI rather than GPT, but, regardless, that's actually a very damaging misconception that is still being very erroneously propagated to this day. I really can't stress this enough: There is absolutely nothing in the UEFI specs that says that it HAS TO boot from FAT32.
As a matter of fact, if you want you can go and purchase any NUC system from intel (as well some systems from other manufacturers), and you'll find that its UEFI firmware will happily boot, in pure UEFI mode, straight from an NTFS partition. So, NO, UEFI does not require FAT32 to work.
The only thing the UEFI specs say is that, at the very least, FAT32 should be supported for boot, but that doesn't preclude other file systems from also being bootable, or utilities, such as Rufus, to work around the possibility that the UEFI firmware's default only includes support for FAT32, and expand on the capabilities of that firmware by adding runtime support for NTFS boot if that is missing.
For more on this, you may be interested in the relevant entry from the Rufus FAQ.
So, to summarize, be mindful about what you hear on the internet about FAT32 and UEFI. Instead, it might be worth to give a little credit to utilities that have been designed, from the ground up, to work around any potential limitations, by testing whether the default configuration they advise you to use might work.
answered Jan 26 '18 at 14:06
Akeo
2,55611219
edited Jan 26 '18 at 14:21
answered Jan 26 '18 at 14:06
Akeo
2,55611219
answered Jan 26 '18 at 14:06
Akeo
2,55611219
answered Jan 26 '18 at 14:06
Akeo
2,55611219
2,55611219
The thing is, I am not a partition mastermind or anything. Even though I am somewhat tech literate, all of this looks somewhat of a battle of the alphabet with UEFI NTFS GPT FAT32 etc. Essentially what I am saying is that you should make the program more foolproof. I tried to use a windows10 image that was larger than 4GB a year ago numerous times and I couldnt get it to work.
– grdgfgr
Feb 8 '18 at 3:18
Did you try to pick NTFS then? If you do and select GPT for UEFI (rather than MBR for BIOS or UEFI-CSM) in Rufus, then I can guarantee that, if your UEFI options are properly configured, and if your firmware does comply with the UEFI specifications, you will be able to boot that drive, even though it contains a >4GBinstall.wim. Now, one thing you may have to temporarily do is disable Secure Boot.
– Akeo
Feb 8 '18 at 14:02
With regards to your other point, unfortunately, holding the hand of users with regards to this whole process is not something that is feasible: People are already mostly ignoring the DD vs ISO prompt, which is is very straightforward ("Try ISO mode, but if that doesn't work, remember to also try DD mode") and only there to help them, and the main issue here is that there are parameters that the application can simply not guess for you, or even guide you on how to guess them, as they are system dependent. There's too much information that can not be summarized in easily digestible bites here.
– Akeo
Feb 8 '18 at 14:11
add a comment |
The thing is, I am not a partition mastermind or anything. Even though I am somewhat tech literate, all of this looks somewhat of a battle of the alphabet with UEFI NTFS GPT FAT32 etc. Essentially what I am saying is that you should make the program more foolproof. I tried to use a windows10 image that was larger than 4GB a year ago numerous times and I couldnt get it to work.
– grdgfgr
Feb 8 '18 at 3:18
Did you try to pick NTFS then? If you do and select GPT for UEFI (rather than MBR for BIOS or UEFI-CSM) in Rufus, then I can guarantee that, if your UEFI options are properly configured, and if your firmware does comply with the UEFI specifications, you will be able to boot that drive, even though it contains a >4GBinstall.wim. Now, one thing you may have to temporarily do is disable Secure Boot.
– Akeo
Feb 8 '18 at 14:02
With regards to your other point, unfortunately, holding the hand of users with regards to this whole process is not something that is feasible: People are already mostly ignoring the DD vs ISO prompt, which is is very straightforward ("Try ISO mode, but if that doesn't work, remember to also try DD mode") and only there to help them, and the main issue here is that there are parameters that the application can simply not guess for you, or even guide you on how to guess them, as they are system dependent. There's too much information that can not be summarized in easily digestible bites here.
– Akeo
Feb 8 '18 at 14:11
The thing is, I am not a partition mastermind or anything. Even though I am somewhat tech literate, all of this looks somewhat of a battle of the alphabet with UEFI NTFS GPT FAT32 etc. Essentially what I am saying is that you should make the program more foolproof. I tried to use a windows10 image that was larger than 4GB a year ago numerous times and I couldnt get it to work.
– grdgfgr
Feb 8 '18 at 3:18
The thing is, I am not a partition mastermind or anything. Even though I am somewhat tech literate, all of this looks somewhat of a battle of the alphabet with UEFI NTFS GPT FAT32 etc. Essentially what I am saying is that you should make the program more foolproof. I tried to use a windows10 image that was larger than 4GB a year ago numerous times and I couldnt get it to work.
– grdgfgr
Feb 8 '18 at 3:18
Did you try to pick NTFS then? If you do and select GPT for UEFI (rather than MBR for BIOS or UEFI-CSM) in Rufus, then I can guarantee that, if your UEFI options are properly configured, and if your firmware does comply with the UEFI specifications, you will be able to boot that drive, even though it contains a >4GB
install.wim. Now, one thing you may have to temporarily do is disable Secure Boot.– Akeo
Feb 8 '18 at 14:02
Did you try to pick NTFS then? If you do and select GPT for UEFI (rather than MBR for BIOS or UEFI-CSM) in Rufus, then I can guarantee that, if your UEFI options are properly configured, and if your firmware does comply with the UEFI specifications, you will be able to boot that drive, even though it contains a >4GB
install.wim. Now, one thing you may have to temporarily do is disable Secure Boot.– Akeo
Feb 8 '18 at 14:02
With regards to your other point, unfortunately, holding the hand of users with regards to this whole process is not something that is feasible: People are already mostly ignoring the DD vs ISO prompt, which is is very straightforward ("Try ISO mode, but if that doesn't work, remember to also try DD mode") and only there to help them, and the main issue here is that there are parameters that the application can simply not guess for you, or even guide you on how to guess them, as they are system dependent. There's too much information that can not be summarized in easily digestible bites here.
– Akeo
Feb 8 '18 at 14:11
With regards to your other point, unfortunately, holding the hand of users with regards to this whole process is not something that is feasible: People are already mostly ignoring the DD vs ISO prompt, which is is very straightforward ("Try ISO mode, but if that doesn't work, remember to also try DD mode") and only there to help them, and the main issue here is that there are parameters that the application can simply not guess for you, or even guide you on how to guess them, as they are system dependent. There's too much information that can not be summarized in easily digestible bites here.
– Akeo
Feb 8 '18 at 14:11
add a comment |
The issue for Rufus, and for other burners, isn't that the ISO is bigger than 4 GB typically but a file is bigger than 4 GB in the ISO.
In particular you need to find the install.wim files from the sources directory and then use DISM to chop it up. You then don't even need to use Rufus.
It took me a while to work this out and there are a few steps so I've put the full details at http://blog.next-genit.co.uk/2018/01/how-to-burn-usb-stick-for-uefi-windows.html
NB My advice about Rufus is wrong according to developer so please ignore that part. My way of creating ISOs does work though and FAT32 does have a 4GB limit, but Rufus can work around they say.
answered Jan 26 '18 at 9:28
Ian McDonald
1092
1
"The issue for Rufus (is that it contains) a file is bigger than 4 GB in the ISO". Rufus developer here: that is actually not an issue, since Rufus includes UEFI:NTFS, which allows it to seamlessly handle >4GB files (such asinstall.wim) in pure UEFI mode. Please look into UEFI:NTFS or simply select NTFS as the file system in Rufus, and try.
– Akeo
Jan 26 '18 at 13:35
Interesting - I agree Rufus has worked for me in the past automatically but having consistent failures on Windows 10 FCU ISO, latest Rufus and Surface Pro 4. I'll put edit on above comment and need to explore some more in Rufus.
– Ian McDonald
Jan 26 '18 at 14:28
add a comment |
The issue for Rufus, and for other burners, isn't that the ISO is bigger than 4 GB typically but a file is bigger than 4 GB in the ISO.
In particular you need to find the install.wim files from the sources directory and then use DISM to chop it up. You then don't even need to use Rufus.
It took me a while to work this out and there are a few steps so I've put the full details at http://blog.next-genit.co.uk/2018/01/how-to-burn-usb-stick-for-uefi-windows.html
NB My advice about Rufus is wrong according to developer so please ignore that part. My way of creating ISOs does work though and FAT32 does have a 4GB limit, but Rufus can work around they say.
answered Jan 26 '18 at 9:28
Ian McDonald
1092
1
"The issue for Rufus (is that it contains) a file is bigger than 4 GB in the ISO". Rufus developer here: that is actually not an issue, since Rufus includes UEFI:NTFS, which allows it to seamlessly handle >4GB files (such asinstall.wim) in pure UEFI mode. Please look into UEFI:NTFS or simply select NTFS as the file system in Rufus, and try.
– Akeo
Jan 26 '18 at 13:35
Interesting - I agree Rufus has worked for me in the past automatically but having consistent failures on Windows 10 FCU ISO, latest Rufus and Surface Pro 4. I'll put edit on above comment and need to explore some more in Rufus.
– Ian McDonald
Jan 26 '18 at 14:28
add a comment |
The issue for Rufus, and for other burners, isn't that the ISO is bigger than 4 GB typically but a file is bigger than 4 GB in the ISO.
In particular you need to find the install.wim files from the sources directory and then use DISM to chop it up. You then don't even need to use Rufus.
It took me a while to work this out and there are a few steps so I've put the full details at http://blog.next-genit.co.uk/2018/01/how-to-burn-usb-stick-for-uefi-windows.html
NB My advice about Rufus is wrong according to developer so please ignore that part. My way of creating ISOs does work though and FAT32 does have a 4GB limit, but Rufus can work around they say.
answered Jan 26 '18 at 9:28
Ian McDonald
1092
The issue for Rufus, and for other burners, isn't that the ISO is bigger than 4 GB typically but a file is bigger than 4 GB in the ISO.
In particular you need to find the install.wim files from the sources directory and then use DISM to chop it up. You then don't even need to use Rufus.
It took me a while to work this out and there are a few steps so I've put the full details at http://blog.next-genit.co.uk/2018/01/how-to-burn-usb-stick-for-uefi-windows.html
NB My advice about Rufus is wrong according to developer so please ignore that part. My way of creating ISOs does work though and FAT32 does have a 4GB limit, but Rufus can work around they say.
answered Jan 26 '18 at 9:28
Ian McDonald
1092
edited Jan 26 '18 at 14:30
answered Jan 26 '18 at 9:28
Ian McDonald
1092
answered Jan 26 '18 at 9:28
Ian McDonald
1092
answered Jan 26 '18 at 9:28
Ian McDonald
1092
1092
1
"The issue for Rufus (is that it contains) a file is bigger than 4 GB in the ISO". Rufus developer here: that is actually not an issue, since Rufus includes UEFI:NTFS, which allows it to seamlessly handle >4GB files (such asinstall.wim) in pure UEFI mode. Please look into UEFI:NTFS or simply select NTFS as the file system in Rufus, and try.
– Akeo
Jan 26 '18 at 13:35
Interesting - I agree Rufus has worked for me in the past automatically but having consistent failures on Windows 10 FCU ISO, latest Rufus and Surface Pro 4. I'll put edit on above comment and need to explore some more in Rufus.
– Ian McDonald
Jan 26 '18 at 14:28
add a comment |
1
"The issue for Rufus (is that it contains) a file is bigger than 4 GB in the ISO". Rufus developer here: that is actually not an issue, since Rufus includes UEFI:NTFS, which allows it to seamlessly handle >4GB files (such asinstall.wim) in pure UEFI mode. Please look into UEFI:NTFS or simply select NTFS as the file system in Rufus, and try.
– Akeo
Jan 26 '18 at 13:35
Interesting - I agree Rufus has worked for me in the past automatically but having consistent failures on Windows 10 FCU ISO, latest Rufus and Surface Pro 4. I'll put edit on above comment and need to explore some more in Rufus.
– Ian McDonald
Jan 26 '18 at 14:28
1
1
"The issue for Rufus (is that it contains) a file is bigger than 4 GB in the ISO". Rufus developer here: that is actually not an issue, since Rufus includes UEFI:NTFS, which allows it to seamlessly handle >4GB files (such as
install.wim) in pure UEFI mode. Please look into UEFI:NTFS or simply select NTFS as the file system in Rufus, and try.– Akeo
Jan 26 '18 at 13:35
"The issue for Rufus (is that it contains) a file is bigger than 4 GB in the ISO". Rufus developer here: that is actually not an issue, since Rufus includes UEFI:NTFS, which allows it to seamlessly handle >4GB files (such as
install.wim) in pure UEFI mode. Please look into UEFI:NTFS or simply select NTFS as the file system in Rufus, and try.– Akeo
Jan 26 '18 at 13:35
Interesting - I agree Rufus has worked for me in the past automatically but having consistent failures on Windows 10 FCU ISO, latest Rufus and Surface Pro 4. I'll put edit on above comment and need to explore some more in Rufus.
– Ian McDonald
Jan 26 '18 at 14:28
Interesting - I agree Rufus has worked for me in the past automatically but having consistent failures on Windows 10 FCU ISO, latest Rufus and Surface Pro 4. I'll put edit on above comment and need to explore some more in Rufus.
– Ian McDonald
Jan 26 '18 at 14:28
add a comment |
UEFI only reads FAT/FAT32 and those do not allow a single file to be larger than 4GB. The solution is to split the large file or to prepare the USB stick with a small FAT32 partition that UEFI recognises and then a larger partition with the installation files. Many ways to do this but here are som explanations:
https://blogs.technet.microsoft.com/askcore/2013/03/20/creating-bootable-usb-drive-for-uefi-computers/
answered Dec 27 '17 at 9:50
Yooakim
1526
add a comment |
UEFI only reads FAT/FAT32 and those do not allow a single file to be larger than 4GB. The solution is to split the large file or to prepare the USB stick with a small FAT32 partition that UEFI recognises and then a larger partition with the installation files. Many ways to do this but here are som explanations:
https://blogs.technet.microsoft.com/askcore/2013/03/20/creating-bootable-usb-drive-for-uefi-computers/
answered Dec 27 '17 at 9:50
Yooakim
1526
add a comment |
UEFI only reads FAT/FAT32 and those do not allow a single file to be larger than 4GB. The solution is to split the large file or to prepare the USB stick with a small FAT32 partition that UEFI recognises and then a larger partition with the installation files. Many ways to do this but here are som explanations:
https://blogs.technet.microsoft.com/askcore/2013/03/20/creating-bootable-usb-drive-for-uefi-computers/
answered Dec 27 '17 at 9:50
Yooakim
1526
UEFI only reads FAT/FAT32 and those do not allow a single file to be larger than 4GB. The solution is to split the large file or to prepare the USB stick with a small FAT32 partition that UEFI recognises and then a larger partition with the installation files. Many ways to do this but here are som explanations:
https://blogs.technet.microsoft.com/askcore/2013/03/20/creating-bootable-usb-drive-for-uefi-computers/
answered Dec 27 '17 at 9:50
Yooakim
1526
answered Dec 27 '17 at 9:50
Yooakim
1526
answered Dec 27 '17 at 9:50
Yooakim
1526
answered Dec 27 '17 at 9:50
Yooakim
1526
1526
add a comment |
add a comment |
simply format your boot USB Stick with exFAT which can handle >4GB files fine and will be recognized by UEFI (and BIOS)
answered Oct 2 '16 at 18:30
Falco Alexander
5182721
3
I don't think exFAT will be recognizable by UEFI. If yes then it's a non-standard UEFI implementaion
– phuclv
Apr 17 '17 at 2:52
2
yeah of course, EFI is not UEFI. "Note that a standard EFI can read FAT, but cannot read NTFS, ext2/3/4fs, HFS+, or any other filesystem. (Apple's EFI can read HFS+, and so can read its boot loader from a Mac OS X root partition rather than from the ESP, but Apple's EFI is the exception rather than the rule. A few EFIs also have ISO-9660 filesystem drivers -- but again, they're exceptions to the rule.)"
– phuclv
Apr 17 '17 at 8:25
2
UEFI exFAT partition? "EFI isn't compatible with exFAT and exFAT isn't backwards-compatible with FAT32"
– phuclv
Apr 17 '17 at 8:27
2
No, it won't work in the real world except some minorities. People have tested it if you have read the links above
– phuclv
Apr 18 '17 at 0:05
1
There's no theory about it. This is not a universal solution nor applicable. UEFI has a set standard and does not support what you're talking about outside Apple's custom EFI environment. EFI is an app/OS that boots from UEFI. Look at a lot of the firmware updaters bootable tools out there, they all have a .efi file. (Windows uses boot.wim and install.wim on the Windows ISO file). That Mac EFI "OS" is what you're talking about, not UEFI.
– PeterFnet
Dec 6 '17 at 0:43
|
show 2 more comments
simply format your boot USB Stick with exFAT which can handle >4GB files fine and will be recognized by UEFI (and BIOS)
answered Oct 2 '16 at 18:30
Falco Alexander
5182721
3
I don't think exFAT will be recognizable by UEFI. If yes then it's a non-standard UEFI implementaion
– phuclv
Apr 17 '17 at 2:52
2
yeah of course, EFI is not UEFI. "Note that a standard EFI can read FAT, but cannot read NTFS, ext2/3/4fs, HFS+, or any other filesystem. (Apple's EFI can read HFS+, and so can read its boot loader from a Mac OS X root partition rather than from the ESP, but Apple's EFI is the exception rather than the rule. A few EFIs also have ISO-9660 filesystem drivers -- but again, they're exceptions to the rule.)"
– phuclv
Apr 17 '17 at 8:25
2
UEFI exFAT partition? "EFI isn't compatible with exFAT and exFAT isn't backwards-compatible with FAT32"
– phuclv
Apr 17 '17 at 8:27
2
No, it won't work in the real world except some minorities. People have tested it if you have read the links above
– phuclv
Apr 18 '17 at 0:05
1
There's no theory about it. This is not a universal solution nor applicable. UEFI has a set standard and does not support what you're talking about outside Apple's custom EFI environment. EFI is an app/OS that boots from UEFI. Look at a lot of the firmware updaters bootable tools out there, they all have a .efi file. (Windows uses boot.wim and install.wim on the Windows ISO file). That Mac EFI "OS" is what you're talking about, not UEFI.
– PeterFnet
Dec 6 '17 at 0:43
|
show 2 more comments
simply format your boot USB Stick with exFAT which can handle >4GB files fine and will be recognized by UEFI (and BIOS)
answered Oct 2 '16 at 18:30
Falco Alexander
5182721
simply format your boot USB Stick with exFAT which can handle >4GB files fine and will be recognized by UEFI (and BIOS)
answered Oct 2 '16 at 18:30
Falco Alexander
5182721
answered Oct 2 '16 at 18:30
Falco Alexander
5182721
answered Oct 2 '16 at 18:30
Falco Alexander
5182721
answered Oct 2 '16 at 18:30
Falco Alexander
5182721
5182721
3
I don't think exFAT will be recognizable by UEFI. If yes then it's a non-standard UEFI implementaion
– phuclv
Apr 17 '17 at 2:52
2
yeah of course, EFI is not UEFI. "Note that a standard EFI can read FAT, but cannot read NTFS, ext2/3/4fs, HFS+, or any other filesystem. (Apple's EFI can read HFS+, and so can read its boot loader from a Mac OS X root partition rather than from the ESP, but Apple's EFI is the exception rather than the rule. A few EFIs also have ISO-9660 filesystem drivers -- but again, they're exceptions to the rule.)"
– phuclv
Apr 17 '17 at 8:25
2
UEFI exFAT partition? "EFI isn't compatible with exFAT and exFAT isn't backwards-compatible with FAT32"
– phuclv
Apr 17 '17 at 8:27
2
No, it won't work in the real world except some minorities. People have tested it if you have read the links above
– phuclv
Apr 18 '17 at 0:05
1
There's no theory about it. This is not a universal solution nor applicable. UEFI has a set standard and does not support what you're talking about outside Apple's custom EFI environment. EFI is an app/OS that boots from UEFI. Look at a lot of the firmware updaters bootable tools out there, they all have a .efi file. (Windows uses boot.wim and install.wim on the Windows ISO file). That Mac EFI "OS" is what you're talking about, not UEFI.
– PeterFnet
Dec 6 '17 at 0:43
|
show 2 more comments
3
I don't think exFAT will be recognizable by UEFI. If yes then it's a non-standard UEFI implementaion
– phuclv
Apr 17 '17 at 2:52
2
yeah of course, EFI is not UEFI. "Note that a standard EFI can read FAT, but cannot read NTFS, ext2/3/4fs, HFS+, or any other filesystem. (Apple's EFI can read HFS+, and so can read its boot loader from a Mac OS X root partition rather than from the ESP, but Apple's EFI is the exception rather than the rule. A few EFIs also have ISO-9660 filesystem drivers -- but again, they're exceptions to the rule.)"
– phuclv
Apr 17 '17 at 8:25
2
UEFI exFAT partition? "EFI isn't compatible with exFAT and exFAT isn't backwards-compatible with FAT32"
– phuclv
Apr 17 '17 at 8:27
2
No, it won't work in the real world except some minorities. People have tested it if you have read the links above
– phuclv
Apr 18 '17 at 0:05
1
There's no theory about it. This is not a universal solution nor applicable. UEFI has a set standard and does not support what you're talking about outside Apple's custom EFI environment. EFI is an app/OS that boots from UEFI. Look at a lot of the firmware updaters bootable tools out there, they all have a .efi file. (Windows uses boot.wim and install.wim on the Windows ISO file). That Mac EFI "OS" is what you're talking about, not UEFI.
– PeterFnet
Dec 6 '17 at 0:43
3
3
I don't think exFAT will be recognizable by UEFI. If yes then it's a non-standard UEFI implementaion
– phuclv
Apr 17 '17 at 2:52
I don't think exFAT will be recognizable by UEFI. If yes then it's a non-standard UEFI implementaion
– phuclv
Apr 17 '17 at 2:52
2
2
yeah of course, EFI is not UEFI. "Note that a standard EFI can read FAT, but cannot read NTFS, ext2/3/4fs, HFS+, or any other filesystem. (Apple's EFI can read HFS+, and so can read its boot loader from a Mac OS X root partition rather than from the ESP, but Apple's EFI is the exception rather than the rule. A few EFIs also have ISO-9660 filesystem drivers -- but again, they're exceptions to the rule.)"
– phuclv
Apr 17 '17 at 8:25
yeah of course, EFI is not UEFI. "Note that a standard EFI can read FAT, but cannot read NTFS, ext2/3/4fs, HFS+, or any other filesystem. (Apple's EFI can read HFS+, and so can read its boot loader from a Mac OS X root partition rather than from the ESP, but Apple's EFI is the exception rather than the rule. A few EFIs also have ISO-9660 filesystem drivers -- but again, they're exceptions to the rule.)"
– phuclv
Apr 17 '17 at 8:25
2
2
UEFI exFAT partition? "EFI isn't compatible with exFAT and exFAT isn't backwards-compatible with FAT32"
– phuclv
Apr 17 '17 at 8:27
UEFI exFAT partition? "EFI isn't compatible with exFAT and exFAT isn't backwards-compatible with FAT32"
– phuclv
Apr 17 '17 at 8:27
2
2
No, it won't work in the real world except some minorities. People have tested it if you have read the links above
– phuclv
Apr 18 '17 at 0:05
No, it won't work in the real world except some minorities. People have tested it if you have read the links above
– phuclv
Apr 18 '17 at 0:05
1
1
There's no theory about it. This is not a universal solution nor applicable. UEFI has a set standard and does not support what you're talking about outside Apple's custom EFI environment. EFI is an app/OS that boots from UEFI. Look at a lot of the firmware updaters bootable tools out there, they all have a .efi file. (Windows uses boot.wim and install.wim on the Windows ISO file). That Mac EFI "OS" is what you're talking about, not UEFI.
– PeterFnet
Dec 6 '17 at 0:43
There's no theory about it. This is not a universal solution nor applicable. UEFI has a set standard and does not support what you're talking about outside Apple's custom EFI environment. EFI is an app/OS that boots from UEFI. Look at a lot of the firmware updaters bootable tools out there, they all have a .efi file. (Windows uses boot.wim and install.wim on the Windows ISO file). That Mac EFI "OS" is what you're talking about, not UEFI.
– PeterFnet
Dec 6 '17 at 0:43
|
show 2 more comments
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1023290%2fhow-to-do-uefigpt-with-a-iso-file-greater-than-4gb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
What you would extract is larger then 4GB currently. What specifically are you trying to burn?
– Ramhound
Jan 8 '16 at 2:01
Rufus is not the only tool for creating a bootable USB drive. Most distributions support writing the
.isofile to a USB flash drive viadd, as indd if=imagefile.iso of=/dev/sdc. There are also other tools, like Unetbootin, that might work. One more point: The partition table type (MBR vs. GPT) of the installation medium is mostly irrelevant, so don't worry about that unless your computer won't boot from your medium. (Some are finicky.) The boot mode (BIOS vs. EFI) is important when you're installing, though.– Rod Smith
Jan 8 '16 at 20:35
1
"I think it HAS TO be fat32 to work with gpt." That's a common misconception, and it is WRONG. Rufus will happily create an UEFI bootable NTFS drive (through UEFI:NTFS). You should try formatting your drive in NTFS in Rufus and see if that works. Rufus will detect if an ISO contains a >4GB file and set all the options you need to be able to boot it from UEFI for you.
– Akeo
Jan 12 '16 at 11:33
There are several workarounds. Basically it's just about creating a small FAT32 partition for UEFI and a big NTFS/ext4/whatever file system for big files. See UEFI Boot a NTFS Drive
– phuclv
Apr 17 '17 at 8:33