Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

11/17/2011
07:58 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Windows 8 To Streamline Patching Reboots

Only one restart per month to coincide with Patch Tuesday

Everybody hates a restart, that disruptive final step to install a new update to Windows or another application. So Microsoft, in the spirit of making the system reboot less annoying, will require just one restart per month for every update to its upcoming Windows 8 operating system.

Windows 8 machines will require a restart only when security updates requiring a restart are installed. That basically means just one restart a month, unless Microsoft issues an emergency patch during that time frame that requires a restart.

"With this improvement, it does not matter when updates that require restarts are released in a month, since these restarts will wait till the security release. Since security updates are released in a single batch on the second Tuesday of every month, you are then getting essentially one restart a month. This simplification helps in three ways: it keeps the system secure in a timely manner, reduces restarts, and makes restarts more predictable," said Microsoft's Steven Sinofsky in a new Windows 8 blog post this week.

If there's a critical security update, such as one to shut down an active worm exploit, Windows Update will automatically install and restart the machine. "But this will happen only when the security threat is dire enough," Sinofsky said.

Windows Update will notify the user of an automatic restart, posting a message on the login screen for three days. "You will no longer see any pop-up notifications or dialogs about pending restarts. Instead, the message appears in a more visible and appropriate place (the log-in screen)," he said in the post.

Not all patches require a restart, however. "The purpose of the changes to the reboot process post updates is to make the whole experience faster and less cumbersome for users," says Andrew Storms, director of security operations for nCircle. "Enterprises will likely continue to manage patch deployment and reboot cycles as they deem necessary using tools like group policies, WSUS, and System Center."

Microsoft isn't saying yet whether the new single-restart policy will be employed with Windows 7, as well. "I think Microsoft will probably take a wait-and-see attitude if these enhancements in Windows 8 will be back-ported to Windows 7. If they find that patches are getting installed more often and faster, then I will put money on Microsoft implementing the change in Windows 7, as well," Storms says.

Meanwhile, it's unclear how the new update strategy for Windows 8 would affect the future possibility of Microsoft's Windows Update eventually helping push third-party application patches. "One topic that has come up often around this topic is the deployment of third-party patches using Windows Update. The real question about third-party product updates is when, or if, Microsoft will utilize its existing update technology to push out updates from other vendors. For example, Microsoft could certainly do a lot of good by helping Adobe distribute their patches," Storms notes.

But pushing other vendors' patches would put some of the responsibility for those updates on Microsoft. "I don't think they are ready to take on this level of risk just yet, but I do think we are headed in the direction of a single update source in the future," he says.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
For Cybersecurity to Be Proactive, Terrains Must Be Mapped
Craig Harber, Chief Technology Officer at Fidelis Cybersecurity,  10/8/2019
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-17537
PUBLISHED: 2019-10-13
Jiangnan Online Judge (aka jnoj) 0.8.0 has Directory Traversal for file deletion via the web/polygon/problem/deletefile?id=1&name=../ substring.
CVE-2019-17538
PUBLISHED: 2019-10-13
Jiangnan Online Judge (aka jnoj) 0.8.0 has Directory Traversal for file reading via the web/polygon/problem/viewfile?id=1&name=../ substring.
CVE-2019-17535
PUBLISHED: 2019-10-13
Gila CMS through 1.11.4 allows blog-list.php XSS, in both the gila-blog and gila-mag themes, via the search parameter, a related issue to CVE-2019-9647.
CVE-2019-17536
PUBLISHED: 2019-10-13
Gila CMS through 1.11.4 allows Unrestricted Upload of a File with a Dangerous Type via the moveAction function in core/controllers/fm.php. The attacker needs to use admin/media_upload and fm/move.
CVE-2019-17533
PUBLISHED: 2019-10-13
Mat_VarReadNextInfo4 in mat4.c in MATIO 1.5.17 omits a certain '\0' character, leading to a heap-based buffer over-read in strdup_vprintf when uninitialized memory is accessed.