Microsoft aims to reduce Windows Update restarts

Summary: Microsoft is tweaking its Windows Update service with Windows 8, and is trying to limit the number of restarts for consumers and small business users to one per month. Also, instead of the current 15-minute warning that a reboot is required, users will have three days to choose the most convenient time to update their PCs.

Microsoft is tweaking its Windows Update service with Windows 8, and is trying to limit the number of restarts for consumers and small business users to one per month. Also, instead of the current 15-minute warning that a reboot is required, users will have three days to choose the most convenient time to update their PCs. In businesses, where IT administrators set group policies to prevent automatic restarts, users will get a notification on their log-on screen to tell them that a restart is required. This notification will remain until a restart is performed.

Farzana Rahman, the group program manager of the Windows Update group, has outlined Microsoft's plans in a post on the Building Windows 8 blog: Minimizing restarts after automatic updating in Windows Update. Microsoft's planned changes are based on many billions of items of data, but the company may adapt them in response to feedback.

"Windows Update is one of the largest services on the Internet by several measures," says Windows boss Steven Sinofsky. It's also one of the most successful. It "currently updates over 350 million PCs running Windows 7 and over 800 million PCs across all the supported Windows platforms," says Rahman. "There are actually many more PCs updated by WU indirectly if you account for our Windows Software Update Server, and for those machines (or customers) that do all updates manually for any number of reasons."

With roughly a billion PCs using Windows Update, and more than a dozen batches of updates every year, the service has proven astonishingly reliable. This has encouraged its adoption to the point where 89.30 percent of Windows 7 users now have auto-updates enabled, and only 4.88 percent never check for updates.

Limiting Windows restarts

Restarts (reboots) have become a greater annoyance for a number of reasons. These include the much greater stability of Windows Vista and Windows 7 compared with Windows XP (reboots may be rare and crashes almost non-existent), and the increased use of mobile computers that are turned off much of the time. Instead of updates being installed automatically at 3am, while they're asleep, users are faced with the need to update when they resume work in the morning.

Where users have chosen to have updates installed automatically, they should, of course, be installed without their intervention -- and that includes a reboot. If they do not want to change their behaviour, they should change the setting.

Rahman says that with Windows 7 users:

"The majority of automatic update users (39 percent) are updating when they shut down their systems. For these users, there is no automatic restart because the system can complete all steps of the installation during shutdown. This is the least disruptive experience for users, and so we do want to 'hitch a ride' whenever we can on user-initiated shutdowns instead of inconveniencing users with a separate restart."

However, Windows Update exists for two reasons. First, it is intended to help protect users from malware by patching security holes in their systems. Second, it helps to stem the incidence of malware by providing a sort of "herd immunity" that helps prevent malware from growing virally. Rahman says:

"There is one exception to the rule to wait for the monthly security release [before forcing a restart], and that is in the case of critical security update to fix a worm-like vulnerability (for example, a Blaster worm). In that case, WU will not wait, but will go ahead and download, install, and restart automatically. But this will happen only when the security threat is dire enough."

No third party software updates

One bugbear is not being addressed, which is the use of multiple update programs by suppliers of third party software. Today, the majority of critical threats to Windows PCs are not due to security flaws in Windows but holes in software from Adobe, Apple, Oracle (Java) and other suppliers. Their updates are irregular and frequently intrusive. As Rahman says:

"People clearly find the experience with multiple updaters on the system less than optimal (and we agree!). Each application updater gives you a different experience, you have to remember to go visit each updater to install updates, you never know when or how updaters will run and what they might do, and so on. People would like one updater for the entire system."

However, Microsoft is currently unwilling to take this on. The high take-up of Windows Update is based on the fact that "they trust the quality of updates distributed by WU". Bundling in updates for third party programs might diminish that trust.

For those users who have problems knowing when or how to update third party software, there is a very convenient solution (for the programs it covers). I recommend, and use, Secunia's Personal Software Inspector (PSI). This scans your Windows hard drive, lists the applications that need updating, and provides a link to each update. Using PSI also means you don't have to run numerous separate updaters.

@jackschofield

Topic: Tech Industry

Jack Schofield

About Jack Schofield

