Can't boot Windows 10 after installing Mint

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
newlinuxuser456
Level 1
Level 1
Posts: 3
Joined: Sat Oct 12, 2019 4:05 pm

Can't boot Windows 10 after installing Mint

Post by newlinuxuser456 » Sat Oct 12, 2019 4:16 pm

Hi,

I installed the 64 bit version of Linux Mint with the "do something else" option since the installer didn't detect Windows. I created two partitions for Mint (one was "swap" or something along those lines, and I made it the size of my PC's RAM - the other one was the main one and I entered "/" - this is all I can remember at this point) and then installed it without issues. Everything seems to work fine in Mint, but I can't get back to Windows.

Windows don't appear in the boot menu, and when I go to setup, I can't run it from there either. It doesn't appear on any of the lists.

I've tried looking for solutions and entered a few things in the command line. I then ran a boot repair tool and followed the instructions (basically entering more stuff into the command line), but that didn't solve the problem either. It did give me this Pastebin report though: http://paste.ubuntu.com/p/fX4M7ZSK9R/

I can see from Mint that Windows is still there. All the files still exist - I didn't erase or overwrite anything.

I'm at a loss right now. I thought this will be an easy way to try Linux, but instead I've been dealing with this for hours. Any help would be greatly appreciated.

UPDATE:
- I've managed to update grub and confirm that I need to add the Windows partition manually
- I've found a way to locate the Windows partition and mount it
- Sadly "sudo grub-install /dev/[BOOT PARTITION eg. Sda6]" doesn't work: it returns "sudo: grub2-install: command not found"

athi
Level 6
Level 6
Posts: 1461
Joined: Sun Mar 30, 2014 10:15 am
Location: USA

Re: Can't boot Windows 10 after installing Mint

Post by athi » Sat Oct 12, 2019 6:04 pm

Got a feeling that Mint was installed in legacy BIOS/CSM mode and GRUB installed in legacy BIOS/CSM mode cannot see UEFI Win10 boot manager. This is a known issue with GRUB.

Please boot into Mint and run ls /sys/firmware and see if you see "efi" in the output. If "efi" is not in output, Mint was installed in legacy BIOS mode. You can still boot Win10 by selecting Win10 from the firmware boot device list.
Mint Mate 19.1. Main rig is HP 800G2 I5 6500 16GB ram, 120GB boot drive, 2x3TB, 1x4TB data drives. Oldest rig is Mate 18.3 on Dell D620 with 32bits core duo.

User avatar
pbear
Level 8
Level 8
Posts: 2161
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Can't boot Windows 10 after installing Mint

Post by pbear » Sat Oct 12, 2019 10:25 pm

FYI, according to the boot repair report, Mint is installed in UEFI mode:

Code: Select all

Presence of EFI/Boot file detected: /boot/efi/EFI/Boot/fbx64.efi
/usr/share/boot-sav/bs-cmd_terminal.sh: line 179: warning: command substitution: ignored null byte in input

=================== efibootmgr -v
BootCurrent: 0004
Timeout: 5 seconds
BootOrder: 0004,0001,0003
Boot0001* Hard Drive	BBS(HD,,0x0)..GO..NO........u.W.D.C. .W.D.S.2.4.0.G.2.G.0.B.-.0.0.E.P.W.0....................A.................................>..Gd-.;.A..MQ..L.9.1.1.0.3.1.0.8.0.2.3.0. . . . . . . . ........BO
Boot0003* UEFI: Built-in EFI Shell	VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0004* ubuntu	HD(3,MBR,0x24f2fb4a,0x16f66ffe,0x4fc0802)/HD(1,MBR,0x0,0x16f67000,0xee6000)/File(EFIubuntugrubx64.efi)..BO

=================== UEFI/Legacy mode:
BIOS is EFI-compatible, and is setup in EFI-mode for this installed-session.
SecureBoot disabled. (maybe sec-boot, Please report this message to boot.repair@gmail.com)
Meanwhile, review of partitions shows the EFI partition at sda5, suggesting it was added by Mint:

Code: Select all

=================== parted -lm:

BYT;
/dev/sda:240GB:scsi:512:512:msdos:ATA WDC WDS240G2G0B-:;
1:1049kB:577MB:576MB:ntfs::;
2:577MB:197GB:197GB:ntfs::;
3:197GB:240GB:42.8GB:::;
5:197GB:205GB:7999MB:fat32::boot, esp;
6:205GB:240GB:34.8GB:ext4::;

