• stoy@lemmy.zip
    link
    fedilink
    arrow-up
    8
    arrow-down
    3
    ·
    2 days ago

    As an IT technician with a decade worth of user support and systems admin experience.

    This is by far the most probable explanation.

    I am not saying it 100% is the problem, just that user error is by far the most common issue I encounter.

    • javiwhite@feddit.uk
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      2 days ago

      I’m also an it technician with over a decade of experience, and I’ve seen this first hand, on multiple occasions.

      I agree PICNIC is the goto in this scenario; it’s not like shutdown commands are new, so why would it not work as intended? it was my initial assumption when faced with these reports; but having seen this occur multiple times, I can confirm it isn’t. My running theory is it’s KB related, as the issue is intermittent by device (though consistent with an affected device… as in the device will exhibit this behaviour every time). It’s also unique to windows 11.

      • stoy@lemmy.zip
        link
        fedilink
        arrow-up
        3
        ·
        2 days ago

        Interesting, thank you for your thoughts, since I haven’t seen it in person it is hard to get my head around it.