Urgent Issue with Verse Language Support in Visual Studio : The Verse Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.

General Issues and Bug Reporting
, ,
1

Summary

Hello,

For the past 2–3 days, I’ve been facing a major issue with Visual Studio that prevents me from working properly with Verse. Syntax errors are never highlighted or corrected, which severely disrupts my workflow—especially for includes, trivial errors, and even basic features like Ctrl+Click to navigate directly to functions in internal files. This is a significant problem.

I noticed that this issue started occurring after seeing the following error:

The Verse Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.

[Info - 5:41:33 PM] Connection to server got closed. Server will restart.
[Info - 5:41:33 PM] Connection to server got closed. Server will restart.
[Info - 5:41:33 PM] Connection to server got closed. Server will restart.
[Info - 5:41:33 PM] Connection to server got closed. Server will restart.
[Error - 5:41:33 PM] Connection to server got closed. Server will not be restarted.

The problem persists even after uninstalling and reinstalling UEFN, Visual Studio, and clearing all caches. This issue affects all maps, including the official UEFN example maps. I’ve tried everything I could think of, and I’m really desperate for a solution. Honestly, resetting my PC would be a last resort, but I’d prefer to avoid that.

I hope a debug or a proper fix can be proposed.

Thank you very much for your help.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

Open any UEFN project.

Launch Visual Studio and observe the issue.

You will see the five output logs as soon as Visual Studio is fully loaded, and a red popup will appear.

Expected Result

Syntax errors should normally be visible, but none are appearing. Additionally, I am unable to use Ctrl+Click to navigate directly to a function’s definition, which is also causing issues.

Observed Result

[Info - 5:41:33 PM] Connection to server got closed. Server will restart.
[Info - 5:41:33 PM] Connection to server got closed. Server will restart.
[Info - 5:41:33 PM] Connection to server got closed. Server will restart.
[Info - 5:41:33 PM] Connection to server got closed. Server will restart.
[Error - 5:41:33 PM] Connection to server got closed. Server will not be restarted.

The Verse Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.

Platform(s)

PC

Upload an image

Capture d'écran 2026-02-17 174228.png

Capture d'écran 2026-02-17 174252.png
Capture d'écran 2026-02-17 174252.png690×180 3.55 KB

2

try re installing the verse extension i think i had this once and that fixed it for me

image
image452×943 76.3 KB

Or something along those lines icr they was a post tho done so maybe check through old posts

3

Hello, thank you very much for your help. This is no longer relevant because, apparently, we can’t reinstall the Verse extension… the Verse extension installs automatically as soon as we launch a UEFN project. After that, I obviously uninstalled the extension and restarted the project, and I still have the same problem…

image_2026-02-17_195814152
image_2026-02-17_1958141521397×671 51.2 KB

4

Found this old post

I know we had a post at some point about it

5

There was a post long while ago

The Verse Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted. - Programming & Scripting / Verse - Epic Developer Community Forums

6

Hello, yes I’ve already seen it, but everything that’s suggested doesn’t work. I’ve already tried Visual Studio Insider and it doesn’t fix anything. I compile before opening Visual Studio, and that doesn’t work either. I’m opening a new topic because I have no solution in my case. Could the problem be coming from a workspace issue?

7

Hello, I’m getting back to you with an update. On my end, it seems the issue was caused by a Windows update that encountered problems during installation. You just need to roll back to a previous version and run the update again, or reinstall the update.

1 Like