Getting "Something Went wrong" error when installing Visual studion 2022 community

Sachwet 1 Reputation point
2026-06-30T09:19:10.7366667+00:00

I am encountering a persistent generic error "Sorry, something went wrong" immediately upon opening the Visual Studio Installer interface while trying to install Visual Studio 2022 Community on my Windows machine.

I have already extensively tried the standard troubleshooting methods, but the issue persists. Here is a log of everything I have checked and executed so far:

Basic Steps: Ran the installer bootstrapper (vs_community.exe) as an Administrator.

Installer Cleans: Used InstallCleanup.exe. Manually cleared and deleted the C:\Program Files (x86)\Microsoft Visual Studio\Installer and %localappdata%\Microsoft\VisualStudio\Packages directories.

System File Checks:

Ran sfc /scannow which successfully detected and repaired corrupted system files.

  Ran `DISM /Online /Cleanup-Image /RestoreHealth` but the online repair failed completely with __Error: 0x800f0915__ (The repair content could not be found).
  
  __Configuration Reset:__ Inspected the `.NET Framework` configuration directory and swapped out a potentially corrupted `machine.config` file with a fresh template from `machine.config.default`.

Despite the system repairs and folder clears, the installer app throws the exact same error screen and won't advance to the workload configuration panel. I prefer not to download bulky, external ISO images if a simpler native environment fix is available.

Could anyone point out what might be blocking the bootstrapper or how to circumvent this specific error based on the failing DISM component store? Thank you!

Developer technologies | Visual Studio | Setup
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lizzy Dinh (WICLOUD CORPORATION) 620 Reputation points Microsoft External Staff Moderator
    2026-06-30T09:58:23.4466667+00:00

    Hi @Sachwet ,

    Thank you for taking the time to share your concerns and provide detailed information about the issue.

    To help you continue narrowing down the cause, I would like to suggest a few additional troubleshooting steps:

    1. Temporarily disable your antivirus or firewall software during the installation process, as security applications can sometimes interfere with installation components.
    2. Repair the .NET Framework using Microsoft's .NET Framework Repair Tool. You could try to replaced the machine.config file first, however there may still be underlying .NET Framework issues that need to be addressed.
    3. Since Visual Studio has already been completely uninstalled, please also consider removing the Visual Studio Installer, downloading the latest version here, and then performing a fresh installation.

    I hope these suggestions help resolve the issue and get you back up and running. If the problem continues or if you have any questions about the steps above, please don't hesitate to reply. I'll be happy to continue assisting you.

    Additionally, if you found my support helpful, I would greatly appreciate your feedback by following this guidance.

    Thank you for your cooperation, and I wish you a wonderful day!

    Was this answer helpful?

    1 person found this answer helpful.
  2. saleha mubeen 0 Reputation points
    2026-06-30T12:19:01.0866667+00:00

    It sounds like you've already covered most of the common troubleshooting steps. Since the error appears immediately when the Visual Studio Installer opens, it may point to a corrupted installer cache, a network/security policy issue, or a problem with the installer service itself rather than Visual Studio.

    A few additional things I'd check are:

    Download the latest vs_community.exe directly from Microsoft's website to rule out a corrupted bootstrapper.

    Temporarily disable antivirus or endpoint security software and try launching the installer again.

    Check the installer logs in %TEMP% and %ProgramData%\Microsoft\VisualStudio\Packages for any specific error codes.

    Verify that the Microsoft Visual Studio Installer service isn't being blocked by firewall or proxy settings.

    If possible, test the installer under a new Windows user profile to rule out profile-specific corruption.

    If you can share the dd_setup*.log or vslogs.zip files, the specific error code in those logs will usually identify the root cause much more quickly.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.