F5F Stay Refreshed Software Operating Systems about dual booting safely

about dual booting safely

about dual booting safely

B
brainothon
Member
187
03-05-2024, 11:43 AM
#1
I've been experimenting with Manjaro and Garuda inside VM for several weeks now. I'm considering a full commit. For work and gaming, I still need Adobe and use anti-cheat tools, so I'm keeping Windows. I've heard on the forum that running Windows alongside another OS in dual boot can be risky—random updates might mess with the other system. So if I turn off automatic updates completely, is it safe to run Garuda as a second OS? If so, how can I protect Garuda during manual updates? Cheers.
B
brainothon
03-05-2024, 11:43 AM #1

I've been experimenting with Manjaro and Garuda inside VM for several weeks now. I'm considering a full commit. For work and gaming, I still need Adobe and use anti-cheat tools, so I'm keeping Windows. I've heard on the forum that running Windows alongside another OS in dual boot can be risky—random updates might mess with the other system. So if I turn off automatic updates completely, is it safe to run Garuda as a second OS? If so, how can I protect Garuda during manual updates? Cheers.

E
EinarIgor1337
Member
106
03-05-2024, 07:14 PM
#2
This scenario seems unlikely, but if both drives are on the same partition and the MBR remains intact, the Linux bootloader might be affected. A simple solution is to wipe it. For added security, move Windows to a different drive before proceeding and choose your boot option in the BIOS.
E
EinarIgor1337
03-05-2024, 07:14 PM #2

This scenario seems unlikely, but if both drives are on the same partition and the MBR remains intact, the Linux bootloader might be affected. A simple solution is to wipe it. For added security, move Windows to a different drive before proceeding and choose your boot option in the BIOS.

R
ReD_T1000
Member
168
03-05-2024, 07:26 PM
#3
To prevent corruption, simply install the systems on distinct physical drives.
R
ReD_T1000
03-05-2024, 07:26 PM #3

To prevent corruption, simply install the systems on distinct physical drives.

M
MTkvc
Junior Member
14
03-13-2024, 07:20 PM
#4
Possible issues may include a minor corruption of boot configurations (bootmgr.efi might be altering settings unexpectedly—this hasn't happened to me). Generally, it's just an annoyance, and using a different drive won't likely resolve the problem if it doesn't occur.
M
MTkvc
03-13-2024, 07:20 PM #4

Possible issues may include a minor corruption of boot configurations (bootmgr.efi might be altering settings unexpectedly—this hasn't happened to me). Generally, it's just an annoyance, and using a different drive won't likely resolve the problem if it doesn't occur.

S
samaclause
Member
142
03-13-2024, 07:44 PM
#5
Issues arise when Windows overwrites the boot partition during dual booting on one drive. Correcting this is possible but often troublesome. The problem disappears when using distinct drives, as each system operates independently without sharing a boot partition.
S
samaclause
03-13-2024, 07:44 PM #5

Issues arise when Windows overwrites the boot partition during dual booting on one drive. Correcting this is possible but often troublesome. The problem disappears when using distinct drives, as each system operates independently without sharing a boot partition.

J
jdclay
Member
154
03-14-2024, 02:51 AM
#6
It won't damage the operating system but will disrupt the boot loader. That issue can usually be resolved by a straightforward chroot operation.
J
jdclay
03-14-2024, 02:51 AM #6

It won't damage the operating system but will disrupt the boot loader. That issue can usually be resolved by a straightforward chroot operation.

C
CanadianOutlaw
Junior Member
7
03-14-2024, 06:42 AM
#7
Refers to the initial part of a computer's storage where the operating system is loaded.
C
CanadianOutlaw
03-14-2024, 06:42 AM #7

Refers to the initial part of a computer's storage where the operating system is loaded.

M
MasterHD7
Senior Member
340
03-14-2024, 03:15 PM
#8
Only if you arrive ten years behind... UEFI relies on a boot partition.
M
MasterHD7
03-14-2024, 03:15 PM #8

Only if you arrive ten years behind... UEFI relies on a boot partition.

X
xLikax
Member
173
03-14-2024, 03:36 PM
#9
I do not.
X
xLikax
03-14-2024, 03:36 PM #9

I do not.

C
CloseToToast
Member
125
03-16-2024, 01:13 PM
#10
Windows could make other operating systems unstartable, though it's improbable to erase their data. An update might bring some hassle, forcing you to repair it so your other OS can boot again, but serious data loss is unlikely. If Garuda runs on a distinct hard drive, disconnect it before updating Windows. Otherwise, if you're comfortable with Arch-based systems, you can perform a standard Arch installation inside a virtual machine. The same tools used for Arch installation—mounting the system, entering chroot, and installing the bootloader—apply to Arch distributions too. After completing one repair, you can switch back to Garuda and handle EFI or MBR issues confidently without a full reinstall. If this seems overwhelming, using a separate physical drive is perfectly fine.
C
CloseToToast
03-16-2024, 01:13 PM #10

Windows could make other operating systems unstartable, though it's improbable to erase their data. An update might bring some hassle, forcing you to repair it so your other OS can boot again, but serious data loss is unlikely. If Garuda runs on a distinct hard drive, disconnect it before updating Windows. Otherwise, if you're comfortable with Arch-based systems, you can perform a standard Arch installation inside a virtual machine. The same tools used for Arch installation—mounting the system, entering chroot, and installing the bootloader—apply to Arch distributions too. After completing one repair, you can switch back to Garuda and handle EFI or MBR issues confidently without a full reinstall. If this seems overwhelming, using a separate physical drive is perfectly fine.