Alright so I tried your solution, and it had a very interesting effect…

Now both boot partitions boot straight to Windows. Entirely skipping systemd-boot and Arch.

On the plus side it does mean that just copying Windows’s bootloader files to Arch’s bootloader partition will boot Windows no problem.

On the downside, my issue remains the same, I can’t get dual boot to work.

Both Windows and Linux (as well as their boot partitions) are on the same drive. I’ve never had problems with my PC automatically recognizing the Linux boot partitions and adding it to the boot list until this PC.

Edit: didn’t work, check new response.

So potentially that solution could work on the same drive with two separate boot partitions like I did earlier then?

Bit of a hacky way to go about it, but if it works it works.

And I guess that would potentially prevent the issue where a Windows update breaks the Linux bootloader from happening as well. Not that this has ever happened to me, but it’s an issue I’ve seen people talk about for years.

I’ll wait a bit longer to see if anyone has any suggestions/fix as to why slapping GRUB/systemd-boot in the same partition as Windows’ bootloader doesn’t seem to work, and if not or if it doesn’t work I’ll go with that.

Thank you!

Our Lord Gaben is a Benevolent God.