Failure configuring Windows update KB2685811

Anonymous
2012-11-16T15:17:43+00:00

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.

Windows for home | Previous Windows versions | Windows update

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
2012-11-16T23:55:33+00:00

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.

Was this answer helpful?

10+ people found this answer helpful.
0 comments

102 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2012-11-26T18:39:50+00:00

    Yet again I tried the temp folder thing  this time in windows\system32\temp but it still doesn't work.  I deleted the temp folder contents and the wsbxs temp folder contents again but it still fails.

    FYI Mine fails at 35% so tartans90 is doing better than me. Mine also stalls before this for a while at "applying operation 3 (or 7 sometimes) of 122 wdfres.dll" if this means anything.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-11-26T18:09:45+00:00

    After successfully installing each update manually except this one, I tried this TEMP change as it was endorsed. It did not work for me, failing yet again at 61% of the configuration. At this point I am not going to waste any more time on it and hope that there is a solution from Microsoft in the next round of updates. This has been very frustrating as I tried clean boots and the other suggestions that I felt confident doing.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2012-11-26T10:13:53+00:00

    Hi all!

    So based on two recent cases with KB2685811 not installing.

    As pointed by Wei Mao you need to inspect cbs.log (i use Notepad ++ for the job)

    In the first case I had error with 5 files in C:\windows\winsxs\temp that couldn't be deleted so I booted with Ubuntu CD and deleted all content of C:\windows\winsxs\temp which then allowed for the update to install fine.

    Second case - with Wei Mao help who pointed to error:

     Error 80 in Function CMofLexer::CMofLexer line 615 C:\Windows\system32

    \wbem\Wdf01000.mof (1): error  in my cbs.log

    I again booted with Ubuntu CD, renamed the following files C:\Windows\system32

    \wbem\Wdf01000.mof and C:\Windows\system32

    \wbem\Wdf01000uninstall.mof (i didn't delete them just in case)

    then the problematic update installed fine.

    So inspect your cbs.log and hope for the best :)

    Peter

    Tried these along with the moving the temp folder.  Still doesn't work.  I am no expert and this is very frustrating.

    Bill

    Was this answer helpful?

    0 comments