Dual Boot Zorin18 Windows 11 impossible?

msjs · November 6, 2025, 12:06pm

May I ask for some additional support, please? It's my first time with Unix for 30 years!!!

I did not have any trouble installing Education to an empty drive but trying to install Pro as a dual op with Windows 11 is proving impossible whilst following your instructions and I really want to see this work with the minimum amount of user intervention. GPT and UEFI are also "givens".

The installation software does not behave in accordance with the help file from the website.

I have 3 physical disks in my pc -

Disk I is a slow scsi phycial disk used as backup mirroring two different sorts of shared remote devices - physical NAS and Cloud;

Disk 2 NVME is used as a system disk and for Windows specific utilities;

Disk 3 NVME used for Games software and programming utilities.

Disk 2 is the logical place to put a dual op.

Following the instructions ... When I reach the screen which says "Install Zorin OS alongside Windows Boot Manager - Select Drive the only option I am given is Disk 1 which is the worst possible option.

I have tried with Disk 2 configured with all free space allocated to drive C:, with 250mb of unallocated space, with an unformatted drive P, and with Drive P formatted.

None of these configurations give me the option to use Disk1 or Disk 2.

Finally, I tried installing to Disk 1. This went through the whole installation process but when I rebooted nothing had actually ben installed anywhere - it was like a "phantom install".

So I merged Drive C with Drive P and tried again using the Zorin install something else routine. Another phantom install. And the free space created by the install now shows as "unallocated". Format as EXT4 and try again.

UEFI still only sees Windows11 boot.

I ran the routine to fix the boot loader but still no grub.

I have attached snapshots.

littlekun · November 6, 2025, 1:20pm

Make sure Fast Startup is disabled inside Windows.
Disable Secure boot inside BIOS/UEFI firmware setup.
If possible remove the additional Drives from the PC before starting the installation and keep the only drive in which you want to install Zorin.
After the Zorin installation finished, go to BIOS/UEFI and locate boot order list -- put Ubuntu option at top.

If still no luck then provide additional information about your system and specifications. You can run the following command in a terminal window during the Zorin live session and share the output here:

inxi -Fxxxz

Ponce-De-Leon · November 6, 2025, 1:53pm

Welcome to the Forum!

Based on Your default Setup where You want use Disk 2 as the Installation Drive:

Use in Windows the Disk Management Tool and create on Disk 2 free Space for Zorin (which You seem to have already done). Create the bootable USB Stick with Zorin on it. Because You are on Windows, Rufus is a good Tool. Choose in Rufus on the ''Partition Sheme'' Option GPT.

Then start the USB Stick. During the Installation choose the Installation Type ''Something else''. Here You create manually the Partitions. You have to do 3 Things here:

Choose the Disc where You want install Zorin (in the upper right Corner)
Take the free Space that You created earlier and give it the Mount Point / and format it to ext4
Under the Option ''Device fo boot loader installation'' choose in the Dropdown Menu the Option ''Windows Boot Manager''

msjs · November 6, 2025, 5:09pm

Thank you for the timely advice.

msjs · November 6, 2025, 5:25pm

Thank you for the good advice.

I've done these things multiple times but the only result is Windows bootloader is screwed (I've lost the correct drivers for keyboard and mouse in PE).

I can force the PC to boot to the GRUB prompt but the bootloader for Zorin also appears to be screwed, which is why I've included the Ubuntu repair report.

I can deal with the Windows stuff, it's just a little inconvenient to have to fix an OS that I want to junk anyway, but I don't know anything about how to fix the problem with Zorin.

I don't even actually understand the problem.

MJS

Ponce-De-Leon · November 6, 2025, 6:13pm

When You start Zorin in Live Mode (choose Try Zorin), search for Boot Repair and let it run. Maybe that helps.

When it is this:

It is hidden behind a Login.

msjs · November 7, 2025, 5:49am

boot-repair-4ppa2081-zorin1                                              [20251106_1033]

============================== Boot Info Summary ===============================

 => No boot loader is installed in the MBR of /dev/nvme0n1.
 => Windows is installed in the MBR of /dev/nvme1n1.
 => No known boot loader is installed in the MBR of /dev/sda.
 => No boot loader is installed in the MBR of /dev/sdb.

