You try to do the right thing by setting your PC to update Windows automatically, only to be stopped in your tracks by some error message or--more likely--a hung browser. Usually there's a simple explanation for the update hiccup. But not always. The steps below for resuscitating a stalled Windows update begin with the simplest solution and end with the trickiest.
Make sure you're logged in an administrator account. To find out if your current account has administrator privileges, click Start > Control Panel > User Accounts (in Vista's standard Control Panel view, click User Accounts and Family Safety, and then choose User Accounts). If the account you're currently using isn't labeled "Computer administrator" in XP, or "Administrator" in Vista, log into an administrator account and try the automatic update again.
If Windows won't update, check the User Accounts Control Panel applet to make sure you're logged on as an administrator.
(Credit: Microsoft)Temporarily disable your security software. Overzealous firewalls and antivirus programs may inadvertently block Windows Update from downloading and installing necessary OS patches. Right-click the program's icon in your system tray and choose Exit or Disable (you may have to open the program's management console and close it from there).
Unfortunately, the only way to disable some security programs, such as Symantec's Norton 360, is to open Task Manager and disable them there. To do so, press Ctrl-Alt-Delete, click the Processes tab, find and select the process for the program (it likely uses a variation of the product's name), and click End Process. The process will restart automatically the next time Windows loads, or restart it manually by clicking its Start menu shortcut to reopen it.
Check Microsoft's update-troubleshooting site. The first time I visited the Windows Update Troubleshooter, I expected to find a great tool that automatically scanned my PC and fixed whatever was blocking Windows from updating. Instead I opened a page with a long list of links to articles intended to help you figure out the problem on your own. You can find much the same information by copying the error code that appears when Windows Update fails and pasting it into your favorite Web search engine to discover information about it, and possible a solution.
Run the Windows Update Fix batch file. The CastleCopsWiki offers a downloadable batch file that automatically addresses many of the causes for a stalled update. Use it by unzipping the download file and double-clicking the file named WUFix.bat. This is far from a guaranteed fix for update woes, but if everything else has failed to resolve the problem, it's worth a try.
Tomorrow: the best alternatives to Adobe Acrobat.
It's the very definition of irony: bugs in the application designed to install bug fixes. Such is Windows Update, which in the two instances described below installs known buggy software--and tells you that all is well when it is not.
Installing IE7
I use Firefox for pretty much everything, so my main desktop and laptop (both running Windows XP) still had Internet Explorer version 6 until recently. I also run Windows Update manually, so keeping IE 7 off my machine involved nothing more than unchecking a box once a month. But now that IE 7 has been out for roughly a year, and I'm addicted to tabs, I finally got around to installing the browser.
Since I was up-to-date on bug fixes, IE 7 was the only thing Windows Update had to install. The installation process includes the option shown below about installing "the latest updates for Internet Explorer," which I did. All went well, at least according to Windows Update.
The first thing I noticed afterward was that IE 7 turned on the language bar toolbar on the task bar. It doesn't take up much room, but I have no interest in the language features and the fewer things running the better.
To get rid of the language bar, go to the Control Panel, click on Regional and Language Options (the globe), then click on the Languages tab, then the Details button, then the Advanced tab. Finally, put a check in the box to "Turn off advanced text services".
All seems well at this point, but it's not. A critical bug fix having to do with something called VML is missing. The fix goes by the names KB938127 and MS07-050 (see Critical Vulnerability in Vector Markup Language Could Allow Remote Code Execution) and dates back to August 2007. Yes, Microsoft has had eight months to make Windows Update smart enough to install this critical bug fix when it installs IE 7. Or, at the least, warn us to run Windows Update again. But no, it instead installs known buggy software.
.Net Framework Version 2
The same thing happens when you install version 2 of the .Net framework. There are three versions of the .Net framework, and all are optional--until, that is, you try to install software that requires it.
Again, I started with a Windows XP system that was up-to-date on all bug fixes and installed nothing but version 2 of the .Net framework using Windows Update. As before, I ran Windows Update manually (Tools -> Windows Update in IE) and opted for a Custom install. All went well, and I rebooted afterwards, just for good luck.
Though all seems well, I ran Windows Update again. Sure enough, the just-installed .Net framework needed updating. And not just one bug fix; it was missing an entire service pack (KB110806). Installing the service pack was uneventful other than the required reboot.
Back to Windows Update and, finally, everything is up to snuff.
There is no excuse for a software update application, such as Windows Update, to install known buggy software. No excuse, but there is a reason: either incompetence or a corporate laziness that sets in when a company is not challenged in the marketplace. I am not sure which applies in this case.
See a summary of all my Defensive Computing postings.
I had occasion to open the C:Windows folder on my old XP machine, and was immediately struck by the number of folders whose names began "$NtUninstall". They were from several hundred kilobytes to 10 megabytes in size, and there were more than 150 of these bad boys just taking up space on my hard drive. There were also a few multi-megabyte files whose names began with "$MSI31Uninstall" or "$NtServicePackUninstall". Some of these folders dated back to when I bought the machine in 2003.
If Explorer won't show you the contents of the C:Windows folder, click Tools > Folder Options > View, select Show hidden files and folders in the Advanced settings window, and click OK.
These uninstall folders are intended to roll back the system in the event of a Windows patch gone bad. Obviously, the OS updates they refer to had done no harm to the machine, which is working just fine. The PC's 30GB hard drive has 5GB of free space, which is slightly less than the 20 percent margin many experts recommend to ensure a smooth-running drive. Clearly getting rid of these unnecessary patch fixers would do my system good. To play it safe, I retained the few uninstall folders that were less than a month or two old.
Make room on your hard drive by deleting old Windows update uninstall folders, but play it safe by retaining the most recent ones.
Unfortunately, the files aren't listed by date, and if you click Date Modified in Explorer's Details view, the uninstall folders get mixed up with other folders in C:Windows. Rather than selecting the uninstall folders one by one, I clicked the first one I wanted to delete, then Shift-clicked the last one, and finally Ctrl-clicked the few recent ones I wanted to keep to deselect them.
The fixes will still be listed in XP's Add or Remove Programs Control Panel applet. To remove their entries, open the program, check Show updates at the top of the window, scroll to Windows XP - Software Updates, select each one at a time, and click Remove. You'll get an error message telling you the file has already been deleted. Click Yes and move on to the next one. Just be sure not to accidentally uninstall an update that you haven't already deleted. If the Software Update Removal Wizard opens rather than the "already deleted" error message, click Cancel.
Play it safe by keeping the folders in the Recycle Bin for a week or so. If you experience problems with a Windows patch for which you've deleted the uninstall folder, simply locate it in the Recycle Bin, right-click it, and choose Restore to return it to the C:Windows folder.
I found only two of these patch-uninstall folders in the C:Windows folder on my Vista PC, both of which were empty. I don't know if that means Microsoft figured out a way to safeguard its Vista fixes without cluttering up your hard drive, or if the update-uninstall folders are now stashed somewhere else.
Tomorrow: Using OpenOffice.org's Writer app in a Microsoft Word world.
Windows breaks; it's a fact. Sometimes the only fix you need is a system restart, but other times you may feel like you'll never get your PC working again. While not even a building full of Microsoft engineers can promise solutions to every Windows problem, these tips will help you begin your quest for a cure.
Windows won't update
First, make sure you're logged into an administrator account. Next, open the Windows Update log, which is at C:\Windows\Windows Update.log, and look for an error message, which may include an error code you can search for in Microsoft's knowledge bases. (Make sure you have Windows set to show hidden files: Open Windows Explorer, and in XP, click Tools>Folder Options>View>Show hidden files and folders; in Vista, click Organize>Folder and Search Options>View>Show hidden files and folders.)
Scan your Windows Update log file for clues to your system's update failures.
Now visit the Windows Update Troubleshooter and browse around for an entry relating to the error. If nothing on this page solves the problem, try disabling your antivirus and anti-spyware programs, your firewall, and any Web accelerators you've installed before going to the Windows Update page. Just be sure to reactivate your security programs before you browse anywhere else.
If you're still unable to update Windows, here are three more things you can try:
Check your clock to make sure your PC is set to the correct time and date. Double-click the time in the bottom-right corner of the screen to open the Date and Time Properties dialog box (in Vista, click Change date and time settings).
Log into another administrator account and try to update. If you don't have two administrator accounts, open the User Accounts Control Panel applet, click Create a new account (in Vista, select Manage Another Account first), and step through the wizard, choosing Computer administrator as the account type (Administrator in Vista).
Start Windows in Safe Mode and retry the update. To enter Safe Mode, press F8 after your PC starts but before Windows loads, and choose Safe Mode from the resulting menu.
You'll find more update-troubleshooting options on DTS-L.org's Windows Update Checklist.
The Registry has gone haywire
The fastest and simplest way to repair a garbled Registry is via Windows' System Restore: In XP, click Start>All Programs>Accessories>System Tools>System Restore>Restore my computer to an earlier time (likely selected by default)>Next. Choose a restore point on the calendar, and step through the wizard. In Vista, press the Windows key, type "system restore," and press Enter. Vista recommends a restore point; if you approve, click Next>Finish. Otherwise, click Choose a different restore point>Next, make your selection, and step through the wizard.
Vista's System Restore applet chooses a restore point for you, or you can opt to select another.
You always have to be careful when you make changes to the Registry, which is why you should triple-check any Registry-cleaning utilities before you use them. One that has been around for a while is TweakNow's RegCleaner Standard (the company also offers a $27 Professional version).
Windows doesn't know when to quit
Sometimes Windows reboots when you only want it to turn off. This may be caused by the OS thinking a shutdown is actually a crash, which it is programmed to respond to by restarting. To disable this feature, right-click My Computer (Computer in Vista), choose Properties>Advanced (Properties>Advanced system settings>Advanced in Vista), and click Settings under Startup and Recovery. Uncheck Automatically restart under System failure, and click OK.
Stop Windows from restarting automatically after a crash by unchecking Automatically restart in the Startup and Recovery Settings dialog box.
This doesn't address the cause of the "crashes", however. A primary reason for such failures is a hardware or software conflict, so if you've recently installed some device or program, check the vendor's Web site for updated firmware or a new driver (more on fixing hardware conflicts tomorrow).
If your shutdowns are just slow, Windows may be clearing your virtual memory and system-hibernation cache (sleep mode in Vista) when it closes, which adds considerably to the shutdown process. To reset this option, click Start>Run (in Vista, simply press the Windows key), type gpedit.msc, and press Enter to open the Group Policy Editor. Navigate in the left pane to Computer Configuration>Windows Settings>Security Settings>Local Policies>Security Options, double-click Shutdown: Clear virtual memory pagefile, choose Disabled (if it isn't selected already), and click OK.
Tomorrow: Remedies for Windows networking and hardware failures.
Blogs were buzzing this week with reports that Windows users who thought they had automatic updates set to either not install or get permission before installing nonetheless had their machines patched and rebooted.
Friday afternoon, the company posted a response to its Web site saying no changes were made to the automatic update mechanism nor did any recent updates change AU settings. The company is looking into whether customers might have actually had their settings changed by Microsoft Office or Windows OneCare, two programs that do have mechanisms that will change a computer's automatic update preference settings.
"We have received some logs from customers, and have so far been able to determine that their AU settings were not changed by any changes to the AU client itself and also not changed by any updates installed by AU," program manager Nate Clinton said on Microsoft's Web site. "We are still looking into this to see if another application is making this change during setup with user consent, or if this issue is related to something else. We are continuing the investigation, and as I have more information I will update this post."
The company is asking anyone experiencing an issue to contact its customer support so that it can get more information.
Meanwhile, in a separate posting, Clinton acknowledged that some people are having trouble manually installing updates after moving to the latest version of Windows Update.
The issues Friday follow an earlier outcry over the discovery that the Windows Update utility updates itself regardless of whether automatic updates are turned on.
Microsoft sought today to downplay the recent, but unpublicized, automatic update of system files on Windows XP and Vista machines as "normal behavior." ZDNet blogger Adrian Kingsley-Hughes has been writing the last two days about a "stealth" update that occurred on his and other machines in late August, even though those machines are set to not install automatic updates. "I just don't like the idea of having updates foisted upon systems without being aware that they are coming in and having the option to postpone them," he wrote.
A Microsoft spokesperson said, "Windows Update automatically updates itself from time to time to ensure that it is running the most current technology, so that it can check for updates and notify customers that new updates are available."
"The point of this explanation is not to suggest that we were as transparent as we could have been; to the contrary, people have told us that we should have been clearer on how Windows Update behaves when it updates itself," said Nate Clinton, Program Manager Windows Update, in a blog today.
Clinton went on to say, "WU does not automatically update itself when Automatic Updates is turned off, this only happens when the customer is using WU to automatically install upgrades or to be notified of updates." That would explain what happened on the machines that Adrian Kingsley-Hughes observed. According to his blog each were set to be notified of any updates.
For the curious, the updated files on Vista are:
- wuapi.dll
- wuapp.exe
- wuauclt.exe
- wuaueng.dll
- wucltux.dll
- wudriver.dll
- wups.dll
- wups2.dll
- wuwebv.dll
- cdm.dll
- wuapi.dll
- wuauclt.exe
- wuaucpl.cpl
- wuaueng.dll
- wucltui.dll
- wups.dll
- wups2.dll
- wuweb.dll
All nine files are system files related to the XP and Vista versions of Windows Update (WU) itself.
Who says there's no such thing as a free ride?
Just ask the 100,000 or so folks who've been infected with malware that has piggybacked on Windows updates, according to a report by security research firm Symantec.
According to the report, a recent Trojan began circulating in March via spammed German email. The Trojan used an "interesting" technique to download malicious files, according to the report. Its method of attack was by way of a Windows component, also known as Background Intelligent Transfer Service (BITS), to do its dirty deeds.
The trouble, however, is Windows updates rely on BITS as its main service for downloading patches and keeping the operating system humming along. And because the BITS service is part of Windows OS, it?s trusted and can bypass the local firewall as it downloads files.
Get the picture.
Javier Santoyo, manager at Symantec's Security Response Center, had this analogy: imagine someone opening a door with a legitimate access badge and an attacker tailgating them to enter the building.
Microsoft weighed in with its comments.
The software giant stated that users would have already had to have been duped, via social engineering, into allowing the TrojanDownloader:Win32/Jowspry to infect their system. Once infected, the Trojan utilizes BITS to download additional malware.
And so it goes, unless an infected user scans their system and removes all variants of the Trojan, Microsoft notes.
- prev
- 1
- next
