"My colleagues over in enterprise product support often get corporate customers who report that 'Your latest update broke our system'. A thorough investigation of log files, dumps, and traces can reveal that the culprit was not the update. In fact, rolling back the update doesn't fix things."
"And then, Patch Tuesday comes around, the update installs, and the system reboots, and now the new software or the new driver or the sketchy configuration settings kick in to make their lives miserable."
"It wasn't the update that broke their system. It was the fact that the system rebooted."
Microsoft updates are frequently blamed for device failures, but many issues stem from prior unnoticed problems. A system reboot during updates can expose these issues. Investigations often show that the update itself is not the cause of the failure. Instead, previous changes, such as new drivers or configurations, may have rendered the system unbootable. The reboot during the update process triggers these existing problems, leading to customer complaints about the updates.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]