=================== lsblk:
KNAME TYPE FSTYPE   SIZE LABEL
sda   disk        223,6G
sda1  part ntfs     549M System Reserved
sda2  part ntfs   183,2G
sda3  part            1K
sda5  part vfat     7,5G
sda6  part ext4    32,4G

KNAME ROTA RO RM STATE   MOUNTPOINT
sda      0  0  0 running
sda1     0  0  0         /mnt/boot-sav/sda1
sda2     0  0  0         /mnt/boot-sav/sda2
sda3     0  0  0
sda5     0  0  0         /boot/efi
sda6     0  0  0         /
My suspicion, therefore, would be that the problem is Win10 was installed in legacy mode.
Time flies like an arrow. Fruit flies like a banana.
If your problem has been solved, please edit the thread title.

athi
Level 6
Level 6
Posts: 1461
Joined: Sun Mar 30, 2014 10:15 am
Location: USA

Re: Can't boot Windows 10 after installing Mint

Post by athi » Sat Oct 12, 2019 10:42 pm

pbear wrote:
Sat Oct 12, 2019 10:25 pm
FYI, according to the boot repair report, Mint is installed in UEFI mode:

Code: Select all

Presence of EFI/Boot file detected: /boot/efi/EFI/Boot/fbx64.efi
/usr/share/boot-sav/bs-cmd_terminal.sh: line 179: warning: command substitution: ignored null byte in input

=================== efibootmgr -v
BootCurrent: 0004
Timeout: 5 seconds
BootOrder: 0004,0001,0003
Boot0001* Hard Drive	BBS(HD,,0x0)..GO..NO........u.W.D.C. .W.D.S.2.4.0.G.2.G.0.B.-.0.0.E.P.W.0....................A.................................>..Gd-.;.A..MQ..L.9.1.1.0.3.1.0.8.0.2.3.0. . . . . . . . ........BO
Boot0003* UEFI: Built-in EFI Shell	VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0004* ubuntu	HD(3,MBR,0x24f2fb4a,0x16f66ffe,0x4fc0802)/HD(1,MBR,0x0,0x16f67000,0xee6000)/File(EFIubuntugrubx64.efi)..BO

=================== UEFI/Legacy mode:
BIOS is EFI-compatible, and is setup in EFI-mode for this installed-session.
SecureBoot disabled. (maybe sec-boot, Please report this message to boot.repair@gmail.com)
Meanwhile, review of partitions shows the EFI partition at sda5, suggesting it was added by Mint:

Code: Select all

=================== parted -lm:

BYT;
/dev/sda:240GB:scsi:512:512:msdos:ATA WDC WDS240G2G0B-:;
1:1049kB:577MB:576MB:ntfs::;
2:577MB:197GB:197GB:ntfs::;
3:197GB:240GB:42.8GB:::;
5:197GB:205GB:7999MB:fat32::boot, esp;
6:205GB:240GB:34.8GB:ext4::;

=================== lsblk:
KNAME TYPE FSTYPE   SIZE LABEL
sda   disk        223,6G
sda1  part ntfs     549M System Reserved
sda2  part ntfs   183,2G
sda3  part            1K
sda5  part vfat     7,5G
sda6  part ext4    32,4G

KNAME ROTA RO RM STATE   MOUNTPOINT
sda      0  0  0 running
sda1     0  0  0         /mnt/boot-sav/sda1
sda2     0  0  0         /mnt/boot-sav/sda2
sda3     0  0  0
sda5     0  0  0         /boot/efi
sda6     0  0  0         /
My suspicion, therefore, would be that the problem is Win10 was installed in legacy mode.
Drive: sda _____________________________________________________________________
Disk /dev/sda: 223.6 GiB, 240065183744 bytes, 468877312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 2,048 1,126,399 1,124,352 7 NTFS / exFAT / HPFS
/dev/sda2 1,126,400 385,247,231 384,120,832 7 NTFS / exFAT / HPFS
/dev/sda3 385,249,278 468,875,263 83,625,986 5 Extended
/dev/sda5 * 385,249,280 400,871,423 15,622,144 ef EFI (FAT-12/16/32)
/dev/sda6 400,873,472 468,875,263 68,001,792 83 Linux
Don't know how I missed the link to boot repair output. If Win10 was installed on /dev/sda which has MBR/MSDOS partition table, then Win10 was installed in legacy BIOS mode. MS locked legacy BIOS installation to MBR/MSDOS disks and UEFI installation to GPT disks.

