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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-12-09T18:22:43+00:00

    I had some time this morning so I returned to this problem.  I booted from the Windows 7 install disk and used SHIFT-F10 at the login screen to bring up a command prompt.  I navigated to the windows\system32\wbem directory and typed

    ren Wdf01000.mof Wdf01000.old

    ren Wdf01000Uninstall.mof Wdf01000Uninstall.old

    I then rebooted to Windows 7 normally and used Windows Update to re-attempt the install of KB2685811.  No change from previous attempts; after reboot, the install resumes but fails after about 61% and the install is backed out.

    Any further ideas?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-12-04T23:54:20+00:00

    Tried also doing a clean boot. Still no good. Have looked at some other threads RE: CBS.log file and found numerous entries about 'Invalid package'. However, as I am not an expert, reading this file and knowing what it means is not within my knowledge base! Also seen posts about WMI and using WMIDIAG.EXE, but reading the results of this is fairly difficult, let alone knowing whether I have run it in the right mode or not. When will this update be fixed so that it just installs please Microsoft?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-12-03T17:45:36+00:00

    Hi tartans90,

    Last time you mentioned you were struggling to copy cbs.log file. Have you figured it out? You can send the file to me once it is done.

    • To troubleshoot the failure of installing Windows updates, it would better start with checking \windows\logs\cbs\cbs.log file.

     - Note the file is protected, and you need admin privilege to access it. To do so, right click "command prompt" icon, select "run as admin", and run "copy \windows\logs\cbs\cbs.log %USERPROFILE%\Documents".

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-12-03T15:16:10+00:00

    Having followed this thread's updates since my first post, I've yet to see a solution that seems conclusive and, more importantly for me, lacking complication and some risk. My take is that the wdf01000.sys seems to be the issue, but the instructions to address the issue aren't an option for someone who knows just enough to try and follow this conversation so to maybe solve the issue but is very gunshy about attempting some of these fixes. Is there a point when Microsoft will issue an alternative update to this one? I've installed my other updates successfully, but still get stuck at the 61% configured and then the reverting.

    Was this answer helpful?

    0 comments