Re: AI Textconv filter misconfiguration on Windows leads to silent corruption of diff output (ongoing investigation)

(I am not yet done with you mtf-ers):

I feed the crash log into Co-Pilot/AI, it knows about it:

The short answer: **your crash codes indicate an *access‑violation* inside Windows Terminal’s rendering/control DLL**, and the specific signature you posted matches a **known Windows Terminal bug** that occurs during **tab drag‑merge operations**, often when scrollback buffers are large.

---

## 🧩 What the codes mean (direct interpretation)

- **Faulting application:** WindowsTerminal.exe  
- **Faulting module:** Microsoft.Terminal.Control.dll  
- **Exception code:** **0xc0000005** → **Access violation** (invalid memory read/write)   [cloudspress.com](https://www.cloudspress.com/how-to-fix-error-code-0xc0000005-on-windows-11/)  
- **Fault offset:** 0x2C924 → The exact instruction inside the DLL where the crash occurred  
- **Process ID / start time:** Just identifiers; not diagnostic

**0xc0000005** specifically means the program tried to **read or write memory it shouldn’t**, typically due to:

- Null pointer dereference  
- Use‑after‑free  
- Corrupted internal state  
- Memory pressure causing unexpected behavior  
- A bug in the module (in this case, Microsoft.Terminal.Control.dll)

---

## 🧠 Why this specific crash is happening

Your crash signature **exactly matches** a documented Windows Terminal issue:

- **Crash during tab drag‑merge**  
- **Faulting module:** Microsoft.Terminal.Control.dll  
- **Exception:** 0xc0000005  
- **Offset:** same region (0x2Cxxx)  
- **Version:** 1.24.2605.12001  

This is confirmed in the Windows Terminal GitHub issue tracker:  
- Issue #20406 describes **intermittent crashes when merging tabs**, with the **same version and same DLL**.   [Github](https://github.com/microsoft/terminal/issues/20406)  
- Issue #19383 shows similar crashes in earlier versions, also during tab merge operations.   [Github](https://github.com/microsoft/terminal/issues/19383)  

The maintainers note:

- The crash occurs **inside the control DLL**, not user code.  
- It is triggered by **dragging a tab from one window into another**.  
- Large scrollback buffers or memory growth (RADAR_PRE_LEAK_64) increase the likelihood.  
- All Terminal windows die because they share a single process.

This is **not caused by your system**, drivers, or RAM.  
It is a **bug in Windows Terminal 1.24**.

---

## 🔍 What 0xc0000005 means in general

Windows uses 0xc0000005 for **any illegal memory access**:

- **0** → invalid read  
- **1** → invalid write  
- **8** → invalid code execution  
  [cloudspress.com](https://www.cloudspress.com/how-to-fix-error-code-0xc0000005-on-windows-11/)

In your case, the GitHub issues strongly indicate a **null pointer dereference** inside the tab‑merge logic.

---

## 🛠 What you can do

### 1. Avoid tab drag‑merge for now  
This is the direct trigger in the known bug reports.

### 2. Reduce scrollback size  
Large scrollback buffers increase memory pressure and crash likelihood.

### 3. Update Windows Terminal  
Check for a newer version than **1.24.2605.12001**.  
The bug is known and under triage.

### 4. If you want deeper debugging  
You can capture a dump and inspect with WinDbg:

- `!analyze -v`  
- Check the call stack around the fault offset  
- Look for pointer dereferences inside Microsoft.Terminal.Control.dll

But based on the GitHub reports, you will likely see the same signature as others.

---

## 🧭 If you want, I can help you:

- Analyze your crash dump  
- Explain how to use WinDbg step‑by‑step  
- Check whether your settings.json might also be contributing

Just pick one.
"


Me:
"
Has a new version of terminal window been released which solves this bug ?
"

**Yes — a newer Windows Terminal build *has* been released that specifically fixes the tab‑drag crash you’re experiencing.**  
The fix landed in **Windows Terminal 1.24.11911.0**, released mid‑July 2026, and confirmed in multiple sources as addressing the drag‑merge crash you hit.   [NT Compatible](https://www.ntcompatible.com/story/windows-terminal-124-and-125-update-released-bug-fixes-and-v126-delay/)

---

## 🟢 **Direct answer: Your crash *is fixed* in 1.24.11911.0**

The NT Compatible release notes explicitly state:

- **“Key fixes include resolving a tab‑dragging crash.”**  
- This fix is included in **Windows Terminal 1.24.11911.0** (stable) and **1.25.1912.0** (preview).   [NT Compatible](https://www.ntcompatible.com/story/windows-terminal-124-and-125-update-released-bug-fixes-and-v126-delay/)

This matches your crash signature exactly:

- Faulting module: **Microsoft.Terminal.Control.dll**  
- Exception: **0xc0000005**  
- Offset: **0x2C924**  
- Version: **1.24.2605.12001**  
- Trigger: **drag‑merging tabs**  
  (Confirmed in GitHub issue #20406)   [Github](https://github.com/microsoft/terminal/issues/20406)

The fix is described as correcting an **EnablePainting viewport desync** that caused crashes during tab dragging between windows of different sizes.   [NT Compatible](https://www.ntcompatible.com/story/windows-terminal-124-and-125-update-released-bug-fixes-and-v126-delay/)

---

## 🧩 **Important nuance: Some *other* tab‑drag crashes still exist**

While your specific crash (faulting in *Microsoft.Terminal.Control.dll*) is fixed, **newer related crashes** were later discovered:

- Crashes when dragging a tab **over terminal content** (not merging)  
  → Faulting in **Windows.UI.Xaml.dll**, exception **0xc000027b**  
  → Still present in 1.24.11911.0 and 1.24.2607.10001  
    [Github](https://github.com/microsoft/terminal/issues/20512)

- Crashes during pointer‑move events due to a race condition  
  → Null dereference in `TermControl::_PointerMovedHandler`  
  → Present in 1.24.11911.0  
    [Github](https://github.com/microsoft/terminal/issues/20477)

These are **different bugs** from yours, with different faulting modules and exception codes.

**Your crash is fixed.**  
**Other drag‑related crashes still exist.**

---

## 🛠 **What you should do now**

### 1. Update Windows Terminal  
Install **1.24.11911.0** or newer:

- Microsoft Store  
- `winget upgrade --id Microsoft.WindowsTerminal`  
- GitHub releases

This update contains the fix for your exact crash.

### 2. If you still see crashes  
They may be one of the newer XAML drag‑boundary bugs.  
Those are still under active investigation.

---

## 🔍 Want me to check your exact version and confirm?  
You can ask:  
- **Check my Windows Terminal version**  
- **Explain how to update Windows Terminal**
"

At least Microsoft fixes bugs, this was a really bad one, going to update my Windows Terminal, or at least try !

Amazing how the AI was able to figure this out and yes indeed it surprisingly took down all cmd/consoles...

This could be nasty for blockchains or lengthy setup of software.

So definetly a must fix.

Bye for now,
  Skybuck.