Solved Persistent group update failures

[Slartybart]

There are two Windows Update specific things you could try

Windows Update Troubleshooter: Control Panel\All Control Panel Items\Troubleshooting\All Categories
--and--
MS Fixit Windows Update

I aslo found this: Windows Update or Microsoft Update repeatedly offers the same update

One might fix the issue your machine is experiencing with WU - not sure if it will, but those are the first steps I would take.

Post the results of each, so members know what worked and what didn't work - thanks.

Bill
.

 

[markg2]

I attempted restoring the OS to a prior restore point. Each successive point back in time I found the same result: the restore failed due to c:\windows.

I've reverted to the factory image and I'm now reinstalling from scratch.

C'est la vie

Mark

 

[Slartybart]

Ok, that will solve many issues =:>

It's usually advisable to make sure your system is bug free before reinstalling. If you have your data backed up, the easiest way to do that is to wipe the HD. If you haven't backed up your data, you might consider doing a safe store copy (nothing fancy, just copying your important data to some external media - a safe copy).

If you run into the WU issue again, try the Troubleshooter and Ms Fixit

Please post what you decide after the restore to factory and updates are completed. If you think the issue is closed, please mark this thread as closed.

Thanks,

Bill
.

 

[markg2]

Thanks but this is a 5 day old computer. No data but test data for application installs. I hadn't even completed the application installs let alone switching this new one for my wife's dying XP.

FWIW, prior to failing in my attempts to get SURT to load and run--I had tried both the troubleshooter and FixIt. From the error I received attempting to revert to earlier restore point(s) it seems that there was a significant corruption in the system files from early in the update process.

Now that I've restored the drive from the Lenovo hidden partition, restore points doesn't want to turn on absent an error code. I'm leaving that one alone until I complete more of the update process in hopes that mess will clear itself.

I can see why folks make a good living off these things

Thanks,

Mark

 

[Britton30]

Hi Mark, you could give this a try: http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164 You will end up with a pristine w7 system with no bloat.

 

[markg2]

Postscript

After reverting to the factory OS image from the machine's hidden partition, I spent several hours installing software and updating.

I then experienced the identical update problem that I initially posted except for the automatic rebooting. The same 21 updates would install and revert on boot.

