this post was submitted on 22 Apr 2025
492 points (93.8% liked)
Technology
69211 readers
3746 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Can't say I would recommend dual booting both OSes off the same drive. Windows causes too many problems. Put Windows on an entirely separate drive instead and boot to it by changing the boot device in the BIOS.
Why not put it in VM?
The only thing I'd suggest if you do that is to have at least 32 GB of RAM, because I was in a situations where running few Electron apps, and Win11 VM caused RAM to fill up. But if you're not running Electron apps you should be fine with 16 GB.
And if you're planning to play games, you could use GPU passthrough for near-native performance, but from what I've heard it's a bit hard to set up.
Oh, I do both. My whole point was to avoid partitioning one physical disk to install both OSes on.
My current setup:
-Windows 11 installed on one NVMe. This is only for playing games that absolutely won't work any other way.
-Pop OS on another NVMe. This is my main OS.
-Windows 11 VM in VirtualBox for work stuff and normal applications (Adobe...)
Proc is a Ryzen 5 9600x. Machine currently has 64gb DDR5 RAM at 5200mhz.
I run a dual boot system with no issues at all. Just need a second drive for Linux and let GRUB chain load the Windows disk.
That's effectively the same as what I described, is it not? The only difference is you're using GRUB to choose what to boot into. It's still a two disk setup with Windows separate from the Linux disk.
When's the last time you tried? I had a hell of a time dual booting in ~2016, but as of the last five years or so I've set up half a dozen dual boots without issue, and Windows (LTSC) hasn't messed up any of the partitions.