You're most welcome Nikolay.
I have tried both methods: rufus latest and manually for installing Windows 7 x64 on 2 or 3 laptops (samsung, toshiba and hp) with uefi and secure boot activated. None of them works, it gives me the message that secure boot signature failed.
With Windows 8 x64 everything is fine.
But in some laptops enabling UEFI over CSM or Legacy bios, it enables automatically Secure boot. So, it's not possible to install Windows 7 over UEFI in those configurations, right?
I will double check tomorrow with the stick I've created based on this tutorial on a laptop with UEFI.
Thank you for the info.
Thanks again, Shawn. Does Rufus handle the .efi file mod needed for Win7 x64?
Yep, Rufus works for Windows 7 UEFI as well.
OK, so over here I got a Windows 8 x64 Pro ISO of approx 6,4GB and whenever I want to create a bootable USB Flash Drive (UEFI), rufus tells me that the file size cannot exceed 4GB because of the FAT32 restriction.
What do I do in this case? Formatting the flash drive in NTFS won't do anything since my BIOS doesn't even detect the USB Flash Drive. An answer asap is much appreciated.
That's because it's x86 + x64 in one ISO
Any way to seperate them?
Actually, Microsoft did release official Windows 8 ISOs that had a file that was > 4GB, and thus incompatible with USB UEFI boot.
One of the Windows x64 8 developer preview was one of those. Thus it's just not an issue for unofficial ISOs. And I think there exists other MSDN ISOs that have > 4GB wim files, though I may stand corrected on that.
Thus, we've got some choice on who to place the blame on:
- Microsoft, for designing a filesystem (FAT32) that they should have realized right from the start, would end up being too limiting too quickly, due to its 32 bit nature, even more so as they designed FAT32 to overcome the limitations of the previous FAT filesystem.
- Intel and the UEFI committee, picking FAT32 as the filesystem of choice for UEFI bootable partitions, despite being acutely aware that UEFI had to work with 64 bit and large files.
Considering that Intel & co. managed to waive the licensing agreement for the use of FAT32 (see here), it's hard to believe that they had much of a legal incentive for using FAT32, when they probably could have stricken a similar agreement for either exFAT or NTFS, none of which suffer from the 4GB limitation. exFAT was actually begging to be used for that purpose, and Microsoft was also promoting it, so why they didn't go exFAT is a major mystery. Or, if they didn't want to fall into a a Microsoft licensing agreement, they could have settled on using the more open UDF filesystem, which is designed for more than optical media, and works equally well for USB flash drives.
- Microsoft (again) and others, producing ISOs that they know have no chance to be bootable from USB, due to the presence of a >4GB file. They probably could devise a way to split wim's into <4GB chunks if they wanted to.
Of course, there's also the possibility that Microsoft may have required a more constraining licensing agreement for the use of either exFAT or NTFS in UEFI, maybe because they got annoyed that their extortion scheme for FAT32 licensing got rightfully shot down initially (though, without insider info, it's difficult to do anything but speculate on that).
Anyway, what this all means is:
- There's nothing Rufus can do right now, about a limitation that is purely between an UEFI design decision and a Microsoft filesystem limitation.
- If UEFI ever decide to pay heed to how their decision to go with FAT32 is actually inconveniencing users, they may decide to add support for UDF (or exFAT), alongside FAT32, for bootable partitions. Right now, I am not aware of any steps having been taken in that direction, and even if that was the case, this won't mean squat for current UEFI firmware implementations, as vendors aren't going to spend time retrofitting them for UDF/exFAT support.
- Maybe there is some arcane way to fool an UEFI system into treating an UDF formatted USB Flash drive as optical drive, in which case you could get away with using UDF instead of FAT32. Outside of someone showing a verifiable proof of concept, I wouldn't spend too much time on that though.
All in all, it looks to me like the only way you currently have to boot an EFI ISO with a >4GB file is to burn it, and get your hands on an optical drive...