after dual boot linux mint 20.3 cannot login on windows anymore

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
lafonso
Level 1
Level 1
Posts: 1
Joined: Mon Jan 24, 2022 7:17 pm

after dual boot linux mint 20.3 cannot login on windows anymore

Post by lafonso »

Hello:

I have installed linux mint from usb pen drive. I was installed in a previous (old) install of linux mint on my asus laptop. I used the same partitions used before (linux partitions) without changing anything on the existing partitions.
It creates grub menu, with entry for linux mint and windows 10 but the entry for windows 10 does not open, it is just a black screen.
I have run grub update and also used the repair boot tool, but it did not solve.
in the link below is the detailed information for partition and grub.
http://sprunge.us/170UtJ

Thanks in advance
Luis Afonso
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
Jo-con-Ël
Level 11
Level 11
Posts: 3589
Joined: Sun Jun 20, 2021 12:41 pm
Location: donde habita el olvido

Re: after dual boot linux mint 20.3 cannot login on windows anymore

Post by Jo-con-Ël »

Maybe it was intentioned or it was a mistake when installing Mint In BIOS Legacy mode before. That sda6 partition is/acts as a fake MBR with grub (bios) first phase installed and pointing to sda7 (Mint's partition) if booting in BIOS Legacy mode (Boot option #4>Hitachi hard disk as per efibootmgr).

Code: Select all

The firmware is EFI-compatible, and is set in EFI-mode for this installed-session.
SecureBoot disabled.

BootCurrent: 000C
Timeout: 0 seconds
BootOrder: 0009,0005,000C,0004,000B,0008,0006,0007
Boot0000  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001  Boot Menu	FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0002  Diagnostic Splash	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0003  Acer D2D:	FvFile(bcc93540-7ea9-11df-8c4a-0800200c9a66)
Boot0004* HDD 0: Hitachi HTS545050A7E380                 	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)..bYVD.A...O.*..
Boot0005* ATAPI CD/DVD: HL-DT-ST DVDRAM GU71N                   	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(4,0,0)......!N.:^G.V.T
Boot0006* USB FDD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0007* Network Boot:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0008* USB HDD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0009* USB CD/DVD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot000A* Internal Shell:	FvFile(c57ad6b7-0515-40a8-9d21-551652854e37)
Boot000B* Windows Boot Manager	HD(2,GPT,bd76bbf5-155a-44ab-9ec8-203377a6072a,0xc8800,0x96000)/File(\EFI\Microsoft\Boot\bootmgfw.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.}...n................
Boot000C* ubuntu	HD(2,GPT,bd76bbf5-155a-44ab-9ec8-203377a6072a,0xc8800,0x96000)/File(\EFI\ubuntu\grubx64.efi)
Now, booting with default UEFI option (Ubuntu), as per BootInfo report you have nothing to do but reinstalling grub-efi (again), IMO you do not need it. That Windows entry in GRUB menu looks like to be correct.

Code: Select all

====================== sda7/boot/grub/grub.cfg (filtered) ======================

Linux Mint 20.3 Cinnamon   92671e6f-d66b-4342-9472-502ee7c9c124
Linux Mint 20.3 Cinnamon, with Linux 5.4.0-96-generic   92671e6f-d66b-4342-9472-502ee7c9c124
Linux Mint 20.3 Cinnamon, with Linux 5.4.0-91-generic   92671e6f-d66b-4342-9472-502ee7c9c124
Windows Boot Manager (on sda2)   osprober-efi-1C03-7F64
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings   uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###
The only relevant in that report are those problems with sda9 (Windows recovery environment) and sda10 (System/BIOS recovery environment) beginning sectors.

In your case, I would try to get into UEFI settings (Computer' s settings, AKA BIOS setup) and disable CSM/Legacy support and also keep on Secure boot disabled. Then try to boot Windows option from boot menu (not grub). Give it time ( i.e. wait 'till that black screen disappears) 'cause maybe Windows was trying (and needs to recheck and complete) to repair itself.

After waiting enough time, if Windows does not boot you will need to use a Windows Installation/Recovery media to repair Windows boot.
Arrieritos semos y en el camino nos encontraremos.
Locked

Return to “Installation & Boot”