]]>"You, Sir, are a steely-eyed missile man!"
As someone, somewhere, said in a different context,
"You, Sir, are a steely-eyed missile man!"
(How did you know I had an ASRock P67 Extreme4 mobo?)
That command seems to have done the trick!
]]>I can't remember if this was an issue two years ago--nor how I fixed it if it was!
]]>How are you setting your EFI variables? I was having a similar issue and was blaming it on Windows. I had been using efibootmgr to set my variables, and all would be fine until I booted Windows, and it would change. I later configured it using the firmware setup tools for my HP Envy (often mistakenly called BIOS set up) and I have not had any problems with it reverting. I am wondering if there is something about how the variables are configured by efibootmgr that Windows does not like causing Windows to take initiative and "fix" it. Conversely, perhaps the firmware tools intrinsic to the laptop set the variables to Windows liking. As I almost never boot to Windows, I really don't care much. Also, I do not use a boot loader -- I just use the efistub capability of the kernel. Windows will exist on my laptop until the day after the laptop warranty expires.
]]>If I boot into Arch, everything is fine. The next boot will give me the grub menu again.
If I boot into Windows via grub, the next time I reboot, "Windows Loader" has replaced my firmware choices and I boot directly into Windows.
I've done some Googling, but most of what I found is several years old and referring to grub-legacy.
I've tried setting the boot sequence with efibootmgr, but things still got overwritten at the next Windows boot.
Thanks in advance.
]]>