JDK Runtime in project settings always shows as jdk 21 while actual runtime isn't it #1443

Activity

1. github-actions commented on Sep 1, 2025

   

   github-actionsbot

   on Sep 1, 2025 – with GitHub Actions

   More actions

   Hi Cindy Liu (@yuyully), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

   Solution

   • Use the VS Code command “Java: Configure Java Runtime” to add your JDK 24 installation and mark it as default. This will update the list shown in Project Settings › JDK Runtime without needing to clear the cache.
   • Alternatively, set your JDK explicitly in settings.json:

     "java.configuration.runtimes": [
       {
         "name": "JavaSE-24",
         "path": "C:\\Program Files\\Java\\jdk-24.0.1",  // adjust to your install folder
         "default": true
       }
     ]

     Then reload the window to apply.

   Other references worth checking

   • Java “var cannot be resolved to a type” – JDK 13.0
     Suggests using “Java: Configure Java Runtime” to verify and switch the active JDK
     Java "var cannot be resolved to a type" - JDK 13.0 #313 (comment)

   • java.configuration.runtimes error The path points to a missing or inaccessible folder
     Shows how to declare your JDK runtime in settings.json and fix path issues
     java.configuration.runtimes error The path points to a missing or inaccessible folder in windows vscode-java-debug#1475

   Other references with low confidence

   • JAVA_HOME is not pointing to a JDK
     Describes checking JAVA_HOME/JDK_HOME environment variables if VS Code cannot locate a JDK
     JAVA_HOME is not pointing to a JDK. redhat-developer/vscode-java#1062

   The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

   👎React with 👎1Reacted by rghsh
2. github-actions

   added

   ai-triaged

   bug

   on Sep 1, 2025