0

I was out for vacation for 3 weeks and then returned back. But this is what I am seeing after selecting Windows Boot Manager on the Grub menu.

I remember on the last day there was some Windows update.

Now I cannot go to Windows, but I can go to Ubuntu.

What I should do?

I tried Boot-Repair and this is what it is stating

LegacyWindows detected. Please enable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB).

enter image description here

And this is what my grub cutomizer and parted states Haven't been doing any system upgrade or installing stuff...so slightly out of touch.enter image description here /dev/nvme0n1p1 seems to have all the active partitions to boot.

I tried this link, but for this I need to able to login to Windows 11 command prompt. I tried two different USB drives and different ports, but I'm facing this issue now:

Stop code DRIVER PNP WATCHDOG

Opened a case with Microsoft Support but they are not of much help after two sessions except telling me "we don't support dual boot" or "seek help from local technician"

I really want to get going. I'm willing to reinstall Windows 11 if needed. Ubuntu Linux is all working fine. Boot-Repair is no good.

enter image description here

sudo cat /boot/grub/grub.cfg | grep menuentry

if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" menuentry_id_option="" export menuentry_id_option menuentry "Ubuntu" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-4cd02128-ebde-4341-ad07-3620623d26ec' { menuentry "Ubuntu, with Linux 6.8.0-51-generic" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.8.0-51-generic-advanced-4cd02128-ebde-4341-ad07-3620623d26ec' { menuentry "Ubuntu, with Linux 6.8.0-51-generic (recovery mode)" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.8.0-51-generic-recovery-4cd02128-ebde-4341-ad07-3620623d26ec' { menuentry "Ubuntu, with Linux 6.2.0-33-generic" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.2.0-33-generic-advanced-4cd02128-ebde-4341-ad07-3620623d26ec' { menuentry "Ubuntu, with Linux 6.2.0-33-generic (recovery mode)" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.2.0-33-generic-recovery-4cd02128-ebde-4341-ad07-3620623d26ec' { menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {

sudo update-grub

Sourcing file `/etc/default/grub'

Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ...

Found linux image: /boot/vmlinuz-6.8.0-51-generic Found initrd image: /boot/initrd.img-6.8.0-51-generic Found linux image: /boot/vmlinuz-6.2.0-33-generic Found initrd image: /boot/initrd.img-6.2.0-33-generic Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Found linux image: /boot/vmlinuz-6.8.0-51-generic Found initrd image: /boot/initrd.img-6.8.0-51-generic Found linux image: /boot/vmlinuz-6.2.0-33-generic Found initrd image: /boot/initrd.img-6.2.0-33-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done

Update 2 Please refer my other question about the same issue. I have multiple drives. Internal SSD Drive(Samsung 860 EVO-1TB) on which Windows 11 Pro was installed finally died. It was deteriorating(without any notice) but finally died while I was on on vacation. Windows installation is not that great, it just doesn't move forward because of faulty hardware(it could have chosen empty space on other drives). Just because there is dead hard-drive but other drives are there with empty partitions/space - it could have move forward. After removing failed SSD-I was able to install Windows 11 Pro again and back to business.

karel
  • 122,292
  • 133
  • 301
  • 332
Ashu
  • 4,004

1 Answers1

1

Please refer my other question about the same issue. I have multiple drives in my desktop. Internal SSD Drive(Samsung 860 EVO-1TB) on which Windows 11 Pro was installed finally died. It was deteriorating(without any notice) but finally died while I was on on vacation. That's the reason when the control went from GRUB to load Windows Bootloader and finally load Windows 11 OS, it was failing with the message:

error no such device : 2632-DF15 error : unknown file system

Windows installation is not that great, it just doesn't move forward because of faulty hardware(it could have chosen empty space on other drives). Just because there is dead hard-drive but other drives are there with empty partitions/space - it could have moved forward and installed Windows 11 out there. After removing failed SSD-I was able to install Windows 11 Pro again and back to business. Another lesson to learn. My desktop is old(Dec 2017) with some upgrades(PCI NVME drive and internal SSDs rather than regular hard drives). It's Dell XPS 8930 and came with Windows 10 Pro. After 1-2 years it got upgraded to Windows 11 Pro. But this time, my desktop was not meeting the standards of Windows 11 and it was not getting installed. I need to get help of Microsoft support to do that(essentially it want Secure boot to be enabled in BIOS).

Ashu
  • 4,004