They are still waiting to receive a properly formatted ticket through official channels before they will start working on it.
this post was submitted on 20 Jul 2024
106 points (98.2% liked)
No Stupid Questions
35834 readers
1342 users here now
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
founded 1 year ago
MODERATORS
“It doesn’t work. Please fix.”
FWIW, It was working before it stopped working
I answered one of these once with "email confirmed to be working, ticket closed"
Did anyone try just turning off the internet and turning it back on?
15 times in a row.
*cover sheet on the tps report
Happy to see my meme is getting extra usage ❤️
- there are currently two (?) fixes
- “You memorized your BitLocker key, right?” – physical access to the computer to boot into safe mode, delete a file, and reboot
- “Thoughts and prayers” – let the computer keep rebooting until it manages (somehow) to grab the fix in the lag or delays between reboots
Everyone in my very large company shares the same bitlocker key for some reason. I guess for today is the reason
There's a third one I've heard:
- Intel VPro (the thing that privacy people disable because runs at a lower level than the OS and does mysterious stuff), is being used to remove the broken file while the OS is booting/crashed.
It’s really up to the individual organizations to fix. There’s not going to be some global “congrats, we pushed and update and now everything is fine” patch, because the crash is preventing a patch from being loaded. It requires manual intervention on every single affected machine. If it’s a large organization with a lean IT team, that could mean days or weeks until every single machine is actually fixed; They’ll be prioritizing the mission-critical systems, so they’ll triage. Start with the wide reaching systems, then the most important employees. The intern will just have to wait.
It’s ok, it was just Windows machines. Nobody in their right mind would run anything critical on a Windows machine.
👀
Omg.. I hate Microsoft and windows as much as the next guy but for the last time this isn't a windows problem ffs. Read any of the thousands of articles published on the matter and you'll find that this theoretically could just as easily happen to Linux machines if they were managed by Crowdstrike - which is the problem.
This never ending Linux elitism on Lemmy is making me tired, boss
I don’t know if I could have made it more obvious that what I said was a joke. But also, it was a Windows problem in that it only affected Windows machines, and that was the premise of my joke (which is why I phrased it that way).
There have been so many folks ranting about Linux being the solution that it's apparently difficult for me to detect sarcasm, but yes, fair enough
Best part is something similar happened with certain Linux distros a few months back.
Nah.
There are fixes but none yet that aren't a PITA.
I thought they were rolling back the update?
It doesn’t fix those already affected. And affected machines require manual intervention, because they cannot boot up to receive any sort of automatic patch.
I also wouldn't accept a fix that isn't a pita souvlaki.
The pita fix only works if you can dig up a CD drive to put it in though. Most people don't have one and are SOL.
At my primary day job, no, they've already announced weekend hours to all employees to resolve issues one by one. I feel for IT/Helpdesk.
At two of my friends day jobs, yes. Everything was fixed by late afternoon.
At another friend's day job, no, and things aren't looking great as their disaster recovery plans, staffing, etc. were not prepared for this. It's sounding like it could extend into next week for them.
For another friend of mine...he got turned away at Starbucks this morning because their computers weren't working. I guess we'll see if he gets turned away tomorrow? Haha.
No, still a shit show at airports at the time of writing.
Lots of kiosks, screens, and other devices still show BSODs in airports. Systems still slow and unstable.
Likely similar in other industries.
Ugh. I fly home in a week. Hope it's not horrible by then.
So, rebooting 15 times wasn't enough, huh?
So this time IT can't say "have you tried restarting it?"
The sixteenth time’s the charm….
It's funny. I didn't have a lot of issues with our company. Three machines, one server. I deleted the bad update on three. When I got to the fourth, it was already fixed because the user just restarted his machine many times.
Yeah we good. The fix was ezpz and even a company with several thousand servers should be up now. End user workstations may take more effort, but it's a 5 min fix per user.
Honestly this was half as stressful as Print Nightmare was, from an IT perspective.
Glad it wasn't too bad for you/y'all.
Unfortunately, I wiped my computer Thursday night before our company mentioned anything. lol. I ended up finding out about the issue on Lemmy/Reddit. My company didn't send anything out until this morning - which I still find insane, my laptop crashed and started looping around 7p (took them like 12 hours).
My laptop just rebooted while I was working so I assumed some program I'd installed caused it (explorerpatcher). I tried everything, safe mode, system restore, uninstall updates. I figured the only option left was to reinstall windows. Done it plenty of times on my personal PC
Oh well, lesson learned. Shit's totally fucked now. It won't even connect to the Internet. lol. Definitely a Monday problem though
Hold up.... You thought maybe you downloaded malware (which in this case that was not the only cause) so you took it upon yourself to reinstall windows on a company issued laptop?
-
Why are you trying to fix it? Submit It ticket and it's their problem.
-
If you suspect malware alert it security immediately. Many malware act as a gateway to lock other systems. Yes you might get in trouble but I'd rather be yelled at for downloading something then yelled at for infecting my company servers will ransomware/malware.
-
Atleast in my company a computer connecting without a company supplied image of windows will be denied. Completely understand you not connecting to the internet.
-
This problem was not caused by you but could of been... Take this as a lesson to be more proactive in the future.
Could have. Have.
You missed a then/than as well
Or just "could've"
They might have a BYOD policy at work where they remote into an azure desktop or something and then reinstalled Windows on their physical device. Who knows. But yeah, they still should have notified their security personnel at the very least before taking any further action, lol.
This is actually the worst type of end-user.
Doesn't make a ticket or notify anyone that there is a problem and then proceeds to try and fix it themselves incorrectly. When it does become a ticket, they won't remember exactly what steps they took to troubleshoot and will waste 5x as much time from support staff trying to fix it than if they just didn't touch it in the first place.
Guaranteed didn't wipe the machine from the built in reset/recovery screen and instead used a windows installer that was created on a different computer and doesn't have the correct network drivers in the image.
Yeah #2 is a big one. I've had to deal with a user who got hit by a supply chain attack, and doing forensics on their box was invaluable.
If they'd wiped their desktop as soon as it got compromised, we'd have nothing to go off of. I'd expect that user to be in some pretty serious trouble tbh for violating our security policy by not notifying us immediately.
I can't help but think most of the servers have been solved. The fix is a pain in the ass but it's not like it's monumentally difficult. Anything that's in a server room with a remote access controller should be pretty straightforward.
Kiosks, workstations, desktops are probably all going to happen in priority order. If somebody needs to run around with a key and unlock a door they're probably just going to replace the storage. And they're probably also waiting on that to happen in contract speed.