@Athena I Paid of ACC Pro, yet the screen for purchase keeps popping up and won't let me proceed

Hello @gjsmitty,

I'm sorry to hear that you're experiencing issues with accessing ARC Pro features after your purchase. Here's what you can do to resolve the issue:

1. Ensure that you are logged into the correct Synthiam account that you used to purchase ARC Pro. Sometimes, being logged into a different account can cause this issue.

2. Restart ARC to ensure that it has a chance to update your account status properly.

3. Check your internet connection to make sure that ARC can communicate with the Synthiam servers to verify your Pro status.

4. Clear the cache of ARC. Sometimes, the cache might hold onto old data, and clearing it can help refresh your account status.

If you've tried these steps and the issue persists, you may want to refer to the support section for additional troubleshooting steps or to reach out for further assistance. You can find the support section here: https://synthiam.com/Support

Remember, you should be using the same Synthiam account with which you purchased ARC Pro, and ensure that your subscription is active. If there's a discrepancy, it might prevent you from accessing the Pro features.

Hi there - I'm sorry to hear you're experiencing issues. Can you explain what screen you are referring to so I can help?

I can see by your account that you have successfully purchased a Pro subscription, and confirmation emails have been sent to your email address. You also have the Pro icon beside your name here on the forum.

1. All you need to do now is download and install ARC Pro
2. When prompted to sign in with ARC Pro, use the email and password for the account that you're using

Happy building!

Thank You. I realized that I had installed the free trial version, after installing the PRO version the issue was resolved Now, ARC Pro is not seeing Visual Studio that is installed and ACR PRO is saying it is not. Is there a plug in that needs to be installed?

I’ve heard of that happening before and I’m not certain what caused it because we can’t reproduce it.

I wonder if it’s how it’s installed. Did you install visual studio from the Microsoft store? Or did you download it from an exe installer?

maybe we can use this opportunity to explore why it happened. The one and only other time we’ve heard about it - the person got it to work but didn’t share what the solution was.

also, is it visual studio community that you installed? (Not visual studio code)

I am looking into this further since the issue was raised. First, this has only happened once in the past, and we don't know how the person resolved it. But let's take this opportunity to figure out what could have triggered it. Please answer these questions to help us help you...

1. This requires Visual Studio, not Visual Studio code. Microsoft made things a bit confusing by naming multiple applications that were entirely different. Did you install Visual Studio? Most likely, I suspect you would have installed Visual Studio Community 2019, as suggested in the tutorial.

2) The Create robot skill checks for Visual Studio by looking for a specific file. The file is C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe. Can you check if you have that file, and if not, which folders are missing from the path on your machine?

Let me know when you can answer those two questions, and we can go from there. Thanks!

Here's some additional information. Microsoft designs the vswhere.exe to help programs identify Visual Studio installation locations. It is documented here on their GitHub page: https://github.com/microsoft/vswhere

Quote:

Over the years Visual Studio could be discovered using registry keys, but with recent changes to the deployment and extensibility models a new method is needed to discover possibly more than one installed instance. These changes facilitate a smaller, faster default install complimented by on-demand install of other workloads and components.

vswhere is designed to be a redistributable, single-file executable that can be used in build or deployment scripts to find where Visual Studio - or other products in the Visual Studio family - is located. For example, if you know the relative path to MSBuild, you can find the root of the Visual Studio install and combine the paths to find what you need.

You can emit different formats for information based on what your scripts can consume, including plain text, JSON, and XML. Pull requests may be accepted for other common formats as well.

vswhere is included with the installer as of Visual Studio 2017 version 15.2 and later, and can be found at the following location: %ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe. The binary may be executed from that location as needed, installed using popular package managers including WinGet, or the latest version may be downloaded from the releases page.