VSCode updates are slow since upgrading to 2026.2.2

A fix for this issue has been implemented in version 2026.3.0

VSCode updates are slow since upgrading to 2026.2.2

avatar

Ever since our latest upgrade to PowerShell Universal (PSU), anytime we modify something in VSCode, it's taking a noticeably long time to save/write those changes to PSU.

We see a spinning wheel at the bottom and it takes anywhere from 5-20 seconds to actually make the change.

Is there a configuration we can change to make this instantaneous like it was before or is this just the new way of saving with the upgrade VSCode extension + PSU?

All Comments (10)

avatar

@davestephenson It shouldn't take that long but we'd likely need to do some additional diagnosis into what may be causing that. The difference between the old extension (really, the old server), was that changes to the remote file system would update the file and would not wait for any configuration to take place. This lead to race conditions where edits were made but not necessarily accepted by the server.

The new editing endpoints now accept the change and then run through the configuration system to reload the resource you are editing. I often do see a noticeable lag in my lab that wasn't there in v5 but it's typically less than a second.

What would be helpful to know is if this happens with every file you attempt to edit. Some general size information about your environment (number of scripts, endpoints, or apps) would be good. Server system logs would also be helpful to see if we can pinpoint configuration file reloads that may be happening unnecessarily.

Adam Driscoll

PowerShell Expert and Software Architect at Devolutions

avatar

Thanks, @Adam Driscoll !

Yes, it appears to happen anytime I go to save any file in VSCode.

It doesn't seem to matter if it's a Script/Module or a Big/Little change.

I'm happy to provide whatever information about our environment that I can.

However, I'm relatively new to the PowerShell Universal world.

Do you have a KB or instruction that can help me find the information you're needing?

avatar

For the size of your environment, if you could just go to the home page of the PSU admin console there is a chart with a breakdown of the resource types and counts. Just a screenshot of that would be good.

As for the log, if you could go to Platform \ Logging and then click Log Files and download the log files from there. If you'd rather not share them on this public forum, you can email them to service@devolutions.net and we can get those linked to this forum post internally.

You can also find the log files on the server at %ProgramData%\PowerShellUniversal\Logs\System

Adam Driscoll

PowerShell Expert and Software Architect at Devolutions

A fix for this issue has been implemented in version 2026.3.0