The java.home variable defined in Visual Studio Code settings points to a missing or inaccessible folder (C:\Users\username\AppData\Local\Programs\AdoptOpenJDK) (WSL)

When I open VSCode in WSL, it show this notification. Nothing happen when I open VSCode in Windows. I have define JAVA_HOME and JDK_HOME in system varibles. Then define the path of jdk-11/bin in the system path. The problem is VSCode in WSL use the same ‘setting.json’ as VSCode in Windows.

Environment

• Operating System: Windows 10 Education Version 2004 OS Build 19640.1
• Local JDK version: AdoptOpenJDK 11
• Visual Studio Code version: 1.46.0
• Java extension version: 0.8.1

Steps To Reproduce

1. Add remote WSL: Ubuntu-20.04 distro
2. Install JDK for WSL with apt install jdk-11-openjdk
3. Now install Java Extension Pack for WSL
4. When opening the Java Source Code (Maven) then pop up opening that “The java.home variable defined in Visual Studio Code settings points to a missing or inaccessible folder (C:\Users\username\AppData\Local\Programs\AdoptOpenJDK)”

Error Screen when I try to open VSCode in WSL: Ubuntu (https://imgur.com/mbnwBqT) Nothing happen when I open VSCode in Windows.

Here is my ‘setting.json’ {

"java.home": "C:\\Users\\Huy\\AppData\\Local\\Programs\\AdoptOpenJDK",

"java.help.firstView": "gettingStarted",

"editor.suggestSelection": "first",

"files.exclude": {

"\*\*/.classpath": true,

"\*\*/.project": true,

"\*\*/.settings": true,

"\*\*/.factorypath": true

},

"[java]": {

"editor.defaultFormatter": "redhat.java"

},

"java.refactor.renameFromFileExplorer": "autoApply", 

}

[Eskibear]

See:

• spec of machine-overridable: https://code.visualstudio.com/api/references/contribution-points
• original discussion: https://github.com/microsoft/vscode/issues/73985#issuecomment-522013185

[Eskibear]

C:\Users\Huy\AppData\Local\Programs\AdoptOpenJDK

@testforstephen above path is valid (on Windows only), which is the default AdoptOpenJDK installation folder in vscode java installer. The problem is, java.home should not be shared accross machines (E.g. Windows & WSL). If I remember correctly, we proposed to change scope of setting java.home to “machine” before, and that’s exactly for such cases.

@nduchuyvp123 In WSL, you may try removing java.home from your settings. After that, /usr/lib/jvm/java-14-openjdk-amd64 will take effect automatically.