[arch-general] Win10 Upgrade makes ArchLinux inaccessible?
Hi All,
So my laptop upgraded to the latest version of Windows 10 recently, and this seems to have undone the hack of replacing the default bootx64.efi file. That is, the file is still SystemD’s boot loader, but somehow I’m back to only being able to boot Windows reliably. Has anyone else seen this particular frustration with an upgrade? I note that my laptop came with Windows 10, so this was just an incremental update as far as I now.
Thanks for any ideas. This is kind of maddening. Best, Zack.
2016-04-29 0:09 GMT+02:00 Zachary Kline zkline@speedpost.net:
Hi All,
So my laptop upgraded to the latest version of Windows 10 recently, and this seems to have undone the hack of replacing the default bootx64.efi file. That is, the file is still SystemD’s boot loader, but somehow I’m back to only being able to boot Windows reliably. Has anyone else seen this particular frustration with an upgrade? I note that my laptop came with Windows 10, so this was just an incremental update as far as I now.
Thanks for any ideas. This is kind of maddening. Best, Zack.
Hi.
Did you check if Windows reactivated fast start-up [1]? What exactly happens when you boot linux?
Greetings, Tim
[1] https://wiki.archlinux.org/index.php/Dual_boot_with_Windows#Fast_Start-Up
On Fri, 29 Apr 2016 00:20:46 +0200 Tim Ohliger ohliger.tim@gmail.com wrote:
2016-04-29 0:09 GMT+02:00 Zachary Kline zkline@speedpost.net:
Hi All,
So my laptop upgraded to the latest version of Windows 10 recently, and this seems to have undone the hack of replacing the default bootx64.efi file. That is, the file is still SystemD’s boot loader, but somehow I’m back to only being able to boot Windows reliably. Has anyone else seen this particular frustration with an upgrade? I note that my laptop came with Windows 10, so this was just an incremental update as far as I now.
Thanks for any ideas. This is kind of maddening. Best, Zack.
Hi.
Did you check if Windows reactivated fast start-up [1]? What exactly happens when you boot linux?
Greetings, Tim
[1] https://wiki.archlinux.org/index.php/Dual_boot_with_Windows#Fast_Start-Up
I've had problems with Win10 setting the 'file system dirty' flag on my shared data partition causing arch boot up to crash when it tries to it.
The only work around I've found is to perform a full defrag & junk file delete with auto shutdown on completion.
On 29 April 2016 at 00:09, Zachary Kline zkline@speedpost.net wrote:
Hi All,
So my laptop upgraded to the latest version of Windows 10 recently, and this seems to have undone the hack of replacing the default bootx64.efi file. That is, the file is still SystemD’s boot loader, but somehow I’m back to only being able to boot Windows reliably. Has anyone else seen this particular frustration with an upgrade? I note that my laptop came with Windows 10, so this was just an incremental update as far as I now.
Thanks for any ideas. This is kind of maddening. Best, Zack.
Hi,
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.
A more awkward (but more stable) hack would be to create an ESP on a USB stick and install rEFInd or grub to that partition. Systemd-boot can only load applications located on the partition it is currently on, but rEFInd and grub both support booting across devices (in principle). My laptop's BIOS Setup allows me to prioritise USB sticks over internal hard drives at boot time so this should be a reliable way to multi-boot, though I haven't had the time to test it.
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.
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.
participants (5)
-
Gerald Klein
-
mick
-
Murari
-
Tim Ohliger
-
Zachary Kline