Windows 10: Windows 10 ISO: file system question

Hi,

I don't want and I never used the "media creation tool".

I Always donwload the ISO and then I usually put it in a dvd and in some pendrives.

But, I Always have some doubts that I want to clarify forever, if you can help me.

We have a WINDOWS 10.ISO (latest version).

If I am correct:

For LEGACY bios just COPY the ISO contents into the pendrive using NFTS and MBR.

For SECURE BOOT and UEFI bios just COPY the ISO into the pendrive using GPT and FAT32.

Said so, a program such RUFUS should be useless.

Please, tell me if I am right or correct me. I want to understand that forever.

PS: if someone use the Media Creation Tool, how this tool knows if the target is LEGACY or UEFI??? What kind of FS will use the tool itself??? It will pass the secure boot too?

:)

 

Question about win 10 ISO File.

You will get the very Latest version available.

 

Question about win 10 ISO File.

I want to download the latest build of win 10 ISO. Does this link provide

https://www.microsoft.com/en-us/software-download/techbench latest build of ISO?

Like currently the latest version of win 10 is 10586.318. So will get this version from the above mentioned link or any previous version.

 

A ISO is basically a disk image and must be written to the device by the correct software copying the contents isn't the correct way of doing it as it needs to write the correct boot sector

 

In this forum, in the last, someone said me that a copy (for gpt uefi fat32 as i remember) was enough.

I am not sure but once it worked without any tools (just copy).

Maybe a Rufus is needed only for ntfs mbr legacy?

I'd like to understand more of this just the have a precise idea. Also need to understand how the WMC tool works.

 

1) use fat32 in all cases.

2) the media creation tool creates a usb drive suitable for either install. It does it automatically - if drive is mbr formatted, it installs as legacy bios, if gpt - uefi. MCT really is easiest way to do it without thinking.

3) it works with secure boot on but in a hyper-v vm, you may need to turn it off.

 

Format the USB flash drive as FAT32. Mark the FAT32 partition on the USB flash drive as Active. Copy the files in the ISO file to the USB flash drive. It will boot in both Legacy BIOS and UEFI, secure boot enabled or not. The Media Creation Tool does not need to know if the target is UEFI or legacy BIOS because an Active FAT32 partition is compatible with both.

There is no need for RUFUS. The commands in diskpart are:

diskpart
list disk
select disk # <- replace # with the disk number of the usb flash drive
clean <- this will erase the flash drive
create part pri
format fs=fat32 quick
active
exit
exit

 

I always use command assign after format as that forces a mount point for a drive letter. I have found some sytems or drives (no idea which) do not automatically assign a drive letter. Should not happen but something causes that now and then. Never had issue since applying assign command.

 

I also do assign, active etc. It's just habit/routine for me now. I hardly ever use the MCT, as I usually use my MSDN ISO's and just use diskpart.

 

Actually I rarely use active as I always use UEFI where it is not needed, but as belts-and-braces, fine.

 

I have a mix of both, my older desktop PC's are legacy and my newer laptops are UEFI. My ASUS laptop will actually do a UEFI install from an NTFS formatted thumb drive. It's just easier to do all my thumb drives the same way and not worry about them working or not working. *Wink

 

I didn't understand this reply to NavyLCDR.

If I am correct, basically, you tell me that:

1) ISO to be extracted
2) format USB as FAT32
3) copy ISO extracted to USB
4) mark USB as active

Those commands I can do with diskpart but also with disk managment of Windows or 3rd party software of partitions (is right?) for people that don't want to use DOS interface.

Assuming what I wrote above is correct, I didn't understand about the "command assign" after format.

 

Formatting the partition with the format command should result in it getting a drive letter (such as E:\) automatically. The command assign will give it a drive letter if that did not happen automatically.

 

diskpart
list disk
select disk # <- replace # with the disk number of the usb flash drive
clean <- this will erase the flash drive
create part pri
format fs=fat32 quick
assign
active

exit
exit

 

Hi,

I worked a little with Disk part because I wanted something very easy, fast and without any other software to use.

I think that using Disk part is though a little Dangerous. In my case, when I select the disk I don't have the LABEL of the disk but only the size and the position. Also, is easy to wrong something in a command interface.

I want only to ask that if I do these things with the simply Disk management of Windows I will achieve the same result.

I mean:

- DELETE the partition of USB
- CREATE IT
- FORMAT FAT32
- MARK as ACTIVE
- COPY ISO (extrated files) inside

This will let me to obtain a WORKING usb pen drive that wil be useful for LEGACY and for UEFI even with SECURE BOOT on?