I’m trying to use the backup in EasyUEFI free to backup the changes I’ve made to the boot order, but it seems to be stuck at 72%. Why is this taking so long? And why did it get stuck?

Attached Files

Thumbnail(s)
   

Hello guys,

I have a problem and i would like to solve it. I bought today a new usb flash drive (Lexar s75 JumpDrive USB 3.0 64 gb) and i used wintousb program.
I just wanted to install windows 8.1 to my usb flash drive. I followed the instructions. I chose .iso file then i click next. After that i chose my usb flash drive and a prompt message appeared and i click to GPT option with VHD option enabled. After that i click next and the process began.
I tested Windows 8.1 and was really really slow... so i decided to format the usb flash drive. I switched back to my main windows and i formated it.
The problem that i have now is.. my usb flash drive is very slow.
1. I use my flash drive in 3.0 usb port..
2. I have enabled in device manager > disk drives > Lexar usb > Properties Tab > Better Performance .
3. The format that i did was exFAT with 128 kilobytes allocation unit size. (I have perform the format procedure with Windows / Rufus / hp flash drive format tool)
4. In Disk Management when i choose the Lexar Usb drive, it says that it is a healthy (Primary Partition).
5. I check for bad sectors but everything is fine.



I attach an image with a test that i perform to check my usb flash drive write/read speeds. When i trying to transfer a file the speed starts with 20 Mb/s and then it drops to 200 kb/s and then back to 20 Mb/s or 30Mb/s and then again back to 500 kb/s. Please can you help me to bring back the speed of my flash drive?

Hi,

I have been using WinTo USB without any issues, then suddenly I get the error:
Failed to run system API. (0x00000015003100000)

I start the application with "run as administrator", my user is local administrator, I have stopped the virus software and added and exception to the virus scanner (alvira) for the application and I still get this error? What can I do next?

My log file is attached.

Please help - I am going bonkers!

Thanks,
Helicopter

Attached Files

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

When I use WinToUSB and create a WinToGo USB drive from a Windows 10 ISO for example, I see that a VHD file is created on the USB drive from which the OS boots. Now my question is, whether we can add a few more VHDs to that same USB drive, so that we can choose which of the VHDs I can boot up from, at startup ?

For example, I want to create a bootable WinToGo USB of Windows 10 using WinToUSB. SO I get an USB containing a VHD file.

Now I can create another such similar WinToGo on a different USB drive, That drive will also contain another VHD file.

Now, I want to add that second VHD also to the SAME [first] USB that WinToGo that I made, and I want the bootloader to ask me at startup as to what VHD I want to boot from...

Can you please tell me how I can do this ?

EDIT:

I have already seen this thread... Hoping to see more clearer steps on how exactly it can be done .. Thank you

Hi,...


I already created a Windows To Go USB drive with WinToUSB and running well thanks to your wonderfull program. But when i want to clone to HDD like in THIS tutorial, i unable to proceed with error CLONING WINDOWS ON A VHD IS NOT SUPPORTED. I think the problem come from system partition that different from tutorial.

Sorry for my English

Attached Files

Thumbnail(s)
       

hi,
recently I'd install windows 10 on HDD and its worked, now i try windows 7 x64 ultimate on same HDD, but when i try to boot it, showing error "windows failed to start a recent hardware or software change might be the cause" and show option to boot in safe mode, safe mode with network, etc, i've try all options and just got same error.
please help me to fix it  

Thanks.

la version de windows que desea instalar no coincide con la arquitectura

Hello, Guys,

I built the Windows 10 WTG (Professional Edition) on external SSD (USB3.0 to SATA3) and run it for 2 months, looks everything is good.
But I confused about disk optimized tool recently, because it shows my disk is "hard disk drive" in media type, not the "solid state drive". And looks the OS treats the SSD like a traditional hard disk to do defragmentation.

So I post a thread on other forum and try to know what happened. According the replies, I guess the rough conclusion is: if you build a WTG by the built-in tools of Windows 10 Enterprise Edition, you'll see the correct media type "Solid State Drive"; if you built by WinToUSB, you'll see the "Hard Disk Drive" like me. The point is the OS may not do the right things to the SSD drive.

I don't know wether it is a correct thought, so I post here and hope to have some help.

Anyone has any idea?

Thanks a lot for any help!

PS. Sorry, I don't mean WinToUSB is bad, actually it is a very good tools and helps me to finish WTG very easily. I just have a confused problem needs to be figured out. Thanks for the team of WinToUSB！！！

Hi, guys -

We're interested in using your command line utility to detect custom USB keys and automatically reboot to them from our application. It's written in C# against .NET version 4.5.2.

I've installed a "trial" of your Enterprise software.

When I run either EasyUEFI.exe *or* EasyUEFIC.exe from the command line, or using the application shortcut, everything is fine.

When I copy your EasyUEFIC.exe and supporting DLLs to our application's folder and set up a new Process to spawn for it, I get a popup saying "EasyUEFIC.exe - Application Error" and "The application was unable to start correctly (oxc000007b). Click OK to close the application." And sure enough, it quits, even before producing any sort of log.

In general, I'm doing this:

Dear Admin!

When installing win 10 on the HDD to 95%, there is a error message: "Failed to run system API (0x0000001500430000)".

Please guide how to fix. Thank you!

Im using WinToHDD Professional v 2.7 Release 1 (Sep 19 2017) , here is log 


  user_log.zip (Size: 37.94 KB / Downloads: 6)