5 ms·

Windows update has a process to rollback bad driver updates after a handful of crashes, and I've seen it work. I think it's about three crashes and it rolls bac

by toast0 2y ago

Windows update has a process to rollback bad driver updates after a handful of crashes, and I've seen it work. I think it's about three crashes and it rolls back. But there's probably situations where it won't work, I'm guessing things like: driver A's update causes a crash in driver B; the updated driver crashes, but not immediately; the driver crashes, but only after writing bad data to disk. I also don't know if Microsoft's security software can rollback from bad definition updates.

ronsor 2y ago
> driver A's update causes a crash in driver B I can't see why this wouldn't work. A should be in B's stack trace, outside of esoteric interactions. The rollback didn't work for the Crowdstrike problem because despite being a ".sys" file, the file that was updated wasn't a driver.
throw0101d 2y ago
> Windows update has a process to rollback bad driver updates after a handful of crashes, and I've seen it work. Does that include "boot-start" drivers? > A boot-start driver is a driver for a device that must be installed to start the Microsoft Windows operating system. * https://learn.microsoft.com/en-us/windows-hardware/drivers/install/installing-a-boot-start-driver https://learn.microsoft.com/en-us/windows-hardware/drivers/i... CS designated their software as one, and when it crashed so did the whole OS to the point that the rollback process doesn't seem to be able to kick-off.
- toast0 2y ago
  > Does that include "boot-start" drivers? I'm not sure... I don't actually know what driver it was that failed; although I suspect it was a video driver. Computer made some noises, blue screened, restarted, repeat N times, then came up, and after login said something about a bad update and may have told me which device, but I forgot. I was across the room for most of it.

5 ms·

Windows update has a process to rollback bad driver updates after a handful of crashes, and I've seen it work. I think it's about three crashes and it rolls bac

by toast0 2y ago

ronsor 2y ago
> driver A's update causes a crash in driver B I can't see why this wouldn't work. A should be in B's stack trace, outside of esoteric interactions. The rollback didn't work for the Crowdstrike problem because despite being a ".sys" file, the file that was updated wasn't a driver.
throw0101d 2y ago
> Windows update has a process to rollback bad driver updates after a handful of crashes, and I've seen it work. Does that include "boot-start" drivers? > A boot-start driver is a driver for a device that must be installed to start the Microsoft Windows operating system. * https://learn.microsoft.com/en-us/windows-hardware/drivers/install/installing-a-boot-start-driver https://learn.microsoft.com/en-us/windows-hardware/drivers/i... CS designated their software as one, and when it crashed so did the whole OS to the point that the rollback process doesn't seem to be able to kick-off.
- toast0 2y ago
  > Does that include "boot-start" drivers? I'm not sure... I don't actually know what driver it was that failed; although I suspect it was a video driver. Computer made some noises, blue screened, restarted, repeat N times, then came up, and after login said something about a bad update and may have told me which device, but I forgot. I was across the room for most of it.