The only correct behavior for EasyBCD on UEFI systems, such as the new motherboards from Gigabyte, is to refuse to run. The current behavior on an UEFI system, is that it runs and does not display any errors. EasyBCD fails to read the bootloader entries, but it does WRITE TO THEM. This is the worst combination. I installed EasyBCD, ran it, and clicked on “Add Entry”. Nothing seemed to happen, but it silently wrote an entry. I clicked on “Add Entry” again, and it silently wrote another entry. I closed the program, and EasyBCD warned me that my system would not boot, but of course it was too late. Only after I read the FAQ did I figure out what was wrong. I made an emergency recovery disk, and rebooted. I was “lucky” in that I went straight to the FAQ after EasyBCD’s unexpected behavior. The two new boot entries are completely un-bootable, I hope to figure out how to delete them later. Most Windows users with UEFI motherboards do not know it. It must be EasyBCD’s functionality to check at startup, before modifying anything on the user’s system.