How to correct failed updates and hotfixes

Topic

New Reply

	LANGALIST PLUS How to correct failed updates and hotfixes
	By Fred Langa Sometimes, Windows updates and hotfixes can fail or install improperly. Here’s how to remove and reinstall problematic patches. Plus: More on SSD maintenance, driver-update questions, and some advice on moving programs to a new system.

---

The full text of this column is posted at windowssecrets.com/langalist-plus/how-to-correct-failed-updates-and-hotfixes/ (paid content, opens in a new window/tab).

Columnists typically cannot reply to comments here, but do incorporate the best tips into future columns.[/td]

[/tr][/tbl]

Reply | Quote

Replies

Techniques for moving apps to a new system

… you can still transfer installed programs between systems.

The simplest option is to use Win7′s free, built-in Windows Easy Transfer (site).
It can usually migrate most programs and settings between two Win7 PCs with relative ease. It can also assist in migrating from Vista and XP.

Can I transfer programs?

No. Windows Easy Transfer transfers only program settings, not the programs themselves.
To use the programs from your old computer, install them on your new computer, and then transfer files and settings for those programs.
Windows Easy Transfer FAQ

Reply | Quote

+1 for BruceR

Reply | Quote

If doing a brute-force clone type of data transfer is prreferred, there’s an easy way to get all of the Target Machine’s drivers collected and reinstalled after cloning the drive from the Source Machine to the Target Machine.

This is one situation where DriverMax‘s Drivers Backup (Driver Export) feature is useful. It first will let you create a single ZIPped archive of all the drivers from the Target Machine. You store this archive on an external drive or media. It helps to unZIP the archive, so that Windows can use the archive directly to reinstall all of the needed drivers later.

Once the transfer is made, the Windows Device Manager is used to point to the DriverMax (expanded) Backup Archive as the source for all drivers needed for the computer to resume its normal functioning. At least one reboot will be necessary, but otherwise, this is a single-stop driver reinstall method.

DriverMax, if installed on the Target Machine after it is set up, can directly Import Drivers from the ZIPped Archive, which is (except for rebooting) truly a one-stop drivers restoration.

Periodic driver backups may be a useful addition to regular backups. Of course, drivers are normally updated very infrequently, so doing this backup once every few months should be more than sufficient.

-- rc primak

Reply | Quote

I’m a ‘non-geek’ helpdesk tech for a state agency and have recently run across 3 different systems… 2 Lenovo’s running 32-bit Win7 and 1 ThinkPad also running 32-bit Win7… the ThinkPad was, unfortunately, not added to a OU container in Active Directory, so it was not receiving ANY updates at all. When we realized this, after adding the machine to the OU, it would start to update… would take forever… then after shutting down, restart, it would take about an hour to get to 13% and it would just stop there. After multiple restarts, it would finally let the user logon. However, none of their updates were ever correctly configured. The fix for this one? Simply running Chkdsk /f, and letting it run overnight. Strange.. I know. Such a simple thing.
One of my Lenovo’s: it’s problem? No updates running – because there was no Windows Update service … PERIOD! Ran this – http://www.microsoft.com/en-us/download/details.aspx?id=5216 Restarted, and found the Windows Update service … made sure it was started. After forcing the WSUS update, and Group Policy… the next day, 157 updates ran and all configured with no problem. The OTHER Lenovo, was in the correct OU, there was seemingly no reason for its updates not to run and configure. Ran a fix I found online… nothing. Stopped the user’s Windows Update Service, then went into C:WindowsSoftwareDistribution folder and deleted everything in it. Also ran a virus scan… it found nothing… no malware.. nothing. Restarted. STILL a problem. A day or two before, I had uninstalled the google toolbar… a known troublemaker, and the user had installed Greenshot which was always running in the background and constantly asking me to update it to a new version. I uninstalled it too. BUT, the remnants of both Greenshot AND the Google Toolbar was stuck in the registry. I deleted all instances of both, and restarted it, and… WAHLAH! Working like a charm! Hope any and all this helps someone out there.

Reply | Quote