On Fri, 29 Apr 2016 00:20:46 +0200 Tim Ohliger <ohliger.tim@xxxxxxxxx> wrote: > 2016-04-29 0:09 GMT+02:00 Zachary Kline <zkline@xxxxxxxxxxxxx>: > > > 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.
