Except we can tell that you didn't...
Uptime: 237 days
Except we can tell that you didn't...
Uptime: 237 days
"I closed the lid..."
Yeah, I think this person is delusional. I would typically indicate I've already tried while while stating I'm proceeding to do it again. I want to keep teir one support on script so I can get to teir two, if needed.
It's also a good procedure to follow their instructions verbatim because software and hardware can be weird in non-obvious ways and those teir one instructions are often written by higher level tiers so they don't get bothered on a weekend.
non-obvious ways
Reminded…
This patient's prescription was for an electron beam, so she positioned the turntable and left the room. In the room next door, shielded from the radiation, was the control terminal. The technician started keying in the prescription to begin the treatment.
If things were exactly following the routine, she'd be able to communicate with the patient via an intercom, and monitor the patient via a video camera. Sadly, that system had broken down today. Still, this patient had already had a number of treatments, so they knew what to expect, so that communication was hardly necessary. In fact, the Therac-25 and all the supporting equipment were always finicky, so "something doesn't work" practically was part of the routine.
Yes good read! (sad aspects too)
And a kinda spoiler from the next paragraph…
The technician had run this process so many times she started keying in the prescription. She'd become an extremely fast typist, at least on this device, and perhaps too fast.
I send the request and list the troubleshooting steps I have tried. Mostly so that they know it's not frivolous but also to avoid duplicate work.
But so often those stupid steps work. Turn it off and back on. Uninstall and reinstall.
If you want them to really like you you've got to list the steps you've already attempted and screenshot any error messages you get.
Don't just say you got an error message, actually tell us what it was.
The number of times I get to tickets which claim up and down that there is some major fault, only for the error message to turn out to be that they didn't enter the correct password cannot be counted.
I do not trust end users with anything.
I usually think "they are lying*
We know you're lying.
Yes, but then you have to wonder if the person understands what a reboot is and didn't just quit the application or just log out of the PC and back in without a clear of RAM
They turned their monitor off and back on again.
i once asked a kid if he turned the laptop off and on again, he said yea. so i started to try to fix the issue, nothing worked. so i decided to reboot anyway and it worked. ive never trusted anyone who responded yes to this question again
If so tell IT that I already restarted they don’t believe me and the make me do it again.
I could literally call and tell them exactly what the problem and how to fix it, I just need administrator access to fix it, and they’ll still make me restart the computer first.
People will tell you they have reset the computer and mean they turned the screen on and off.
It’s true. I’m the “tech support” member of my team. The call me before they call IT. You’re absolutely right.
I immediately open task manager and check the CPU up time, "7:01:69:13" no you didn't, liar.
Only 7 days?
Their previous IT issue was a week ago.
Back in my service desk days, I used to just request to perform a restart on their behalf. If they said they already had, I'd make up some nonsense about how I had just manually edited a regkey for them remotely, and it not taking effect til another restart or something like that.
In my experience, the majority of the time someone claimed to have restarted; they either did so incorrectly, or for some reason believed it held no relevance and just wanted to get to 'the actual solution'.
That little white lie allowed them to save face, and me save time and brain cells. It was a win-win.
How do you restart it wrong? And more importantly - what's the correct way to do it?
It's so annoying (and slightly embarrassing, and funny how often it happens), to restart it myself to no avail... then have it work after a second identical restart just because someone else is spectating.
A lot of people just close the laptop lid or turn off the monitor thinking that's rebooting. Or they shutdown thinking it's better than restarting, but Windows' default shutdown is more of a close all programs and hibernate, so it often doesn't fix things.
I called my ISP because my internet went down. They asked if I'd unplugged the router and plugged it back in. I slightly smuggly said, "Yes." Then, they asked if I'd left it unplugged for at least 30 seconds...
Well, fuck.
Sadly, Windows can never leave well enough alone. The current biggest confusion is that they changed restart vs shutdown. There are currently TONS of people who think they're restarting their computer regularly and saving themselves a lot of pain, but Windows decided to change the definition of shutdown.
Did you restart your computer?
Yes.
Did you use start-> restart?
No, I used start -> shutdown, then powered back on!
Sorry, that doesn't help; it saves the current running state, so when you use it later, it doesn't need to reload everything. For what's currently wrong, we really want to make sure we don't just have some memory corruption. Please perform start -> restart.
Does shutdown /r still work fine?
kinda hard to tell :)
i found one that talks about win 8 https://superuser.com/questions/495240/how-to-instruct-windows-8-not-to-perform-a-fast-shutdown
that says /s works and if you want fastboot at cli use /hybrid, but that's an old article, ymmv
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
RULES:
Related communities: