The javaToolchains in the activity bar and the javaToolchains in the terminal(CMD) within vscode are different.

[itcasim0]

Extension Name: vscode-gradle
Extension Version:3.16.4
OS Version:Windows 11
VSCode version:1.92.2

Describe the bug
The javaToolchains in the activity bar and the javaToolchains in terminal(CMD) within vscode are different.

To Reproduce
Steps to reproduce the behavior.
If you go to help > javaToolchains > Run Task in the activity bar, only jdk-17 is detected.

When you run the below command in terminal(CMD), jdk-8 is also detected.

gradlew javaToolchains

Jdk-8 is registered in the Path of the system environment variable.
And jdk-17 is not registered at all, but is located in the path of C:\Program Files\Java\jdk-17.

Jdk-8 is detected only when java.import.gradle.java.home is specified in setting.json in vscode.

Expected behavior
Jdk paths should be detected.

Screenshots

• Run in the activity bar
  
  

• Run in the terminal(CMD)
  

Output from "Gradle for Java"

Does the bug still exist if you disable all other extensions?
Yes/No

Additional context
It is very inconvenient to specify java.import.gradle.java.home for each project every time.
So, I want to know the mechanism by which gradle detects jdk in activity bar.

[jdneo]

What if you close all vscode windows. And launch it via code . from your CMD. In that case, will jdk 8 be detected?

[itcasim0]

Is this what you want to know?

[jdneo]

Still cannot detect jdk8 from task explorer?

[itcasim0]

yes, still cannot detect jdk8