New
#51
It does not matter if you put the assign command before or after the active command.
When you mount the ISO file, all the files and folders you need are visible. Just select all, copy and paste.
Query for others who use Rufus to create a bootable Win10 flash drive
-
-
New #52
Yeah. I'm still struggling to get my head around the difference between disk, partition and volume...i.e if in the future sometime I wanted to assign a letter to a removable flash drive do you assign it to the drive, the partition or the volume...confusing?
I noticed that Navy didn't type in the full command but like you I'll probably type in the full word so that I don't mess up. I read up a bit on Diskpart online apparently the first three letters of each word is sufficient though e.g cre par pri
-
New #53
-
New #54
Hi Cerberus, as you probably know..yes mine is a UEFI system. In order to create a bootable Windows 10 USB flash drive Navy has shown me how to use Diskpart to clean the USB flash drive and then create a new primary partition and then Format in Diskpart. There are loads of other websites showing Navys same instructions for creating a bootable USB flash drive. Are you saying none of that is necessary? You appear to be suggesting the same as Chappie did above ...to Format the USB flash drive using Windows File Explorer. What about all the Diskpart stuff?
-
New #55
Hi, sportsfan148. Hopefully @Cereberus doesn't mind me giving you input. Cereberus describes all that's needed for a UEFI boot of the flash drive. If you additionally use diskpart or another utility to mark the flash drive "active", this will enable the option to boot the flash drive in MBR/Legacy mode.
Cereberus gives the minimum needed for UEFI boot.
NavyLCDR's instructions, OTOH, cover many bases. This works to clean off any pre-existing format (NTFS being common for flash drives as sold) and then sets it up to be bootable either UEFI or MBR/Legacy - The latter needing to see an "active" partition.
Hope that helps clarify.
-
New #56
Thanks Word Man. That confirms what I thought. NavyLCDR was giving me the complete diskpart instructions in case my USB flash drive might have problems because of other methods that Ive used before i.e Rufus. Rufus would have left a GPT partition on the drive so the method Navy showed me would have converted the partition back to MBR. Diskpart being a much more thorough way of ruling out having any problems.
I wasn't aware though until Cerberus and Chappie pointed it out that in the case of a UEFI system a Windows File Explorer FAT32 format was sufficient..although obviously the partition structure would have to be correct. I was under the impression that the Diskpart method was standard practice. Wouldnt you say though that the Diskpart method is an extra step worth taking each time I create a bootable Windows 10 flash drive? I'll probably download a newer version of the Windows 10 ISO later in the year onto the same drive USB flash drive..wouldn't it be safer to follow the Diskpart procedure again on the drive so set it up fresh again?
-
New #57
You can mark a partition active from disk management. Diskpart is not needed for flash drives as a rule as flash drives normally only have one partition. In fact since FCU, you can add or delete multiple partitions from disk management.
This makes use of diskpart pretty redundant really in most cases with usb flash drives.
-
New #58
I'm glad I could help, sportsfan148.
The diskpart procedure is a "standard practice" (IMO) in the sense that it's quite broad in its applicability and failsafe given the number of different systems that various users reading it may have. Of course, as someone mentioned earlier, you need to be a meticulous typist. :)
Each time you create a NEW bootable flash drive, the diskpart method would be advisable (unless you know the drive is already FAT32 and active, as applicable). However, doing it over again to that same flash drive would perhaps be overkill.
Note, you aren't downloading the ISO directly to the flash drive but mounting it and then copying and pasting all of the files shown in the mounted ISO to the flash drive.
It should suffice to simply delete all files on the flash drive and then copy the new mounted ISO contents to the (already prepped but now empty) flash drive.
@cereberus - understood. I just wanted to clarify the difference between your instructions and NavyLCDR's. I think the route taken will be up to the individual's preference (and perhaps manual dexterity).
I can't speak for NavyLCDR but I would imagine that, given his career field, redundancy may be highly valued.
-
-
New #59
Sure but it is worth noting that disk management has undergone some changes, now,coping with multiple partitions,on standard flash drives. 1703 CU introduced ability to recognise multiple partitions,on standard flash drives, but disk management lagged behind (still only handling one) necessitating use of diskpart. However with FCU 1709, disk management can now handle multiple partitions on flash drives.
@Kari made a significant point in one of his posts ie the install.wim file is now getting close to the maximum file size limit of 4GB for fat32 formatted drives.
IIRC, Rufus can handle larger install.wims by creating two partitions ie a small boot fat32 partition and a larger ntfs partition.
Doing this in diskpart or disk management might be possible, but iirc, Rufus can handle this more elegantly. @Kari can probably elaborate better than I can.
-
New #60
Thanks, I wasn't aware of that up to this point.
This will come in useful for my 128 GB flash drive to set up the (Macrium) bootable rescue and backups storage - it's already that way with FAT32 to boot and the rest NTFS on an external USB HDD of mine but it may be more convenient (or redundant :) ) to set up that flash drive through Disk Management as another layer of protection - I'll give it a go and see what like I have.
Quote
Related Discussions
