> 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 rollb

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