Unable to activate Robocorp Code extension, *.lck files generated but not deleted

I cannot activate the Robocorp Code extension on VS Code when clicking on a .robot file, an error occur even with environnement setup, admin access and Privileged Internet access.

Steps :
-Installing VS Code
-Installing “Robocorp Code” and “Robot Framework Language Server” extensions
-Cloning a git project
-Clicking on .robot file to see the content

Here is the end of the log (Robocorp Code), it seems like there is an issue with *.lck files that are not supposed to be here, but I may be wrong.
Sorry I cannot send the entire log as there are URL in it (for conda files…), and as a new user on this forum it’s blocking me (I also cannot upload it as an attachment)

Error code: 6

Error name: Error

Unable to activate Robocorp Code extension because python executable from RCC environment was not provided.

– Most common reason is that the environment couldn’t be created due to network connectivity issues.

– Please fix the error and restart VSCode.

Error getting Python

[Error - 1:17:09 PM] Starting client failed

[object Object]

Error initializing Robocorp code.

Robocorp Code initialization finished. Took: 111.8s

Error executing: c:\Users\201053355.vscode\extensions\robocorp.robocorp-code-1.4.0\bin\rcc.exe feedback metric -t vscode -n vscode.code.error -v INIT_PYTHON_ERR

Error: Error: Command failed: c:\Users\201053355.vscode\extensions\robocorp.robocorp-code-1.4.0\bin\rcc.exe feedback metric -t vscode -n vscode.code.error -v INIT_PYTHON_ERR

Warning: #1: Serialized config access [config lock] (rcc lock wait)

FATAL: could not lock C:\Users\201053355\AppData\Local\robocorp\rcc.yaml.lck, reason The process cannot access the file because another process has locked a portion of the file.; ignored.

Tracking is disabled. Quitting.

Error message: Command failed: c:\Users\201053355.vscode\extensions\robocorp.robocorp-code-1.4.0\bin\rcc.exe feedback metric -t vscode -n vscode.code.error -v INIT_PYTHON_ERR

Warning: #1: Serialized config access [config lock] (rcc lock wait)

FATAL: could not lock C:\Users\201053355\AppData\Local\robocorp\rcc.yaml.lck, reason The process cannot access the file because another process has locked a portion of the file.; ignored.

Tracking is disabled. Quitting.

Error code: 1

Error name: Error

Stderr: Warning: #1: Serialized config access [config lock] (rcc lock wait)

FATAL: could not lock C:\Users\201053355\AppData\Local\robocorp\rcc.yaml.lck, reason The process cannot access the file because another process has locked a portion of the file.; ignored.

Tracking is disabled. Quitting.

One way to get out of file locks are logging off your account and logging back in