Windows and WSL
Filesystem mounts that exist but cannot serve I/O, drive letters WSL2 refuses to read, and where Windows desktop apps actually keep their data.
- The new Teams keeps its local chat cache in WV2Profile_tfw, not Default
Exporting your own Teams chat history without admin help: why the Graph route stops at an Approval required page, why the EBWebView Default profile looks empty, and where the IndexedDB data actually lives.
- The Windows drives WSL2 cannot reach: Google Drive returns ENODEV, mapped network drives are simply absent
A Google Drive letter is listed in /proc/mounts yet every read fails with No such device (os error 19), while a mapped network drive never shows up at all. How to tell the three failure families apart and reach the files anyway.
- WSL2: /mnt/c fails with "Input/output error (os error 5)" after the laptop sleeps
After a suspend/resume cycle every Windows drive mount in WSL2 returns os error 5 while native Linux paths keep working. Here is how to tell it apart from a permissions problem, and why the only reliable fix has to be run from Windows.