I get an error when opening a repo using VS Code

[Rod-at-DOH]

🏷️ Discussion Type

Question

Body

When I open a legacy application in my local repo using Visual Studio Code, I'll get this error:

I don't understand why I'm getting this error. This is the first time I've gotten into VS Code since turning on my machine earlier this week. How could I have a VS Code process running when I just opened it? The only VS Code processes running is the ones related to the process I just opened.

Guidelines

• I have read and understood this category's guidelines before making this post.

[Mahatva1303]

Hi,
This usually happens because some VS Code background processes are still running even after the main window was closed previously. Extensions, terminals, update services, or crashed processes can sometimes remain active in the background, which prevents the updater from modifying or deleting VS Code files.

A few things you can try:

• Completely close VS Code
• Open Task Manager and end all Code.exe or “Visual Studio Code” processes
• Then run the updater again
• If that does not work, restart your PC and try updating before opening any project

Sometimes antivirus software or Windows permissions can also lock files temporarily, which can trigger the same “Access is denied (os error 5)” message.

You can also try:

• Running VS Code as Administrator
• Temporarily disabling antivirus protection during update
• Downloading the latest installer manually and reinstalling over the existing version
• Reinstalling vs code (if nothing works)

Since the error points to the updater failing to delete a folder inside the VS Code installation directory, it is most likely a locked file/process issue rather than a problem with your repository or legacy application itself.

[Mahatva1303]

@Rod-at-DOH hope this answers your query if yes please mark it as answered

[Rod-at-DOH]

@Mahatva1303 unfortunately, they took the ability to run anything as Administrator away, over a year ago.

[Mahatva1303]

Ah, I see. In that case, it sounds more like a permissions or updater limitation introduced in newer VS Code versions rather than a normal background-process issue alone.

If running as Administrator is no longer available in your environment, you could try:

• Fully uninstalling VS Code and reinstalling the latest version manually
• Installing the User Installer version instead of the System Installer (or vice versa)
• Deleting leftover temporary update folders inside %LocalAppData%\Programs\Microsoft VS Code\
• Checking whether another security policy, antivirus, or company-managed restriction is locking the updater

Since the error specifically occurs during the updater’s delete step, it may also be related to how VS Code handles self-updates under restricted Windows permissions now.

[Rod-at-DOH]

Thank you very much for this additional information! I wasn't aware of that %LocalAppData%\Programs\Microsoft VS Code\ folder. I'm looking at it now and this is what I see:

I suspect that the unins000.* files aren't related to the temporary update folders. It's probably the folder named 0958016b2a. If that is correct, then can I just delete that folder?