you are viewing a single comment's thread
view the rest of the comments
[+] -6 points 1 year ago (6 children)

Probably just misclicked and blames it on the OS.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 7 points 1 year ago (4 children)

    "this has never happened to me, therefore this can't happen"

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 1 year ago (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 1 year ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 1 year ago

    so with that logic, I've misclicked like 50 times and never actually clicked the update and shutdown option? Yeah no, the option is two buttons above the update and restart one, so I've only ever accidentally misclicked around once or twice.

  • source
  • parent