#1 Le 21/06/2025, à 02:57
- soujaa
[OK] Dual-boot Win11 brisé dans grub [Win11 (nvme0) Kubuntu (nvme1)]
Bonjour amis linuxiens
Le Grub de ma nouvel installation ne fait pas booter le Windows. J'ai installer Win11 pour mon fils (Roblox 
)sur un nvme et sur l'autre Nvme KUBUNTU. Malgré les différentes modifications au Grub même si Win11 s'affiche il ne boot pas.
Os-prober ne détecte rien. Boot-repair ne répare rien.
a@a:~$ sudo os-prober
a@a:~$ boot-repair info
boot-repair-4ppa2081 [20250620_2031]
============================== Boot Info Summary ===============================
=> No boot loader is installed in the MBR of /dev/nvme0n1.
=> Grub2 (v2.00) is installed in the MBR of /dev/nvme1n1 and looks at sector
1 of the same hard drive for core.img. core.img is at this location and
looks for (,msdos1)/boot/grub. It also embeds following components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_msdos biosdisk
---------------------------------------------------------------------------
=> No boot loader is installed in the MBR of /dev/sda.
=> No boot loader is installed in the MBR of /dev/sdb.
nvme0n1p1: _____________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/SecureBootRecovery.efi
nvme0n1p2: _____________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
nvme0n1p3: _____________________________________________________________________
File system: ntfs
Boot sector type: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 10 or 11
Boot files: /Windows/System32/winload.exe
nvme0n1p4: _____________________________________________________________________
File system: ntfs
Boot sector type: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
nvme1n1p1: _____________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 25.04
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
/boot/grub/i386-pc/core.img
sda1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: ntfs
Boot sector type: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sdb2: __________________________________________________________________________
File system: ntfs
Boot sector type: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
================================ 2 OS detected =================================
OS#1 (linux): L'OS actuellement utilisé - Ubuntu 25.04 on nvme1n1p1
OS#2 (windows): Windows 10 or 11 on nvme0n1p3
================================ Host/Hardware =================================
CPU architecture: 64-bit
Video: TU116 [GeForce GTX 1650 SUPER] from NVIDIA Corporation
BOOT_IMAGE of the installed session in use:
/boot/vmlinuz-6.14.0-22-generic root=UUID=708676df-abc7-496c-bd32-1478d56bc258 ro quiet splash vt.handoff=7
df -Th / : /dev/nvme1n1p1 ext4 916G 269G 602G 31% /
===================================== UEFI =====================================
BIOS/UEFI firmware: 3057(30.57) from American Megatrends Inc.
The firmware is EFI-compatible, but this installed-session is in Legacy/BIOS/CSM mode (not in EFI mode).
ebef7a45f83ac9d2dea89339f3777638 nvme0n1p1/Boot/bootx64.efi
ebef7a45f83ac9d2dea89339f3777638 nvme0n1p1/Microsoft/Boot/bootmgfw.efi
c7d15830df7619f88cf202d7d54533c4 nvme0n1p1/Microsoft/Boot/bootmgr.efi
ec1a7209fec9f8fe72783101362b7e66 nvme0n1p1/Microsoft/Boot/SecureBootRecovery.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
nvme1n1 : notGPT, no-BIOSboot, has-noESP, not-usb, not-mmc, has-os, no-wind, 2048 sectors * 512 bytes
nvme0n1 : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, has-win, 2048 sectors * 512 bytes
sdb : notGPT, no-BIOSboot, has-noESP, not-usb, not-mmc, no-os, no-wind, 2048 sectors * 512 bytes
sda : is-GPT, no-BIOSboot, has-noESP, not-usb, not-mmc, no-os, no-wind, 2048 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
nvme1n1p1 : is-os, 64, apt-get, signed grub-pc grub-efi , grub2, grub-install, grubenv-ok, update-grub, end-after-100GB
nvme0n1p3 : is-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
nvme0n1p1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
nvme0n1p4 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
sdb2 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
sdb1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
Partitions info (2/3): _________________________________________________________
nvme1n1p1 : isnotESP, fstab-without-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ext4
nvme0n1p3 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot, ntfs
nvme0n1p1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, vfat
nvme0n1p4 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot, ntfs
sdb2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ntfs
sdb1 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ntfs
sda1 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ext4
Partitions info (3/3): _________________________________________________________
nvme1n1p1 : not--sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, nvme1n1
nvme0n1p3 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme0n1p1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme0n1p4 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
sdb2 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sdb
sdb1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sdb
sda1 : maybesepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk nvme1n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 0xeb599480
Boot Start End Sectors Size Id Type
nvme1n1p1 * 2048 1953525167 1953523120 931.5G 83 Linux
Disk nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk identifier: DBC2FA49-4B6A-4B06-8934-21BB80C6DD30
Start End Sectors Size Type
nvme0n1p1 2048 206847 204800 100M EFI System
nvme0n1p2 206848 239615 32768 16M Microsoft reserved
nvme0n1p3 239616 1999087615 1998848000 953.1G Microsoft basic data
nvme0n1p4 1999087616 2000406527 1318912 644M Windows recovery environment
Disk sda: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors
Disk identifier: 57A4D7F2-DAFD-432C-8262-691716EF6180
Start End Sectors Size Type
sda1 2048 4000796671 4000794624 1.9T Linux filesystem
Disk sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 0xd2892678
Boot Start End Sectors Size Id Type
sdb1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
sdb2 206848 1953521663 1953314816 931.4G 7 HPFS/NTFS/exFAT
parted -lm (filtered): _________________________________________________________
sda:2048GB:scsi:512:512:gpt:ATA SSD:;
1:1049kB:2048GB:2048GB:ext4::;
sdb:1000GB:scsi:512:4096:msdos:ATA WDC WD10EZEX-22R:;
1:1049kB:106MB:105MB:ntfs::boot;
2:106MB:1000GB:1000GB:ntfs::;
nvme0n1:1024GB:nvme:512:512:gpt:Lexar SSD NM620 1TB:;
1:1049kB:106MB:105MB:fat32:Basic data partition:boot, esp, no_automount;
2:106MB:123MB:16.8MB::Microsoft reserved partition:msftres, no_automount;
3:123MB:1024GB:1023GB:ntfs:Basic data partition:msftdata, no_automount;
4:1024GB:1024GB:675MB:ntfs::hidden, diag, no_automount;
nvme1n1:1000GB:nvme:512:512:msdos:Samsung SSD 970 EVO Plus 1TB:;
1:1049kB:1000GB:1000GB:ext4::boot;
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
└─sda1 ext4 9bebeba8-b221-4428-ae2a-c8a1937664de ea8243fa-0251-4a67-bd94-f0bda0baeec7 Musique
sdb
├─sdb1 ntfs 8442119B42119352 d2892678-01
└─sdb2 ntfs 345C13905C134BCC d2892678-02
nvme1n1
└─nvme1n1p1 ext4 708676df-abc7-496c-bd32-1478d56bc258 eb599480-01 kubuntu_2504
nvme0n1
├─nvme0n1p1 vfat 9498-F47D ae3728e8-7119-4e3f-bf1b-92d876aacb24 Basic data partition
├─nvme0n1p2 395c4994-d171-4b28-a66b-6c20e97003ad Microsoft reserved partition
├─nvme0n1p3 ntfs 822A9BDF2A9BCE93 08656ec7-d089-4347-819f-dbdbc9f9714f Basic data partition
└─nvme0n1p4 ntfs 8A469E69469E5633 126c595b-e1c5-4bc9-b73f-50bae1211ea4
Mount points (filtered): _______________________________________________________
Avail Use% Mounted on
/dev/nvme0n1p1 62.7M 35% /mnt/boot-sav/nvme0n1p1
/dev/nvme0n1p3 871.4G 9% /mnt/boot-sav/nvme0n1p3
/dev/nvme0n1p4 70.9M 89% /mnt/boot-sav/nvme0n1p4
/dev/nvme1n1p1 601G 29% /
/dev/sda1 1.1T 34% /mnt/boot-sav/sda1
/dev/sdb1 89.9M 10% /mnt/boot-sav/sdb1
/dev/sdb2 924.5G 1% /mnt/boot-sav/sdb2
Mount options (filtered): ______________________________________________________
/dev/nvme0n1p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/nvme0n1p3 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p4 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme1n1p1 ext4 rw,relatime
/dev/sda1 ext4 rw,relatime
/dev/sdb1 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sdb2 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
=================== nvme1n1p1/boot/grub/grub.cfg (filtered) ====================
Kubuntu 708676df-abc7-496c-bd32-1478d56bc258
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###
Windows 11
======================== nvme1n1p1/etc/fstab (filtered) ========================
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=708676df-abc7-496c-bd32-1478d56bc258 / ext4 defaults 0 1
/swapfile swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
==================== nvme1n1p1/etc/default/grub (filtered) =====================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR='Kubuntu'
GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=true
GRUB_DISABLE_OS_PROBER=false
================= nvme1n1p1: Location of files loaded by Grub ==================
GiB - GB File Fragment(s)
104,700706482 = 112,421527552 boot/grub/grub.cfg 1
265,336009979 = 284,902371328 boot/grub/i386-pc/core.img 1
1,460971832 = 1,568706560 boot/vmlinuz 1
265,352535248 = 284,920115200 boot/vmlinuz-6.14.0-15-generic 2
1,460971832 = 1,568706560 boot/vmlinuz-6.14.0-22-generic 1
265,352535248 = 284,920115200 boot/vmlinuz.old 2
76,540035248 = 82,184237056 boot/initrd.img 3
1,347839355 = 1,447231488 boot/initrd.img-6.14.0-15-generic 1
76,540035248 = 82,184237056 boot/initrd.img-6.14.0-22-generic 3
1,347839355 = 1,447231488 boot/initrd.img.old 1
=================== nvme1n1p1: ls -l /etc/grub.d/ (filtered) ===================
-rwxr-xr-x 1 root root 18133 avr 10 09:23 10_linux
-rwxr-xr-x 1 root root 43202 avr 10 09:23 10_linux_zfs
-rwxr-xr-x 1 root root 14513 avr 10 09:23 20_linux_xen
-rwxr-xr-x 1 root root 786 avr 10 09:23 25_bli
-rwxr-xr-x 1 root root 13120 avr 10 09:23 30_os-prober
-rwxr-xr-x 1 root root 1174 avr 10 09:23 30_uefi-firmware
-rwxr-xr-x 1 root root 730 mar 25 12:35 35_fwupd
-rwxr-xr-x 1 root root 77 jun 19 20:13 40_custom
-rwxr-xr-x 1 root root 215 avr 10 09:23 41_custom
================== nvme1n1p1/etc/grub.d/40_custom (filtered) ===================
menuentry "Windows 11" {
set root=(hd0,gpt1)
chainloader +1
ntldr /bootmgr
}
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would reinstall the grub-efi of
nvme1n1p1,
using the following options: nvme0n1p1/boot/efi
Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file
Blockers in case of suggested repair: __________________________________________
WindowsEFI detected. Please disable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB) that is compatible with UEFI booting mode. For example, use a live-USB of Boot-Repair-Disk-64bit (www.sourceforge.net/p/boot-repair-cd), after making sure your BIOS is set up to boot USB in EFI mode.
Final advice in case of suggested repair: ______________________________________
Please do not forget to make your UEFI firmware boot on the L'OS actuellement utilisé - Ubuntu 25.04 entry (nvme0n1p1/efi/****/grub****.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\****\grub****.efi (**** will be updated in the final message)
The boot of your PC is in BIOS-compatibility/CSM/Legacy mode. You may want to retry after changing it to UEFI mode.cmd bcdedit dans win11
Microsoft Windows [Version 10.0.26100.4351]
(c) Microsoft Corporation. All rights reserved.
C:\Windows\System32>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {1987aac8-49c6-11f0-8f09-cb599d4a8a06}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 11
locale en-US
inherit {bootloadersettings}
recoverysequence {1987aaca-49c6-11f0-8f09-cb599d4a8a06}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {1987aac8-49c6-11f0-8f09-cb599d4a8a06}
nx OptIn
bootmenupolicy Standard
C:\Windows\System32>i /etc/grub.d/40_custom
menuentry "Windows 11" {
set root=(hd0,gpt1)
chainloader +1
ntldr /bootmgr
}grub
# If you change this file or any /etc/default/grub.d/*.cfg file,
# run 'update-grub' afterwards to update /boot/grub/grub.cfg.
# For full documentation of the options in these files, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR='Kubuntu'
GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
GRUB_DISABLE_OS_PROBER=true
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE/GOP/UGA
# you can see them in real GRUB with the command `videoinfo'
#GRUB_GFXMODE=640x480
GRUB_DISABLE_OS_PROBER=false
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"merci de votre aide
Dernière modification par soujaa (Le 24/06/2025, à 00:30)
Hors ligne
#2 Le 21/06/2025, à 04:47
- nany
Re : [OK] Dual-boot Win11 brisé dans grub [Win11 (nvme0) Kubuntu (nvme1)]
Bonjour,
Kubuntu est installé en LEGACY alors que Windows est installé en EFI.
Il faudrait donc refaire l’installation de Kubuntu en EFI.
À noter qu’il y a deux entrées GRUB_DISABLE_OS_PROBER dans l’actuel fichier /etc/default/grub.
Hors ligne
#3 Le 21/06/2025, à 08:27
- O_20_100_O
Re : [OK] Dual-boot Win11 brisé dans grub [Win11 (nvme0) Kubuntu (nvme1)]
Bonjour,
Une des autres solutions possibles, vu que Windows est en UEFI, serait d'utiliser rEFInd en remplacement de Grub.
Il permet de démarrer tous les OS de la machine, qu'ils soient installés en mode UEFI ou en legacy.
Hors ligne
#4 Le 21/06/2025, à 08:41
- iznobe
Re : [OK] Dual-boot Win11 brisé dans grub [Win11 (nvme0) Kubuntu (nvme1)]
Bonjour , il me semble ( mais me rappelle plus précisément la manip a effectuer ) que c' est assez simple de " transformer " ubuntu LEGACY en EFI .
il faut à minima monter la partition EFI dans le fstab , et les variables .
c' est @geole qui sait précisément comment faire . et c' est bien plus rapide qu ' une réinstallation ( meme sur un NVME 
) .
retour COMPLET et utilisable de commande | script montage partitions
MSI Z490A-pro , i7 10700 , 32 GB RAM .
Hors ligne
#5 Le 21/06/2025, à 10:01
- geole
Re : [OK] Dual-boot Win11 brisé dans grub [Win11 (nvme0) Kubuntu (nvme1)]
Bonjour
Hormis le fait que windows est capable d'installer refind......
https://doc.ubuntu-fr.org/uefi#convertir_ubuntu_en_mode_efi a écrit :
Convertir Ubuntu en mode EFI ou non-EFI
Convertir Ubuntu en mode EFIPour que cette conversion soit possible, il faut régler votre BIOS pour qu'il démarre sur le disque dur en mode EFI (voir le paragraphe Régler le démarrage en mode EFI ou classique ci-dessus). De plus, il faut opérer depuis une session live démarrée en mode EFI (voir le paragraphe Identifier si l'ordinateur démarre sur le CD (ou la live USB) en mode EFI).
Vérifiez que votre disque a une table de partition GPT et pas MBR, si besoin faites la conversion avec gdisk.
Démarrer Boot-Repair, cliquer sur "Options avancées", et aller dans l'onglet "Emplacement de GRUB".
Si vous ne voyez pas une ligne "Partition /boot/efi séparée", cela signifie que votre PC n'a pas de partition EFI. Dans ce cas, quittez Boot-Repair, puis créez une partition EFI (voir paragraphe "Créer une partition EFI" ci-dessus).
Si vous voyez une ligne "Partition /boot/efi séparée", cochez-la puis cliquez sur le bouton "Appliquer".Une partition installée en mode 32 bits n'est pas convertible par boot-repair en mode EFI.
Il suffit de le faire en ligne de commandes.
Si pour une raison spéciale, vous ne pouvez pas booter en EFI alors que le bios est EFI, vous pouvez tenter de faire cette installation en ligne de commandes.
sudo apt install grub-efi-amd64 sudo grub-install /dev/sda --no-nvram --efi-directory=/boot/efi --target=x86_64-efi
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#6 Le 21/06/2025, à 13:54
- soujaa
Re : [OK] Dual-boot Win11 brisé dans grub [Win11 (nvme0) Kubuntu (nvme1)]
Bon matin
Merci a tous pour vos reponses. Je dois voyager a mon retour j'essaie vos solutions. Encore merci et à tantôt
Hors ligne
#7 Le 24/06/2025, à 00:26
- soujaa
Re : [OK] Dual-boot Win11 brisé dans grub [Win11 (nvme0) Kubuntu (nvme1)]
Bonjour
De retour
J'ai eu peur de la grosse manip proposé par geole alors j'ai installé rEFInd.
comme la documentaion
sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc) universe"
sudo apt update
sudo apt install refindValider sur non puis
sudo mount -v $(sudo blkid | grep vfat | cut -d: -f1 | head -1) /mnt # Monter la partition de boot ESP.
sudo cp -rv /usr/share/refind/* /mnt/EFI/boot # Installer refind dans le répertoire de boot.
sudo cp -v /mnt/EFI/boot/refind_x64.efi /mnt/EFI/Boot/bootx64.efi # Dire qu'il devient le fichier de boot officiel.
exitEt surtout regler le demarrage sur Windows Boot Manager.
Ainsi j'ai obtenu un tres beau REFIND
Merci O_20_100_O merci a tous
Vive le libre
Hors ligne