Thanks again for the report! It appears that this issue is caused by an older version of Visual Studio (17.0), where certain internal interfaces are not yet available.
We recommend updating Visual Studio to the latest version if possible — newer versions include important fixes and improvements that can help avoid issues like this.
Please let me know if the update helped.
Thanks!