Installed VSCode to writable volume - VSCode cannot read extensions folder occasionally with an error message "no such file or directory"

[solgaeDK]

Hello,

One of my users started reporting problems after installing Visual Studio Code (VSCode) on his writable volume (UIA+Profile) - which, by the way, installs itself on the AppData\Local. After installed and adding some extensions. The user started getting this error when launching VSCode:

[Extension Host] Activating extension 'ms-vscode.Go' failed: ENOENT: no such file or directory, lstat 'C:\SnapVolumesTemp\MountPoints\{8e399ec3-0000-0000-0000-100000000000}\SVROOT\Users\(insert user name here)'.

This doesn't happen all the time, but lately, it started to happen more often than it doesn't.

We are running App Volumes 2.13.1 on our environment. It looks like VSCode doesn't seem to like the redirected path done by IO filter driver. Has anyone experienced this issue?

[jmatz135]

Can't you just uninstall VSCode and then install it for all users which then installs it to C:\Program Files (x86)?

[solgaeDK]

The add-ons/extensions are always installed inside the User profile directory (C:\Users\(username)\.vscode\extensions), so the location of the application itself doesn't matter.