[hilbert42]

You'd think that with Windows having an install size of some 7GB that Microsoft would still have room for a tiny amount of code that would prevent this stupid behavior from happening.

For decades, there have been other stupid annoyances with Windows Explorer such not providing options in 'Copy' to allow the automatic renaming of files in cases where the destination contains files of the same name. It stands to reason that there'll be occasions when one doesn't want to overwrite destination files.

For years, I often wondered about how Microsoft employees actually use the stuff they create—or if they use it at all.

How can they continue to use a 'nobbled' Windows when they have the power to actually fix these annoyances? It sort of defies all logic and reason.

Does anyone know the reason?

[marcosdumay]

> How can they continue to use a 'nobbled' Windows when they have the power to actually fix these annoyances?

In a large company, just because you use something, develops it, and is on the specification process, it still doesn't mean you have the power to actually fix anything.

[Joe_Boogz]

I think you’re underestimating how difficult it is to communicate cross team at a corporation as large as Microsoft.