Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Some Windows security updates not loading

Jul 3, 2010 2:53PM PDT

I've been working with Microsoft Tech Support and trying to get this problem fixed. We've run through all the tips they had and now we're regretfully at the point where it looks like I need to blow away my system and reinstall Windows 7.

Here's the problem. For the last 4 months or so, my system has slowly been failing to install security updates. Right now, there are 14 updates that won't load. However, many other updates ARE loading just fine -- including updates to MSE.

Here are most of the files that won't load:
KB978607, KB979482m KB980846, KB981332, KB978542, KB980232, KB975496, KB981078, KB979683, KB980408, KB980218, KB979683, KB979559, KB981796

Here's essentially what Microsoft Tech Support has had me do:
Run the Windows Update Tool and System Readiness Tool
Rename the Windows Update Software Distribution Folder
fsutil resource setautoreset true C:\

Now we're at the "In-Place Upgrade" step... Before I did that, I thought I'd check to see if anyone here has any hints on this... My guess is that an important file is locked and I just need to find out what file is needed and unlock it...

Thanks in advance -- have a great holiday!
Steve

Discussion is locked

- Collapse -
How long have you run Windows?
Jul 3, 2010 9:13PM PDT

This issue is as old as it can be. New users tend to get upset by updates that don't install and could lose a lot of time and money over this one. Let me be very short here. The process is far from perfected.

My advice is to look at each update and decide if you can do without. For example I'll pick KB981796 which is for the issue "Japanese characters are displayed incorrectly in the Configuration Manager console after you use ConfigMgr Site Repair Wizard in ConfigMgr 2007 SP2"

It would be interesting to know if you use the "ConfigMgr Site Repair Wizard in ConfigMgr 2007 SP2".

While Microsoft could do better, what we learn is to look at the ones that don't install and decide to ignore it or fix it. I think you are trying to fix it. But that's a problem since it's too likely you don't have CongigMgr or do you?
Bob

- Collapse -
Of course, accuracy when I'm typing would help, too, right?
Jul 4, 2010 2:03AM PDT

@R. Proffit -- Thanks for the suggestions. To answer your question, I've been running Windows since there was a Windows - or to be specific, I believe I bought Windows 2.0 and never installed it, so I think Windows 3.0 or 3.11 was my first installed version. That would have been what, 1992? I've been using PCs since 1978 (TRS-80 Model w/16k ram) and supporting computers in a business environment since 1984. Today, I own my own business that supports SOHO computers and technology (http://completek.biz). I hope that helps determine how technical you can get in your replies to me...

Actually, the random update you chose was mistyped by me, it should have been:
KB981793 -- not KB981796

My bad.

That update is to fix a Daylight Savings Time issue, I believe, on x64-based systems.

Generally, the names for all of these updates are either "Security Update for Windows 7 for x64-based Systems" or "Update for Windows 7 for x64-based Systems." That's what led me to believe that eventually, one or more of these fixes unpatched will leave me with a vulnerability that a script kiddie in North Korea will exploit...

Again, thanks for any and all suggestions and help!

- Collapse -
No problem.
Jul 4, 2010 3:14AM PDT

Sorry I picked the last item on your list. It was by sheer luck I suppose it was one that didn't apply.

Ok, what I know is that Microsoft's KB system is far from perfect with many examples so let's move to possible solutions that many of the moderators have used.

1. For the .NET fiasco (uh, KB?) we uninstall .NET and that usually does it. There's a long discussion with a rather nice ROOT CAUSE found. To place the blame here it's both Microsoft and that other company at fault. The company's app did something wrong and that uncovered a flaw in the KB's rollback system. Fingers are pointing in all directions with confused owners by the thousands.

At least we know how to cure that one but how to explain it without owners getting a bad feeling about all the steps?

2. For many other KB updates I know to manually download the patch, boot safe mode and try there. Safe mode stops many things that can interfere.

3. KB RESEARCH can't be understated. I've lost count of how many times a KB for "IIS" won't install but the owner didn't install IIS, IIS is not to be found and the owner doesn't know what IIS is. After we are sure IIS is not installed we set that one to ignore.

Hope this helps,
Bob