this is my new kingston 3.0 usb that i just bought today and it not working.I have another kingston 2.0 one but same error. I thing it windows problem, i will test it later.
EndlessInstaller20170704_23_24_04.log (33.8 KB)
Kingston 2.0 EndlessInstaller20170704_23_28_00.log (81.7 KB)
Hey @teamza555666 hows it going ?
I may be wrong but theres an application called Etcher which is well maintained and been going for a while now as an ISO installer.
It’s amazing how ‘easy’ it is to install -almost fool-proof.
While it set up the USB I actually wondered if I’d done something silly and done a school-boy error -which I hadn’t.
@mhall119 forgive me if I’ve stepped over the mark (on recommending something outside of the standard ISO-boot-loader) but this guy has been waiting for nearly five hours, so I thought I’d help him out. 
@teamza555666 I understand your fustration and if Etcher works, please get back in touch & share your story below, thanks.
What appears to be happening is windows seems to think you have two drives it can’t read, due to being a non readable filesystem(to windows). If you’re sure you have no important data on F and G, you could use windows built in partition manager to wipe both drives(if you’re sure they’re really just the usb drive with no data) and then when you remove it and plug it back it, you should have windows recognising a single drive that needs to be formatted for windows.
Thank for reply. I will try etcher and other solutions when I back home. If anything happens I will let you guy know.
This is a known bug in the Windows tool, which I haven’t figured out yet despite it being pretty common 
If you can get an ISO and use Etcher to write it to USB, that should work.
@jimmybot @wjt
i thought it was .net framework 4.7 problem. I remove it and manage to pass 2% progress now i geting new error.
EndlessInstaller20170705_17_13_35.log (127.2 KB)
EDIT: so weird. now it the same error it cant write 512. and i dont know how i manage to do that.
EDIT2: error that i cant write 512 maybe i forgot to format it to FAT32. and is that error code mean my usb is out of space (8gb)
I don’t think .net 4.7 is relevant: it’s a pure C++ application. I think it is a race condition.
This new error:
17:14:47 - EndlessUsbToolDlg.cpp:2601 CEndlessUsbToolDlg::UnpackImage C:\Users\TMTEAMZ\Downloads\eos-eos3.1-amd64-amd64.170520-055517.base.img.xz -> E:\endless\endless.img^M
17:14:47 - EndlessUsbToolDlg.cpp:4252 CEndlessUsbToolDlg::GetCompressionType C:\Users\TMTEAMZ\Downloads\eos-eos3.1-amd64-amd64.170520-055517.base.img.xz^M
17:14:47 - EndlessUsbToolDlg.cpp:2585 CEndlessUsbToolDlg::UnpackFile^M
17:14:47 - Operation OP_NEW_LIVE_CREATION(14) - unpacked 64 KB/1.6 GB^M
17:14:47 - unsupported check; not verifying file integrity^M
17:15:01 - write^M
17:15:01 - write error (errno: 28)^M
17:15:01 - EndlessUsbToolDlg.cpp:2625 Error unpacking image (GLE=[112])^M
17:15:01 - EndlessUsbToolDlg.cpp:5076 Error unpacking image to USB drive (GLE=[112])^M
17:15:01 - EndlessUsbToolDlg.cpp:4755 Error on CopyFilesToexFAT (GLE=[112])^M
17:15:01 - CreateUSBStick exited with error.^M
errno 28 is “No space left on device.” But your USB stick is 7.2 GB (7748976640 bytes) according to the log. The extracted size of the OS image 6212612096. Can you check how big the exFAT partition (named “eoslive”) is on the USB stick after this error?
eoslive is gone after installer error,but i know that Disk 2 partition 1 is eoslive
i try to capture image before eoslive gone and they is only folder name endless and endless.img(note that i capture before it gone so file size is not correct.)
As long as your solution helps him and you’re willing to support him through it, I’m happy for community support 