Failure configuring Windows update KB2685811

Anonymous

On Windows 7 pro x64 with SP1, I've been getting this message when rebooting after installing KB2685811 ("Update for Kernel-Mode Driver Framework version 1.11 for Windows 7 for x64-based Systems"): "Failure configuring Windows update". All updates from last Tuesday (13/Nov/2012) were installed correctly, only this one fails.

I tried...

Rebooting, F8 and then using repair. It detected no errors.

Installing the patch with the antivirus (Avira free) disabled, which changed nothing.

Downloading the update manually and installing it. Made no difference.

Installing KB947821, found here: https://www.microsoft.com/en-us/download/details.aspx?id=20858

I then found a file I had downloaded yesterday (can't remember where from) called windowsupdate.diagcab

I ran it and it detected 2 errors:

[a] Potential Windows update database error detected (0x80070002)

[b] Problem with Background Intelligent Transfer Service (BITS)

I eventually solved [a] and [b] with MicrosoftFixit50202.msi, but not the original problem. I still get the "Failure configuring Windows update" message after rebooting, once the installation reaches 61%.

There were a couple of other things I did, but I can't remember exactly what they were...

Any help is appreciated.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

I had the same problem and found a solution.

For this update, TEMP file location should be set to default C:.

I changed Temp file location from RAM disk to C:\ for this update and it worked. Thereafter I changed the Temp file location back to RAM disk.

0 comments

102 additional answers

Anonymous

2012-11-20T20:13:59+00:00
First of all, as always, backup your important files before doing anything. Even there should not be a big risk for messing the system, with computers anything can happen. Specially if there is a problem with hardware, which seems to be the initial reason for WMI failures in my computer. A year ago I had a memory fault with two of four Corsair Dominator memories. Replaced them with a set of Kingstons and Memtest86+ memory test showed no error after running through all night. Last July my computer crashed during Windows Update and after running just few minutes, memory test found errors in reminding two Corsair dimms. I removed them reducing mem size to 4 GB and everything looked fine. Apparently something was messed with WMI, but it didn't come up at that time. There is no way any desktop operating system can handle hardware failures reliably even if modern operating systems are quite stable. So do your backups. There is no quarantee these instructions will work in every case but here goes:
1. Disconnect from internet. This might not be necessary, but just to be on the safe side.
- Pull out ethernet cable or
- Turn off wlan or
- Disconnect USB broadband connection or
- Disconnect network connections from Control Panel-> Network and Internet-Network Connections (File-Disconnect) or
- What ever way you computer connects to internet.
Note: Might be a good idea to copy/paste these instruction to a file before disconnecting

from internet.
1. Start Command Prompt in administrator mode. Right click from the Start menu Start->All Programs->Accessories->Command Prompt. Choose "Run as adminstrator" from the menu.
2. Click "Yes" when Windows asks "Do you want to allow following program to make changes to this computer"
3. In command promt run:
winmgmt /resetrepository

You should get an error message:

"WMI repository reset failed

Error code:     0x8007041B

Facility:       Win32

Description:    A stop control has been sent to a service that other running services are dependent on."

and see a tray icon message:

"Turn on Windows Security Center service.

The Windows Security Center service is turned off.

Click to turn on."

DO NOT click the icon. Leave Security Center service off.

Run "winmgmt /resetrepository" command again. Now it should reset the WMI.
1. Turn on Windows Security Center service by clicking message icon in the tray, right bottom corner of the screen. Select "Turn on Windows Security Center service (Important)". You can also turn it on from Control Panel->System and Security->Action Center. You can also reconnect to internet now if you want. Note: Window does not need internet connection for update if updates are already downloaded.
2. Start Control Panel->System and Security->Windows Update. If you have more than one important upgrades available select only KB2685811 for now. Windows update will reverse all selected upgrades if even a single one fails. You can update other ones later. Run the update and see how it goes.
Was this answer helpful?

0 comments No comments
Anonymous

2012-11-21T23:59:12+00:00

HerrGoo,

Could you please try:

- Reproduce the problem one more time

- Copy the file \windows\logs\cbs\cbs.log to a temp folder, and compress it

- Send the file to : w e i m a o / a t / m i c r o s o f t ~do t ~ c om (remove all spaces)

This posting is provided "AS IS" with no warranties, and confers no rights.
Was this answer helpful?

0 comments No comments
Anonymous

2012-11-22T08:52:56+00:00

I have tried to set env variable = C:\ or C:\TEMP. And test serveral, cannot solve my window update failure problem.
Was this answer helpful?

0 comments No comments
Anonymous

2012-11-22T13:18:56+00:00

Thx - after checking the log the problem was obvious, there were some temporary files that couldn't be deleted in C:\windows\winsxs\temp - I booted with Ubuntu CD, deleted them, rebooted to windows and the update kb2685811 installed just fine.

All I tried before as setting %temp% to C:\temp, reseting repository etc. didn't work

Regards

More specific as I was asked - I deleted all folders and files in C:\windows\winsxs\temp

I didn't try to do it from Windows as some files are locked, so I booted from Ubuntu CD and deleted all this way. If you need to do it from Windows then maybe a tool like Unlocker will help, for me Ubuntu was better option.

I'm not sure if deleting all the files there is safe, so consider yourself warned :)

I just have another computer with similar problem, but errors in cbs.log look different so my solution will probably not work on this one, so it is far from universal.
Was this answer helpful?

0 comments No comments