Not getting much by Googling.

If not, what’s the ETA?

  • PM_Your_Nudes_Please@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 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.

  • douglasg14b@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    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.

  • hperrin@lemmy.world
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    2 months ago

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

  • Kit@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    2 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.