Forum Discussion

kopbeen's avatar
kopbeen
Copper Contributor
Oct 24, 2026

Feature messages keep popping up in Visual Studio Community 2026

Good day, 

I am trying to fix/get rid of these annoying messages that keeps popping up in my IDE. 

  1. Microsoft.ServiceHub.Framework.ServiceActivationFailedException : Activating the "Microsoft.VisualStudio.LanguageServices.AssetSynchronizationCore64" service failed. ---> StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete.

  2. Microsoft.ServiceHub.Framework.ServiceActivationFailedException : Activating the "Microsoft.VisualStudio.LanguageServices.DocumentHighlightsCore64" service failed. ---> StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete.

  3. Microsoft.ServiceHub.Framework.ServiceActivationFailedException : Activating the "Microsoft.VisualStudio.LanguageServices.NavigationBarItemCore64" service failed. ---> StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete.

Any idea how I can get rid / fix 'em 

Tried:  

  1. Repairing VS
  2. Clearing MEF & component cache
  3. Environment reset
  4. Manually Add CET Features via XML

Setup:

  1. Windows 11 (OS Build 21996.1) on KVM/QEMU

Thank you all!

visual studio

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Nov 05, 2026

    Those messages report failed language-service activation and a lost JSON-RPC connection, so hiding feature notifications would not resolve the underlying problem. The exceptions alone do not identify why the remote service stopped.

     

    Your reported Windows build, 21996.1, is outside the currently supported Windows 11 releases. Visual Studio 2026 requires a supported operating-system version. Before further cache resets or CET changes, reproduce the issue in a persistent VM running a current, supported Windows release and an updated Visual Studio installation. KVM/QEMU by itself is not enough information to establish the cause.

     

    On that supported baseline, start Visual Studio with devenv /SafeMode to compare behavior with the default environment and services. Also run devenv /Log to capture ActivityLog.xml, then reproduce the failure.

     

    If it persists, use Report a Problem with the exact Visual Studio version, VM configuration, logs and reproduction steps. Include that repair and cache clearing already failed.