Jack Schofield spent the 1970s editing photography magazines before becoming editor of an early UK computer magazine, Practical Computing. In 1983, he started writing a weekly computer column for the Guardian, and joined the staff to launch the newspaper's weekly computer supplement in 1985. This section launched the Guardian’s first website and, in 2001, its first real blog. When the printed section was dropped after 25 years and a couple of reincarnations, he felt it was a time for a change....

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

13 comments
Log in or register to join the discussion
  • Interesting this was posted at the time when we have been hashing over Microsoft Update in other blogs. It appears that Microsoft has heard its customers complain about the current situation with updates, despite those that have used it for 50 years without a problem. But, from the sounds of it, they still aren't up to par with GNU/Linux, which can still patch both the operating system and supported software without a reboot. Unless... this is something that will be introduced in the next Windows server OS. One could argue that a kernel upgrade requires a reboot which is true, unless KSplice is used which gets around it so that no reboots are ever needed for updates.
    Chris_Clay
  • This is good news. There is nothing more terrifying than being woken up at 3am with laptop in bedroom, with the loud Windows 7 audio fanfare! Perhaps an option for a muted reboot at night might be useful.
    anonymous
  • The way I read this article (reading between the lines) is that for Windows 8, Microsoft are rearranging the deck chairs - they're not curing the problem, tweaks to notifications, reboots will still be required, makes no attempt at tackling the issue of third party updates, updates of updates, basically more of the same.

    Employees will still get caught out by Windows installing updates on shutdown/leaving work. To their annoyance, many still don't notice that Updates are required. Most do the shutdown process without thinking only to find out as shutdown begins that they then have to wait up to 20 minutes while Windows shuts down and installs updates.

    A second opt out once shutdown begins would be good, so if your in a hurry, it will just abort, and shutdown.

    In essence, Windows updates will be carried out when you really don't want them to be carried out. Yep, its more of the same.

    'Clunky'
    The stats must be fasinating reading, the vast number of hours from initiation of downloads, install process, failures, reboots, to completion. Updates stood aside while others are installed, then renotified. The .net updates really need sorting out, these seem to be the ones that take forever, often fail, or can't be installed along with other updates.

    While, it's nice to see Windows Development Team admitting things could be better, they are also admitting that in Windows 8 the improvements will be very marginal.

    Is Windows 8 worth upgrading to? Probably not. Microsoft have missed an opportunity, because improvement to the Clunky Windows Update would be one area that would show a cost effective reason to update from Windows 7 to Windows 8. Personally - I can't see a reason to even bother, even less so if Windows Phone 7 (WP7) turns out to be a failure , because the 'strap-on' Metro Interface in Windows 8 will be also be a failure.
    SoapyTablet
  • @apexwm

    > they still aren't up to par with GNU/Linux, which can still patch both
    > the operating system and supported software without a reboot.

    So GNU/Linux patches *never* require a reboot? Really?

    Actually, a lot of Windows updates can be done without a reboot as well, and it would be more if more developers paid attention to Windows Restart Manager. Otherwise, it's delusional to compare updating a billion PCs with the tiny number of GNU/Linux systems. Being able to make breakfast for two people doesn't give you any clue how to handle the arrival of 100 coachloads of people wanting breakfast.

    @SoapyTablet

    > Employees will still have to wait upto 20 minutes while Windows shuts downs at 5pm
    > Windows 8 worth an upgrade for? Probably not.

    You do have some weird notions. Say hello if you ever visit Planet Earth.
    Jack Schofield
  • "So GNU/Linux patches *never* require a reboot? Really?"

    Please, read on the KSplice web page: http://www.ksplice.com/

    I've got countless servers that have only rebooted due to extended power failures, and I patch them all of the time without rebooting. So the answer is yes, really. Why is GNU/Linux still the primary OS for Internet facing servers? Extended uptime perhaps? Stability?

    "Otherwise, it's delusional to compare updating a billion PCs with the tiny number of GNU/Linux systems."

    Stating the number of machines is irrelevant when comparing the two operating systems, the fact remains that GNU/Linux doesn't require rebooting like Windows does. My answer is based on many many years of experience in the corporate and enterprise environments managing countless numbers of servers, and dealings with many other professionals in the same line of work. I know it's hard to believe, but check the Netcraft uptime survey, http://uptime.netcraft.com/, and plug in a few sites that use a form of Unix/Linux vs. Windows Server and I suspect you will see a definite pattern. Even doing a query against Microsoft.com, you can see that their systems have an uptime of around 4 months or so before a reboot (I'm assuming for updates).
    Chris_Clay
  • @apexwm

    Yes, I'm familiar with KSplice, but not everybody is, and it doesn't entirely eliminate rebooting. Either way, it's still not comparing like-with-like, either in the level of attack (dramatically higher for Windows) or in the volume of systems that need updating.

    Also, if you look at http://uptime.netcraft.com/, you will see that 46 of the 50 systems with the longest uptimes are all running Windows Server. A Linux system happens to be top, but the next Linux system is in 33rd place, and it's all Windows Server between the two.
    http://uptime.netcraft.com/up/today/top.avg.html

    Perhaps if you were less intent on hating Microsoft and spent more time improving your competence you might do better? Just a thought...
    Jack Schofield
  • "Yes, I'm familiar with KSplice, but not everybody is, and it doesn't entirely eliminate rebooting."

    The main headline on KSplice's home page is, and I quote, "Keep Linux up to date. Never reboot". Not sure it gets any clearer than this. And if you choose not to use KSplice, that is fine, and you would need to reboot in order to upgrade the running kernel, which is not very often. Other packages can be updated without a reboot. Windows can't really do this because of the "files are in use" problem.

    "Also, if you look at http://uptime.netcraft.com/, you will see that 46 of the 50 systems with the longest uptimes are all running Windows Server."

    Yes, and there is an article that sums up this phenomenon:
    http://blog.eracc.com/2009/07/24/linux-and-unix-uptime-vs-microsoft-on-netcraft/

    Based on my personal experience, this article is right on the money.

    "Perhaps if you were less intent on hating Microsoft and spent more time improving your competence you might do better?"

    I know you love to say that over and over again, but I'm simply pointing out faults with Windows when compared to other operating systems like GNU/Linux, and there's really nothing wrong with that. And I consider my competence high enough to make these judgements, from using these operating systems in the real world for many years, in many different (and LIVE) environments, but thanks for checking.
    Chris_Clay
  • If you look up some real websites on netstats you'll find a lot of them have no data for uptime.
    I've looked up google, bbc, yahoo, amazon, zdnet and microsoft the first five have no data (therefore not listed) but run GNU/Linux and microsoft runs Windows Server 2003 (last reboot 4.1 days ago).
    stubright
  • Those netcraft uptime figures are just laughable. They claim to "limit this monitoring process to the most frequently requested sites". Yet there's no Google, no Microsoft, no eBay, no Amazon, no Yahoo... you get the picture.

    I've never heard of any of the sites listed there, and some of them look decidely suspicious. Take the 5th listed site, http://www2.kungsmadskolan.se, for example. Not much there that I can see. A cynic would say that the site's been parked there with no intention other than gaming the stats in Microsoft's favour.

    And as many others have pointed out, would any admin *want* to be running a Window server that hadn't been rebooted in months? (Assuming that you could persuade it to stay up that long?) That would likely mean that it hadn't been patched in months either, because in Microsoft's world patch=reboot most of the time.


    @Jack,
    > it's delusional to compare updating a billion PCs with the tiny number
    > of GNU/Linux systems. Being able to make breakfast for two people
    > doesn't give you any clue how to handle the arrival of 100 coachloads
    > of people wanting breakfast.

    That argument may be valid in some contexts but sorry, not here. There are enough users - millions, whoever's figures you believe - running Linux Desktops and Servers to get a statistically valid sample for how the system actually works. If it were billions not millions it would all work the same way. What we're talking about here is the basic, underlying artchitecture of the OS and the truth is that *nix systems are propertly architected, whereas Windows is a dog's breakfast (DLL hell, the Registry and so on).


    > So GNU/Linux patches *never* require a reboot? Really?

    Yes, they do when there's a kernel update (Ksplice etc not withstanding). For Ubuntu, that's every month or two. But there's a crucial differences with Windows here. With Linux, there's only one update and reboot required, assuming a reboot is required at all. You *never* have the Windows situation of install updates, reboot, then you see *more* updates which weren't there before, so you install them and reboot again to be greeted by even *more* updates. Repeat and rinse ad nauseum.
    BrownieBoy-4ea41
  • In support of the comments made by BrownieBoy, I recently (3 days ago) installed Windows XP Pro SP2 in a VM. It required 140 updates, including SP3, once I installed VS2005, plus the service pack for it. Total time was approximately 4 and half hours. Some of that time was delays associated with the VM but most was just shear download time AND reboot time on a 6Mb/sec DSL line. I lost count at about 15 reboots.

    I have in the past installed updates on my Ubuntu systems and had reboots occur only with the kernel updates even when there are 140 or more files to be replaced.

    Windows 7 has gotten better but still a weekly reboot seems to be typical either for a security update or a suspicion that something isn't right, like Visual Studio 2010 is running inordinately slow or IE9 has locked up. Microsoft still has a ways to go.
    mileswade
  • @mileswade

    Windows XP Pro SP2 dates from 2004, which is 8 years ago. It came out around the same time as Ubuntu 4,10 Warty Warthog, which was "the first official Ubuntu release". Let me know how many updates it takes if you start with that, will you?

    Otherwise, it sounds like the main problem is a slow internet connection. I did an update from SP2 a couple of years ago and it took a lot less than two hours, and nothing like 15 reboots.

    > Windows 7 has gotten better but still a weekly reboot seems to be typical
    > either for a security update or a suspicion that something isn't right,

    Might be typical for you but it's not typical for me, and I don't believe it's typical for the rest of the world either. But then, I don't even reboot XP once a week...
    Jack Schofield
  • If you leave out all of the dot Net runtimes, don't allow Internet Explorer to update from version 6 etc, yeah you can get it down to a lot fewer reboots and updates. The goal was to have a totally updated XP PRO SP3 image, with the latest runtimes and the latest IE I could get on it, all in a Virtual Machine running on my Windows Server 2008 box. A virtual machine doesn't insulate you from having to reboot the running image. When the guest OS says its time to go, it happens.

    Once all that updating is done YES I can leave my Win XP Pro running for weeks at a time, even in an image. I'm not interested in trolling or trolls. The idea was to create a "perfect" running XP image for some development work I'm doing. I'm also running MS anti-malware software and usually it doesn't require a reboot but a few times it has, probably to replace the "engine" software. The malware definitions don't seem to cause reboots. I do all of my updates manually after I look at the items being updated.

    As to Ubuntu Warty WartHog, why bother? I'm running Ubuntu 11.10 and Linux Mint 12 on some of my other machines and they are extremely stable. When the kernel gets changed, the Linux box gets rebooted, I would expect that. It also happens when MS updates one of its kernels.

    One of my old XP era DELL's is running Ubuntu 9.1 because 10.04 broke the video driver. And that's just fine. It was annoying when it happened but enh! I'm not expecting the Linux community to continue support for 10 year old computers.
    mileswade
  • Perhaps I hexed myself. I [u]totally forgot[/u] today was Patch Tuesday! There were 11 updates for the Windows 7 64 bit box and 14 updates for the Windows 7 32 bit box waiting for me when I got home. The Windows XP Pro image had 2 updates. BUT it had 4 dotNet Framework patches to install that I somehow or the other missed. The Win 7 32 bit box rebooted TWICE. The WIn 7 64 bit box rebooted once. And the XP Pro image had to reboot 3 times. So yes they are getting better BUT its still more aggravating than Linux updates. I know, I see both sides of the fence.

    If you install a dotNet framework on your computer it will take a loooong time to download and install and almost everytime requires a reboot if its anything more complicated than a small patch.

    I see it every time I install a fresh image of any Windows OS. You can have as many as 4 reboots necessary if you are installing one of the older dotNet 3 or dotNet 3.5 frameworks.

    The point of doing fresh installs is that I try my best to emulate what my customer has running in his server room. What I'm delivering needs to work using what he's got. Most of the time they don't want you messing with their systems. So the only way to get the obvious bugs out is to emulate what they have here at home.
    mileswade