VS2022 crashes with version 17.5.2 (as it did with 17.5.1)

Question

VS2022 crashes with version 17.5.2 (as it did with 17.5.1)

HeSitated 15

After updating VS2022 to v17.5.2 I get this popup:

2023-03-16_08h56_33

Restarting VS makes it even worse: after the solution is fully loaded, VS crashes completely.

In the ActivityLog.xml is this error:

  <entry>
    <record>384</record>
    <time>2023/03/16 07:56:23.099</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>SetSite failed for package [VSPackage]Source: &apos;mscorlib&apos; Description: The JSON-RPC connection with the remote party was lost before the request could complete.&#x000D;&#x000A;StreamJsonRpc.ConnectionLostException: The JSON-RPC connection with the remote party was lost before the request could complete.&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at StreamJsonRpc.JsonRpc.&lt;InvokeCoreAsync&gt;d__156.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at StreamJsonRpc.JsonRpc.&lt;InvokeCoreAsync&gt;d__145`1.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.Developer.IdentityService.PipeManager.&lt;InvokeRpcFuncAsync&gt;d__14.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.Developer.IdentityService.StorageService.StorageServiceClient.&lt;SetAdditionalContextPropertiesAsync&gt;d__17.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.Developer.IdentityService.StorageService.StorageServiceClient.&lt;InitializeAsync&gt;d__14.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.Developer.IdentityService.StorageService.StorageServiceClient.&lt;CreateAsync&gt;d__13.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.Developer.IdentityService.AccountManager.&lt;GetStoreAsync&gt;d__31.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.AppInsights.GettingStarted.AppInsightsAccountService.&lt;InitializeAsync&gt;d__10.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.AppInsights.GettingStarted.AppInsightsAccountService.&lt;CreateAsync&gt;d__9.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.AppInsights.GettingStarted.VSPackage.&lt;&gt;c__DisplayClass25_0.&lt;&lt;InitializeAsync&gt;b__0&gt;d.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Shell.AsyncPackage.&lt;&gt;c__DisplayClass29_0.&lt;&lt;AddService&gt;b__1&gt;d.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Threading.AwaitExtensions.ExecuteContinuationSynchronouslyAwaiter`1.GetResult()&#x000D;&#x000A;   at Microsoft.VisualStudio.Threading.AsyncLazy`1.&lt;&gt;c__DisplayClass13_0.&lt;&lt;GetValueAsync&gt;b__0&gt;d.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.AppInsights.GettingStarted.CodeLens.AISolutionDataManager.&lt;InitializeAsync&gt;d__51.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.AppInsights.GettingStarted.VSPackage.&lt;&lt;InitializeAsync&gt;b__25_5&gt;d.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Shell.AsyncPackage.&lt;&gt;c__DisplayClass29_0.&lt;&lt;AddService&gt;b__1&gt;d.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Threading.AwaitExtensions.ExecuteContinuationSynchronouslyAwaiter`1.GetResult()&#x000D;&#x000A;   at Microsoft.VisualStudio.Threading.AsyncLazy`1.&lt;&gt;c__DisplayClass13_0.&lt;&lt;GetValueAsync&gt;b__0&gt;d.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.AppInsights.GettingStarted.AppInsightsMenuCommandService.&lt;InitializeAsync&gt;d__21.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.AppInsights.GettingStarted.VSPackage.&lt;InitializeAsync&gt;d__25.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Shell.AsyncPackage.&lt;&gt;c__DisplayClass21_0.&lt;&lt;Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize&gt;b__1&gt;d.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)&#x000D;&#x000A;   at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)</description>
    <guid>{1A4EFADE-F6B2-4490-A2EF-21D5F3D1C8E0}</guid>
    <hr>0x80131500</hr>
    <errorinfo></errorinfo>
  </entry>

With VS v17.5.1 I had the same problem.

Edit

