off topic but because of things like this I have relegated windows to the VM Gerald Klein DBA jk121960@gmail.com jk@zognet.com 708-599-0352 Arch, Gentoo I3, Ranger & Vim the coding triple threat. Linux registered user #548580 Brought to you by the Amish Mafia On Sat, Apr 30, 2016 at 12:13 PM, Zachary Kline <zkline@speedpost.net> wrote:
On Apr 30, 2016, at 5:53 AM, Murari <murari.ksr@gmail.com> wrote:
On 29 April 2016 at 00:09, Zachary Kline <zkline@speedpost.net> wrote:
I haven't updated Windows 10 in quite a while so I haven't experienced this, but have you checked to see if both the locations to which you copied the systemd-bootx64.efi are still OK? On my (HP) laptop, I have systemd's boot loader copied to both $ESP$/EFI/Boot/BOOTX64.efi and $ESP$/EFI/Microsoft/Boot/bootmgr.efi. Windows 10 does make changes to critical files through regular updates, but these are the only two files that should mess with the boot process.
Thanks for the tip. I forgot that I indeed copied the systemd EFI file to two places. In retrospect, I don’t know if the default bootx64.efi replacement was necessary. Anyway, this seems to have solved the problem.
Best, Zack.