Easy UEFI starts with: Failed to run system API.(0x00CB0015017E0000)

In Programm are no interactions possible (various failed to run y´system API errors).

I tried to reinstall severall time and to adjust compatibility settings.

Please find attached the user.log

System: HP ProBook 450 G1
           Windows 10 Version 1703 Build: 15063.413

Any help would be apretiated.

Attached Files

  user.zip (Size: 2.62 KB / Downloads: 2)

I'm following this guide on install Windows on my Samsung T1 SSD Portable

http://www.easyuefi.com/wintousb/resourc...drive.html

However I cannot do step 7 as when i select the destination disk there is no popup window like shown below in the guide.

While attempting to Create a UEFI boot entry, this error window popped up: The system cannot find the file specified (0x0003007F03880000). And the Browser button is dimmed, so I cannot change the location to find the bootmgfw.efi file.

Is is possible and/or recommended to create a Dynamic VHDX-based Windows To Go Workspace?

I am trying to convert an existing Windows Server 2008 R2 Standard to boot via USB.  When I try to boot it after running your tool, I get a blue screen.  I am assuming this has to do with the USB 3.0 drivers, but I am not sure.  Any fixes or thoughts?

I have a new Lenovo AIO and I was able to finally get Windows 7 on the hard drive after many hours of trying to inject the usb drivers.. I'm now trying to make it portable but when it boots to WinPE to clone the drive its not loading the USB drivers (as expected). I've tried a few of the following links (https://goo.gl/yOSfgg) but I cannot locate the "Boot.sdi" or "boot.wim" in the install directory. Ive tried putting the Win10PE sdi and wim's into the path's below but it still is not recognizing the USB devices so I dont think its actually using the Win10PE files...

C:\Program Files\Hasleo\WinToUSB\bin
C:\Program Files\Hasleo\WinToUSB\x64\WinToUSB\bin
C:\Program Files\Hasleo\WinToUSB\x86\WinToUSB\bin


I was also going to try injecting the drivers myself (i have the working drivers that worked for my initial install) following this article https://goo.gl/DrcJzV but again, i cannot locate boot.wim. I've even tried installing older versions hoping it would have the file but no luck...

Where can I locate this WIM file? I'd like to either A. Inject the files myself or B. Use the Windows10 PE Files.... TIA.

Hi,

Do it is possible to use the easyuefic.exe (command line) for changing the boot order but only by knowing the name of a entry (not the index).

Exemple:
>EasyUEFIC.exe --list-efi
# Name
--------------------------------------
0 : USB Memory
1 : Windows Boot Manager
2 : HDD/SSD
3 : LAN
4 : Diagnostic Menu
5 : HDD Recovery

I want to place 3:LAN at the first. So i can use
> --top-efi --index 3

But i don't want to visually confirm the index number of LAN and it's is not always at Index:3. Hopefully, the name LAN is always the same.

So, do it's possible to use a command like
> --top-efi --name "LAN"
Or any workaround that do the same thing?

Ok, i know that it's a little bit ugly because in theory we can have multiple entry with the same name. But i can manage to have only 1 entry named "LAN", that's not a problem.

Thanks in advance and have a good day.
Sorry for my english.

Hi,

As my old USB stick was very slow I bought one of the fast GTX Voager USB stick without knowing that this stick is more like a mini external SSD as a normal USB Stick. It reports itself as disk so I read the guide on how to prepare the disk in order to use WinToUSB.

I first tried MBR mode with a small fat32 partition 100MB and a big ntfs partition but the stick always hangs at 95% of the install process (after copying the vhd file I use as starting point). It seems that it cannot create normal files to boot from. I then fiddled around and in the end (as my system runs from UEFI disks anyway) I used diskpart to wipe the disk, convert it to gep and create ESP/EFI partition and windows partition (interestingly a 128MB msr partition also got created although I did not opt for that). But here I have exactly the same problem installation stops at 95%.

Interesting thing I found out is, that once the installation reaches 95% you can not open any partitioning tool cause it hangs when trying to read the USB SSD Partitions. It's like WinToUSB somehow crashes access to the stick completely.

Best regards,

Marc

Hi,

I was unsuccessful trying to run my WinToUSB stick's image in Virtualbox so far (obviously I don't know how to correctly set it up, for example where to put the boot partition etc.).

So I though let's try the Windows To Go Upgrader because it does exactly what I need, creates a VirtualBox Image from the WinToUSB Stick. So I downloaded it and started the "check for upgrade" with a "Windows 10 Pro (x64)" GPT/UEFI WinToUSB enabled USB Stick. The process starts and creates the VM and tries to start it. At first I see the virtualbox logo and the turning dots at the bottom which everyone knows, but after about 5-10 seconds I get a BSOD saying "UNMOUNTABLE_BOOT_VOLUME". So, question is, whe isn't it able to boot? I'm using Virtualbox 5.1.20.

I would be even be willing to pay if I can boot the WinToUSB image so I can modify it. And it also seems that other people are having also big problem to boot a WinToUSB volume in Virtualbox if you look into the forum threads about WinToUSB.

Any help would be greatly appreciated.

Best regards,

Marc

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?