Windows 10
-
@Mike-Ralston Why do they modify the filesystem?
-
@scottalanmiller A PC can't read an ISO from a USB as a bootable file, you have to pull it apart into another format.
-
@Mike-Ralston said:
@scottalanmiller A PC can't read an ISO from a USB as a bootable file, you have to pull it apart into another format.
Ah, you are right. The Windows 7 USB utility (the one right from Microsoft) puts NTFS onto the USB. It does a file system conversion of the ISO. How bizarre.
-
@scottalanmiller said:
@Mike-Ralston said:
@scottalanmiller A PC can't read an ISO from a USB as a bootable file, you have to pull it apart into another format.
Ah, you are right. The Windows 7 USB utility (the one right from Microsoft) puts NTFS onto the USB. It does a file system conversion of the ISO. How bizarre.
So far as I know, that's the only way to do it at BIOS level with a USB?
-
@scottalanmiller Rufus has become one of my new favorite utilities for creating bootable USB drives, for the very reason that @Mike-Ralston explained.
-
Correct - to install from a USB stick you have to use a utility to pull the ISO apart and put it on the USB.
You can't use the Windows 7 USB maker tool because it only creates a NTFS filesystem on the USB Stick.
If you are booting from UEFI mode (not legacy mode), you must use FAT32 as UEFI won't boot from NTFS.
During the install the boot partition is 300 megs of FAT32, and the system partition is NTFS.
Believe me I know - I spent 6-8 hours digging around trying to figure out why I couldn't get Win8 on my new Thinkpad Yoga S1.
In the end I used Rufus, pointed to the ISO (which changes the default from FAT32 to NTFS), then change it back to FAT32 - click make drive - done.
-
@Dashrender said:
Correct - to install from a USB stick you have to use a utility to pull the ISO apart and put it on the USB.
You can't use the Windows 7 USB maker tool because it only creates a NTFS filesystem on the USB Stick.
If you are booting from UEFI mode (not legacy mode), you must use FAT32 as UEFI won't boot from NTFS.
During the install the boot partition is 300 megs of FAT32, and the system partition is NTFS.
Believe me I know - I spent 6-8 hours digging around trying to figure out why I couldn't get Win8 on my new Thinkpad Yoga S1.
In the end I used Rufus, pointed to the ISO (which changes the default from FAT32 to NTFS), then change it back to FAT32 - click make drive - done.
That seems really odd.
-
@Dashrender said:
If you are booting from UEFI mode (not legacy mode), you must use FAT32 as UEFI won't boot from NTFS.
I haven't had this issue, I can boot from UEFI into a NTFS configured drive. Possibly a special UEFI designed around that, I have no idea.
-
@Mike-Ralston said:
@Dashrender said:
If you are booting from UEFI mode (not legacy mode), you must use FAT32 as UEFI won't boot from NTFS.
I haven't had this issue, I can boot from UEFI into a NTFS configured drive. Possibly a special UEFI designed around that, I have no idea.
Exactly.
The UEFI specification explicitly requires support for FAT32 for EFI System partitions (ESPs), and FAT16 or FAT12 for removable media;[20]:section 12.3 specific implementations may support other file systems.
http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Disk_device_compatibility
