Whenever Microsoft releases new updates for Windows, it’s pretty much expected now that users around the world will run into all kinds of error codes and messages. But one Microsoft veteran thinks it’s wrong to assume problems are always caused by the updates themselves.
In a recent post on his Microsoft dev blog, Raymond Chen says: “Before you check if an update caused your problem, check that it wasn’t a problem before the update.”
What he’s saying is that issues can actually stem from various other changes that might’ve happened around the same time as the update. For example, the IT department installed a new driver, modified a group policy, or updated a program. But you haven’t restarted your system in a while, so those changes haven’t fully taken place.
Then comes Patch Tuesday and you install the latest Windows update, which forces a system reboot. Now the new software, driver, or incomplete config settings bump into each other and break things. In cases like these, it wasn’t the Windows update itself that broke your system—it was the fact that your system finally restarted.
The takeaway? Windows users should make it a habit to restart their computers after every change and before installing Windows updates. Make sure there are no problems prior to installing that new Windows update. It’ll make troubleshooting easier.
By the way: If you’re using Windows 11 Home, you’re missing out on the many benefits of Windows 11 Pro. To learn more, see our comparison of Windows 11 Home and Pro. If you want to upgrade, snag it for cheap in the PCWorld Software Store: now just $59 instead of $99.
