I'm a die hard Linux user, and have been for many many years. The closest I get to Windows is in VMs, and usually only boot those to update them.


Now, I have some (non-PC) stuff that needs firmware upgrades that simply cannot be done from a VM, so I figured, why not just bung Win 10 on a USB HDD to get going.


I do hold a valid license for Win 10, so that's not an issue.


The ISO I have is 4.7Gb, and whether I try k3b or xfburn, they both see blank DVDs as 4.4Gb, and I don't know how to change this (I understand the reasons).


But not a problem, stick it on a 16Gb USB flash drive, which has plenty of room. I figured balenaEtcher would be ideal.


So off I went. Etcher immediately saw what I wanted to do, and popped up a message suggesting that I use WoeUSB instead.


So now I am, and off it goes.


But how jolly polite of Etcher.

It is! I had the same issue. I think I used Woe USB as well and it creates a valid Windows 10 boot thumbdrive, using grub I believe, which I found amusing. Figures that Microsoft needs some convoluted process to create a bootable thumbdrive from the ISOs THEY provide for free. Of course everything Microsoft does is convoluted so I am not surprised...

Hi,

> The ISO I have is 4.7Gb, and whether I try k3b or xfburn, they both see
> blank DVDs as 4.4Gb

This might be simply the difference between merchants' GB (1000*1000*1000)
and programmers' GiB (1024*1024*1024).
A usual DVD has 2295104 blocks of 2048 bytes = 4,700,372,992 bytes.
In programmers' GiB this is 4.3775634765625, rounded 4.4 GiB.

So if the ISO has less than 4,700,372,992 bytes it would fit on a DVD-R,
DVD+R, DVD-RW, or DVD+RW.
The only single layer DVD type that is smaller would be DVD-RAM, where the
size depends on formatting parameters.

Have a nice day

Thomas