I called MS support. Summarizing 3-4 hours of work, the tech ran the MS support diagnostic tool and found no problem of note. I asked that he run SURT to clear my name--which he did and (for reasons he couldn't explain) SURT would not run post install.

He then selected 1 small update for a trial install--it was successful. He then tried a group of several smaller updates with equal success. He successfully completed all remaining update installs in the same manner. He explained that for reasons they cannot explain (although they do have conjectures) MS sees this odd update behavior not infrequently. The reason he starts with the 1 small update--if it fails, there's something going on with the OS. If 1 small update succeeds, then the update portion of the OS is okay. FWIW, all the error codes associated with the 21 failed updates were useless.

Additionally, he resolved the new problem that cropped up post image install--System Restore was set to off by default and any attempt to configure a drive ON and give it some space resulted in an error--could not apply settings filename, dir name or vol name syntax is incorrect. In the sys restore config window drive listing there was a duplicate of the C drive that was ON (the only drive that wasn't off) with 'missing' adjacent to it's name. Apparently this was a residue from the image restore. He set the drive to OFF, booted, the 'missing' drive disappeared and then the other 2 drives could be configured.

Thank you all for your efforts.

All's well that ends well.

Mark

 

[Slartybart]

Ok, thanks. That makes decisions easier - a new machine, no data.... couldn't be better. Well, perhaps if it didn't cause the issue in the first place......

Britton30 makes a valid point - the tutorial is well written and easy to follow (lots of people skip a step or two and that causes some problems-don't know why, but they do). One thing I will stress is to have your network drivers on a disc or flash drive so you can conect when you get to that point (it is in the tut - some folks miss it and then they're stuck going to the library or a friend's house to download it)

Also, thanks for letting me know that you did try the troubleshooter and the MS Fixit. I don't recall if it is Win7, Vista, or XP but one or two updates do get stuck (I've had my battles with my machines over the past few months- each one behaving badly- so I ended up re-installing all of them).

I tend to turn off automatic updates and just execute Windows Updates manually until I get through the lot. The Windows Update service still checks and presents the list to you when you fire it up. I always hit the check for updates - sometimes WU gets out of sync and doing it this way makes sure WU knows what's on the system and what it needs. Occassionally there will be an update that's not checked, I put add that one to the queue and let it run. Make sure you reboot when WU tells you it needs to reboot.

And finally, if one particular update gets in your way - hide it, then try WU again.... hiding any trouble updates until you get thorugh the list you're currently trying to update. Once that list is cleared - restore the hidden updtes and let WU figure out if it still needs them. Lots of time, one update supercedes another and tthe "trouble" update just goes away.

Hiding updates is a last resort workaround and you must always restore them (except for things you know you don't want - Bing bar, Silverlight (there are actually 5 WU for this @#%&#).... are two on my systems that are banned for good)

Give a shout if you need more help after you go through the process of restoring/updating.

If you don't need any further assistance, please mark this thread as solved and

have a wonderful holiday and a prosperous New Year

Bill
.

Thanks but this is a 5 day old computer. No data but test data for application installs. I hadn't even completed the application installs let alone switching this new one for my wife's dying XP.

FWIW, prior to failing in my attempts to get SURT to load and run--I had tried both the troubleshooter and FixIt. From the error I received attempting to revert to earlier restore point(s) it seems that there was a significant corruption in the system files from early in the update process.

Now that I've restored the drive from the Lenovo hidden partition, restore points doesn't want to turn on absent an error code. I'm leaving that one alone until I complete more of the update process in hopes that mess will clear itself.

I can see why folks make a good living off these things

Thanks,

Mark

 

[Layback Bear]

Small note: This is what I use and it works for me.
Check for updates but let me choose whether to download and install them.
I check Windows Updates 3 or 4 times a day.

 

[markg2]

Makes sense if you understand decision criteria.

So if it's an important update always yes, if not, why not?

If there's an optional update and it's for an installed device--always yes?

What update types would you tend to ignore?

 

[Layback Bear]

At this time I have three hidden. A Nvidia driver I don't want and two Bings. My method will also allow you to select one or two updates to download and install at a time instead of all at one time. Installing one or two Windows updates at a time and rebooting whether ask to or not allows you the ability to know which update might be causing a problem. This will give you a idea.

View attachment 246743

 

[Britton30]

Makes sense if you understand decision criteria.

So if it's an important update always yes, if not, why not?

If there's an optional update and it's for an installed device--always yes?

What update types would you tend to ignore?

For me I hide Silverlight too, for one, since it could have the same vulnerabilities as does Java, which I don't use. MS considers Silverlight important but I don't. Critical updates I always install since they often address some security issue but the reasons MS gives for what they do, is very cryptic and doesn't mean anything to a normal human.

For installed devices that's a personal preference. MS offers a driver for my Samsung monitor when installed I have a light beige background when I view pictures (I do that a lot). I have to go to the Colors console, jump through several hoops to reset a different default color profile. WU usually has older device drivers than the manufacturer has.

I have mine set as Jack does as well, Check for updates but let me choose whether to download and install them.
Also in a big list of found updates one may uncheck several, install a few, reboot and do a few more.

I experienced 4 updates that failed today and I did what the MS tech did, picked one to install, it succeeded, then got the rest, and some more came up then too. WU seems very buggy to me.

 

[markg2]

I can see where your update setting, which is also now mine, makes following the MS tech's approach to installing updates more second nature and practical to follow.

Thanks--

Mark

 

[Britton30]

You're welcome Mark, glad we could help.
Merry Christmas, Gary