卸载Visual Studio 2022 Community Preview后，Visual Studio 2022 Community无法启动

Hey there, let’s work through this frustrating VS launch problem together— I’ve dealt with similar assembly binding conflicts before, so here are some targeted fixes you might not have tested yet:

1. Wipe out leftover preview components and run a full repair #

Uninstalling the preview version sometimes leaves behind rogue components that mess with the正式版’s DLL references. Try this:

• Open the Visual Studio Installer, select your VS 2022 Community instance, click Modify.
• Go to the Individual components tab and double-check no preview-related tools (like preview SDKs or toolchains) are checked. Uncheck any if you find them.
• Go back to the Summary tab and click Repair— this will force the installer to refresh all core dependencies, including the correct 17.0 version of the.Threading DLL.

2. Manually override the assembly binding redirect #

Your FusionLog shows the system is redirecting to 17.1, so we can force VS to use the 17.0 DLL directly:

• Navigate to your VS IDE config file: C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\devenv.exe.config (open it with admin privileges in Notepad/VS Code).
• Find the <runtime> section and add this binding rule inside it:

  <dependentAssembly>
    <assemblyIdentity name="Microsoft.VisualStudio.Threading" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-17.1.0.0" newVersion="17.0.0.0" />
  </dependentAssembly>
  

• Save the file and restart VS.

3. Clean up the GAC and re-register the correct DLL #

Even if you tried adding the DLL to the GAC before, the 17.1 version might still be lingering. Use an admin Command Prompt:

• First, remove the 17.1 version from GAC:

  gacutil /u Microsoft.VisualStudio.Threading, Version=17.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
  

• Then locate the 17.0 DLL (usually in C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\PublicAssemblies) and register it:

  gacutil /i "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Threading.dll"
  

• Adjust the file path if your VS is installed in a different location.

4. Run a forced repair with the VS bootstrapper #

Regular repairs can miss some corrupted files— try using the official bootstrapper for a deeper fix:

• Download the VS 2022 Community bootstrapper (if you don’t have it already).
• Open an admin Command Prompt, navigate to the folder with the bootstrapper, and run:

  vs_community.exe --repair --norestart
  

• This will re-download all core components from scratch, replacing any mismatched or damaged DLLs.

5. Rule out conflicting extensions #

Third-party extensions often cause unexpected DLL binding issues. Test launching VS in safe mode:

• Open a Command Prompt and run:

  devenv.exe /safeMode
  

• If VS launches successfully here, disable extensions one by one (go to Extensions > Manage Extensions) and restart VS each time to find the culprit.

If none of these steps work, double-check for pending Windows updates— sometimes system-level .NET or framework updates can resolve underlying assembly loading problems without needing a full OS reinstall.

内容的提问来源于stack exchange，提问作者DatenThielt