A terminally deprecated method in java.lang.System has been called (System::setSecurityManager)

Installing a local instance of SonarQube using zip file
sonarqube V10.4.1.88267, sonar-scanner-cli-5.0.1.3006-windows
java 17.0.10+7 Windowsx86, jdk-package

While trying to run SonarQube locally, I am getting the following error:

PS C:\sonarqube-10.4.1.88267\bin\windows-x86-64> .\StartSonar.bat
Starting SonarQube...
2024.04.04 19:29:36 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\sonarqube-10.4.1.88267\temp
2024.04.04 19:29:36 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:27110]
2024.04.04 19:29:36 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\sonarqube-10.4.1.88267\elasticsearch]: C:\Program Files (x86)\Eclipse Adoptium\jdk-17.0.10.7-hotspot\bin\java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=C:\sonarqube-10.4.1.88267\elasticsearch -Des.path.conf=C:\sonarqube-10.4.1.88267\temp\conf\es -Des.distribution.type=tar -cp C:\sonarqube-10.4.1.88267\elasticsearch\lib\*;C:\sonarqube-10.4.1.88267\elasticsearch\lib\cli-launcher\* org.elasticsearch.launcher.CliToolLauncher
2024.04.04 19:29:36 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.04.04 19:29:48 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
2024.04.04 19:29:48 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\sonarqube-10.4.1.88267]: C:\Program Files (x86)\Eclipse Adoptium\jdk-17.0.10.7-hotspot\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\sonarqube-10.4.1.88267\temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED --add-exports=java.base/jdk.internal.ref=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 -Dcom.redhat.fips=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-10.4.1.88267.jar;C:\sonarqube-10.4.1.88267\lib\jdbc\h2\h2-2.2.224.jar org.sonar.server.app.WebServer C:\sonarqube-10.4.1.88267\temp\sq-process4941359071387706981properties
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecurityManager (file:/C:/sonarqube-10.4.1.88267/lib/sonar-application-10.4.1.88267.jar)
WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
2024.04.04 19:31:32 INFO  app[][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2024.04.04 19:31:32 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.04.04 19:31:32 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

The relavant path’s to sonar scanner cli & java have been added in the system environment variables
Kindly help me resolve the issue

Hey there.

This is a red herring, and just a warning. You can find what the rule issue is by looking at the process log files.