This is due to a VS 2019 issue - there is a workaround for it previously here:
(it helps to search the forum )