The Windows Shell works the way it does because it worked that way before. If I wrote an extension for explorer 15 years ago and it used a bug or even an undocu

The Windows Shell works the way it does because it worked that way before. If I wrote an extension for explorer 15 years ago and it used a bug or even an undocumented api it probably still works. That’s the good thing. The other side of the coin is that things can never fundamentally be fixed. It appears that explorer must block the UI thread while waiting for a network share operation (for example) due to some fundamental eternal compatibility promise.