make a boot install of windows mount iso
copy contents onto a usb stick.

Ubunutututututu has some piece of software by whatever name they call it, that essentially does the same.

Microsoft Windows has an online service themselves that will create a usb bootable install stick.

first, I'd let Microsoft create my stick.

second, if not Ubuntutututu, then mount and copy over everything in the iso onto that stick.

IF YOUR SYSTEM IS SETUP UEFI BOOT ONLY, THEN THE USB STICK HAS TO BE A GPT PARTITION TABLE. SO THAT WINDOWS WILL INSTALL ITSELF UEFI, ELSE YOU WILL NOT GET A UEFI INSTALL STICK, BUT A LEGACY INSTALL VERSION OF WINDOWS 10.

I loaded a USB drive with E2B (Easy 2 boot) and copied on ISO files for windows and a dozen distributions of Linux. When I boot from the USB drive I get a beautiful menu from which I can select what image I want to load. I did this from a Linux machine, and it works just fine. I had to dig for the instructions, as the main page assumes you are starting from a Windows PC (there is a link to the alternate/linux instruction page).

2 members found this post helpful.

i'm weighing in on this since i just tried to use woeusb to create a windows live pe using GandalfsWindows10PE.iso which woe is specifically designed for along with regular windows iso's. i'm only running kununtu 19.10 and tell everyone for a fact when i was running both linux and 10 there were plenty of times i did not want to reboot and boot into 10 just to create a windows key, and to be honest there is no reason to have to do so. i have used woe on cinnamon, neon, and kubuntu to create my 10 meadia without issue in the past, but for some reason i cannot under kubuntu 19.10. this issue is to try to get woe to work like it's suppose to. rather the op wants to login to windows isn't the issue,they just want to create the key without leacing their linux environment. as techowned5 said it may be an issue with the op's flash drive, i know in my case it is not. i have 4 drives, 2 16gig, and 2 8gig. i can create any linux live environment on any of them without issue using either unetboot or etcher. what i normall have is the live for the os i'm actually running, a live for one i want to test, parted magic live, and the gandalf's for trouble shooting win 10 machines. all of which i've created in the past without issue under the above mentioned os's. the error code i get with woe is 512.

I think the OP and probably others have unrealistic expectations. Why on earth would any Linux programmer/developer waste his or her time making things work on windows to profit microsoft? Obviously they do as the link I posted above is a perfect example. The instructions are extremely detailed and the method works as it is what I used to put the windows installer on a usb and install windows 10. People are being lazy, want something where they can click a mouse a few times and magically have what they want.

please stay on topic. you are entitled to your opinion, but the thread is for getting help on a issue. NOT for expressing one's personal opinions.

Perhaps, then, it might be useful to NOT restrict yourself to a single tool. What would you suggest to someone who needs to avoid using or referring to WOE?

if i had another tool to suggest i would of done so. i love using linux but when it comes to usb creation tools it truly sucks. in windows it does not matter the iso rufus will create the key correctly each time. in linux for linux iso's alone the use key creator depends on which distro of linux you want on your key. woe is suppose to be the defacto key maker in linux for any iso that's for windows, including windows pe. just saw your one post might of wanted to include the link so peeps don't have to go hunting for it.

Woeusb works with a windows iso if ran from the command line with the correct options.
I believe the 512 error is the drive needs to be unmounted first.

i have tried it mounted fat, mounted fat32, mounted ntfs, unmounted fat, unmounted fat32, unmounted ntfs and no configuration works. i know it's not a issue with the drive cause if i go to put ubuntu, kubuntu, pasrted magic on it no issue, but those are done with either unetbootin or etcher. as for using woe from the command line it is a gui tool.

yes it is a gui tool, but in gui mode by default woes auto formats the usb to fat32 which won't work with windows 10 iso. The work around is to run woes from the command line per what I posted in post #4. Running woes from the command line with the options I posted in post 4 formats the usb as ntfs, installs windows 10 iso, and sets it up to boot. If you don't won't to run woes from the command line then you will have to use some other method to put the iso on usb.

Why the creators of woes didn't give the option to use ntfs in the gui mode, I don't know. Maybe the next woes release will fix this if there is one.

actually until the last 6 months or so woeusb DID create the key PERFECTLY from the gui. i know cause my roommate messed up his win 10 install and then couldn't find his install key. i went out looking for something that would actually create a win 10 key and found and used woe. the only thing with woe at that time was if you made the key from mbr it would not boot efi / gpt, and if you made the key on a efi / gpt os it won't boot mbr. maybe what you're referring to is their attempt to fix woe.

After a 2 second search, you will turn up www.easy2boot.com using any internet search engine in the world.

Along the same lines, a simple search might have presented a dozen different tools and tutorials for burning any ISO to USB using Linux.
Everything from 'dd' to this listing of useful tools: https://www.dedoimedo.com/computers/...ite-image.html.

Sorry, but my post is on topic as the post is about creating a bootable windows install on a usb. The method at the link I posted does exactly that and apparently a number of other tools suggested do also.

you just keep believing your post was on topic while the rest of us actually stay on topic. that said i'll be contacting the creator(s) of worusb today to see if they can figure out why it doesn't work the way it use to.

first don't blame the person who called you out for not completing your post. second i can't speak to what the op wants but i'm not interested in a command line program, and most of those programs including ez2boot are command line.