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
    2013-01-10T18:51:16+00:00

    Wei. I've been dealing with this since November. I am sending you my CBS file because mine shows a completely different error than any I've seen here. I still cannot install update KB2685811. I'm beyond frustrated at this point. I am about to start a new semester, and I simply cannot have my pc reboot and lose any work that I might leave on screen overnight. Yes it's good form to save and quit, but I shouldn't be FORCED to do it.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-01-06T07:18:05+00:00

    I also received quite some emails that have the following error message. In this case, I cannot offer much help. Read on to check whether yours is the same:

    1. open cbs.log. search for "error " (notice the extra space at the end of it)
    2. if you find the following (note: complete message is at the end of this post):

        Info Detected corrupt repository. Trying to Recover data"

        Error MOF (install online) $(runtime.wbem)\Wdf01000.mof

        Error WMI repository data recovery Failed

    Then I'm out of luck. The suggestion I’ve given out is to 1) check for virus, and 2) try reset WMI repository.

    Some people do report back that they find virus infection and after cleaning it up the update is installed properly. Some others never replied, possibly my suggestion did not help them.

    Anyway, from what I have collected, the problem is not caused by the update KB2685811 itself; instead, the problem has already been there before KB2685811 was ever installed. The failure to install only makes the underline WMI corruption problem more visible to the user.

    Some other forum or people who is more familiar with WMI might be able to help, but I do not have any contact on my hand. Sorry about that.

    There is also no point for Microsoft to re-release a updated KB2685811 as the package itself is not the problem.

    As a last resort, the update KB2685811 is categorized as “recommended”, not “important”. Therefore you can safely ignore the installation failure, and hide it in Windows Update list, so that you won’t get notified to install it again and again.

    P.S. complete cbs.log:

    2013-01-04 23:28:45, Info                  CSI    00000001@2013/1/4:22:28:45.680 [70]"Install (Online) : Detected corrupt repository. Trying to Recover data"

    2013-01-04 23:28:46, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 61.

    2013-01-04 23:29:25, Error                 CSI    00000002 (F) Logged @2013/1/4:22:28:45.578 : [ml:100{50},l:98{49}]"MOF (install online) $(runtime.wbem)\Wdf01000.mof" [gle=0x80004005]

    2013-01-04 23:29:25, Error                 CSI    00000003 (F) Logged @2013/1/4:22:29:25.421 : [ml:138{69},l:136{68}]"Install (Online) : WMI repository data recovery Failed = -2147024770" [gle=0x80004005]

    2013-01-04 23:29:28, Error                 CSI    00000004@2013/1/4:22:29:28.873 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(ERROR_MOD_NOT_FOUND)  [

    [87]"An error occurred while opening the namespace for object 1 defined on lines 21 - 142:

    This posting is provided "AS IS" with no warranties, and confers no rights.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-01-03T18:09:07+00:00

    Reprinting this on Wei Mao's behalf with no warranty, real or implied.  The solution did work for me.

    Brilliant!  Thanks a million.  This was getting to the point where it was interfering with my network devices and becoming a serious issue.  Thanks for replying!

    On Thu, Jan 3, 2013 at 11:44 AM, Wei Mao <weimao@microsoft.com> wrote:

    Hi Matthew,

    Your problem seems to be the same as Naomi_D replied on December 18, 2012, on page 8 of the thread. Here is the same suggestion that was given to him:

     

    1 - start “command prompt” as administrator

    2 - cd \windows\system32\wbem

    3 - mofcomp.exe wmi.mof

     

    Reboot, try install the update again. If you still have any issue, send me a new cbs.log file.

     

    Best Regards,

    Wei Mao

     

    P.S. the original discussion on the topic: http://answers.microsoft.com/

     

    P.P.S. your cbs.log:

    2013-01-01 03:18:11, Error                 CSI    00000001@2013/1/1:09:18:11.802 (F) Logged @2013/1/1:09:18:07.231 : [ml:100{50},l:98{49}]"MOF (install online) $(runtime.wbem)\Wdf01000.mof" [gle=0x80004005]

    2013-01-01 03:18:11, Error                 CSI    00000002@2013/1/1:09:18:11.802 (F) CMIADAPTER: Inner Error Message from AI HRESULT = 80041002 [Error,Facility=FACILITY_ITF,

    [139]"An error occurred while creating object 1 defined on lines 21 - 142:

    0X80041002 Class, instance, or property 'EventTrace' was not found.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-01-02T03:31:14+00:00

    I have looked in my CBS log and get a ton of the following:

    2013-01-01 13:10:29, Info                  CBS    Session: 30271571_2850261514 initialized by client WindowsUpdateAgent.

    2013-01-01 13:10:29, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    It appears I have a corrupted package of some kind.  Can I remove it somehow and let it redownload?

    Was this answer helpful?

    0 comments