Nice catch.
Reproduced here : i440fx doesn't boot with ISO Windows 10 build 1904x.6456 (the EoL build)
on a PVE 8.4.16 EPYC 2th Gen host and a PVE 9.1 i5 6th Gen host , vCPU type isn't relevant.
EDIT : Only reproduced with the updated iso , with the ISO Windows 10 RTM 20H1 build 19041 boot is OK...
if device is not mounted, backups are written to / filesystem.
umount and delete backups if they exist in the mount point.
use chattr +i /mnt/.../proxback to prevent its usage when mount is missing.
Proxmox VE, with its default vmbr0 Linux bridge, acts like a hardware switch, it does not manage guests network configuration.
But you can block ipv6 with PVE Firewall. Enable it in each guest and each guests nic.
Then set NDP to "No" in each guest.
if PVE firewall ON , try
https://forum.proxmox.com/threads/turning-on-firewall-with-accept-policies-everywhere-makes-hosts-unreachable.182123/post-846186
because compression is not reproductible.
rsync can't be efficient with compressed stream as data is mixed.
hook script at stop is the solution for your use case.
Once you have tried PBS, you will keep it.
Here PBS alongside PVE.
PBS datastore/disk is the real backup data to take care of.
PBS...
it's same as baremetal,
it's not a really Proxmox side.
You will find tutos online.
System disk need conversion to gpt, then make EFI boot partition to create EFI boot files.
BTW, Legacy Boot / SeaBIOS is not Secure Boot capable, and have not certificates.