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
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19642
PUBLISHED: 2019-12-08
On SuperMicro X8STi-F motherboards with IPMI firmware 2.06 and BIOS 02.68, the Virtual Media feature allows OS Command Injection by authenticated attackers who can send HTTP requests to the IPMI IP address. This requires a POST to /rpc/setvmdrive.asp with shell metacharacters in ShareHost or ShareNa...
CVE-2019-19637
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19638
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function load_pnm at frompnm.c, due to an integer overflow.
CVE-2019-19635
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19636
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_encode_body at tosixel.c.