In case anyone else had this issue, it was resolved by rebuilding after downgrading VS2019 to 16.2 (issue occurs on 16.3)....