For me, the issue disappeared after I restarted Visual Studio as an Administrator
Visual Studio Community 2022 17.11.5