Windows Terminal no longer starts #23735

@tabris17 commented on GitHub (Oct 20, 2025):

Same issue. I’m sure it was caused by the latest Windows update.

@tabris17 commented on GitHub (Oct 20, 2025): Same issue. I’m sure it was caused by the latest Windows update.

claunia commented

@MonolithOrchids commented on GitHub (Oct 20, 2025):

Same issue as well.
Portable version, Windows 10. Preview version works fine.

@MonolithOrchids commented on GitHub (Oct 20, 2025): Same issue as well. Portable version, Windows 10. Preview version works fine.

claunia commented

@devenrgy commented on GitHub (Oct 21, 2025):

The same goes for Windows 10 with the latest updates

@devenrgy commented on GitHub (Oct 21, 2025): The same goes for Windows 10 with the latest updates

claunia commented

@pot-code commented on GitHub (Oct 21, 2025):

Portable version 1.20-1.23 are doomed. Terminal preview works fine though

@pot-code commented on GitHub (Oct 21, 2025): Portable version 1.20-1.23 are doomed. Terminal preview works fine though

claunia commented

@nagromc commented on GitHub (Oct 21, 2025):

Same behaviour here.

Windows Terminal version

1.23.12811.0

Windows build number

10.0.19044.0

Additional information

Installed with scoop install windows-terminal
No problem with Windows Terminal Preview v1.24.2812.0 (scoop install windows-terminal-preview)
Same behaviour with the three latest versions (scoop install windows-terminal@1.23.12681.0, scoop install windows-terminal@1.23.12371.0, scoop install windows-terminal@1.22.12111.0). This might be caused by an update of Windows as others said.

@nagromc commented on GitHub (Oct 21, 2025): Same behaviour here. ### Windows Terminal version 1.23.12811.0 ### Windows build number 10.0.19044.0 ### Additional information * Installed with `scoop install windows-terminal` * No problem with Windows Terminal Preview v1.24.2812.0 (`scoop install windows-terminal-preview`) * Same behaviour with the three latest versions (`scoop install windows-terminal@1.23.12681.0`, `scoop install windows-terminal@1.23.12371.0`, `scoop install windows-terminal@1.22.12111.0`). This might be caused by an update of Windows as others said.

claunia commented

@dashque commented on GitHub (Oct 21, 2025):

The latest Windows update appears to have caused significant issues with the Terminal application. It's currently non-functional on my Windows 10 system. This is highly disruptive to my workflow. Please address this critical issue promptly.

@dashque commented on GitHub (Oct 21, 2025): The latest Windows update appears to have caused significant issues with the Terminal application. It's currently non-functional on my Windows 10 system. This is highly disruptive to my workflow. Please address this critical issue promptly.

claunia commented

@serpentx commented on GitHub (Oct 22, 2025):

Same problem, Windows 11 Enterprise, 26100.6899

@serpentx commented on GitHub (Oct 22, 2025): Same problem, Windows 11 Enterprise, 26100.6899

claunia commented

https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

@DHowett commented on GitHub (Oct 22, 2025):

Can one or more of you please enable automatic dump collection and send us .dmp files? We haven't been able to reproduce this here on our side. Sorry >_<

@DHowett commented on GitHub (Oct 22, 2025): Can one or more of you please enable automatic dump collection and send us .dmp files? We haven't been able to reproduce this here on our side. Sorry >_< https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

claunia commented

@DHowett commented on GitHub (Oct 22, 2025):

You can send the dumps to my @microsoft.com e-mail address, which is available on my GitHub profile.

@DHowett commented on GitHub (Oct 22, 2025): You can send the dumps to my `@microsoft.com` e-mail address, which is available on my GitHub profile.

claunia commented

2026-01-31 08:50:50 +00:00

@MonolithOrchids commented on GitHub (Oct 22, 2025):

You can send the dumps to my @microsoft.com e-mail address, which is available on my GitHub profile.

Sent, subject:
"Windows Terminal no longer starts DMP"

It's a Onedrive link since the file is over 300mb lol

@MonolithOrchids commented on GitHub (Oct 22, 2025): > You can send the dumps to my `@microsoft.com` e-mail address, which is available on my GitHub profile. Sent, subject: "Windows Terminal no longer starts DMP" It's a Onedrive link since the file is over 300mb lol

