3 ms·
From what I understand, the problem was not caused by an update of the driver itself, but an update of a config file that the driver uses. As an OS author, how
by jenadine 2y ago
From what I understand, the problem was not caused by an update of the driver itself, but an update of a config file that the driver uses. As an OS author, how could you possibly know what to rollback when this is just an unrelated file fron a third party?
Maybe you could try to rollback the whole file system to a previous snapshot? Assuming the file system supports automated snapshots, that might work, but this also has costs.
- russellbeattie 2y agoOh, I didn't know that it was just a config file, thanks. I'm not sure if this makes it better though. The idea that an update to a single text file used by a third party Windows service can take down the whole OS permanently is a bit extreme, no? Windows BSODs have been a reality for a long as it has existed. There's no reason at this point any third party software should be able to cause it. Hardware fault? Sure. Badly installed or configured driver? Crazy.