Skip to main content
Topic: Grub Isn't detecting windows10 (Read 380 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Grub Isn't detecting windows10

Hello everyone, I dual booted Artix with Windows 10 for several months because I have to use Windows for Some Adobe products ): ,
However I reinstalled Windows 10 recently and for sure it broke grub, I booted into live Artix to fix the boot loader as I usually do, However this didn't work, eventually I solved the problem by fixing some hard disk issues with fscl, and grub is now working and I can boot into Artix, The thing is now grub isn't detecting Windows 10 actually I can browse Windows 10 file system when I mount it manually from the terminal but Nautilus and other GUI file managers aren't detecting Windows 10 Partition even tho I have ntfs-3g and os-prober...

Output of `smartctl --all /dev/sda`:
https://paste.centos.org/view/8c867eb3

So what should I do ?
Thanks in advance.

Re: Grub Isn't detecting windows10

Reply #1
"Ceterum censeo M$ esse delendam"
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: Grub Isn't detecting windows10

Reply #2
Remove your Linux hard disk before installing windows or running their repair tool otherwise windows mucks up your UEFI for Linux.

Then afterwards install Linux with UEFI hard disk and boot up and sudo update-grub

Never share a UEFI between Linux and windows
Cat Herders of Linux

 

Re: Grub Isn't detecting windows10

Reply #3
Quote
The thing is now grub isn't detecting Windows 10 actually I can browse Windows 10 file system when I mount it manually from the terminal but Nautilus and other GUI file managers aren't detecting Windows 10 Partition even tho I have ntfs-3g and os-prober...

Common problem i have sometimes too.

For me, most the time, helps if i mount the EFI/BIOS partition of Windows (where Windows put his bootloader, if not the same like grub), and Windows self, and then run os grub-mkconfig again.

If this dont help, be sure that you have os-prober enabled in the grub/default file. If nothing helps, a complete (with all configs etc) reinstall of grub can bring wounders.