It still has the old annoying bug where the entire explorer.exe crashes if your mouse cursor gets anywhere near a network drive that can’t be reached. Accidentally hover over its icon in the left sidebar, and explorer just freezes up unrecoverably. I guess the technology to safely handle hovering over the icon of a disconnected drive is just not there yet.
I have honestly no idea how microsoft still hasn’t fixed that issue. Granted I’ve never had it crash from waiting for a directory to respond, it just waits the full 1 minute for the packet to die before coming back.
Also can’t say I’ve had it happen for stuff pinned to the side bar, only when typing it in, or clicking on a mapped directory on the “this pc”
It still has the old annoying bug where the entire explorer.exe crashes if your mouse cursor gets anywhere near a network drive that can’t be reached. Accidentally hover over its icon in the left sidebar, and explorer just freezes up unrecoverably. I guess the technology to safely handle hovering over the icon of a disconnected drive is just not there yet.
I have honestly no idea how microsoft still hasn’t fixed that issue. Granted I’ve never had it crash from waiting for a directory to respond, it just waits the full 1 minute for the packet to die before coming back.
Also can’t say I’ve had it happen for stuff pinned to the side bar, only when typing it in, or clicking on a mapped directory on the “this pc”