Re: Win10 Upgrade makes ArchLinux inaccessible?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



> On Apr 30, 2016, at 5:53 AM, Murari <murari.ksr@xxxxxxxxx> wrote:
> 
> On 29 April 2016 at 00:09, Zachary Kline <zkline@xxxxxxxxxxxxx> 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.



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux