This is a brand new Win 2k19 install on Azure, with same issue being experienced on Win 2k22 server in Azure. An on-prem Win2k16 server running the print management role does not experience this issue with any of the same drivers mentioned below (and has been running for several years).