Two colleagues do not have this problem (one with and one without R#)

Garry Amann 0 Reputation points

2023-04-06T11:56:24.0633333+00:00

On a system with existing VS2022-17-3 the upgrade worked ok. On a clean 22621.1485 OS install, using Visual Studio Installer 3.5.2145.59678, after installing 17.5, 17.5.3, 17.4, 17.2 all have the issue listed and VS2022 does not successfully launch. Log xml reports SetSite failed for package [Feature Flags Package]Source: 'mscorlib' Description: The satellite assembly named "Microsoft.VisualStudio.Shell.UI.Internal.resources.dll, PublicKeyToken=b03f5f7f11d5a3a" for fallback culture "en" either could not be found or could not be loaded. On exporting configuration from working system and importing on non-working system I get this message Microsft.VisualStudio.Component.VC.CoreBuildTools: No matching workload or component found. This can be easily duplicated on a system that has not had and VS installed. This is a serious issue as VS2022 cannot launch and cannot be installed on a new dev system.
Garry Amann 0 Reputation points

2023-04-07T11:05:46.83+00:00

Testing 4/7/2023 I was able to install and run 17.5.3. OS 25335.

Garry Amann 0 Reputation points

2023-04-06T11:56:24.0633333+00:00

On a system with existing VS2022-17-3 the upgrade worked ok. On a clean 22621.1485 OS install, using Visual Studio Installer 3.5.2145.59678, after installing 17.5, 17.5.3, 17.4, 17.2 all have the issue listed and VS2022 does not successfully launch. Log xml reports SetSite failed for package [Feature Flags Package]Source: 'mscorlib' Description: The satellite assembly named "Microsoft.VisualStudio.Shell.UI.Internal.resources.dll, PublicKeyToken=b03f5f7f11d5a3a" for fallback culture "en" either could not be found or could not be loaded. On exporting configuration from working system and importing on non-working system I get this message Microsft.VisualStudio.Component.VC.CoreBuildTools: No matching workload or component found. This can be easily duplicated on a system that has not had and VS installed. This is a serious issue as VS2022 cannot launch and cannot be installed on a new dev system.
Garry Amann 0 Reputation points

2023-04-07T11:05:46.83+00:00

Testing 4/7/2023 I was able to install and run 17.5.3. OS 25335.

Answer 1

HeSitated 15

After step 1-3 VS completely refused to start with the message:
2023-03-21_16h33_59

So I'm back to 17.4.5.

Kirill Ovcharenko 0 Reputation points

2023-03-22T08:56:50.2466667+00:00
I had the same error after updating to a new version of Visual Studio (17.5.3)

Could not start visual studio due to an error - StreamJsonRpc.ConnectionLostException The JSON-RPC connection with the remote party was lost before the request could complete

Repaire and reinstall didn't help.
Then I installed StreamJsonRpc manully in GAC. That error dissapeared, but I got another errors:
The 'Settings Package' package did not load correctly
The 'Environment Package Window Management' package did not load correctly
Tianyu Sun-MSFT 20,686 Reputation points Microsoft Vendor

2023-03-30T10:05:29.5866667+00:00

Hi @Kirill Ovcharenko , @HeSitated ,

Probably, this is a potential issue, could you please submit a ticket on our Developer Community and attach the corresponding ActivityLog.xml for further investigation?

If you can’t open VS to submit a ticket, please try this .NET entry instead and after you submit the ticket, edit and add the Visual Studio tag.

Feel free to let us know if you have any further concerns.

Thanks for helping us make Visual Studio better.

Best Regards,

Tianyu
zrinyi 0 Reputation points

2023-03-30T10:22:33.73+00:00

I had the same error after upgrading from 17.4.4 to 17.5.3. I tried fixing it as suggested by others above but that did not solved the problem. I reverted back to 17.4.4.
Kirill Ovcharenko 0 Reputation points

2023-04-05T17:38:25.74+00:00

I couldn't fix the error so I cleared the VS entirely from the system and installed 17.4 version. It works for now and I will not update to 17.5 again.

Answer 2

Tianyu Sun-MSFT 20,686 Microsoft Vendor

Hello @HeSitated ,

Welcome to Microsoft Q&A forum.

Please first open Developer Command Prompt for Visual Studio 2022, type and run this command devenv /SafeMode. After running this command, VS 2022 will be opened automatically, please check if the same error appears.

If the same error doesn’t appear, the error should be caused by installed extension(s). Please open Visual Studio and go to Extensions > Manage Extensions > Installed, disable the third-party extensions one by one to narrow down this issue. If you finally find the corresponding extension, please try to uninstall it.

If the same error appears again, please try following:

Repair VS from VS Installer > More > Repair.
Reset VS settings by running devenv /ResetSettings command in Developer Command Prompt for Visual Studio 2022.
Remove Visual Studio cache by renaming/removing every folders called ComponentModelCache in C:\Users\username\AppData\Local\Microsoft\VisualStudio\17.0_XXXXXXXX folder.
If the issue only appears on specific project, please try to clean project cache by removing the hidden .vs, bin and obj folders.
Try to reinstall the corresponding workload(s) in VS Installer if this issue occurs for specific development.

Besides, please press Win+R > type and run regedit > select Computer > click Edit > Find… > input the guid number that shows in the ActivityLog.xml > click Find Next button to check if this guid points to any specific program.

Please feel free to let us know if it works.

Sincerely,

Tianyu

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

HeSitated 15

Starting Vs with devenv /SafeMode resultet in:

<entry>
  <record>1090</record>
  <time>2023/03/16 15:52:34.967</time>
  <type>Error</type>
  <source>GlobalBrokeredServiceContainer</source>
  <description>Microsoft.ServiceHub.Framework.ServiceActivationFailedException: Activating the &quot;Microsoft.VisualStudio.Extensibility.ExtensionMetadataService (0.3)&quot; service failed. ---&gt; System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)&#x000D;&#x000A;   at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)&#x000D;&#x000A;   at Microsoft.VisualStudio.Services.VSGlobalBrokeredServiceContainer.PackageServiceRegistration.&lt;LoadProfferingPackageAsync&gt;d__4.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Utilities.ServiceBroker.GlobalBrokeredServiceContainer.View.&lt;LoadProfferingPackageAsync&gt;d__25.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Utilities.ServiceBroker.GlobalBrokeredServiceContainer.View.&lt;TryGetProfferingSourceAsync&gt;d__24.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Utilities.ServiceBroker.GlobalBrokeredServiceContainer.View.&lt;GetProxyAsync&gt;d__19`1.MoveNext()&#x000D;&#x000A;   --- End of inner exception stack trace ---</description>
</entry>

And many errors more....

Tianyu Sun-MSFT 20,686 Reputation points Microsoft Vendor

2023-03-17T06:49:48.59+00:00
Hi @HeSitated ,

Thanks for your reply.

May I ask if you have tried the five troubleshooting methods that I shared above?

Just to confirm if you also have any third-party extension installed in/for VS 2022, for example R# that you mentioned? If you do have any of them installed, could you please try to uninstall them => repair VS => check if the errors disappear and then try to reinstall them again?

Besides, please go to Extensions => Manage Extensions => Installed => Live Share 2022 => click Disable and check if the errors disappear.

Please feel free to let us know if the errors disappear.

Sincerely,

Tianyu
HeSitated 15 Reputation points

2023-03-29T05:38:09.0866667+00:00
The answers to your questions:

Yes

Tried no luck

I've had Live share only installed shortly when i installed VS2022, but because of many updates and never being used, I deinstalled it.

Now I've deinstalled VS completely and installed the LTSC version.

VS2022 crashes with version 17.5.2 (as it did with 17.5.1)

2 answers

Activity