Fixing Systemd-Boot with Archlinux After Windows Anniversary Update on a Dual-Boot EFI Setup

Fixing Windows' mess, again.
Fixing Systemd-Boot with Archlinux After Windows Anniversary Update on a Dual-Boot EFI Setup

So, as expected, windows updates like breaking things.

This time, however, things were a little trickier than usual to fix. I was present with an error screen claiming that the root partition had the wrong file system(?).

It turned out that windows created a new partition, actually changing my linux root partition from sda7 to sda8, which made Systemd attempt to boot from my data partition, which happens to be an ntfs system.

I tried a few times to just change the root partition at /etc/fstab to sda8 followed by reinstalling the kernel to force the mkinitcpio. But that didn't fix it.

It so happens that the partition is mounted by systemd prior to boot, and upon inspecting /boot/loader/entries/arch.conf I could find the culprit:

 options root=/dev/sda7 rootfstype=ext4 add_efi_memmap pcie_port_pm=off

Changing it to:

options root=/dev/sda8 rootfstype=ext4 add_efi_memmap pcie_port_pm=off

Fixed my problem, and everything is working again.