This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 40%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJA%3C/text%3E%3C/svg%3E)
Getting the following error while launching the newly installed visual studio 2022
While tr
ying to repair getting this error, but I don't see any restrictions in my settings. Also, no issue with visual studio 2026, but as I need 2022 version.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 49%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Thank you for your response. This helps me better understand your issue.
Visual Studio requires PowerShell to run scripts for pre check tasks and to process the installation. PowerShell can be blocked not only by antivirus settings, but also by PowerShell execution policies. If you are using a company managed computer, these settings are usually enforced by Group Policy.
You can check whether Visual Studio is blocked from executing PowerShell by following the steps below:
cd "C:\Program Files (x86)\Microsoft Visual Studio\Installer\PrecheckTools"
.\Microsoft.VisualStudio.Setup.TestPowerShell
If it returns the same result as shown in my screenshot, Visual Studio is working normally and can use PowerShell for execution. Otherwise, you will need to change the policy as described in the next step.
In the PowerShell command-line interface, copy and paste the following command to set the execution policy to RemoteSigned:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
Then check the status again using this command to confirm the change was successful:
Get-ExecutionPolicy -List
If the output looks like the expected result, the policy has been updated successfully and you can try installing Visual Studio again. If the error still persists, please proceed to the next step to check Publisher Trust.
Go to Control Panel → search for Internet Options → Content → Publishers → Untrusted Publishers. If there are any entries in the list, please remove them (as shown in the screenshot below).
If you have not installed any third-party antivirus software, Windows will use Windows Security as the default. Please check whether Smart App Control is enabled and turn it off if applicable.
I look forward to hearing from you soon.
Has your issue been resolved? If you have any further questions, please don't hesitate to let me know in the comment. I'm happy to assist you. If my support was helpful so far, kindly follow the instructions here so others with the same problem can benefit as well.
Thank you for sharing the screenshot. Based on the error message shown, Visual Studio is failing to start due to the following exception:
StreamJsonRpc.ConnectionLostException: The JSON‑RPC connection with the remote party was lost before the request could complete.
This error indicates that one of those background services crashed or failed to initialize during startup, causing Visual Studio to lose communication with it and shut down.
Here are a few troubleshooting steps you can try to resolve this issue. I’ve listed them in order, starting with the most commonly recommended solutions.
1. Delete the Identity Service cache
Corrupted identity data is the most common cause of this error.
2. Start Visual Studio in Safe Mode
This helps determine whether an extension is causing the failure.
devenv /safemodeIf Visual Studio opens, disable or uninstall recently added extensions, then restart normally.
3. Repair Visual Studio
If the issue persists, repairing the installation can restore corrupted components.
Restart the machine after the repair completes.
Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.