Louis Frank.

Notes ·

What annoys me about Windows

by Louis Frank
Contents

My work machine runs Windows, my machines at home run Arch Linux. Most days Windows does its job. This is the list of things that do not.

Work in progress: I add to this list while I suffer through new points, and I strike entries out when they get fixed.

No file-system deduplication for work trees

I usually have several Git work trees of the same large repository checked out side by side, one per branch I am working on. Their contents are almost identical. On Linux I keep them on btrfs, where identical data is stored once and shared between the copies, so a fifth work tree costs next to nothing.

On Windows every work tree takes its full size again. NTFS deduplication exists, but only on Windows Server. Dev Drive can share blocks between copied files, but Git does not copy files when it creates a work tree, it writes them fresh, so nothing is shared.

Scaling between monitors of different resolution

Drag a window from a monitor at one scaling factor to a monitor at another and Windows rescales it halfway across. Well-behaved apps redraw at the new size. Others end up blurry, with the wrong window size, or with a layout that stays broken until I restart the app.

The freeze when a network drive is not reachable

Click a mapped network drive that does not exist on the current network, which happens by accident all the time on a laptop, and Explorer freezes until the connection attempt times out. That takes far too long, and there is no way to cancel it.

The Downloads folder takes a minute to open

Only Downloads, no other folder. The usual explanation is that Explorer treats it as a special folder, groups it by date and reads metadata from every file before it shows anything. Setting the folder to “General items” under Properties → Customize is the commonly suggested fix. That I have to know this is the annoyance.

NTFS is slow, and ReFS is not a full replacement

NTFS is slow at exactly what development does all day: creating, reading and deleting huge numbers of small files. Microsoft’s answer is Dev Drive, which uses ReFS. But ReFS is missing features NTFS has, Windows cannot boot from it, and when I set one up as a Dev Drive it did not even work as one: all I got out of it were errors and instabilities.

The WSL disk image only grows

WSL 2 keeps each distribution in a virtual disk file. The file grows when I write data and does not shrink when I delete it. The automatic shrinking (sparse VHD) is an experimental setting and, in my experience, very unreliable.

So the choice is between a script I run by hand and a scheduled job that shuts WSL down and compacts the image. Without one of them the image grows until the disk is full.

More from Notes

← All posts