Grub only boots working Windows, so Windows cannot have hibernation on, or need chkdsk.
Windows turns hibernation back on with updates, so then you have to directly boot Windows from UEFI boot menu, probably f12, fix Windows & then boot Ubuntu.
Major updates from either Ubuntu or Windows may reset UEFI boot order. Then you still should be able to boot from UEFI boot menu.
Boot-Repair shows different GUIDs for Windows entry & Ubuntu. This may because you have not updated UEFI and SSD firmware or had Windows fast start up on, so installer could not see the ESP on the NVMe drive. So it installed Ubuntu/grub to ESP on HDD. That should be ok, but normally it would have installed into the ESP on the NVMe drive.
You also show you must have deleted the Windows entry & added a new one using grub. Very old versions of Boot-Repair also did that and years ago that was one work around. But not recommended for years as when Windows turns fast start up on, grub will not boot Windows & you then have no way to boot it.
You need to delete that UEFI entry & create new correct Windows UEFI boot entry. I assume it is in the ESP on the NVMe drive. If not then you have to boot your Windows repair disk and run a full set of repairs.
Code:
efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000,0002,0001,0007,0008,0006
Boot0000* Windows Boot Manager HD(1,GPT,89597315-219c-4bfb-9f4c-58367fdc412c,0x800,0xfa000)/File(EFIubuntugrubx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* Onboard NIC (IPV4) PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/MAC(28f10e04ba5e,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0002* Onboard NIC (IPV6) PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/MAC(28f10e04ba5e,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0003* ubuntu HD(4,GPT,b31b06b7-939e-464b-a9aa-15a1cdf5bcc7,0x581dc000,0x7a000)/File(EFIubuntushimx64.efi)
Boot0006* NetWork BBS(PCMCIA,,0x0)..GO..NO........o.N.e.t.W.o.r.k.........................rN.D+..,.;..........@..Gd-.;.A..MQ..L.Q.u.a.l.c.o.m.m. .A.t.h.e.r.o.s. .B.o.o.t........BO
Boot0007* Hard Drive BBS(Floppy,,0x0)..GO..NO..........H.a.r.d. .D.r.i.v.e....................A..................1.N........>.;......J..Gd-.;.A..MQ..L.P.1.:. .S.T.1.0.0.0.L.M.0.4.4. .H.N.-.M.1.0.1.S.A.D........BO
Boot0008* Second HDD BBS(USB,,0x0)..GO..NO..........S.e.c.o.n.d. .H.D.D....................A...........................%8Ca..Z.....F..Gd-.;.A..MQ..L.P.M.9.5.1. .N.V.M.e. .S.A.M.S.U.N.G. .2.5.6.G.B........BO
to see GUID, also called partUUID
lsblk -o name,mountpoint,label,size,fstype,uuid,partuuid | egrep -v "^loop"
Issues on Alienware are usually the same as many Dell systems. They use same UEFI with just the options adding features.
I do not see Alienware listed, although new Dell models are.
https://github.com/rhboot/fwupdate/b...ster/README.md
https://fwupd.org/lvfs/devicelist &
https://fwupd.org/vendorlist
sudo efibootmgr -v
The "-v" option displays all the entries so you can confirm you're deleting the right one, and then you use the combination of "-b ####" (to specify the entry) and "-B" (to delete it). Examples #5 is delete:, with Ubuntu you need sudo, others must be at root. some need all 4 hex chars, others only need significant digits
sudo efibootmgr -b XXXX -B
man efibootmgr
http://linux.die.net/man/8/efibootmgr
To add new entry to have to specify drive & partition. UEFI normally defaults to sda1 (not sure if really sda1 or first drive and then would it default to your nmve drive?)
sudo efibootmgr -c -L "Windows Boot Manager" -l "\EFI\Microsoft\Boot\bootmgfw.efi" -d /dev/nvme0n1 -p 1
Others with sdX drive, drive & partition parameters not required if sda1.
New Windows entry - assumes default sda1 add -d /dev/sda -p 2 if sda2:
sudo efibootmgr -c -L "Windows Boot Manager" -l "\EFI\Microsoft\Boot\bootmgfw.efi"
Bookmarks