Open JakubFojtik opened 6 years ago
It seems once an iso image (that contains MBR?) is written to a partition, Windows cannot interpret the filesystem anymore and assume the filesystem to be broken or it contains no media. Even if the writing was correctly performed on the entire disk, windows, hence mbusb as well, can't detect any partitions if they consists of linux specific filesystem (e.g. ext2/3/4, xfs).
On Windows with some linux.iso, after Write image to disk (instead of just Install distro), the USB's filesystem is not detectable by Windows and it loses its \.\PhysicalDriveX path.
It can no longer be booted from Multibootusb's UI, and after clicking Detect drives it no longer shows there. Booting its letter address \.\E: works manually.