How to Install Visual Studio Community 2017 and Fix the Startup Error

Ah Yes. Visual Studio 2017. What a good memory. That was a good year before COVID-19 happened.

I still install it sometimes, especially when dealing with older projects that don’t behave nicely in newer Visual Studio versions. Legacy apps are real, and sometimes the safest move is just using the original toolchain.

Here’s how I install Visual Studio 2017 Community Edition plus how I fix that annoying System.InvalidOperationException startup error that sometimes appears right after installation.

Not in the mood for reading? Watch the video instead.

Step 1: Download Visual Studio 2017 Installer

I’ve prepared the official download links for the genuine Visual Studio 2019 installers below. You can, of course, visit the official Visual Studio website, but that usually requires signing in and navigating through several pages to find the correct download.

You can use the Community edition without an active paid subscription, as long as your usage complies with Microsoft’s license terms.

Edition	Installer
Visual Studio 2017 Community	⬇️ vs_Community.exe
Visual Studio 2017 Professional	⬇️ vs_Professional.exe
Visual Studio 2017 Enterprise	⬇️ vs_Enterprise.exe

Step 2: Run the Installer

• Click Continue
• Let it prepare the setup

Then you’ll be asked to select workloads.

For me, I usually select:

• .NET Desktop Development
• ASP.NET and web development

These two cover most of my classic .NET Framework use cases. You can of course select other workloads.

Click Install, and now we wait. This part can take a while depending on your internet speed and machine specs.

Step 3: Launch Visual Studio 2017

Once installation is complete:

• Click Launch

Now here’s where things can get interesting.

If You See: “Could Not Start Visual Studio”

Sometimes after clicking launch, you’ll get an error like:

“Could not start Visual Studio due to an error.”

The first time this happened to me, I thought the installation was corrupted.

Turns out, in many cases, the problem is related to Node.js and the NODE_OPTIONS environment variable.

If you have NodeJS installed (which most developers do), this can interfere with Visual Studio 2017 installation.

Here’s how to fix it.

Temporary Fix: Rename NODE_OPTIONS

1. Open Start Menu

2. Type: Environment Variables

3. Click Edit the system environment variables

4. Click Environment Variables

5. Under System Variables, find NODE_OPTIONS

6. Click Edit

7. Rename it temporarily For example:

   NODE_OPTIONS_

   (Just add an underscore at the end.)

8. Click OK

9. Click OK again

Now try launching Visual Studio 2017 again.

It should open without issues.

Important: Restore NODE_OPTIONS After Launch

Once Visual Studio successfully launches:

1. Go back to Environment Variables

2. Edit the renamed variable

3. Remove the last underscore from NODE_OPTIONS_ so it’ll becomes:

   NODE_OPTIONS

4. Click OK

5. Click OK again

Now close and reopen Visual Studio 2017 to confirm everything works properly. It should start normally this time.

Video

Final Thoughts

Visual Studio 2017 might be old, but it’s still perfectly usable—especially for maintaining legacy applications.

If you run into the startup error, don’t panic. In many cases, it’s just the NODE_OPTIONS environment variable conflicting with it. A quick rename and restore usually solves the issue.

That’s it. Now you’re ready to build your apps like it’s 2017 again 😄

As usual, if you have any questions or a better method, leave a comment below. Thanks for reading, and see you next time 👋