The slow consistent degeneration of file explorer, the primary core service for users in the entire OS, is truly a sign of the times at Msoft.
This shit crashes all the time in our office workflow, hard restarting explorer process. USB issues, soft freezing on certain types of file transfer.
Mapping drives and credentials integration have been bugged as fuck for at least 3 years. I shouldn’t have to edit every connection in our office in credential manager to fix this.
And anything happening with the explorer process is infuriating to try and diagnose. It almost never throws an error code or event code when it fucks up. So good luck trying to fix it yourself.
Try dragging a file and accidentally hovering over an unavailable network drive. Explorer will freeze for 5+ minutes with no timeout or cancel option. The entire UI locks up while it waits for a TCP timeout on an obviously unreachable resource. Been reported since Windows XP, still not fixed.
Lay-off the engineers and promote the mouthpieces. It’s not a Microsoft issue, it’s an industry 1.
They’re making poor choices because there was a major shift to incompetence. Using web technologies on the desktop when we as engineers know it was birthed as a whack-a-mole hack job that continues today as a accumulation of human-centric decisions not computing (engineered) 1s.
Applications really don’t need such flexibility to look (ie. dom), they need to function and cohabitate to be resourceful, which clearly they’re not.
And that’s not to say engineers haven’t tried to fix those mistakes but the catalyst was already set.
Design should have never taken precedence over compute, just as much as interpreted/runtime over compiled. They need to be balanced if not swayed back.
We still have the capability to learn the machine and shift the narrative as long as we’re willing to lose the brand for the generic. That’s the biggest obstacle because we sell out to the language, the architecture, etc. by the marketing of efficiencies in time to create rather than compute and each iteration of that deteriorates the experience and the art.
When the WinUI marketing team says it is now used on application XYZ, which now includes Explorer, it doesn't have the effect among Windows developer community that they think it is.
Anything that WinRT touches, after the Project Reunion was announced back in 2020, has been a mess, and they keep pushing it.
Unfortunately some of the newer APIs, like Windows ML, are only available in WinRT components.
25H2 is better than previous versions, where I used Beyond Compare to do file copies because explorer.exe would crash, corrupting the copy. Still needs a lot of work to improve reliability.
between w10 and w11 they even changed some parts off how bat scripts works too, just basic scripts that work in w10 explorer dont work in w11. I had few issues. Total mess and bad product
This shit crashes all the time in our office workflow, hard restarting explorer process. USB issues, soft freezing on certain types of file transfer.
Mapping drives and credentials integration have been bugged as fuck for at least 3 years. I shouldn’t have to edit every connection in our office in credential manager to fix this.
And anything happening with the explorer process is infuriating to try and diagnose. It almost never throws an error code or event code when it fucks up. So good luck trying to fix it yourself.