Hello,

i saw in the changelog that some releases specifically add support for a new version of windows (e.g. for example version 5.8 add support for windows 20H2).

What kind of improvement are done to the sofware with these new version (for example 5.8) compared to the previous ones (for example 5.6) for the process of cloning an existing windows 20H2 installation? 

The improvements are confined to the wintousb software itself or some improvement are also applied to the resulting cloned portable Windows?

Thanks

I have used WinToUSB to clone Windows 10 home to an external SSD with USB 3.0. I find overall performance to be superior to that of the computer from which it was cloned  Initial bootup is much quicker, as is waking from “sleep.”  Also, it feels like there does not seem to be as much background junk going on. The clone USB seems equally as speedy on a different computer from which it was cloned. I would like to understand why this is happening. My imagination?  Any thoughts?

EasyUEFI starts with the error; Failed to run system API.(0x00CB0015017E0000)

After that any attempt to use the program results in the same error. I see this was an issue three years ago. Has anything been done to resolve it in this time?
This is occurs using an Asus Windows 10 installation which has been kept updated I've attached the log file 

Attached Files

  user.zip (Size: 24.03 KB / Downloads: 1)

Hi
I'm trying to install windows to go on a SanDisk Extreme PRO USB 3.1 256GB Drive
WinToUSB Does not report any errors however when I boot the USB it shows a Black blank screen no windows logo, nothing
However when I resize the NTFS partition of the drive to less then 120 GB the Drive boots up
Please help I'm very confused
I'am using the VHD method to install windows to go

I would like to use Windows 8.1 x86 and Windows x64 on the Same USB 
Is it possible to dual boot both operating systems using WinToUSB ?

so everywhere says i have a UEFI base system . i checked in the Sysinfo and log text 
i even disabled CSM in bios but i still getting the error that you dont have a UEFI system 
can someone please tell me what is happening? 
i searched couple of times on google but didn't found much

I am a registered user of EasyEFI Enterprise.
After the update to 4.2, if I try to rebuild the EFI I get this error while rebuilding

Failed to run system API.(0x.000000150310000)

Please help!

I wanted to backup my PC Windows from a bootable Acronis drive. It failed because my PC partitions have Bitlocker encryption. I then tried to make a new pure windows install with my paid WinToUSB (Version 5.6 Release 1 Build from August 10 2020) on an external USB hard disk to install Acronis to it and open the encrypted PC partition with Bitlocker from this external Windows. But it did not work:
WinToUSB did not write any files to the USB drive only the folder and file structure. The progress indicator remained at zero all the time. I tried to install Windows from my notebook to and it was the same. One error message was that WinToUSB could not extract files from the WIM file. The source ISO was downloaded freshly from Microsoft in both cases.
I used two versions of Windows-ISO, two hard drive enclosures, two 250GB hard drives, two differrent computers both only running Windows Defender as antivirus software (I had to kill Acronis Protection).

But when I ran WinToUSB from my WtU-copy of my main system (on an external SSD) suddenly I could write an windows installation on to a external USB hard drive, including a working percentage info. (Unfortunately my first attempt for this windows pure thing did not boot properly and crashed while still in boot.)

What went wrong?

Hello!

I use Win10 2014 on a 1 TB SanDisk Extreme Portable SSD. The installation work quite fine and fast, but when I start a VM in VMware Workstation 15.5.6 build-16341506 the host system shows a high CPU load (the VMware Workstation VMX consume the CPU) in idle and gets under load much higher (the same VM on the same host with a default Windows installation performs smoothly and consumes 10% of the CPU). I tried the WinToGo installation on different hardware platforms all BIOS/UEFI settings for virtualization are on. I assume there are some registry keys in the WinToGo installation which makes the life of the hypervisor difficult.

THX

I successfully got Bitlocker running on my main W2G drive with Bitlocker Anywhere after I tried it without success with the Microsoft built in Bitlocker version. But if I upgrade my W2G drive by writing it anew with my system partition in a few weeks, is my license lost with the old overwriten W2G partition or is it dongled to the specific SSD and can be installed anew on this USB SSD as long as I do not change the physical SSD?