Hello!
I created USB bootable flash drive by USB Creator (1.png) but computer doesn't want to load with it.
Linux can't recognize it's file system (2.png), but it shows files (3.png)! It's inconceivable. Windows can't recognize flash drive recorded by this way (4.png).
The only exit it's to use UltraISO on Windows, and computer loads with it correctly.
Don't you know how to solve it?
P.S. Don't tell to run UltraISO under Wine, it's not very comfortable.
OS: Lubuntu 16.04 x64, USB flash drive: Transcend 8Gb.

Attached Thumbnails

       

I guess you mean the drive won't boot. If you're creating a bootable drive you must put an operating system on it. Usually you take a USB bootable image and use the dd command to write it to a USB drive.

So, what is it? You don't mention the filesystem type. Generally in this situation it will be FAT32 and should be recognized in both Linux and windowss (windows if it is on the first partition anyhow). You say it doesn't load but give no indication of what happens. Did you do an md5 checksum on the iso before beginning and have you tried the usb on another computer>

Is the second image before or after running the install? The third image seems to show that the installation was successful, there are lots of files and directories shown, and they wouldn't be if the entire drive is unallocated. What symptoms do you get when you try to boot from the drive? Does it even try to boot? We need more information.

There's no need to use any special "creator" tool when making a bootable USB for the vast majority of Linux ISOs on Linux. You can simply use dd:
That's it

Usb creator should usually work.

There are many ways to make a usb from linux. Just depends on how you want to use it. In your way you tried to make a usb drive that can be used somewhat like a live cd.

I find that most people try to boot off a usb choice when they should be selecting a hard drive order choice.

Reboot the machine into bios and see if you can select the "hard drive" order to move the usb up above the internal hard drive and see if that fixes it.

I'm having the same problem. I used Image Writer in LINUX Mint (17.3)_and the dongle won't boot. I used the Boot Manager and moved the Boot Sequence in the BIOS to move the USB to a position preceding the HDD.

No luck.

Any ideas?

It depends on the bios these days. I have a gateway desktop that doesn't remember boot USB first. So I have to set that manually at every boot or spam a key to bring up a boot device this time preference (F12 for that machine). It's also an early UEFI machine, so it only really does the older MBR style partitioning.

Normally when it can't find the / filesystem then the initrd line is missing from grub.cfg. Or /etc/fstab has the wrong information in it. It could also be using /dev/ names in both grub.cfg and fstab and those can be unpredictable when multiple devices are plugged in and on various "other" computers.

Yeah, this is the first time I have had this happen. This is a 5 or 6 year old Toshiba Satellite and has the Boot Select (F12) and BIOS setting. I set both to have the box boot from the USB device in both and still no joy. On this, the Boot Select matches the BIOS setting. I noticed that after changing the BIOS.

Another of those, "Go Figure!", moments.

Another thought....I may try foprmatting a bootable drive on the wife's Windows machine. That might work. This doesn't seem like it sees the USB drive on boot. The drive shows up after Mint is loaded. Strange.

If you have other high bandwidth things plugged into the usb ports it might be picky about which usb port it will boot from. Webcam, gigabit ethernet dongle, and such which might force you to use the first port on the bus/hub to get priority treatment as a boot device. If you're using a SDHC card and card reader, not all card readers are bootable, the "multi" card readers tend to NOT be bootable. And of course the card reader built into your laptop or other device tends to NOT be bootable. I've also had issues with using two of the same model hubs on one machine. Take one hub away or use two different model hubs and the oddities go away. Not that any of those are your issue.

I have started making it a habit of having only the Drive plugged in that I want to boot from, so that probably isn't the situation. When I locate the wife's VISTA laptop, I'm going to try creating a bootable stick under that OS and see what happens. That's my last shot, for now. If that doesn't work, I'll figure another approach.

"Never, never, never, never, never, never, never give up!" LOL

(excuse my sticking my newbie-nose in here... I subscribed because learning boot/iso issues)

Re: #7: "SAME problem": No, I'm *guessing* it's totally different!

(Maybe a "Moderator" could 'split' this [#7-on] to a new/separate Thread...)

Maybe what happened was: #7 [Title] matched "Similar Thread" [almost] exactly
and the "necro-post" warning is 6months (maybe 3mo. is plenty)
(Plus, OP [who now may be getting "Reply to thread" emails] didn't post solution & mark "Solved")

Anyway, 'fwiw' sorry... yea, selecting fully-precise 'keywords' is quite an 'art'...
...and|but/maybe I wish I'd learn '"*not*"' (to write [in code])

Not a problem! Search engines can be good or not so good. I searched for a product and found nothing over at a large retail site. I changed from the common name to the more technical name and it was found. Oh well!

I am still totally flummoxed as to why a USB drive, formatted with LINUX Image Writer will not boot, but when I installed WinUSB, it worked. I thought that an MBR would be an MBR! That's why I'm a Newbie here. I was booting a Windows OS, so maybe LINUX did not like that. The "square peg in a round hole" situation.

that always works for me