Not getting much by Googling.

If not, what’s the ETA?

  • cerement@slrpnk.net
    link
    fedilink
    arrow-up
    55
    ·
    4 months ago
    • 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
    • igg@lemmy.world
      link
      fedilink
      arrow-up
      16
      ·
      4 months ago

      Everyone in my very large company shares the same bitlocker key for some reason. I guess for today is the reason

    • SteveTech@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      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.
  • hperrin@lemmy.world
    link
    fedilink
    arrow-up
    43
    ·
    4 months ago

    It’s ok, it was just Windows machines. Nobody in their right mind would run anything critical on a Windows machine.

    • Retrograde@lemmy.world
      link
      fedilink
      arrow-up
      18
      ·
      edit-2
      4 months ago

      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

      • hperrin@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        4 months ago

        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).

        • Retrograde@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          4 months ago

          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

      • KyuubiNoKitsune
        link
        fedilink
        arrow-up
        2
        ·
        4 months ago

        Best part is something similar happened with certain Linux distros a few months back.

  • PM_Your_Nudes_Please@lemmy.world
    link
    fedilink
    arrow-up
    24
    ·
    edit-2
    4 months ago

    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.

  • AlecSadler@sh.itjust.works
    link
    fedilink
    arrow-up
    19
    ·
    4 months ago

    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.

  • Kit
    link
    fedilink
    arrow-up
    14
    ·
    4 months ago

    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.

    • Psychodelic@lemmy.world
      link
      fedilink
      arrow-up
      13
      ·
      4 months ago

      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

      • vrek@programming.dev
        link
        fedilink
        English
        arrow-up
        26
        ·
        4 months ago

        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?

        1. Why are you trying to fix it? Submit It ticket and it’s their problem.

        2. 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.

        3. 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.

        4. This problem was not caused by you but could of been… Take this as a lesson to be more proactive in the future.

        • bassomitron@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          4 months ago

          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.

        • CoopaLoopa@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          4
          ·
          4 months ago

          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.

        • Shadow@lemmy.ca
          link
          fedilink
          arrow-up
          2
          ·
          4 months ago

          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.

  • linearchaos@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    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.

  • Don_Dickle@piefed.social
    link
    fedilink
    Afaraf
    arrow-up
    1
    ·
    4 months ago

    Yes it should be fixed. I currently am using the WIFI of JBHUNT who relies on NWA airport and its working fine… I got a vpn and it kind of seems that other countries are doing good. The last I have seen is that the last holdout is China.