Hi there @Akrys ! Welcome and thanks for reporting this weird behaviour
SonarQube for IDE requires JRE in order to even start. But we embed the JRE in the platform-specific packages so that users don’t need to install it themselves.
Would you be able to check the content of ~/.vscode/extensions/sonarsource.sonarlint-vscode-4.35.1-darwin-arm64 ? Is this folder even present? Or do you maybe have a universal folder named like sonarsource.sonarlint-vscode-4.35.1? We have had a case in the past where Microsoft marketplace fails to detect the target platform correctly and instead of installing OS-specific package it installs universal one that does not include the JRE.
As a workaround, you can also try downloading the package directly from our releases page & install it manually via the install from vsix... command.
This is the same issue, or at least very similar to the one seen with 4.29 when it first came out. You did something to rerelease it with the JRE properly embedded back then.
If it’s from OpenVSX marketplace, we started shipping smaller platform-specific artefacts there starting from v4.35.1, and they still have JRE embedded.
For some reason VS Code forces installation of the universal VSIX (without JRE). Even though on the marketplace I see the MacOS-specific packages were published.
Facing this with SonarQube for IDE version 4.35.1 and VSCode 1..106. Issuing the connect command manually via F1 leads to the same dialog as the OP.
The output log shows the following:
2025-11-17 12:59:12.303 [info] [Error - 12:59:12 PM] SonarLint Language Server client: couldn't create connection to server.
Downgrading the extension back to 4.35.0 fixes the issue, so this looks like a regression.
No response from Microsoft yet, but at least I found that we are not alone! Other extensions also experience the same and this is the link to the issue reported on VS Code.
Workaround still stands - you can download the platform-specific build from our releases page and install it manually
Hi, I still have the errors when the SonarQube extenssion starts.
I’m using now the SonarQube extension version 4.35.1 within VSCode version 1.106.2 in Windows 11.
I really don’t know why it says the last message about the JAVA_HOME environment variable because there isn’t ‘bin’ in the path. I don’t know from where it gets this “bin”.
Also I don’t understand why it triggers the first error because I’m not connected to any SonarQube Server nor Cloud.
We’ve merged your posts into this existing one. You can try the workaround described here.
We have not received any updates from neither marketplace support nor VS Code support regarding the issue. We are in the process of releasing v4.36 of the plugin. Maybe the republishing will help, but since we are not sure of the root cause, we cannot promise it will
Thank you for your patience and for raising the topic here!
Welcome and thanks for reporting this weird behaviour 