claunia commented

@serpentx commented on GitHub (Oct 22, 2025):

I have also sent a OneDrive link because of the file size

@serpentx commented on GitHub (Oct 22, 2025): I have also sent a OneDrive link because of the file size

claunia commented

2026-01-31 08:50:50 +00:00

@DHowett commented on GitHub (Oct 23, 2025):

Thanks so much! Kinda a good news bad news situation.

Good news: You're both hitting the same issue, and I found an internal crash reporting bucket that points to the same issue.

Bad news: It's failing to load a control out of the XAML controls library, which we haven't changed in three years. So that's really quite alarming... and we're not any closer now to solving it.

@DHowett commented on GitHub (Oct 23, 2025): Thanks so much! Kinda a good news bad news situation. Good news: You're both hitting the same issue, and I found an internal crash reporting bucket that points to the same issue. Bad news: It's failing to load a control out of the XAML controls library, _which we haven't changed in three years._ So that's really quite alarming... and we're not any closer now to solving it.

claunia commented

2026-01-31 08:50:51 +00:00

@MonolithOrchids commented on GitHub (Oct 23, 2025):

Thanks for the feedback.
We are running WT Preview version without any issues (well, I am at least), we're bound to face the same problem in the future or at least here we're safe?

@MonolithOrchids commented on GitHub (Oct 23, 2025): Thanks for the feedback. We are running WT Preview version without any issues (well, I am at least), we're bound to face the same problem in the future or at least here we're safe?

claunia commented

2026-01-31 08:50:51 +00:00

@serpentx commented on GitHub (Oct 23, 2025):

Preview is also working fine for me. Thanks for the info

@serpentx commented on GitHub (Oct 23, 2025): Preview is also working fine for me. Thanks for the info

claunia commented

2026-01-31 08:50:52 +00:00

@SebastianNiehaus commented on GitHub (Oct 23, 2025):

I started running into the same problem, but noticed when i choose the "open tab with default profile" on the "when terminal starts" setting, it works fine again.
Is it the same for you guys?

@SebastianNiehaus commented on GitHub (Oct 23, 2025): I started running into the same problem, but noticed when i choose the "open tab with default profile" on the "when terminal starts" setting, it works fine again. Is it the same for you guys?

claunia commented

2026-01-31 08:50:52 +00:00

@Flower101010 commented on GitHub (Oct 23, 2025):

I started running into the same problem, but noticed when i choose the "open tab with default profile" on the "when terminal starts" setting, it works fine again.
Is it the same for you guys?

Unfortunately, that's not the case for me. It seems we might be running into different issues.

@Flower101010 commented on GitHub (Oct 23, 2025): > I started running into the same problem, but noticed when i choose the "open tab with default profile" on the "when terminal starts" setting, it works fine again. > Is it the same for you guys? Unfortunately, that's not the case for me. It seems we might be running into different issues.

claunia commented

2026-01-31 08:50:53 +00:00

@MonolithOrchids commented on GitHub (Oct 23, 2025):

I started running into the same problem, but noticed when i choose the "open tab with default profile" on the "when terminal starts" setting, it works fine again. Is it the same for you guys?

No, it doesn't even open here, your problem is different from ours.

@MonolithOrchids commented on GitHub (Oct 23, 2025): > I started running into the same problem, but noticed when i choose the "open tab with default profile" on the "when terminal starts" setting, it works fine again. Is it the same for you guys? No, it doesn't even open here, your problem is different from ours.

claunia commented

2026-01-31 08:50:54 +00:00

@DHowett commented on GitHub (Oct 23, 2025):

Wait... do any of you have PowerToys, and have you updated to 0.95?

@DHowett commented on GitHub (Oct 23, 2025): Wait... do any of you have PowerToys, and have you updated to 0.95?

claunia commented

2026-01-31 08:50:54 +00:00

@SebastianNiehaus commented on GitHub (Oct 23, 2025):

i have

@SebastianNiehaus commented on GitHub (Oct 23, 2025): i have

claunia commented

2026-01-31 08:50:54 +00:00

