Alt Text:
Six habits of happy people

  • doom scrolling on lemmy
  • feeling superior to people who use reddit
  • closing the app because no new posts
  • installing gnu+linux
  • bootoader not found
  • doom scrolling on lemmy
  • PM_ME_VINTAGE_30S [he/him]@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 months ago

    My understanding is that GRUB (using the chainloader command) successfully calls the Windows bootloader when I ask it to run Windows, but I think the Windows bootloader is corrupted. It is corrupted to the point that I cannot even use the recovery disk or install disk to fix the system.

    I think a Windows update broke it. I have OS probing enabled, and it successfully detected (and booted into) the Windows partition back when I first installed Debian. It still detects the Windows partition, but Windows bluescreens with an error message that I can’t remember off the top of my head, but both Microsoft’s support forum and other resources basically indicated could only be fixed with a reinstall. Debian, of course, boots just fine.

    I ran chkdsk on the Windows partition with the Windows Recovery Disk and I also checked the partition in Gparted, and both processes found no errors. The Windows partition is perfectly readable from Debian.

    So I’m inclined to believe that Windows broke itself.

    • ProgrammingSocks@pawb.social
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      If that’s the case, then yeah. Rescatux might have a tool that can fix it but I don’t really bother fixing Windows installs usually. I would still try regenerating /etc/boot/grub.cfg but if you’ve done that already it is probably Windows’ fault