How to Fix VS Code Terminal Slow or Lagging on Windows

What Causes This?

A slow or lagging terminal in VS Code usually comes from one of three places: the shell you’re running, the terminal renderer, or high system load in Windows. PowerShell profiles, shell startup scripts, heavy extensions, and GPU rendering issues can all delay input, scrolling, or command output. In some cases, antivirus scanning, low memory, or a stuck background process makes the integrated terminal feel much slower than a normal Command Prompt window.

Common Symptoms

• Typing in the VS Code terminal feels delayed or skips characters
• Terminal output scrolls slowly or stutters
• A new terminal takes several seconds to open
• PowerShell, Git Bash, or WSL starts much slower in VS Code than outside it
• VS Code becomes sluggish only when the integrated terminal is open

How to Fix It Manually

1. Check whether the problem is VS Code-specific

   1. Press Win + R, type cmd, and press Enter.
   2. Open Command Prompt or PowerShell outside VS Code and test basic commands like dir or git status.
   3. If the shell is also slow outside VS Code, the issue is likely with the shell, Windows, or system performance rather than VS Code itself.

2. Switch the terminal profile in VS Code

   1. Open VS Code.
   2. Press Ctrl + Shift + P, type Terminal: Select Default Profile, and press Enter.
   3. Choose another shell such as Command Prompt if you normally use PowerShell, or vice versa.
   4. Open a new terminal with `Ctrl + Shift + `` and test responsiveness.
   5. If one shell is much faster, the original shell may have a slow startup script or profile.

3. Disable GPU terminal rendering

   1. In VS Code, press Ctrl + Shift + P and open Preferences: Open Settings (UI).
   2. Search for gpu acceleration.
   3. Set Terminal › Integrated: GPU Acceleration to Off.
   4. Close and reopen VS Code, then test the terminal again.
   5. This often fixes laggy scrolling, delayed text rendering, or flickering caused by graphics driver issues.

4. Start VS Code without extensions

   1. Close VS Code.
   2. Press Win + R, type:

      code --disable-extensions

      and press Enter.
   3. Open the terminal and test it.
   4. If the terminal is faster, an extension is likely interfering. Re-enable extensions one at a time in VS Code under Extensions (Ctrl + Shift + X) until you find the cause.

5. Check Windows resource usage

   1. Open Task Manager with Ctrl + Shift + Esc.
   2. On the Processes tab, look for high CPU, Memory, or Disk usage from VS Code, PowerShell, antivirus, or background apps.
   3. End any clearly stuck non-essential task, then reopen VS Code.
   4. If memory is nearly full, close other heavy apps like browsers, game launchers, or virtual machines.

6. Test for a slow PowerShell profile

   1. If you use PowerShell, open it outside VS Code.
   2. Run:

      powershell -NoProfile

   3. If that opens much faster, your PowerShell profile is slowing startup.
   4. You can temporarily use a no-profile shell in VS Code or review your PowerShell profile scripts for slow modules, prompts, or network-based commands.

7. Update VS Code and graphics drivers

   1. In VS Code, go to Help > Check for Updates.
   2. In Windows, right-click Start and open Device Manager.
   3. Expand Display adapters, right-click your graphics device, and choose Update driver.
   4. Restart your PC after updates to clear stuck processes and reload drivers.

Fix It Automatically with Kudu

Kudu can automatically check for the common Windows issues behind a slow VS Code terminal, including overloaded startup apps, background processes, and system settings that hurt responsiveness. Instead of digging through Task Manager, shell configs, and Windows performance settings manually, Kudu helps identify and fix the slowdown faster.

Download Kudu Free →