@MonolithOrchids commented on GitHub (Oct 23, 2025):

Yes, I do have PowerToys and WT did stopped working at same week of the 0.95 update. I even suspected it was PowerToys, so I closed it before running it but still didn't worked so I didn't think it was this.

@MonolithOrchids commented on GitHub (Oct 23, 2025): Yes, I do have PowerToys and WT did stopped working at same week of the 0.95 update. I even suspected it was PowerToys, so I closed it before running it but still didn't worked so I didn't think it was this.

claunia commented

2026-01-31 08:50:55 +00:00

@DHowett commented on GitHub (Oct 23, 2025):

!!!

Okay, so the working theory is that PowerToys comes with a copy of Microsoft.UI.Xaml.dll and as of 0.95 puts it on the PATH. This predictably explodes anything that needs XAML, even when PT is not running.

Credit to @katewang-js from #19492, who figured this out.

Can you try removing PowerToys from your PATH and relaunching Terminal?

@DHowett commented on GitHub (Oct 23, 2025): !!! Okay, so the working theory is that PowerToys comes with a copy of Microsoft.UI.Xaml.dll _and as of 0.95 puts it on the PATH._ This predictably explodes anything that needs XAML, even when PT is not running. Credit to @katewang-js from #19492, who figured this out. Can you try removing PowerToys from your PATH and relaunching Terminal?

claunia commented

2026-01-31 08:50:55 +00:00

@MonolithOrchids commented on GitHub (Oct 23, 2025):

It worked, thanks.

@MonolithOrchids commented on GitHub (Oct 23, 2025): It worked, thanks.

claunia commented

2026-01-31 08:50:55 +00:00

@Flower101010 commented on GitHub (Oct 23, 2025):

!!!

I removed PowerToys from my PATH and Terminal worked fine.

Thanks

@Flower101010 commented on GitHub (Oct 23, 2025): !!! I removed PowerToys from my PATH and Terminal worked fine. Thanks

claunia commented

2026-01-31 08:50:56 +00:00

@devenrgy commented on GitHub (Oct 23, 2025):

Thanks, it's working. Bad Power Toys 😁

@devenrgy commented on GitHub (Oct 23, 2025): Thanks, it's working. Bad Power Toys 😁

claunia commented

2026-01-31 08:50:56 +00:00

@Chris-Dickerson commented on GitHub (Oct 23, 2025):

!!!

Okay, so the working theory is that PowerToys comes with a copy of Microsoft.UI.Xaml.dll and as of 0.95 puts it on the PATH. This predictably explodes anything that needs XAML, even when PT is not running.

Credit to @KateWang-js from #19492, who figured this out.

Can you try removing PowerToys from your PATH and relaunching Terminal?

Acknowledged - removed PowerToys path and now Terminal works. 👍

