terminal icon indicating copy to clipboard operation
terminal copied to clipboard

Two Terminal will be opened simutaneously when open WT, one of which is totally transparent while another is an old version CMD terminal.

Open BugBubbles opened this issue 10 months ago • 3 comments

Windows Terminal version

1.22.2503.14001

Windows build number

Windows 11 24H2 26100.3775

Other Software

No response

Steps to reproduce

Just open "Windows Terminal" in user mode, then there will be two terminal windows on desktop. The one on the bottom is totally transparent and cannot click any botton on it. The other on the front is an old version of Windows CMD terminal. Windows Event Viewer record coresponding ERROR like below:

Log Name: Application Source: Application Error Date: 2025/4/24 17:08:52 Event ID: 1000 Task Category: Application Crash Level: Error Keyword: User: ************ Computer: ********** Description.

Faulty application name: WindowsTerminal.exe, version: 1.22.2503.14001, timestamp: 0x67d4a8f9 Faulty module name: MSVCR90.dll, version: 9.0.30729.9635, timestamp: 0x6090b7af Exception Code: 0xc0000005 Error Offset: 0x0000000000019353 Faulty Process ID: 0xBA54 Faulty Application Start Time: 0x1DBB4F87F27FD68 Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.10731.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting ModulePath: C:\WINDOWS\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9635_none_08e2c157a83ed5da\MSVCR90.dll Report ID: 14473d03-afcc-45f1-a325-fa6d0223b539 Faulting Package Full Name: Microsoft.WindowsTerminal_1.22.10731.0_x64__8wekyb3d8bbwe Faulting Package RatiosApplication ID: App individual Event Xml. <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-04-24T09:08:52.2390466Z" /> <EventRecordID>27849</EventRecordID> <Correlation /> <Execution ProcessID="35796" ThreadID="50480" /> <Channel>Application</Channel> <Computer>DESKTOP-******</Computer> <Security UserID="S-1-5-21-194957425-2785942792-3603075891-1002" /> </System> <EventData> <Data Name="AppName">WindowsTerminal.exe</Data> <Data Name="AppVersion">1.22.2503.14001</Data> <Data Name="AppTimeStamp">67d4a8f9</Data> <Data Name="ModuleName">MSVCR90.dll</Data> <Data Name="ModuleVersion">9.0.30729.9635</Data> <Data Name="ModuleTimeStamp">6090b7af</Data> <Data Name="ExceptionCode">c0000005</Data> <Data Name="FaultingOffset">0000000000019353</Data> <Data Name="ProcessId">0xba54</Data> <Data Name="ProcessCreationTime">0x1dbb4f87f27fd68</Data> <Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.10731.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data Name="ModulePath">C:\WINDOWS\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9635_none_08e2c157a83ed5da\MSVCR90.dll</Data> <Data Name="IntegratorReportId">14473d03-afcc-45f1-a325-fa6d0223b539</Data> <Data Name="PackageFullName">Microsoft.WindowsTerminal_1.22.10731.0_x64__8wekyb3d8bbwe</Data> <Data Name="PackageRelativeAppId">App</Data> </EventData> </Event>

Expected Behavior

No response

Actual Behavior

The bug state is like below: Image However when I use administrator mode to open WT, everything goes ok.

Image

BugBubbles avatar Apr 24 '25 09:04 BugBubbles

Several discussion about the same BUG can be browsed from here

BugBubbles avatar Apr 24 '25 09:04 BugBubbles

Faulty module name: MSVCR90.dll, version: 9.0.30729.9635, timestamp: 0x6090b7af

I believe you are using a piece of software called SyncDisk.

SyncDisk is attaching to all applications and in some of them it causes crashes.

DHowett avatar Apr 24 '25 23:04 DHowett

Thanks for your reply! I just check out my softwares however I have not installed this SyncDisk software. When I open WT and check my TaskManager, there is not a SyncDisk program running in backend. Then I try to uninstall a similar software called BaiduSyncDisk and that also does not work. The log is nearly the same as above.

BugBubbles avatar Apr 27 '25 02:04 BugBubbles

Thanks! I solve my problem which was really triggered by a SyncDisk program. After removing it from C disk, this problem was gone and I reinstalled it in D disk. Thanks for your patient help!

BugBubbles avatar May 15 '25 12:05 BugBubbles