this post was submitted on 05 Feb 2024
820 points (97.0% liked)

linuxmemes

19733 readers
2409 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] agent_flounder@lemmy.world 24 points 5 months ago (1 children)

If I were you I would install Mint on a second drive.

Pretty sure your issues aren't with Mint they're with the virtualization platform.

You can get a cheap $40 SSD and install the OS on that.

Be sure to unplug the windows drive before installing Mint to the other drive. Then plug the Win drive back in. Now you can use the bios boot menu to boot into either.

[–] Vlyn@lemmy.zip 7 points 5 months ago (2 children)

Be sure to unplug the windows drive before installing Mint to the other drive.

Why would you do that? Totally unnecessary. When Windows is already installed any Linux installation respects it without issues. The problem is the other way around, if you install Linux first and then install Windows afterwards on a second partition/drive it nukes your Linux bootloader.

Especially in times of M.2 drives (which are often behind the GPU) you only annoy people by telling them to unplug their Windows drive first. And they might want to use a second partition on that drive if it's bigger.

[–] histic@lemmy.dbzer0.com 5 points 5 months ago (1 children)

always unplug the windows drive I've fucked my windows bootloader so many times because if your windows drive shows up in drive order before your Linux drive it'll fuck with it

[–] just_the_ticket@sh.itjust.works -4 points 5 months ago

All I can read is "I don't know how to install linux"

[–] agent_flounder@lemmy.world 3 points 5 months ago

I would do that because the last time I tried installing a new distro it fucked my windows bootloader. So your statement isn't universally true, sorry to say. I have only had this issue once on one distro. I have not spent the time digging into the underlying cause yet. It may well be distro related. I figured I would save a noob a potential gotcha, however.