VSCode updates are slow since upgrading to 2026.2.2

@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.

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?

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

Scripts: 142
Schedules: 50
Endpoints: 27
Apps: 18
Terminals: 3

I couldn't find the log files in ProgramData path, I found some in ..Logs\PowerShellHost
For the past two weeks or so, they all look similar to this:
FileName:
host-5828-134309547103450186.txt

Contents:
2026-08-11 16:45:10.443 -04:00 [ERR] PSUModulePath not set

Are those the correct log files or are you looking for something else?

The system logs would likely be what we need since they will include the resource reload sections. The logs could be in:

%ProgramData%\PowerShellUniversal\systemLog<date>.txt

You can check in Help -> Support Tools -> Configuration or Environment Variables to see the configured SystemLogPath value to see where it would write the logs.

Thanks, Adam!

I think we have something misconfigured because we don't have any systemLog<Date>.txt files since 2024.
But, I didn't see any configuration to change that.
All we have is this:
SystemLogLevel=Error (JsonConfigurationProvider for 'appsettings.json' (Optional))
SystemLogPath=%ProgramData%\PowerShellUniversal\ (JsonConfigurationProvider for 'appsettings.json' (Optional))


I did find logs that are just log<date>.txt that I think are what you're needing and just emailed those in for the last few days.