@Chris-Dickerson commented on GitHub (Oct 23, 2025): > !!! > > Okay, so the working theory is that PowerToys comes with a copy of Microsoft.UI.Xaml.dll _and as of 0.95 puts it on the PATH._ This predictably explodes anything that needs XAML, even when PT is not running. > > Credit to [@KateWang-js](https://github.com/KateWang-js) from [#19492](https://github.com/microsoft/terminal/issues/19492), who figured this out. > > Can you try removing PowerToys from your PATH and relaunching Terminal? Acknowledged - removed PowerToys path and now Terminal works. 👍

claunia commented

2026-01-31 08:50:56 +00:00

@DHowett commented on GitHub (Oct 23, 2025):

Copying notes from 19492

Windows Terminal version

1.23.12811.0

Windows build number

10.0.22631

Other Software

PowerToys 0.95.0

Steps to reproduce

(We used our own Nuget package to install Windows Terminal, but nothing too special other than we put the WindowsTerminal.exe and all the other files in C:\Program Files\WindowsTerminal ) WT always working fine unless we updated PowerToys to 0.95.0 from 0.94.2. Since PowerToys 0.95.0, WT failed to launch with below error (Application event log with error 1000): Faulting application name: WindowsTerminal.exe, version: 1.23.2510.8001, time stamp: 0x68e7198d Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.5983, time stamp: 0xe081eb6a Exception code: 0xc000027b Fault offset: 0x0000000000875470 Faulting process id: 0x0x6460 Faulting application start time: 0x0x1DC43DC358EF426 Faulting application path: C:\Program Files\WindowsTerminal\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: e91910e1-59bc-40bc-9502-1742d6828da9 Faulting package full name: Faulting package-relative application ID:_

We captured process monitor trace while PowerToys 0.95.0 is installed. Found it failed because WT loaded C:\Program Files\PowerToys\Microsoft.UI.Xaml.Controls.dll, which caused C:\Windows\System32\Windows.UI.Xaml.dll crash. (Added process monitor trace) In our system environmental path ($env:path), we found "C:\Program Files\PowerToys".
We captured process monitor trace while PowerToys 0.94.2 is installed. Found it also tried to load Microsoft.UI.Xaml.xx but nothing was found from the other Apps' folder , so finally WT loaded C:\Program Files\WindowsTerminal\Microsoft.UI.Xaml.dll and it does not crash. (Added process monitor trace) In our system environmental path ($env:path), we do not find "C:\Program Files\PowerToys". ### Expected Behavior Windows Terminal launch successfully.
Actual Behavior

WIndowsTerminal.exe failed to launch with below error (Application event log with error 1000): Faulting application name: WindowsTerminal.exe, version: 1.23.2510.8001, time stamp: 0x68e7198d Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.5983, time stamp: 0xe081eb6a Exception code: 0xc000027b Fault offset: 0x0000000000875470 Faulting process id: 0x0x6460 Faulting application start time: 0x0x1DC43DC358EF426 Faulting application path: C:\Program Files\WindowsTerminal\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: e91910e1-59bc-40bc-9502-1742d6828da9 Faulting package full name: Faulting package-relative application ID:_

@DHowett commented on GitHub (Oct 23, 2025): Copying notes from 19492 > ### Windows Terminal version > 1.23.12811.0 > > ### Windows build number > 10.0.22631 > > ### Other Software > PowerToys 0.95.0 > > ### Steps to reproduce > (We used our own Nuget package to install Windows Terminal, but nothing too special other than we put the WindowsTerminal.exe and all the other files in C:\Program Files\WindowsTerminal ) WT always working fine unless we updated PowerToys to 0.95.0 from 0.94.2. Since PowerToys 0.95.0, WT failed to launch with below error (Application event log with error 1000): _Faulting application name: WindowsTerminal.exe, version: 1.23.2510.8001, time stamp: 0x68e7198d Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.5983, time stamp: 0xe081eb6a Exception code: 0xc000027b Fault offset: 0x0000000000875470 Faulting process id: 0x0x6460 Faulting application start time: 0x0x1DC43DC358EF426 Faulting application path: C:\Program Files\WindowsTerminal\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: e91910e1-59bc-40bc-9502-1742d6828da9 Faulting package full name: Faulting package-relative application ID:__ > > We captured process monitor trace while PowerToys 0.95.0 is installed. Found it failed because WT loaded _C:\Program Files\PowerToys\Microsoft.UI.Xaml.Controls.dll_, which caused _C:\Windows\System32\Windows.UI.Xaml.dll_ crash. (Added process monitor trace) In our system environmental path ($env:path), we found "C:\Program Files\PowerToys". > > <img alt="Image" width="2000" height="1881" src="https://private-user-images.githubusercontent.com/221918049/504571868-f7b9875d-5e7f-4fba-84a7-cb1fad5b5176.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjEyMzc5MjQsIm5iZiI6MTc2MTIzNzYyNCwicGF0aCI6Ii8yMjE5MTgwNDkvNTA0NTcxODY4LWY3Yjk4NzVkLTVlN2YtNGZiYS04NGE3LWNiMWZhZDViNTE3Ni5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMDIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTAyM1QxNjQwMjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02M2YwZjE5ZmEyOWQ3YzQxOGEyZWE1YjE2ZjQxNGNiMDhjNGE4NjhiZTVmMmY5MzU2YjIyZTYwZmE3MzgxZDEyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.SAWLW8cjLjKsbWl0GRPi5y_YTjGooaabNFoqax_Arcs"> > We captured process monitor trace while PowerToys 0.94.2 is installed. Found it also tried to load Microsoft.UI.Xaml.xx but nothing was found from the other Apps' folder , so finally WT loaded C:\Program Files\WindowsTerminal\Microsoft.UI.Xaml.dll and it does not crash. (Added process monitor trace) In our system environmental path ($env:path), we do not find "C:\Program Files\PowerToys". > > <img alt="Image" width="2000" height="688" src="https://private-user-images.githubusercontent.com/221918049/504572685-28dfcffc-6c20-4268-b456-05f422b59715.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjEyMzc5MjQsIm5iZiI6MTc2MTIzNzYyNCwicGF0aCI6Ii8yMjE5MTgwNDkvNTA0NTcyNjg1LTI4ZGZjZmZjLTZjMjAtNDI2OC1iNDU2LTA1ZjQyMmI1OTcxNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMDIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTAyM1QxNjQwMjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iODUzOWNhOGNlNDAzYzRhOWY4MDI5YjJmN2U0MmI3Y2Q5N2I1ZGQ5MzJmN2JkM2U0NjY0ZGFlMDkxNGJhZjg1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.5kAXFFOg64ERAMfHzw6Tb-UNni7e4oRGtcqJVsmjaR8"> > ### Expected Behavior > Windows Terminal launch successfully. > > ### Actual Behavior > WIndowsTerminal.exe failed to launch with below error (Application event log with error 1000): _Faulting application name: WindowsTerminal.exe, version: 1.23.2510.8001, time stamp: 0x68e7198d Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.5983, time stamp: 0xe081eb6a Exception code: 0xc000027b Fault offset: 0x0000000000875470 Faulting process id: 0x0x6460 Faulting application start time: 0x0x1DC43DC358EF426 Faulting application path: C:\Program Files\WindowsTerminal\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: e91910e1-59bc-40bc-9502-1742d6828da9 Faulting package full name: Faulting package-relative application ID:__

claunia commented

@serpentx commented on GitHub (Oct 23, 2025):

I can confirm, after removing PowerToys from my PATH, Windows Terminal v1.2.3.12811.0 is working fine again. Thanks everyone!

@serpentx commented on GitHub (Oct 23, 2025): I can confirm, after removing PowerToys from my PATH, Windows Terminal v1.2.3.12811.0 is working fine again. Thanks everyone!

claunia commented

@stderr-to-devnull commented on GitHub (Oct 23, 2025):

@DHowett I also confirm that modifying the PowerToys entry in PATH (I just added an s at the end so I can recover it more easily once it's fixed) fixes the issue.

@stderr-to-devnull commented on GitHub (Oct 23, 2025): @DHowett I also confirm that modifying the PowerToys entry in PATH (I just added an `s` at the end so I can recover it more easily once it's fixed) fixes the issue.

claunia commented

@MonolithOrchids commented on GitHub (Oct 24, 2025):

Just to let everyone know, at PT v0.95.1 update, it auto add again to the PATH.

@MonolithOrchids commented on GitHub (Oct 24, 2025): Just to let everyone know, at PT v0.95.1 update, it auto add again to the PATH.

claunia commented

@KateWang-js commented on GitHub (Oct 24, 2025):

Is there any negative impact if we remove PT from PATH?

@KateWang-js commented on GitHub (Oct 24, 2025): Is there any negative impact if we remove PT from PATH?

claunia commented

@MonolithOrchids commented on GitHub (Oct 24, 2025):

I only use PT for the FancyZones and Workspaces apps and I can't see any problem.

@MonolithOrchids commented on GitHub (Oct 24, 2025): I only use PT for the FancyZones and Workspaces apps and I can't see any problem.

claunia commented

@pot-code commented on GitHub (Oct 24, 2025):

@DHowett removing PT from System Path works for me

@pot-code commented on GitHub (Oct 24, 2025): @DHowett removing PT from System Path works for me

claunia commented

@ivanrododendro commented on GitHub (Nov 19, 2025):

Hi there,
is this fixed in 0.96.0?

@ivanrododendro commented on GitHub (Nov 19, 2025): Hi there, is this fixed in 0.96.0?

claunia commented