Crash while pasting text into terminal window #18926

Open
opened 2026-01-31 06:28:39 +00:00 by claunia · 0 comments
Owner

Originally created by @tolache on GitHub (Nov 19, 2022).

Windows Terminal version

1.15.2210.14005

Windows build number

10.0.22621

Other Software

No response

Steps to reproduce

  1. Paste any text into a terminal Window (Ctrl+V or right click).

Expected Behavior

Text pastes. Terminal doesn't crash.

Actual Behavior

Terminal crashes. Event 1000 from Application Error is logged:

Faulting application name: WindowsTerminal.exe, version: 1.15.2210.14005, time stamp: 0x6349fd20
Faulting module name: windows.applicationmodel.datatransfer.dll, version: 10.0.22621.1, time stamp: 0xd1b91d78
Exception code: 0xc0000005
Fault offset: 0x0000000000065009
Faulting process id: 0x0x3DC4
Faulting application start time: 0x0x1D8F8E77C39BCAB
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2875.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\windows.applicationmodel.datatransfer.dll
Report Id: 536af586-d6e2-4e58-a5c8-5bcf020c20b9
Faulting package full name: Microsoft.WindowsTerminal_1.15.2875.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Also Event 1026 from .NET Runtime is logged:

Application: pwsh.exe
CoreCLR Version: 7.0.22.51805
.NET Version: 7.0.0
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException: Cannot read keys when either application does not have a console or when console input has been redirected. Try Console.Read.
   at System.ConsolePal.ReadKey(Boolean intercept)
   at Microsoft.PowerShell.Internal.VirtualTerminal.ReadKey()
   at Microsoft.PowerShell.PSConsoleReadLine.ReadOneOrMoreKeys()
   at Microsoft.PowerShell.PSConsoleReadLine.ReadKeyThreadProc()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

Restarting OS fixes it.

Originally created by @tolache on GitHub (Nov 19, 2022). ### Windows Terminal version 1.15.2210.14005 ### Windows build number 10.0.22621 ### Other Software _No response_ ### Steps to reproduce 1. Paste any text into a terminal Window (`Ctrl`+`V` or right click). ### Expected Behavior Text pastes. Terminal doesn't crash. ### Actual Behavior Terminal crashes. Event 1000 from Application Error is logged: ``` Faulting application name: WindowsTerminal.exe, version: 1.15.2210.14005, time stamp: 0x6349fd20 Faulting module name: windows.applicationmodel.datatransfer.dll, version: 10.0.22621.1, time stamp: 0xd1b91d78 Exception code: 0xc0000005 Fault offset: 0x0000000000065009 Faulting process id: 0x0x3DC4 Faulting application start time: 0x0x1D8F8E77C39BCAB Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2875.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\windows.applicationmodel.datatransfer.dll Report Id: 536af586-d6e2-4e58-a5c8-5bcf020c20b9 Faulting package full name: Microsoft.WindowsTerminal_1.15.2875.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` Also Event 1026 from .NET Runtime is logged: ``` Application: pwsh.exe CoreCLR Version: 7.0.22.51805 .NET Version: 7.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException: Cannot read keys when either application does not have a console or when console input has been redirected. Try Console.Read. at System.ConsolePal.ReadKey(Boolean intercept) at Microsoft.PowerShell.Internal.VirtualTerminal.ReadKey() at Microsoft.PowerShell.PSConsoleReadLine.ReadOneOrMoreKeys() at Microsoft.PowerShell.PSConsoleReadLine.ReadKeyThreadProc() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) ``` Restarting OS fixes it.
claunia added the Needs-TriageIssue-BugNeeds-Author-Feedback labels 2026-01-31 06:28:39 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18926