Installing extension through the commande line show installed extension unabled to be used

[lx78WyY0J5]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chromium based
• Local OS: Windows
• Remote OS: Ubuntu 20.04
• Remote Architecture: amd64b
• code-server --version: 4.100.3 409c64e with Code 1.100.3

Steps to Reproduce

1. Install code-server
2. install an extension with the command line ex:

code-server --install-extension GitHub.vscode-pull-request-GitHub
code-server --install-extension PKief.material-icon-theme
code-server --install-extension ms-vscode.live-server
code-server --install-extension vscjava.vscode-java-pack

3. Reload code-server (I guess)
4. Visit your code-server page
5. The extension won't be visible
6. Confirm Installation of the extension by using the same command :

root@vps:~# code-server --install-extension ms-vscode.live-server

Installing extensions...

Extension 'ms-vscode.live-server' v0.4.15 is already installed. Use '--force' option to update to latest version or provide '@<version>' to install a specific version, for example: 'ms-vscode.live-server@1.2.3'.

root@vps:~# code-server --install-extension ms-vscode.live-server --force

Installing extensions...
Extension 'ms-vscode.live-server' is already installed.

Expected

NB : From a local VScode Windows Portable setup

Actual

From the Code-Server

Does this bug reproduce in native VS Code?

I did not test native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

• I am using a secure context.

Notes

The Local VScode extension are installed through a drive syncing a portable VSCode with an extension pack installed a while ago, so i haven't tested running this command in a local VSCode only in code-server

Notes ²

I restarted Apache2, Code-Server, and runed the test with a browser in private tab, with no cache, and also with my "normal" browser after disabling cache, and with it

Notes 3

Stoping server, and reloading a new session seem to do nothing for me
CF : similar issue

Sorry for my English