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?

Doh! Stupid me accidentally formatted what I believe was the EFI partition. I had to format the partition again as FAT32 before it would let me reinstall Windows 7. The problem now is that my dual boot for Windows 10 is no longer listed at boot up. The partition is healthy and the drive letter D shows up under My Computer and all the data is still there.  I was hoping this software would help with this.

I tried rebuilding the EFI system partition by selecting the Windows 10 (second partition) instead of the Windows 7 because I don't have the media for that. But it gave "Failed to run system API. (0x0780001500DF0000)"

Attached is the user.log.

Any help or ideas how to restore the second OS option is greatly appreciated! Thank you!

Attached Files

  user.zip (Size: 3.98 KB / Downloads: 3)

hi gurus

how can i use wintohdd to create a system image, for recovery use?

TIA

On my PC I have 3 Linux: Kubuntu, Linux Mint and opensuse, and the Bios NVRAM bootmenu shows Windows Boot Manager, ubuntu and opensuse. Kubuntu and Linux Mint both install to the \EFI\ubuntu\ folder, which means I get the bootmenu of the last one installed of the two. I would like to be able to choose either of them, just like I now can choose the opensuse bootmenu.

I copied the \EFI\ubuntu folder and renamed the copy to \EFI\mint, and edited its grub.cfg to show the Mint partition's UUID and gpt-number. Then in EasyUEFI I created a "mint" entry and gave it the path to \EFI\mint\grubx64.efi. When rebooting "mint" does show up in the NVRAM bootmenu, but choosing "mint" starts the Kubuntu bootmenu. Please advise!

Successful installation with version 3.4  http://youtu.be/47Tk9Oeuxfg and https://goo.gl/3AkWW7