Windows and WSL on errno

The new Teams keeps its local chat cache in WV2Profile_tfw, not Default

Mon, 14 Sep 2026 00:00:00 +0000

Symptom

I wanted a copy of my own chat history out of the new Teams desktop client. Not somebody else’s messages, not the whole tenant — mine, for archiving, in a form I could grep. No administrator available to help.

Two walls, in this order. The first is the documented API. A device-code flow against a first-party client id, asking for the delegated Chat.Read scope, gets as far as the sign-in page and then stops:

The Windows drives WSL2 cannot reach: Google Drive returns ENODEV, mapped network drives are simply absent

Wed, 19 Aug 2026 00:00:00 +0000

Symptom

I needed a report out of a Google Drive folder from inside WSL2. The drive letter exists in Windows, the mount exists in Linux, and every single access fails:

$ ls /mnt/g
ls: reading directory '/mnt/g': No such device

$ stat /mnt/g
stat: cannot statx '/mnt/g': No such device

From Python the same thing reads as os error 19:

OSError: [Errno 19] No such device: '/mnt/g'

At the exact same moment /mnt/c, /mnt/d and /mnt/e list normally. Windows interop works. Nothing else is broken. And the mount is there — it looks indistinguishable from a working one:

WSL2: /mnt/c fails with "Input/output error (os error 5)" after the laptop sleeps

Wed, 12 Aug 2026 00:00:00 +0000

Symptom

The laptop was suspended with a WSL2 session open. After resume, every path under /mnt is dead:

$ ls /mnt/c
ls: reading directory '/mnt/c': Input/output error

$ cat /mnt/d/some/file
cat: /mnt/d/some/file: Input/output error

Python, Node and anything else that touches those paths reports the same thing as os error 5:

OSError: [Errno 5] Input/output error: '/mnt/c'

Native Linux filesystems are unaffected. /, /home, /mnt/wsl and /mnt/wslg behave normally, and long-running processes that never touch /mnt keep going.