4 ms·

> "Took down our entire emergency department as we were treating a heart attack." Not questioning that it happened, but this was a boot loop after a content up

• sleepydog 2y ago
  Not OP, but some (most? many?) machines receiving the update crashed with a BSOD. So that's how they could enter the boot loop.
  • jodrellblank 2y ago
    I just realised I had read that, but 4 minutes later and it's too late to delete my comment now; Thanks, yes it makes sense.
• lupire 2y ago
  What happens when a computer gets rebooted as part of daily practice or because of the update, and then it becomes unusable, and then the treatment team needs to use it hours later?
  • jodrellblank 2y ago
    I dunno, but they'd know about it hours earlier in time to switch to paper, or pull out older computers, or something - in that scenario it wouldn't have happened "as we were treating a heart attack" and they would have had time to prepare.
• TeMPOraL 2y ago
  Beyond the BSOD that happened in this case, in general this is not true with Windows: > And if they were on and you were using them, they wouldn't be rebooting, and it would be fine. Windows has been notorious for forcing updates down your throat, and rebooting at the least appropriate moments (like during time-sensitive presentations, because that's when you stepped away from the keyboard for 5 minutes to set up the projector). And that's in private setting. Corporate setting, the IT department is likely setting up even more aggressive and less workaround-able reboot schedule. Things like this is exactly why people hate auto-updates.
  • axlee 2y ago
    Windows Update has nothing to do with it.
    • olyjohn 2y ago
      But it has created a culture of everything needing to be kept up to date all the time no matter what, and pulling control of those updates out of your own hands into the provider's.
      • p_l 2y ago
        Windows update actually provides sensible control over when and how to supply updates since I think Windows 2000 (definitely was there by vista time). You just need to use it.
        • TeMPOraL 2y ago
          It was degrading since Windows 2000, with Microsoft steadily removing and patching up any clever workarounds people came with to prevent the system from automatically rebooting. The pinnacle of that, an insult added to injury, was introduction of "active hours" - a period of, initially, at most 8 or 10 hours, designated as the only time in the day your system would not reboot due to updates. Sucks if your computer isn't an office machine only ever used 9-to-5.
          • p_l 2y ago
            No, it was not degrading - Windows 10 introduced forced updating in home editions because it was weighed to be better for general cases (that it got abused later is separate issue). The assumption is that "pros" and "enterprise" either know how to use provided controls or have WSUS server setup which takes over all of scheduling updates.
      • whydoyoucare 2y ago
        True, especially when a reboot of Windows takes several minutes because it started auto-applying updates!
• newhotelowner 2y ago
  Half of the hotels (Choice) computers were down. We never reboot the computer, unless it's not working or working slowly or Windows update.
  • p_l 2y ago
    A lot of security software updates on-line, workout rebooting. If said update pushes you into bsod where automatic watchdog (by default set enabled in windows) reboots...well, here you have a bootloop
• a0123 2y ago
  idk, a lot of system are never meant to be rebooted outside of the update schedule, so they wouldn't have been off in the first place. And if those systems control others, then there is a domino effect. I can see very well how one computer could have screwed all others. It's really not hard to imagine.
  • p_l 2y ago
    And dove software is supposed to hot patch itself because you might not have time to take systems offline to deal with ongoing attack, for example