Since the last version, I've been having problems with the icons, some of which look ghostly. #23405

Closed
opened 2026-01-31 08:41:15 +00:00 by claunia · 6 comments
Owner

Originally created by @joseanoxp on GitHub (Jun 30, 2025).

Windows Terminal version

1.22.11751.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

  1. I click on open terminal in Win + X run terminal as administrator
  2. When opening some icons are no longer visible and even resetting the icon does not allow saving
  3. This message always appears when opening Windows Terminal in its stable version

Image

https://github.com/user-attachments/assets/4b856206-3b6d-4a7d-9292-35d0e032a1b5

Expected Behavior

No response

Actual Behavior

I hope that when I open this it works properly and these bugs disappear

Originally created by @joseanoxp on GitHub (Jun 30, 2025). ### Windows Terminal version 1.22.11751.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce 1. I click on open terminal in Win + X run terminal as administrator 2. When opening some icons are no longer visible and even resetting the icon does not allow saving 3. This message always appears when opening Windows Terminal in its stable version ![Image](https://github.com/user-attachments/assets/cfe59f27-2dc5-4007-aeaf-584fc4b2bf3f) https://github.com/user-attachments/assets/4b856206-3b6d-4a7d-9292-35d0e032a1b5 ### Expected Behavior _No response_ ### Actual Behavior I hope that when I open this it works properly and these bugs disappear
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:41:15 +00:00
Author
Owner

@DHowett commented on GitHub (Jul 2, 2025):

Thanks for the report! This change was made intentionally, to reduce the leakage of information to uncontrolled websites. We're tracking user concerns over in /dup #19075.

@DHowett commented on GitHub (Jul 2, 2025): Thanks for the report! This change was made intentionally, to reduce the leakage of information to uncontrolled websites. We're tracking user concerns over in /dup #19075.
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Jul 2, 2025):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Jul 2, 2025): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Author
Owner

@Frulfump commented on GitHub (Jul 9, 2025):

@DHowett Shouldn't the bot close the issue as duplicate and not completed?

@Frulfump commented on GitHub (Jul 9, 2025): @DHowett Shouldn't the bot close the issue as duplicate and not completed?
Author
Owner

@DHowett commented on GitHub (Jul 9, 2025):

@frulfump alas, the bot was authored1 before GitHub had support for the different types of issue closure. I'm not sure it's even actively maintained.


  1. EDIT: oh, not by us. ↩︎

@DHowett commented on GitHub (Jul 9, 2025): @frulfump alas, the bot was authored[^1] before GitHub had support for the different types of issue closure. I'm not sure it's even actively maintained. [^1]: EDIT: oh, not by us.
Author
Owner

@Frulfump commented on GitHub (Jul 9, 2025):

Oh can you get someone to update it or use another one? Makes it much harder to understand what's happening in the repo.

@Frulfump commented on GitHub (Jul 9, 2025): Oh can you get someone to update it or use another one? Makes it much harder to understand what's happening in the repo.
Author
Owner

@Frulfump commented on GitHub (Jul 10, 2025):

Created an issue https://github.com/microsoft1estools/.github/issues/23 not sure if that's actually watched but at least it's an attempt at getting it changed.

@Frulfump commented on GitHub (Jul 10, 2025): Created an issue https://github.com/microsoft1estools/.github/issues/23 not sure if that's actually watched but at least it's an attempt at getting it changed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23405