starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

arm64 | all prompts are blank when Terminal is the default application #22862

New Issue
Closed
opened 2026-01-31 08:25:30 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:25:30 +00:00
Owner
Copy Link

Originally created by @aremmell on GitHub (Feb 7, 2025).

Windows Terminal version

1.21.10351.0

Windows build number

10.0.26100.3037

Other Software

  • PowerShell 7 (arm64) 7.5.0 | installed from GitHub release page, MSI version
  • CMD
  • Developer [Command Prompt|PowerShell] for VS 2022
  • Any other Terminal profile when Terminal is set to the default application

Steps to reproduce

Open PowerShell 7 (arm64), CMD, or just Terminal. You will be met with a screen that looks like this:

Image

I have run repair, reset, uninstall, reinstall from Store for both PowerShell and Terminal. Also tried everything on the first page from Google. Terminal was working fine last week; this seems like a regression that was applied via an automatic update.

Expected Behavior

The prompt to appear

Actual Behavior

Prompt does not appear. Ctrl+C has no effect.

Originally created by @aremmell on GitHub (Feb 7, 2025). ### Windows Terminal version 1.21.10351.0 ### Windows build number 10.0.26100.3037 ### Other Software - PowerShell 7 (arm64) 7.5.0 | _installed from GitHub release page, MSI version_ - CMD - Developer [Command Prompt|PowerShell] for VS 2022 - Any other Terminal profile when Terminal is set to the default application ### Steps to reproduce Open PowerShell 7 (arm64), CMD, or just Terminal. You will be met with a screen that looks like this: <img width="379" alt="Image" src="https://github.com/user-attachments/assets/88e896a1-dbd4-4ef4-80b2-0bf3982f23e4" /> I have run repair, reset, uninstall, reinstall from Store for both PowerShell and Terminal. Also tried everything on the first page from Google. Terminal was working fine last week; this seems like a regression that was applied via an automatic update. ### Expected Behavior The prompt to appear ### Actual Behavior Prompt does not appear. Ctrl+C has no effect.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:25:30 +00:00
claunia commented 2026-01-31 08:25:31 +00:00
Author
Owner
Copy Link

@aremmell commented on GitHub (Feb 7, 2025):

Closing this. I think it had something to do with Edge/Chromium web view controls not rendering correctly. Uninstalling/reinstalling Edge and rebooting fixed it (and Visual Studio, FWIW).

@aremmell commented on GitHub (Feb 7, 2025): Closing this. I think it had something to do with Edge/Chromium web view controls not rendering correctly. Uninstalling/reinstalling Edge and rebooting fixed it (and Visual Studio, FWIW).
claunia commented 2026-01-31 08:25:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 7, 2025):

Well that sure is weird! Terminal isn't a webview (and neither is big VS), but I'm guessing it has to do with DirectX surfaces. Glad it went away for you though!

@zadjii-msft commented on GitHub (Feb 7, 2025): Well that sure is weird! Terminal isn't a webview (and neither is big VS), but I'm guessing it has to do with DirectX surfaces. Glad it went away for you though!
claunia commented 2026-01-31 08:25:31 +00:00
Author
Owner
Copy Link

@aremmell commented on GitHub (Feb 10, 2025):

Even the VS installer UI was not rendering correctly. I also could not interact with the controls on these windows, even if I tabbed around and saw a selection rect around the selected invisible control (label/button, etc.); clicking did nothing, space bar did nothing.

It was really weird. I have never seen anything like it, and I've been devving on Windows since it used to BSOD every few hours (> 25 years 🙅)

@aremmell commented on GitHub (Feb 10, 2025): Even the VS installer UI was not rendering correctly. I also could not interact with the controls on these windows, even if I tabbed around and saw a selection rect around the selected invisible control (label/button, etc.); clicking did nothing, space bar did nothing. It was _really weird_. I have never seen anything like it, and I've been devving on Windows since it used to BSOD every few hours (> 25 years 🙅)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22862
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?