Jinbo Wang

The debugger doesn't support untrusted workspace, we need declare `"supported": false` in package.json.

Can you click "check details" link to see any progress there? Also, did you find any logs at Output channel for "Language Support for Java"? 

The output channel says the extension got closed. Could you try to see the log files to get more info? **F1 -> Java: Open All Log Files**

@Carsonc8 Thanks for sharing the logs. Are you running VS Code on Mac M1 chip? The logs show that Java extension is using an embedded 17.0.2-macosx-x86_64 JRE to start Java...

Here is how to change VS Code user setting. https://user-images.githubusercontent.com/14052197/162654012-b5f24682-c2cf-49d9-bd71-3ba39f0c1c9b.mp4

@jakopo87 The original issue is that Mac M1 used a wrong embedded JRE to launch Java extension. Your issue is different with the issue. Could you pls share the logs...

@jakopo87 The root cause for your issue is that your VS Code user setting `java.format.settings.url` is pointing to `file:C:/astir/eclipse-java-google-style.xml`, which is not a valid url format. You should set it...

> I opened another folder in vscode which used to work earlier, and it still works but my current folder open will not work and is stuck at the "debug:...

@chris-hunter206 When you simply open a standalone folder with Java files, and don't use any project system to manage source file structure, VS Code Java will try to understand your...

@GamesDoneWr0ng Thank you for providing logs. The log shows your workspace state file is corrupted and failed to restore it, that's a duplicated issue with https://github.com/microsoft/vscode-java-pack/issues/954#issuecomment-1119330452. ``` Caused by: org.eclipse.core.internal.dtree.ObjectNotFoundException:...