We are having the same issue. We are upgrading to 26.1.0.118079 because the upgrade page says not to upgrade to the December 2025 version due to issues. I had to upgrade from Java 17, so we went to Openjdk Java 26.
I deleted the service and readded it with SonarService.bat. Starting the service fails. Event viewer just shows… Child process [10628 - java.exe -Xms8m -Xmx32m -Djava.awt.headless=true --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.management/sun.management=ALL-UNNAMED --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED -cp “......\lib\sonar-application-26.1.0.118079.jar” “org.sonar.application.App” ] finished with 1
I’m not seeing anything in the logs folder indicating any issues.
I can start the server with no issues using “StartSonar.bat”.
I figured this one out. I think most of the people reporting the issue had to upgrade Java. That means they changed their system PATH environmental variable. Services.exe grabs the PATH environmental variable when it starts running on server startup. It then continues to use that copy of it for it’s entire life. So, the fact that we changed the PATH to point to the new JAVA_HOME/bin doesn’t change the fact that Services.exe is using the old PATH when it tries to start a service.
So the fix is easy. If you can restart the server and Services.exe will pick up the new PATH and the service will start successfully. If for some reason you cannot restart the server, I think you can set SONAR_JAVA_PATH to the path of the new java.exe, then run:
