You only need one EFI partition on your machine. Why would you want a second one?

True, but my thought was that if there is every a Windows 10 update that rewrites the EFI partition it won't take down grub with it if they are separate. But I understand your assessment that there really isn't much need for more than one.

If you want an opinion on that, Windows10 has never messed up my grub boot-loader (ESP). Chances are that only by doing big updates, those called "feature updates", mess up the block devices order thus making block devices declared at /etc/fstab wrong. That can be avoided by using UUID instead of block devices /dev/sdxX.

The solution to that is not to run Windows natively. Run it in a VM.

1 members found this post helpful.

Yeah I have never had it happen to me. Even if it did I would just use live-slack or a USB slack installer and rescue the system that way. This whole thing just seemed like a good idea, but in practice is kind of not necessary. But at least it gave me something to tinker with today lol.

lol. I say its ok to run Windows for games and a few other programs that make life a little easier than doing it in Linux... just don't pay full price for it .

Actually, I have to use Windows for work. This is due to some industry-specific software which is only available for Windows.

But I don't dual boot... I run Windows in a Virtual Machine (with a retail license which I bought directly from Microsoft). It runs perfectly. I've not had any issues in the >5 years I've been operating this way.

As for gaming, all of that is done under Linux.

How much resources do you give that Windows 10 virtual machine. I have a four core host with 8GB of memory, I give my Windows 10 3072 MB and 2 cores. Kind of sluggish but livable. I can probably get away with give it 4096 MB and 3 cores, since when I have that machine running that all I use.

Same here.

In an EFI partition of course, the windows and Slackware (or other Linux) EFI files are in separate directories so windows updates won't affect the Linux EFI. What some windows updates will do (experienced this myself more than once) is turn on Secure Boot and hibernation. Since some people access windows partitions from their Linux, that will no longer be available until hibernation is again turned off and Slackware needs Secure Boot off to boot EFI. I've also read posts in differnt forums where windows changed the boot priority to set itself first though I've never experienced that.

I don't think there are enough users who want/need this to warrant making the change in the installer. I don't really do much multibooting any more but I'm not aware of any Linux installer which does this. Changing the boot/esp flags or copying the Slackware directory to the 2nd EFI partition seem like the simplest solutions.

My host machine is an i7 with 32GB. The Windows VM gets 8GB, 4vCPUs and an 80GB dynamic disk. Networking is in bridge mode, so the VM gets its own IP address from the router.

Thanks. I do the same with networking. Guess I should start saving up for a more better computer. LOL

Just get some more RAM...

Last I checked, prices were ridiculously low!

Last I checked my box won't take more ram.