hhow to remove win 10 loader from sda1 and sda2 in grub

#Hhow to remove win 10 loader from sda1 and sda2 in grub install#

Sda4: _īoot files: /boot/grub/grub.cfg /etc/fstab Mounting failed: mount: unknown filesystem type '' But according to the info fromīoot files: /Windows/System32/winload.exe Sda5: _īoot sector info: According to the info in the boot sector, sda5 startsĪt sector 6555650. Sda1: _īoot sector info: Grub2 (v1.99) is installed in the boot sector of sda1Īnd looks at sector 933979528 of the same hard driveįor core.img. => Windows is installed in the MBR of /dev/sda. Do not post RESULTS.txt here without using code tags!Ĭode: Select all Boot Info Script 0.61 I recommend you run the Boot Info Script and post the RESULTS.txt file that it generates, either as a link or using code tags. If my analysis of the problem is incorrect - if you've actually got a BIOS-mode installation on an MBR disk - then you'll need to post more details. rEFInd is better at launching Windows than is GRUB, so this should fix the problem. This will then take over as the primary boot manager on the system, bypassing GRUB.

#Hhow to remove win 10 loader from sda1 and sda2 in grub install#

Install the Debian package version of my rEFInd boot manager.Run the Boot Repair utility, which should fix GRUB's ability to launch the Windows boot loader.There are many ways to fix this problem, but a couple of them are likely to be easiest. This has nothing to do with the fact that the Windows boot loader is on the ESP and Windows is elsewhere.

Mint doesn't always set up dual-booting with Windows on an EFI-based computer correctly. If this is correct, then your /dev/sda1 is not a Windows partition it's your EFI System Partition (ESP), which is where boot loaders live.

Based on your partition numbers (namely, partitions 1-5 all in use, and none of them being an extended partition), it's logical to surmise that you've got a GUID Partition Table (GPT), which in turn implies that Windows is booting in EFI mode.