Question: I found a bug in the latest version of VS Community (16.7.0) which is preventing my solution from building, so I need to roll back to 16.6.5. However the only [download link](https://learn.microsoft.com/en-us/visualstudio/releases/2019/history#installing-an-earlier-release) I can find has downloads for only Enterprise and Professional, not Community. How do I downgrade my installation of VS Community? It's completely unusable for me now because one of my solutions is failing to build even though there are no compile errors.

Answer: 
Here is the official source for all previous versions of all 3 product lines: <https://learn.microsoft.com/en-us/visualstudio/releases/2019/history#release-dates-and-build-numbers>
I had a similar challenge, where I needed an older minor version(16.5) of VS 2019 with Xamarin together with the latest and updated C++ features of 16.10 [side-by-side](https://learn.microsoft.com/en-us/visualstudio/install/install-visual-studio-versions-side-by-side?view=vs-2019#install-minor-visual-studio-versions-side-by-side), both Community.

What worked for me was:

1. On another machine without any VS 2019 versions installed, [download the vs\_Professional.exe bootstrap file for the minor version you want](https://learn.microsoft.com/en-us/visualstudio/releases/2019/history#release-dates-and-build-numbers) and install in a custom folder name(e.g. 2019\_16.5) the Community flavor by cancelling the workload selection, like [@Alejandro describes in his answer here](https://stackoverflow.com/a/64491972/12802435).
2. Copy the whole VS installation folder to the developer computer where you already have Visual Studio 2019 installed.
3. Copy the corresponding folder inside *[%USERPROFILE%\AppData\Local\Microsoft\VisualStudio\Packages\\_Instances\](https://developercommunity.visualstudio.com/t/visual-studio-installer-cant-find-existing-install/784940#T-N786634)* to the same place on the developer computer.
4. On the developer computer, run the Visual Studio Installer. The new minor version should appear in the list. Choose *Repair*.
5. Modify and add the workloads and components you need for this installation.

I am not sure if step 2 is required or whether this just worked by chance for me and maybe can not be reproduced, but it might be worth a try.

[Screenshot of my VS Installer](https://i.stack.imgur.com/oMO7d.png)