Microsoft will kick off the Patch Tuesday rollout in a few hours, and Windows 10 systems are expected to get its own batch of fixes, including brand new cumulative updates for the original version released in July 2015 (10240), November Update (1511), and Anniversary Update (1607).
Just like usual, cumulative updates are particularly important for Windows 10 users because they bring computers completely up-to-date once they are installed, but it’s no secret either that plenty of them actually came with bugs and caused trouble on PCs.
Microsoft is yet to deliver a cumulative update that installs fine on all Windows 10 computers, but given the fact that new ones are expected today, we’ll keep an eye out on reports and will let you know should anything go wrong.
This month’s Patch Tuesday also brings an important change for Windows 7 and 8.1 systems, as Microsoft switches to a rollup servicing cycle that’s similar to the cumulative updates shipped to Windows 10 computers.
Challenging month for companies
Chris Goettl, product manager at Shavlik, expects this Patch Tuesday to be particularly challenging for many companies, as it could raise additional problems, some of which would involve application compatibility.
“While well intentioned, Microsoft¹s change will likely impact many companies, and in some cases, push them to make difficult decisions. At first glance, it appears application compatibility is going to be the most significant change,” Goettl stated.
“That said, because most companies are already aware of which products are sensitive to updates, it would be especially proactive to reach out to those vendors in advance and confirm they understand the changes and potential ramifications. It¹s also important to note, while the changes will likely spur organizations to make some challenging decisions, with planning and other security measures, companies can overcome the issues.”
If you want to remain on the safe side, backing up systems before installing today’s patches could be the first thing to do. Also, keep in mind that reboots will be necessary, so work needs to be saved before starting the deployment process.
