Language Services initialization fails with ServiceActivationFailedException and host exit code -2146233082

[severity:It’s more difficult to complete my work] [regression] [worked-in:18.4&18.5] Microsoft.ServiceHub.Framework.ServiceActivationFailedException : 激活“Microsoft.VisualStudio.LanguageServices.InitializationCore64”服务失败。 —> Microsoft.ServiceHub.Utility.HostCrashException: Failed to start host ‘dotnet$C94B8CFE-E3FD-4BAF-A941-2866DBB566FE’. Host exited with code ‘-2146233082’ (ErrorKind: HostExited) (ErrorKind: HostExited HResult: 80131500) 在 Microsoft.ServiceHub.Client.HubClient.RemoteServiceBrokerWrapper.<>c__DisplayClass9_0.<<RequestServiceChannelAsync>b__0>d.MoveNext() — 引发异常的上一位置中堆栈跟踪的末尾 — 在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 在 Microsoft.ServiceHub.Utility.Shared.ServiceHubRetry.<ExecuteAsync>d__01.MoveNext() --- 引发异常的上一位置中堆栈跟踪的末尾 --- 在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 在 Microsoft.ServiceHub.Utility.Shared.ServiceHubRetry.<ExecuteAsync>d__01.MoveNext() — 引发异常的上一位置中堆栈跟踪的末尾 — 在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 在 Microsoft.ServiceHub.Client.HubClient.RemoteServiceBrokerWrapper.<RequestServiceChannelAsync>d__9.MoveNext() — 引发异常的上一位置中堆栈跟踪的末尾 — 在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 在 Microsoft.ServiceHub.Client.HubClient.RemoteServiceBrokerWrapper.<RequestServiceChannelAsync>d__9.MoveNext() — 引发异常的上一位置中堆栈跟踪的末尾 — 在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 在 Microsoft.VisualStudio.Services.ServiceBroker.VsHubClient.VsHubClientRemoteServiceBrokerWrapper.<RequestServiceChannelAsync>d__8.MoveNext() — 引发异常的上一位置中堆栈跟踪的末尾 — 在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 在 Microsoft.ServiceHub.Framework.RemoteServiceBroker.<GetProxyAsync>d__361.MoveNext() --- 内部异常堆栈跟踪的末尾 --- at async Microsoft.ServiceHub.Framework.RemoteServiceBroker.GetProxyAsync[T](<未知参数>) at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Threading.Tasks.ValueTask1.get_Result() at async Microsoft.VisualStudio.Utilities.ServiceBroker.GlobalBrokeredServiceContainer.ProfferedRemoteServiceBroker.GetProxyAsyncT at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Threading.Tasks.ValueTask1.get_Result() at async Microsoft.VisualStudio.Utilities.ServiceBroker.GlobalBrokeredServiceContainer.View.GetProxyAsync[T](<未知参数>) at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Threading.Tasks.ValueTask1.get_Result() at async Microsoft.ServiceHub.Framework.ServiceBrokerClient.<>c__DisplayClass21_01.<GetProxyAsync>b__0[T](<未知参数>) at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at async Microsoft.VisualStudio.Threading.AsyncLazy1.<>c__DisplayClass20_0.<GetValueAsync>b__0T at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at async Microsoft.VisualStudio.Threading.ThreadingTools.WithCancellationSlowT at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at async Microsoft.ServiceHub.Framework.ServiceBrokerClient.GetProxyAsyncT at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Threading.Tasks.ValueTask1.get_Result() at async Microsoft.CodeAnalysis.Remote.BrokeredServiceConnection1.RentServiceAsyncTService at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Threading.Tasks.ValueTask1.get_Result() at async Microsoft.CodeAnalysis.Remote.BrokeredServiceConnection1.TryInvokeAsyncTService,TResult

====

1. Since installing version 18.3, I have encountered persistent compatibility issues with all subsequent update versions.
2. The built-in repair tool fails, showing an error that WebView2Runtime is required.
3. Due to organizational policies/system configurations, my Edge browser updates are restricted, which appears to block the standalone offline installation of WebView2Runtime.
4. The current dependency design that links Visual Studio and WebView2Runtime directly to Edge browser updates creates significant deployment challenges for users who prefer managed browser environments.

Additionally, the feedback submission process encountered technical difficulties and could be optimized for better user experience.