nvme0n1p1: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  According to the info in the boot sector, nvme0n1p1 
                       starts at sector 0. But according to the info from 
                       fdisk, nvme0n1p1 starts at sector 2048.
    Operating System:  
    Boot files:        

nvme0n1p2: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

nvme1n1p1: _____________________________________________________________________

    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/Boot/fbx64.efi 
                       /efi/Boot/mmx64.efi /efi/ubuntu/grubx64.efi 
                       /efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi 
                       /efi/ubuntu/grub.cfg /efi/Microsoft/Boot/bootmgfw.efi 
                       /efi/Microsoft/Boot/bootmgr.efi 
                       /efi/Microsoft/Boot/cbmr_driver.efi 
                       /efi/Microsoft/Boot/SecureBootRecovery.efi

nvme1n1p2: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

nvme1n1p3: _____________________________________________________________________

    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:        /bootmgr /Windows/System32/winload.exe

nvme1n1p4: _____________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        

nvme1n1p5: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

nvme1n1p6: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sda1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /boot/grub/grub.cfg /syslinux.cfg

sda2: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT16
    Boot sector info:  According to the info in the boot sector, sda2 starts 
                       at sector 0. But according to the info from fdisk, 
                       sda2 starts at sector 122907582. According to the info 
                       in the boot sector, sda2 has 0 sectors.
    Operating System:  
    Boot files:        /efi/Boot/bootaa64.efi /efi/Boot/bootarm.efi 
                       /efi/Boot/bootia32.efi /efi/Boot/bootx64.efi 
                       /efi/Rufus/exfat_aa64.efi /efi/Rufus/exfat_arm.efi 
                       /efi/Rufus/exfat_ia32.efi /efi/Rufus/exfat_x64.efi 
                       /efi/Rufus/ntfs_aa64.efi /efi/Rufus/ntfs_arm.efi 
                       /efi/Rufus/ntfs_ia32.efi /efi/Rufus/ntfs_x64.efi

sdb1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sdb2: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        


================================ 1 OS detected =================================

