Random text glitches when using WSL1 #8066

Closed
opened 2026-01-31 01:19:53 +00:00 by claunia · 3 comments
Owner

Originally created by @BitTheByte on GitHub (May 11, 2020).

Environment

Windows build number: Version 10.0.19041.207
Windows Terminal version (if applicable): Version: 0.11.1251.0
GPU0: Intel UHD Graphics 630 | Driver: 26.20.100.7637
GPU1: Nivida GTX 1060 6GB | Driver: 445.87

Steps to reproduce

  1. Open a new tab with "Ubuntu" on WSL1
  2. Type any command e.g(ls)
  3. Wait for 2 or 3 seconds

Behavior

The text starts to break and glitch out. I've had this problem before with VS CODE and was fixed by disabling GPU acceleration

Originally created by @BitTheByte on GitHub (May 11, 2020). # Environment ```none Windows build number: Version 10.0.19041.207 Windows Terminal version (if applicable): Version: 0.11.1251.0 GPU0: Intel UHD Graphics 630 | Driver: 26.20.100.7637 GPU1: Nivida GTX 1060 6GB | Driver: 445.87 ``` # Steps to reproduce 1) Open a new tab with "Ubuntu" on WSL1 2) Type any command e.g(ls) 3) Wait for 2 or 3 seconds # Behavior The text starts to break and glitch out. I've had this problem before with VS CODE and was fixed by disabling GPU acceleration ![](https://i.ibb.co/tBXsrWc/image.png)
claunia added the Resolution-Duplicate label 2026-01-31 01:19:53 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (May 11, 2020):

Thanks for the report! This looks like a /dupe of #5759.

Do you have "Conservative Morphological Anti-Aliasing" turned on in the Intel driver settings?

@DHowett-MSFT commented on GitHub (May 11, 2020): Thanks for the report! This looks like a /dupe of #5759. Do you have "Conservative Morphological Anti-Aliasing" turned on in the Intel driver settings?
Author
Owner

@ghost commented on GitHub (May 11, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (May 11, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Author
Owner

@BitTheByte commented on GitHub (May 11, 2020):

Thanks @DHowett-MSFT for the fast response. this was actually fixed by disabling Image sharpening at Nivida control panel

@BitTheByte commented on GitHub (May 11, 2020): Thanks @DHowett-MSFT for the fast response. this was actually fixed by disabling `Image sharpening` at Nivida control panel
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8066