Programmer Humor

yeah many linux systems will run fsck on mount as well if that same thing is detected, it's not a windows specific thing

Reminds me of that story about Windows's format dialog. It's on Xitter, so here's the text:

Dave W Plummer

I wrote [Windows's] Format dialog back on a rainy Thursday morning at Microsoft in late 1994, I think it was.

We were porting the bajillion lines of code from the Windows95 user interface over to NT, and Format was just one of those areas where WindowsNT was different enough from Windows95 that we had to come up with some custom UI.

I got out a piece of paper and wrote down all the options and choices you could make with respect to formatting a disk, like filesystem, label, cluster size, compression, encryption, and so on.

Then I busted out VC++2.0 and used the Resource Editor to lay out a simple vertical stack of all the choices you had to make, in the approximate order you had to make. It wasn't elegant, but it would do until the elegant UI arrived.

That was some 30 years ago, and the dialog is still my temporary one from that Thursday morning, so be careful about checking in "temporary" solutions!

I also had to decide how much "cluster slack" would be too much, and that wound up constraining the format size of a FAT volume to 32GB. That limit was also an arbitrary choice that morning, and one that has stuck with us as a permanent side effect.

So remember... there are no "temporary" checkins :)

yeah a fresh windows 11 install has like 20 different control panels, all built at different times by different teams using different UI toolkits. It's basically their philosophy to not unify anything but instead just keep bolting new things to different pieces of the OS, no matter how similar

Yes that was the old Microsoft. The new Microsoft has fixed that problem All teams share the same design philosophy. >!Enshitification!<

It's definitely that one

Windows
mountvol (drive letter) /p

Just because you don't know the command doesn't mean it's not possible.

The equivalent long option is --fuck-you

Have you tried turning off thumbnails? In my experience when it slows down on large directories like that it's either trying to generate thumbnails or index a bunch of new files (which is also a possibility in your use case)

I can also tell you that if you are working with file numbers in the 10,000, windows will notoriously interfere with their built-in services. When copying or moving, msdefender might delay every file copy because it marks the action as suspicious and begins scanning the files beforehand. And also the trkwrks or however that drive observation service is called may block actions on specific files just because.

In short, you are not only fighting drive formats at that point, you are also fighting your built-in system services. Source: I wanna die.

People who say this I'll tell you what actually happens so you can know. When you tell it to safely eject all the volatile memory saved in RAM it actually writes to the permenant storage memory instead of holding it in volatile storage. Every time you yank you're betting that its not in volatile storage anymore and was written to storage. That's what safely eject does, forces the CPU to write to permenant storage.

Edit: the problem comes from whats doing what at what time and you will see why you can lose everything.