OS#1 (windows):   Windows 10 or 11 on nvme1n1p3

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] from Advanced Micro Devices, Inc. [AMD/ATI]
Live-session OS is Zorin 64-bit (Zorin OS 18, noble, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: A.40(5.17) from American Megatrends Inc.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0003,0000,0001
Boot0000* Windows Boot Manager	HD(1,GPT,ae1343d9-326b-42bb-9b1b-95b482625cf8,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0001* Zorin OS	HD(1,GPT,ae1343d9-326b-42bb-9b1b-95b482625cf8,0x800,0x32000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0002* UEFI: Generic STORAGE DEVICE 1404, Partition 1	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(3,0)/HD(1,GPT,6d00ee85-a41e-4f86-9628-99f8d455d0e7,0x800,0x7536398)0000424f
Boot0003* UEFI: Generic STORAGE DEVICE 1404, Partition 2	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(3,0)/HD(2,GPT,1a109b60-8b2f-4a6b-8647-8cf325b2a3e4,0x7536bbe,0x81f)0000424f

07e25dcaf57c776875f78fa36827c58e   nvme1n1p1/Boot/bootx64.efi
39bc76ff6662f4fbe9aa116e4c997b41   nvme1n1p1/Boot/fbx64.efi
4ba5a5aad43c197e9fb58b76b404d287   nvme1n1p1/Boot/mmx64.efi
94c7467f956700d44c5b4dcd3967535c   nvme1n1p1/ubuntu/grubx64.efi
4ba5a5aad43c197e9fb58b76b404d287   nvme1n1p1/ubuntu/mmx64.efi
07e25dcaf57c776875f78fa36827c58e   nvme1n1p1/ubuntu/shimx64.efi
5a2a56ec90a9e18a186e8aecf57515f5   nvme1n1p1/Microsoft/Boot/bootmgfw.efi
cee6ba033a2c963880f0d92778ed36a7   nvme1n1p1/Microsoft/Boot/bootmgr.efi
b8796e68099026aabcebb8fcf75b21f6   nvme1n1p1/Microsoft/Boot/cbmr_driver.efi
2460f2fe283f93b48d7618e4d8fcf05e   nvme1n1p1/Microsoft/Boot/SecureBootRecovery.efi
04f7ca0c54a2599ae03a76a07b70fbc6   sda2/Boot/bootaa64.efi
aad0826b374492d46765e285074fadc7   sda2/Boot/bootarm.efi
2d17324aae2d8a34afb37eb23abc6c54   sda2/Boot/bootia32.efi
b9a759335d3910c0762b020946174e70   sda2/Boot/bootx64.efi
4a4e8e66e0d3712f19d964a7bca4fafc   sda2/Rufus/exfat_aa64.efi
93f66a43d49990f986a81c67843d66a5   sda2/Rufus/exfat_arm.efi
3c5f23f198267df4a64fe2a3587039e7   sda2/Rufus/exfat_ia32.efi
81d015f35982a0bbf4056f09a2eca39a   sda2/Rufus/exfat_x64.efi
a03e27b0e7f2e03519166bf6b41f68c5   sda2/Rufus/ntfs_aa64.efi
2f31c70d3f4235476cd9ed6a18e13221   sda2/Rufus/ntfs_arm.efi
7e7e67c33ce9ff2961a4be4080d23352   sda2/Rufus/ntfs_ia32.efi
30c7e0752040cf5e31843d897a53e055   sda2/Rufus/ntfs_x64.efi

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

nvme0n1	: is-GPT,	no-BIOSboot,	has-noESP, 	not-usb,	not-mmc, no-os,	no-wind,	2048 sectors * 512 bytes
nvme1n1	: is-GPT,	no-BIOSboot,	has---ESP, 	not-usb,	not-mmc, has-os,	has-win,	2048 sectors * 512 bytes
sdb	: is-GPT,	no-BIOSboot,	has-noESP, 	not-usb,	not-mmc, no-os,	no-wind,	2048 sectors * 512 bytes
sda	: is-GPT,	no-BIOSboot,	has-noESP, 	usb-disk,	not-mmc, no-os,	no-wind,	2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

nvme0n1p1	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB
nvme0n1p2	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB
nvme1n1p1	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	not-far
nvme1n1p3	: is-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB
nvme1n1p4	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB
nvme1n1p5	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB
nvme1n1p6	: 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,	end-after-100GB
sda2	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB

Partitions info (2/3): _________________________________________________________

nvme0n1p1	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ntfs
nvme0n1p2	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ntfs
nvme1n1p1	: is---ESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, vfat
nvme1n1p3	: isnotESP,	part-has-no-fstab,	no-nt,	haswinload,	no-recov-nor-hid,	bootmgr,	notwinboot, ntfs
nvme1n1p4	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ext4
nvme1n1p5	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	recovery-or-hidden,	no-bmgr,	notwinboot, ntfs
nvme1n1p6	: 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
sda2	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, vfat

Partitions info (3/3): _________________________________________________________

nvme0n1p1	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme0n1
nvme0n1p2	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme0n1
nvme1n1p1	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme1n1
nvme1n1p3	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme1n1
nvme1n1p4	: maybesepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme1n1
nvme1n1p5	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme1n1
nvme1n1p6	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme1n1
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
sda2	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	sda

fdisk -l (filtered): ___________________________________________________________

Disk sda: 58.61 GiB, 62929764352 bytes, 122909696 sectors
Disk identifier: 5887E279-1DC2-47C0-9ED8-CA93CBA28867
         Start       End   Sectors  Size Type
sda1       2048 122907543 122905496 58.6G Microsoft basic data
sda2  122907582 122909660      2079    1M Microsoft basic data
Disk sdb: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk identifier: 0DFB13BD-5858-9090-8081-828310111213
          Start        End    Sectors  Size Type
sdb1        2048 2574620130 2574618083  1.2T Microsoft basic data
sdb2  2574621056 5860529071 3285908016  1.5T Microsoft basic data
Disk nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk identifier: 0EF01726-5858-9090-8081-828310111213
              Start        End    Sectors   Size Type
nvme0n1p1       2048 2481660208 2481658161   1.2T Microsoft basic data
nvme0n1p2 2481673005 3907024064 1425351060 679.7G Microsoft basic data
Disk nvme1n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk identifier: AD605763-43DB-4791-AD4B-2F6473085B06
             Start       End   Sectors   Size Type
nvme1n1p1      2048    206847    204800   100M EFI System
nvme1n1p2    206848    239615     32768    16M Microsoft reserved
nvme1n1p3    239616 525044303 524804688 250.2G Microsoft basic data
nvme1n1p4 525045760 974261923 449216164 214.2G Microsoft basic data
nvme1n1p5 974262272 975732735   1470464   718M Windows recovery environment
nvme1n1p6 975732736 976769071   1036336   506M Windows recovery environment

parted -lm (filtered): _________________________________________________________

sda:62.9GB:scsi:512:512:gpt:Generic STORAGE DEVICE:;
1:1049kB:62.9GB:62.9GB:ntfs:Main Data Partition:msftdata;
2:62.9GB:62.9GB:1064kB::UEFI:NTFS:msftdata, no_automount;
sdb:3001GB:scsi:512:4096:gpt:ATA ST3000DM007-1WY1:;
1:1049kB:1318GB:1318GB:ntfs:Basic data partition:msftdata;
2:1318GB:3001GB:1682GB:ntfs:Basic data partition:msftdata;
nvme0n1:2000GB:nvme:512:512:gpt:Samsung SSD 980 PRO 2TB:;
1:1049kB:1271GB:1271GB:ntfs:Basic data partition:msftdata;
2:1271GB:2000GB:730GB:ntfs:Basic data partition:msftdata;
nvme1n1:500GB:nvme:512:512:gpt:Samsung SSD 970 EVO 500GB:;
1:1049kB:106MB:105MB:fat32:EFI system partition:boot, esp, no_automount;
2:106MB:123MB:16.8MB:ntfs:Microsoft reserved partition:msftres, no_automount;
3:123MB:269GB:269GB:ntfs:Basic data partition:msftdata;
4:269GB:499GB:230GB:ext4:Basic data partition:msftdata;
5:499GB:500GB:753MB:ntfs::diag;
6:500GB:500GB:531MB:ntfs::diag;

blkid (filtered): ______________________________________________________________

NAME        FSTYPE   UUID                                 PARTUUID                             LABEL                 PARTLABEL
sda                                                                                                                  
├─sda1      ntfs     685C95D85C95A17C                     6d00ee85-a41e-4f86-9628-99f8d455d0e7 Zorin OS 18 Pro 64bit Main Data Partition
└─sda2      vfat     FA4D-00ED                            1a109b60-8b2f-4a6b-8647-8cf325b2a3e4 UEFI_NTFS             UEFI:NTFS
sdb                                                                                                                  
├─sdb1      ntfs     0EAA07AC0EAA07AC                     f82ef5ef-5fe6-11eb-abdd-806e6f6e6963 Linkstation Backup    Basic data partition
└─sdb2      ntfs     0DF2023E0DF2023E                     f82ef5f0-5fe6-11eb-abdd-806e6f6e6963 More Backup           Basic data partition
nvme0n1                                                                                                              
├─nvme0n1p1 ntfs     0EF015010EF01501                     dda2497c-4cc7-11ee-acfe-2cf05d5cf07b Games Volume          Basic data partition
└─nvme0n1p2 ntfs     0E9402110E940211                     f587fa3d-b8d1-11f0-b234-90775e87693d Witcher               Basic data partition
nvme1n1                                                                                                              
├─nvme1n1p1 vfat     E012-10ED                            ae1343d9-326b-42bb-9b1b-95b482625cf8                       EFI system partition
├─nvme1n1p2 ntfs     0E9D08B50E9D08B5                     5b0b9d9f-f8c8-4478-969b-68fe5d9f3cb1 odd                   Microsoft reserved partition
├─nvme1n1p3 ntfs     8A74129074127EDF                     dd88b6cb-3862-4525-b443-c9d71cf67a09                       Basic data partition
├─nvme1n1p4 ext4     cd77a1b9-c071-8c4a-ba47-0ab5b66154dd 293e56ea-baec-11f0-b243-d6bb46ce4b70                       Basic data partition
├─nvme1n1p5 ntfs     7AC2E393C2E351C5                     2c1cbaa8-71a6-474a-acc8-a2e4194a343a                       
└─nvme1n1p6 ntfs     7CEAD9B6EAD96D40                     2ee1cc9e-a337-47c8-8423-7a95aafb5bde                       

Mount points (filtered): _______________________________________________________

                Avail Use% Mounted on
/dev/nvme0n1p1 804.4G  32% /mnt/boot-sav/nvme0n1p1
/dev/nvme0n1p2 515.5G  24% /mnt/boot-sav/nvme0n1p2
/dev/nvme1n1p1  58.9M  39% /mnt/boot-sav/nvme1n1p1
/dev/nvme1n1p3  72.7G  71% /mnt/boot-sav/nvme1n1p3
/dev/nvme1n1p4 199.1G   0% /mnt/boot-sav/nvme1n1p4
/dev/nvme1n1p5  84.7M  88% /mnt/boot-sav/nvme1n1p5
/dev/nvme1n1p6 496.1M   2% /mnt/boot-sav/nvme1n1p6
/dev/sda1       50.9G  13% /cdrom
/dev/sda2        130K  87% /media/zorin/UEFI_NTFS
/dev/sdb1      147.7G  88% /mnt/boot-sav/sdb1
/dev/sdb2      482.2G  69% /mnt/boot-sav/sdb2
efivarfs        94.1K  23% /sys/firmware/efi/efivars

Mount options (filtered): ______________________________________________________

/dev/nvme0n1p1 fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p2 fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme1n1p1 vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/nvme1n1p3 fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme1n1p4 ext4            rw,relatime
/dev/nvme1n1p5 fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme1n1p6 fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sda1      fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sda2      vfat            rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro
/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/efi/ubuntu/grub.cfg (filtered) ===================

search.fs_uuid 7cc33f26-eb40-42b4-99fe-c4757f3698b7 root 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

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

Try or Install Zorin OS
Try or Install Zorin OS (safe graphics)
Try or Install Zorin OS (modern NVIDIA drivers)
UEFI Firmware Settings
Power Off

========================= sda1/syslinux.cfg (filtered) =========================

DEFAULT loadconfig

LABEL loadconfig
  CONFIG /isolinux/isolinux.cfg
  APPEND /isolinux/

==================== sda1: Location of files loaded by Grub ====================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/grub.cfg                             1

================== sda1: Location of files loaded by Syslinux ==================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             syslinux.cfg

======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown MBR on /dev/sda


/dev/nvme1n1p1: unknown GPT attributes
8000000000000000

/dev/nvme1n1p2: unknown GPT attributes
8000000000000000

/dev/sda2: unknown GPT attributes
9000000000000000



Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the MBR.
Additional repair would be performed:  win-legacy-basic-fix

sprunge.us ko ()

Aravisian · November 7, 2025, 6:01am

Above, we can see that Windows is detected as MBR (Legacy) boot, despite you having an EFI partition with bootloaders in it.
You can see both the Microsoft and Zorin OS bootloaders in EFI:

Correct me if I am wrong, but it looks like Windows 7 was installed in MBR, then later upgraded/converted to Windows 10 or 11 with EFI boot.

If you can boot Windows, open a CMD prompt and run

mbr2gpt /convert /allowfullos

IF that completes successfully, then repair Grub.
You can do this by booting the Zorin LiveUSb, ensuring that the drive is Unmounted using Disks app, then in terminal, run

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Zorin

sudo update-grub

doobre · November 7, 2025, 10:12am

Hi there.
I have not been able to set things up the way you wish to either. Select your choice of OS from the Bios Boot List.

Good suggestion to remove all other drives 'temporarily' and make unallocated space ahead of time.

However, even though I create all three necessary partitions efi, root and home on the only installed disk, and booting from that disk works when on it's own. When the windows disk (which is an internal nvme) is seen by the bios the zorin disk is ignored.

Booting from the Z USB 'live' and running the 'boot repair' only results in the report saying that the "nvme is locked" and leaves the pc unbootable.

If start another install with the nvme being 'seen' during the installation and choosing the nvme drive as the "location for the boot device", the install completes up until the point where it needs to restart to complete the installation process.
There again I get the nvme locked message, and I need to fix the windows booting again.
Furthermore, if I choose the 'install along side' an OS, I get the same result.
Perhaps I have two separate issues.

Bios doesn't seems to recognise the zorin disk's efi partition, so doesn't show up in the bios boot list.

Anyway, good luck with your install and please keep this updated with any more info, or successes.

cheers CD

swarfendor437 · November 7, 2025, 10:22am

Another possible reason, if mbr has been used is that if there are 4 partitions in Windows all marked as Primary, then even making space for Zoein will result in a failed install. At this point if there are essential partitions, then backup the least important partition before deleting it. I would also take a look at Neosmart's free version of EasyBCD which I believe now supports Windows 11.

Here is a video I made a long time ago about dual booting Windows 7 and Zorin 9 Ultimate:

I also recomnend removing other drives. I recently lost my PCLOS Debian install when attempting to install Endeavour OS, I identified the drive it should have installed to but it overwrote my PCLOS Debian install. Aaaarrrrgggghhhh!

msjs · November 7, 2025, 3:41pm

"Correct me if I am wrong, but it looks like Windows 7 was installed in MBR, then later upgraded/converted to Windows 10 or 11 with EFI boot"

Thank you for this insight - I clearly need to do a lot more research into this.

This desktop was a ground up build in January 2021 with a clean install of Windows 10 Pro, then rebuilt as Windows 11 Pro as soon as it was available. Always efi. Always kept up to date.

There is some real weirdness here.

The last release of Windows 11 is seriously bugged. So much that I have just finished applying manual patches released by Microsoft to enable access to WinRe to at least take a look at repairing the Windows Boot. The automatic repair says it has corrected some disk IO errors which is a surprise on a lightly used NVMe but I'll take a further look into this along with repairing Grub.

mbr2gpt fails with typically unhelpful messages. There must be a log buried somewhere!

I have no idea what else doesn't work following 25H2.

Thank you again.

msjs · November 7, 2025, 3:50pm

Good thought. EasyBCD is an old friend but apparently no longer

Take a look ...

Ponce-De-Leon · November 7, 2025, 5:51pm

Did You already checked that YourBIOS is in UEFI or Legacy Mode? Another Thing would be the Drive itself. On Your Pictures above stands that it is in GPT ...

When You start Zorin from the USB Stick in Live Mode and open GParted or Disks, what show these for the Drives?

Aravisian · November 7, 2025, 6:18pm

Was the SSD a used SSD?

msjs:

nvme0n1p1: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  According to the info in the boot sector, nvme0n1p1 
                       starts at sector 0. But according to the info from 
                       fdisk, nvme0n1p1 starts at sector 2048.
    Operating System:  
    Boot files:        

nvme0n1p2: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:

Wait...

It was used.
Think it retained the old Win 7 Bootloader?

doobre · November 8, 2025, 5:40am

Hi there, OKi doki, answering my own query..

Finally a breakthrough with getting the bios to recognise the two separate SSD disks with two separate installs (Win11 and Z17.3 Pro).

This time, I avoided completely using the HP-Z4 and carried out the Z pro install on an old HP desktop, again removing the windows10 installed disk, and using the complete install option in Zorin. The "Erase Everything" option. This created only two partitions, a 537MB Fat32 EFI partition and the remaining space as the root and home directories.

The bios of the old HP was already setup for UEFI and Legacy boot options.

I checked that it booted from the Z disk correctly, connected up the win10 disk and checked that the two options were there.

edit - forgot to mention that I restored the earlier version of the bios and reset that back to factory.

Removed the Z disk and connected it to the HP-Z4 and the bios recognised only the two SSD's ("UEFI Ubuntu" and "Windows Boot Manager") with Ubuntu as the top option, Yippee, just what I wanted.

So that is a big headache out of the way, I can now concentrate on personalising the Z setup. On the same hardware, Zorin is so much more zippy than win11, even with the 32Gb ram and i9. It feels unencumbered to use without the lag you get with Windows, waiting for a window to open etc. I'm a bit fussy these days.

One thing I want to mention that caused me unnecessary distraction > in Win11 every disk installed in the PC is shown as a removable drive, even to the extent that they show up in the 'USB Remove' list on the win11 taskbar. Also the bios showed them as a boot option in the boot list (press ESC during startup) which was a surprise to me until I, only recently, understood what was happening. I have since disabled them in the bios setup, and now have only the Ubuntu and the Windows Boot Manager options.
However, having tried many suggestions from many forums they still appear as such. A bios update didn't sort it out. So just be aware of this weirdness and don't be distracted, as I was.
cheers CD

P.S. I will be staying on Pro 17.3 though. 18 has too many 'issues' for me.

msjs · November 8, 2025, 11:43am

The NVMe drive was straight out the packet but it might be a Windows 10 bug.

Anyhow, I bumped heads with Windows TrustedInstaller this morning and it has effectively bricked Windows 11 25H2 by blocking any access to windows repair Routines and all my backups. it will only allow a clean install of Windows 11 or I can boot from w2go. But the w11 install with the ubuntu boot files is verbotten.

I can still access Grub through the bios so I guess I'll use that.

So all I have to do now is repair Grub

doobre · November 11, 2025, 5:55am

Hi there, thanks for your update.

I think you'll prefer to do the switching only through the bios, since over time it will only take a win11 update to muck up the grub. Which is what I was avoiding.
cheers CD

msjs · November 12, 2025, 8:16am

Brief update / what I've learned so far in testing the install ...

Windows 11 25H2 is a pain. Windows 11 24H2 isn't much better.

Following Zorin 18 install instructions to the letter "bricked" my Windows 11 Boot routine. Then Microsoft blocked the repair routine as it failed to authenticate the damaged Windows 11 install. Microsoft also tried to block my backup WTG system disk until I got the correct Secure Boot keys loaded. This whole area is a mess for Microsoft users and way beyond my "pay grade".

Samsung Magician is the only tool I've tried that does OS migration correctly for Windows 11.

Windows RE leaves traces of Windows 7 on the system.

I've now got Windows 11 and Zorin 18 to co-habit peacefully.

I ran the Zorin 18 install with Secure Boot and TPM turned on and 3 disks installed in the PC.

I used the install routine to split the system disk.

When I got to the part that says where do you want to put the Boot I specified the current sector with the Windows Boot Manager, despite the warning not to.

Linux is so much friendlier then Windows even though I don't know what I'm doing yet.

I will do some more clean up in Windows then do another, more carefully controlled Zorin 18 install.

wesoliv429 · November 12, 2025, 1:37pm

hmm i saw he posted that he installed win 25H2 this is a problem as microsoft is now blocking the install of any linux/other OS my understanding of correcting this is to low format write 0's to entire drive to make it back to factory. may have to do to all drives to get whatever 25H2 did to all connected drives. gotta love when Microsoft dont want you to use another OS but this is what they are doing now

msjs · November 13, 2025, 10:35am

I also said this is above my pay grade.

However, I do now have a working dual boot of Zorin18 and Windows 11 25H2 and give thanks to the guys here (and at Microsoft) whose advice was invaluable.

From my experience in testing this, taking the drive back to "factory" is unlikely to make any difference if you're unable to get Linux/Windows 11 to work.

If you're doing a clean install of Windows 11 it will put a fresh copy of whatever it needs on disk into a fresh partition wherever it thinks it needs it.

There are other factors at work here.

The registry/boot store is only one part of the Microsoft security strategy. The key that proves the software is Microsoft certified is also available in Bios and in the Microsoft central repository.

All three sources have to agree the key is valid. It might be possible to install Windows as a "Local Account" but that's a level of complexity I haven't investigated. I used run everything Microsoft from a local account but that was a while ago so I am very out of date.

Wrapped up in all this is Microsoft's evolving strategy towards authentication which is creating another layer of complexity. Many copies of Windows now only have a digital signature that is tied to a single drive. If you change the drive Windows should automatically update the central server with details of the new drive. Windows has to be the same version and you have to be online. Otherwise it's "phone Microsoft". Good luck with that process working faultlessly every time!

I've gone back to 24H2 because I have a clean backup that I know works. 25H2 has bugs I don't want to have to manually patch every time I mess with the OS.

When I finish testing Linux distros and I have a stable environment I will go back to 25H2 because I see no point in moving away from Windows 10 to a dual boot Linux/Windows environment if I don't try to keep the whole environment up to date.