Remotely I often have to deal with reinstallation and more often there is not a boot stick
So in this program, I found a great solution. Thanks.  
But there is one caveat, during the reinstallation on the current system at the end of the first part of the installation the computer shuts down as there is checked.
So my question is how to make so that it was not switched off and rebooted and continued the installation?  

Hi,

Windows installation from ISO file to USB is failing with the following error message:

Failed to run system API.(0x03F0001500A60000)

This happens right when it reaches 100%. I have tried twice.

Please see the attached log file.

Thanks.

The other day, I installed WinToUSB for the purpose of being able to use windows on other macs without bootcamp. The process was smooth, I put windows 10 on a partition of a large external hard drive that I had, and when I restarted it and opened up that copy of windows on my mac, everything worked pretty well. I installed the driver for the network adapter, and I could access google, etc.

However, when I plugged in the hard drive to another mac, I was unable to connect to the wifi. This mac is about as old as mine, so I thought I should see no difference, yet when I look under the devices for the network adapter, it tells me that it is unable to start, and so I can't access the internet on windows for that laptop. I tried a bunch of things, like un/reinstalling the driver, but nothing seems to work and google is quite sparse with information on this. If anyone has any answers, that would be great!

The first laptop, mine, is a mid-2014 macbook pro with bootcamp, which is what I used to get Windows on my hard drive
the second laptop is an early-2015 macbook pro, which is very similar, hence my confusion as to why it's not working.

Hi!

I've created a Multi-Installation USB with WinToHDD. I boot the PC from the pendrive (legacy from boot options) and choose 32bit or 64bit. When I click on the New Installation, it says:

Failed to get operation system information. (0x0000009202C70000)

It happens regardless of what iso is on the pendrive (Windows 7,8), the same message if there aren't any iso files. What is the cause of this error?

A big change on version 1703 is that windows can now read multiple partitions on a normal flash drive.

Wintousb 3.5 will now install a uefi install on a standard flash drive - no longer needs special drives with hard disk bit enabled.

How do I get a bootable USB stick created?

I keep getting the following error:

Failed to run system API.(0x03F0001500610000)

Here is my Error Log file (user.log):

https://www.dropbox.com/s/y9xeewzqz00hozo/user.log?dl=0

Please help me.

Thank you.

Attached Files

Thumbnail(s)
   

  user.log.txt (Size: 123.58 KB / Downloads: 2)

Am Attempting to install from an ISO image to a Samsung 128 GB Evo Plus Micro SD. Have already succeeded with a San Disk 32 GB Micro SD but now only get Unsupported File system.(0x0570009004590000) error. Have tried pre formatting to FAT32 and NFTS. Have tried reducing the primary partition on the card to 32GB - all to no avail. Any suggestions?? The really annoying thing is that after the error EaseUS shows the entire drive formatted as a WINTOUSB drive!

Hasleo Data Recovery is a free, powerful and reliable data recovery software to recover lost files due to unexpectedly deleting, formatting or partition loss.
For more information please visit:
https://www.hasleo.com/win-data-recovery...overy.html

I booted to USB w/EasyUEFI and tried to do the Rebuild of the EFI Partition but after it runs for 10 seconds or so it stops with the "Failed to run system API" (0x0000001500DF0000) error message. Any idea why this is happening?

The reason I'm trying this: I have an Acer Aspire Switch 11 with Windows 10 and 128GB Flash or SSD (not sure which). I made the mistake of splitting the C: drive into 2 partitions. I forgot you can't do that like the old days (pre-Win 8) because of the different boot design. After splitting the C: drive I could no longer boot up to Windows 10 and all the Auto Recovery fixes (Win 10 USB boot thumb drive) as well as numerous Command Prompt fixes to fix the boot problem don't work. I used a Paragon HDM boot disk to merge the C: drive and extra partition back together but I must have jacked the boot system on the EFI and the C: drive. I was hoping this EFI Rebuild might fix my problem. The 100mb EFI partition is still there (to the left of C drive) as well as the 500mb Recovery partition (to the right of C drive). I'm trying to avoid doing a complete Win 10 re-install and I'm not even sure that will fix it.

Hello,

When trying to upgrade from Windows 8.1 to 10, I get a window saying "Something went wrong" with the error code 0x8007001f.

When I press retry, I run through an install while stil in Windows 8.1 but then I get an error on the Windows 10 setup window that says
"Sorry, we're having trouble determining if your PC can run Windows 10. Please close Setup and try again.

Does this have to do with the fact that my USB drive is a removable drive rather than a fixed/local one?