I had this same problem come up when running VS Code in a devcontainer (linux). It started about 3 days ago which is when 4.29 was released, and I had auto-update on for this extension, so I’m assuming it was related to this release. I was not having this issue in a devcontainer prior to then.
I was able to solve it by downloading and installing the sonarlint-vscode-linux-x64-4.29.0.vsix file from GitHub.
I am also seeing this while working in Windows 10 connected to a WSL. Reverting to 4.28 solves the problem for me. We have seen it on several machines so the theory of a one-off doesn’t seem correct.
I have tried to switch between the two versions several times and with each try it works with 4.28 and fails with 4.29.
Hello @kkroier, thanks for the report! 
You are right, it was not a one-off, temporary problem. We were able to reproduce same behaviour on a Ubuntu machine even today. And we still believe it is a problem on VS Marketplace / VS Code side. We have double-checked the artifacts that were published on the marketplace and they correctly include the embedded JRE in them.
To fix the issue on your side, the workaround will still be to either point SonarQube for IDE to a valid JRE installation path via sonarlint.ls.javaHome setting, or download and install the latest platform-specific version from our releases page.
In the meantime, we will reach out to the VS Code team to better understand what is going on (and make sure it will not happen again for the upcoming versions).
We will keep this thread updated.
Thanks everyone again for your quick engagement and proactivity!!
All the best,
Sophio
Hi everyone, 
The problem should be resolved now. We have reached out to VS Marketplace support and they updated the Linux & MacOS Intel artefacts for us. We are still trying to understand the root cause of the problem though 
Thanks for your patience,
Sophio
It still doesn’t work for me. Is the version expected to stay at 4.29.0 with the fix?
Edit: VSCode says the plugin was released two days ago when I go to install a fixed version.
@kkroier yes, the version is expected to be still 4.29. VS Code might have cached the previously installed package. You can have a look at the ~/.vscode/extensions folder and check if there are any entries with version sonarsource.sonarlint-vscode-4.29.0 before you try to update.
I hope that helps,
Sophio
Hi Sophio.
Deleting the cached copy solved the problem. Thanks.
A post was split to a new topic: SonarQube for VS Code - Error during start up - H2 issue
A post was merged into an existing topic: 4.35.0 → 4.35.1: SonarLint Language Server client: couldn’t create connection to server. + JRE