• mrgoosmoos@lemmy.ca
    link
    fedilink
    English
    arrow-up
    27
    ·
    5 days ago

    I went back to Win10 at work because file explorer on Win11 was unusable. I’m not waiting a half second every single time I enter a subfolder.

    and even worse in a OneDrive directory, often a full two seconds

    that wasn’t the only issue, but it legitimately prevented me from being able to do my job, because I needed to be able to multitask on several projects at once. what used to be a two minute turnaround on a question somebody would ask me became hours, simply because I could not navigate to a directory in fifteen seconds and check a file quickly. and oh god the file explorer crashes

    unfortunately I still deal with a bunch of that on Win10 now, because they somehow introduced that behaviour with greater frequency into Win10 in the past year

    • corsicanguppy@lemmy.ca
      link
      fedilink
      English
      arrow-up
      22
      ·
      5 days ago

      It’s amazing how a second or 5 at so many levels causes micro-frustration. And it builds up, too.

      I admit I lose just a bit of my shit when the neu web-service web-apps get sluggish, which seems to be very often. Those of us who remember the halcyon days where things were responsive on a pentium know better than to accept the current mess.

      My tolerance for the poor performance and saas-linked core services is rapidly waning.

    • cabillaud@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      5 days ago

      File explorer has always been a weak point in Windows, it just got better in the later versions. Which speaks volumes about this OS too.

    • JigglySackles@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 days ago

      I’m so glad I blocked all the updates from MS on mydesktopm. It’s a nice stop gap until I get moved to linux

    • InFerNo@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      7
      ·
      5 days ago

      I have that problem on my son’s pc. It’s definitely an io issue. A faster disk would solve the problem.

      • mrgoosmoos@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        4 days ago

        lol that’s not the issue here

        that can give you the same symptoms, but the tiniest bit of troubleshooting proves that that is not the scenario I have

        • InFerNo@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 days ago

          Could be, my kids have identical pc’s, but the disks are different. One has a slower ssd and its symptoms are exactly how you described, I knew it was slower but it’s all I had around. Both pc’s have SATA ssds. We’re saving for new disks, which I’m sure will alleviate the symptoms.

          At work a similar problem with Windows server. The hosting company changed the IO tier and like snow these issues disappeared. Clicking start and waiting for it to open would take a minute, completely unacceptable, but ultimately fixed by having faster storage.

          I’m not saying Microsoft is doing good work, I’m suggesting a workaround until they do, which we both know is very probably never.

          They already pushed out older hardware with Windows 11, they won’t care about slower storage options.