Context menu alone takes a few hundreds milliseconds to load every time. And then you have the infamous "show more options" to click if you want to do most of things (in my use case).
Open a folder isn't much faster either, there is visible delay. with the current-day hardware there is no reason why this isn't instant.
Compare it with Windows XP or Windows 7, the difference is night and day.
Interaction with OneDrive is horrible too, this is particularly bad because it was fine on Win10. When a folder is syncing it constantly "refreshes" itself which causes you to lose the focus if you're renaming files. This is the single most annoying thing because I do close a doc -> immediately rename it all the time.
I still had spinning rust when I upgraded. Win7 was fine. UI wasn't quite as snappy as XP, but it still felt pretty responsive.
After upgrading? EVERYTHING took forever. The friggin' start menu lagged noticeably on almost every interaction.
Upgrading to a solid state disk mostly fixed it, so they had clearly done something foundational that'd radically increased disk IO system wide. Solid state's fast, but it's not fast enough, if they'd kept going down that road. Eventually it'd start to show up there, too.
Windows 7 with spinning rust microsoft did ReadyBoost, where something could have incredibly fast seek times but mediocre throughput.
Vista was the worst windows, other than 8 and ME.
Suffice to say if windows was actually slow when i used it, i would not use it. I didn't use ME, XP, Vista, or 8. There's a pattern here. I did use Xp x64 edition, but that came out ~2 years after XP, and did not have the pre-service-pack issues XP did.
It’s comforting knowing that I’m not the only one being driven crazy by the renaming file focus thing.
Now when I paste a file and go to rename, I wait and watch the focus selection switch 3 times before I know I’m good to type
i replied to this person who ignored what i asked for, and i uploaded a video and linked it. I right clicked, clicked "rename" and then typed a name, pressed control-Z and then enter.
If we're talking about a transactional file sync service preventing you from editing a file while it's synchronizing; then i am not sure what to tell you. Both you and the person you replied to seem to merely like complaining.
just installed win 11 pro an hour ago and https://i.imgur.com/61AdEBR.png context menu looks fine. Maybe they fixed it? i didn't change any settings at all.
i don't get it. Where's the sluggishness? Do you think i also modified my system to somehow run faster or otherwise tampered with the video evidence i provided?
Are you serious? who cares about the context menu, it's such a non-issue it took me like 15 seconds to figure out how to get the "archive" and rename commands back. The rest of the stuff in there is all software that added context menu items.
I get the feeling you haven't really used windows since win95 or something. like, you have a windows machine at work that you don't like because it's slow for whatever reason. Three people made specific complaints, i responded with a video and a screenshot disproving what they said, and... yeah i don't get it.
(not OP) I open the “videos” folder and it takes 10 seconds to show the files list (there’s only like 50 files). I tried various forum solutions (whose existence proves it’s a bug) and nothing worked. Only happens on the videos folder.
Have you tried searching with Explorer? Or opening the start menu or a folder? I'm currently 100% a Windows shop, and it's embarrassingly slow on my silly fast computer.
To be fair, searching with Spotlight has been equally slow and useless for me… Whenever I need to find a file and mistakenly use Command F in my Finder, the complete cessation of activity that inevitably results reminds me yet once again to just go to my terminal to use trusty GNU’s find instead.
but more to the point you have to enable indexing and let the indexing service run. Microsoft caught flak for "SearchIndexer.exe" using 25% of a CPU 24/7 that i think it's much less aggressive now. But i don't use that search because windows searches CIFS shares slowly, too. Everything.exe indexes and the searches are near enough instant that it's not even worth splitting hairs or stopwatch timers.
