USB flash drive --assign drive letter back to dynamic from static

I'd assigned my test USB the letter X: before the test. After using Diskpart it got (my usual) dynamic letter F: and when inserted with another USB already using F: it got G:

Hi,

Is a partition the same as a volume?..bearing in mind that I will have set up a new simple volume on the USB flash drive.

No. But the partition on the USB drive will be the same as a volume in this case.
If you do as @Bree has shown in Diskpart W10 will then assign a drive letter dynamically.

Cheers,

Ive just had a thought. If I'm using the flash drive for creating bootable Windows 10 USB flash drive installation media will it make any difference what the drive letter is? My PC has C: (the system drive) and D: (DVD drive)...that's all. So every time I insert a flash drive it uses E:
I'll be downloading the ISO using Media Creation Tool. Then, using Rufus with the ISO to create my bootable USB flash drive. I realise Rufus will format the drive again so will that revert the drive letter back to dynamic anyway?
I don't like messing with things I don't fully understand that's why I prefer drive letters to be left at default because I don't know if changing them can cause me problems. Especially as this flash drive is going to be used to clean install Windows 10 not just a PC Reset. I want to be sure I don't have any more issues after the way the Media Creation Tool messed things up. That's why I don't know what drive letter to choose when I have to create a New Simple Volume on the drive because it just shows it as unallocated space at the moment and I know that part of the process is having to Assign a drive letter. Should I just select the letter E: or something else?
Sorry to trouble you all again. You've all been brilliant in helping me. Its just all above my knowledge level

Caledon Ken said:

If this is for Bootable media then it doesn't matter. You tell the system which drive to boot from, they won't have letters.

Not sure why you are using Rufus. The Media Creation Tool produces a full function, bootable device in the right format. It was designed so no other tools or steps are needed.

Once the tool creates the key you can boot from it or you can do in place repairs by navigating to key and double clicking setup.

Ive always used the Media Creation Tool in the past. Earlier in the week I used the Media Creation Tool to do a clean install. Everything went fine with the download. After the two hour download the Media Creation Tool automatically started to create the media. Everything working normally so far..then suddenly at 50% a screen popped up with an unexpected error message Error code beginning 0x80004005. That was it I had to stop there.
After searching the net it seems that other people have had the same issue after the Fall Creators Update...with the installation stopping at 50%. After contacting Microsoft Chat Support they didn't offer any suggestions that worked either. When it stopped at 50%..it was creating the media. It must have been formatting/partitioning the drive etc because that's what has left me having to ask all these questions. Ive had to go into Disk management which Ive never had to use before to sort USB flash drive out. That's why Ive had to ask loads of questions this week. My USB drive was unusable..no drive letter, all the space on it was unallocated..basically it was totally blank

sportsfan148 said:

...After the two hour download the Media Creation Tool automatically started to create the media. Everything working normally so far..then suddenly at 50% a screen popped up with an unexpected error message Error code beginning 0x80004005. That was it I had to stop there.... My USB drive was unusable..no drive letter, all the space on it was unallocated..basically it was totally blank

Caledon Ken said:

Strange. I used Tuesday night on an old flash drive and it worked flawlessly. I going to have a read on that error, thanks for posting.

It's not new for the FCU. That error code has been around since the first release in 2015 (including the USB ending up 'unallocated'). Apparently one possible cause is that the USB had GPT rather than MBR partitioning before trying to use it with the MCT.

https://answers.microsoft.com/en-us/...5dee7ec?auth=1

Caledon Ken said:

Strange. I used Tuesday night on an old flash drive and it worked flawlessly. I going to have a read on that error, thanks for posting.

How big was your key?

The key is a Sandisk 16GB