Edit: This MS requirement was fairly recent (with UEFI firmware?), you used to be able to install Win7 on GPT on BIOS only machines.
Mint Mate 19.1. Main rig is HP 800G2 I5 6500 16GB ram, 120GB boot drive, 2x3TB, 1x4TB data drives. Oldest rig is Mate 18.3 on Dell D620 with 32bits core duo.

newlinuxuser456
Level 1
Level 1
Posts: 3
Joined: Sat Oct 12, 2019 4:05 pm

Re: Can't boot Windows 10 after installing Mint

Post by newlinuxuser456 » Sun Oct 13, 2019 1:53 am

athi wrote:
Sat Oct 12, 2019 6:04 pm
Got a feeling that Mint was installed in legacy BIOS/CSM mode and GRUB installed in legacy BIOS/CSM mode cannot see UEFI Win10 boot manager. This is a known issue with GRUB.

Please boot into Mint and run ls /sys/firmware and see if you see "efi" in the output. If "efi" is not in output, Mint was installed in legacy BIOS mode. You can still boot Win10 by selecting Win10 from the firmware boot device list.
The output is "code]acpi dmi efi memmap".
It looks like the issue is with my Windows installation.

newlinuxuser456
Level 1
Level 1
Posts: 3
Joined: Sat Oct 12, 2019 4:05 pm

Re: Can't boot Windows 10 after installing Mint

Post by newlinuxuser456 » Sun Oct 13, 2019 2:11 am

Don't know how I missed the link to boot repair output. If Win10 was installed on /dev/sda which has MBR/MSDOS partition table, then Win10 was installed in legacy BIOS mode. MS locked legacy BIOS installation to MBR/MSDOS disks and UEFI installation to GPT disks.

Edit: This MS requirement was fairly recent (with UEFI firmware?), you used to be able to install Win7 on GPT on BIOS only machines.
Thank you so much for the info. Things are starting to look a bit more manageable - any suggestion how should I approach resolving this?

If all else fails, would formatting the partitions with Mint on it automatically give me the option to boot Windows again? Or would it just result in me being unable to boot anything?

EDIT: I think I'll just try to reinstall Mint in legacy BIOS mode

athi
Level 6
Level 6
Posts: 1461
Joined: Sun Mar 30, 2014 10:15 am
Location: USA

Re: Can't boot Windows 10 after installing Mint

Post by athi » Sun Oct 13, 2019 9:16 am

newlinuxuser456 wrote:
Sun Oct 13, 2019 2:11 am
Don't know how I missed the link to boot repair output. If Win10 was installed on /dev/sda which has MBR/MSDOS partition table, then Win10 was installed in legacy BIOS mode. MS locked legacy BIOS installation to MBR/MSDOS disks and UEFI installation to GPT disks.

Edit: This MS requirement was fairly recent (with UEFI firmware?), you used to be able to install Win7 on GPT on BIOS only machines.
Thank you so much for the info. Things are starting to look a bit more manageable - any suggestion how should I approach resolving this?

If all else fails, would formatting the partitions with Mint on it automatically give me the option to boot Windows again? Or would it just result in me being unable to boot anything?

EDIT: I think I'll just try to reinstall Mint in legacy BIOS mode
A reinstall in legacy BIOS mode would be best. Just run ls /sys/firmware and check for no "efi" in output before installation to confirm that Mint live USV/DVD booted in legacy BIOS mode. On UEFI capable machines, it can be tricky to get Mint live USB/DVD to boot in legacy BIOS mode.

With both Win10 and Mint installed in the same mode, GRUB will find both boot loaders and show them in the GRUB boot listing.
Mint Mate 19.1. Main rig is HP 800G2 I5 6500 16GB ram, 120GB boot drive, 2x3TB, 1x4TB data drives. Oldest rig is Mate 18.3 on Dell D620 with 32bits core duo.

Post Reply

Return to “Installation & Boot”