I'm looking at moving from Windows to Linux and decided to try Zorin OS. Windows 10 is install on one SSD and I did install Zorin OS Pro 18 on a second SSD. Safe Boot is off in Bios and it seems I do not have the option to turn off either MSI Fast Boot or Fast boot. At the start of the install of Zorin, Windows was not picked up as a installed OS. I checked on Safe Boot once again and it was off and I continued to install even though Windows wasn't detected. Install when well and I updated things that needed to be updated based on the update screen after logging into Zorin. I also ensured Grub was updated but still no Windows as a boot option. Even though Bios sees the Windows SSD listed upon entering the boot menu options with F11, only Zorin was listed as a boot device. So, no option to boot Windows. I removed the SSD with Zorin on it and now Windows isn't even a boot option any longer even thought the drive is listed as a drive in Bios. I can see that all the folders and files are still on the Windows SSD. So, it doesn't look like anything was messed with during Zorin install. Suggestions would be great. Thanks
I will start by trying to help you get back to booting Windows. Then we (as a community) can help you with Zorin.
Can you boot into Windows by manually selecting it via F11 (was F11 your BIOS boot option key?) Wouldn't it be lovely if the industry got together and said "let's all use the same key".
And did you turn safe boot back on?
Windows requires safe boot, so unless you modified Windows to not (like using Rufus) it will demand it.
The other thing I've heard is that Windows itself has fast boot in the power/performance settings (iirc "choose what happens with the power button", in advanced). If that is using "fast boot" then Windows doesn't properly shut down. It goes into some kind of hybrid hibernate state. In such cases Linux can't see the bootloader and Grub doesn't update.
Lastly, if I were you, I would use this as an opportunity to "upgrade" (
) to Win11. 10 is unsupported and is a security risk. If you do, use Rufus to create the installer which removes the need for safe boot.
This can be done in-place (upgrade) or as a fresh install. I can find videos for you if you're interested, there's a couple of really good and easy to follow ones somewhere in my watch history.
Hi and welcome 
Also, is Legacy/CSM (MBR) enabled in your BIOS settings?
It sounds like Windows is on MBR boot, Zorin OS is installed as EFI boot.
Here's what I found and not sure how it occured but have fixed the issue. The Windows 10 SSD did not have a EFI bootloader on it at all. So, no boot. I'm assuming it was using the 1TB drive (previous Win11) I have as a bootloader to lunch Win 10. However, after installing Zorin on the 1TB SSD, the Windows bootloader was erased. I did a clean install of WIn 10 (2TB SSD) and clean install of Zorin (1TB SSD). Windows 10 was picked up during Zorin install. So, all worked out. Why, Windows 10? I was one of the many effected by the Microsoft **** storm back in Jan and could never get back into Windows 11. Win 10 is covered until Oct 2026, which gives me time to take Zorin and probably Mint for a test drive and fix any hiccups for the final move. Done with Windows but my work is in Windows for right now.
Issue now: System only boots into Windows. I don't receive a Dual-boot option, which my understanding is a known issue with dual-booting Windows/ Linux. What is the fix? I assume a WIndows issue. Thanks
Did you try @Aravisian suggestion about a legacy/UEFI mismatch? If that isn't the problem, are both your bootloaders in the same partition, even though you have everything else on separate SSDs? They should be. If not, and assuming no mismatch, you might be able to use OSProber in terminal (there are threads about this if you search the forum). Are you completely powering off before trying to get a dual boot grub menu, or is windows doing a fast boot "hibernation" instead? BTW for me windows works just fine with safeboot disabled.
Yes, your assumption is on target. The EFI is programmed to Only See Windows OS as Trusted.
You can try these steps here:
These are the steps you are most concerned with:
- At the BIOS/UEFI settings screen, navigate to the “Boot” tab using the ← → keys.
- Make sure that the “Secure Boot” option is enabled. If it’s disabled, scroll down to it using the ↑ ↓ keys and press Enter to set it.
- Navigate to the “Security” tab.
- Use the ↑ ↓ keys to highlight the “Select a UEFI file as trusted for executing” option and press Enter.
I'm not using legacy. Windows is GPT and both are on EFI boot and both bootloaders are on separate drives. Disk0 is Windows and Disk1 is Zorin.
Let's cover the boot location. As stated they are on separate drives but.... Unless this is something I don't know about dual booting Widnows with Linux, I went into my boot screens with F11. Windows and Zorin are listed but they both show the same drive even though in previous image their bootloaders are separate.
Secure Boot is on but for me it's located in the security tab. Had it off during Zoring install as it was suggested but turned it on after install. As for the ability to select a Trusted UEFI file, I do not have that option anywhere in my BIOS. The Zoring drive also doesn't show up in my boot option in Bios. That's probably because it's pointing to the Windows drive based on above image. So, can't reorder boot drives as there is only one.
As stated, I can F11 into boot menu to go into Zorin. It is an option. Not an ideal option especially when I drop Windows. Not sure what the fix is maybe outside fresh installs of both after wiping all volumes and maybe installing Zoring first and see how that goes.
Try moving Zorin up above Windows.
Here is my advice.
Linux boot loader should be installed on Disk 0 same partition where Windows is already installed. there is no need to select operating system boot from BIOS every time. I had similar issue and only way to change boot order is to edit LINUX Boot loader setings and run comand to generate new Bootloader @GRUP binary. happy to help via whatsapp video call.
After Linux instalation and linux Boot please install old school program called Midnight Commander
sudo apt install mc
next run command
sudo mc
go to /etc/default and find file "grub" hit F3 to view file, do not edit just yet.
find line: GRUB_DEFEULT=0
hit F10 quit
open file for edition hitting F4, you might be asked which editor you prefer as default choose "MC" option 2 I think
using arrows go to the line and change GRUB_DEFEULT=0 to 2 hit F2 to save
hit F10 to exit editor
ten run command: sudo update-grub
if all OK restart laptop, the default system should be Windows
The boot locations was decided by the install but if you go by the second image where I when into the Boot menu with F11, it looks like Zorin is defaulting to the EFI of the Windows drive. However, i did make the change in the Grub file, which you stated should default to Windows but it's already defaulting to Windows as the primary and only boot without interfering with F11. No F11, straight to Windows, with F11 get 2 options to boot from.
Here is my advice:
Fix Zorin install dualboot on 2 different drives. I installed it 3 times and still cant get the bootmenu. You need to be an Expert to get it working properly. Did all the buis and start things mentioned above and more.
Installed Linux Mint with dualboot win11 and no problem at all!
Figured it out. Needed to run Probe.
Zorin should fix this in the installation menu. Zorin says its the most user friendly and windows minded Linux version. Well, a lot of people do a dual boot to test things out for a few weeks. The single drive install works perfectly but this dual drive install is broken and can only be fixed if you are smart enough and have plenty of time to figure it out.
I almost gave up and I think a lot of people actually do give up and wont come back.
Just my thoughts on it.
I marked your post as solution.
Sorry, I did not notice this thread until now - when you posted something that causes a facepalm.
Needing to Probe: You did not used to need to. Now, however, os-prober is disabled by default.
It should be enabled.
The reason why it is disabled by default is not particularly valid or true - it falls back on the excuse of "for security" but is far-fetched.
The actual reason it is disabled by default is due to one the developers for GRUB who wrote a replacement for GRUB actively sabotaging GRUB in order to force acceptance of its replacement.
@kiordthedreamer isn't the OP of the thread.
O_o
Unmarked...