Windows 10: Will there be fix to Visual Studio Community 2019 and Visual Studio Tools 2017?

This has been going on since the 16.4.3 release for Visual Studio Community 2019 update. After the second update since the error, 16.4.4, I switched to Enterprise.

I scrolled through several forums in a relationship base search but no success in finding a solution.



This is the issue set given for Studio Build Tools 2017, similar to Studio Community. At the first glance aside from recommended reset options, I attempted to browse Windows Catalog for file updates that matched. I ended up compiling most of the security packages that did not show up in extended optional updates.

Microsoft does not have a direct path to file sourcing new file sets through visual studio. There does seem to be an option of rummaging through packages; deleting error files; replace with source files- managed precautions before taking this route as in that most of the tools workobject icon changed for some tools; extensions fail to update. Final inspection of the programs does not allow for removal of them by Visual Studio InstallerMay contain certificates and object determinations.

The primary question is, were Tools 2017 and Community 2019 set to a final update by 2020 with Windows 7? If not, has anyone else experienced a similar issue? When issue noticed, was there a solution path that worked without destroying the integrity of the previous version that is in part successful at being a base build? To correlate this subject, pyramids changed angle, not material, required assurance and specifications went up thus the decommissioning of older structures though not to the extent to remove said buildings.

:)

 

Visual Studio Roadmap Updates and Visual Studio 2019 Information

Source: Visual Studio Roadmap Updates and Visual Studio 2019 Information | The Visual Studio Blog

 

Visual Studio Roadmap Updates and Visual Studio 2019 Information

Source: Visual Studio Roadmap Updates and Visual Studio 2019 Information | The Visual Studio Blog

 

Visual Studio (.NET Framework)

Do you still have the Visual Studio Installer or Visual Studio Manager still installed?

If you have it still installed and it opens up correctly, you could try removing all additional packages that are installed, and try reinstalling them again. It could have been a corruption issue relating to package extensions that you may have installed
into Visual Studio 2017 Community Edition. If that does not work, go to apps in settings, and select Visual Studio 2017 Community Edition and select repair. If that does not work, you could try going to TechNet, and asking there for help. It could be a
bug with the current version of the .NET Framework 48 or with the recent version of Visual Studio 2017 Community Edition.

If you can not find Visual Studio Installer or Visual Studio Manager, unfortunately in this situation the only thing I can think of is if you still have the installation file that you downloaded from the Visual Studio website. If you can't find that, then
I suggest that you download Visual Studio 2019 Community Edition, since the 2017 Community edition is not given for free anymore unless you have some sort of subscription. However, I suggest that you still check with TechNet before taking this step.