Microsoft is moving forward with its plans to turn Windows 11 into a full-fledged “AI” operating system amidst Copilot backlash. The first big move in that direction is an experimental feature called “Agent Workspace,” which gives AI agents access to the most-used folders in your directory, such as Desktop, Music, Pictures, and Videos. It will […]
I had this happen before but not in recent times. Not sure if others have experienced the same.
For a while I had my bootloader on a single drive but I now have my Linux bootloader on /dev/sda and my windows on /dev/sdb and toggle it in the bios when I need to use Windows. I haven’t had Windows overwrite anything in a long time. Could be a coincidence though.
It’s mostly an issue when you have them sharing boot drives via partitions. If you keep them isolated to their own separate drives, Windows doesn’t tend to muck with things. It’s because Windows is bad about killing bootloaders, and automatically setting itself as the default in the boot order. So if you have it sharing a drive, it’ll nuke your boot. But if you don’t have them sharing a drive, and boot via a loader on the Linux drive, there is no boot loader on the Windows drive to nuke.
I’ve read that dual booting Windows and Linux can have temperamental quirks and I’ve had my share of them.
Now, if I’m doing that, Windows fs gets isolated and I refuse to even connect it to the internet. But, outside of a legacy automotive shop program meant for XP, I’ve not needed Windows for a couple years.