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-28T12:07:03+00:00

    Hi Wei,

    great findings! You finally made me solve this. I can now install KB2685811 and KB2592687 without issues!

    I used your blog to recreate the WMI repoistory. And it was the very last approach, to rebuild the repo manually, which was able to repair/recreate a working and no longer corrupted repository.

    Thank you!

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-11-27T19:58:07+00:00

    I received some cbs.log file which points out the issue is due to corrupted WMI repository.

    Searching around and I found the following blog which describes how to reset repository to the initial state when the OS was first installed. Please give it a try.

    http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx

    http://blogs.technet.com/b/askperf/archive/2012/02/03/wmidiag-2-1-is-here.aspx

    P.S. here is the logs:

    2012-11-26 23:21:44, Info                  CSI    00000014 Begin executing advanced installer phase 32 (0x00000020) index 8 (sequence 41)

        Old component: [ml:318{159},l:316{158}]"Microsoft-Windows-WDF-Kernel Library, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"

        New component: [ml:318{159},l:316{158}]"Microsoft-Windows-WDF-Kernel Library, Culture=neutral, Version=6.1.7601.17803, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"

        Install mode: install

        Installer ID: {9f4ec79f-3a97-4772-b635-2899468900a2}

        Installer name: [3]"Mof"

    2012-11-26 23:21:44, Info                  CSI    00000001@2012/11/26:22:21:44.982 [70]"Install (Online) : Detected corrupt repository. Trying to Recover data"

    2012-11-26 23:21:45, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 61.

    2012-11-26 23:23:07, Error                 CSI    00000002 (F) Logged @2012/11/26:22:21:44.842 : [ml:100{50},l:98{49}]"MOF (install online) $(runtime.wbem)\Wdf01000.mof"

    2012-11-26 23:23:07, Error                 CSI    00000003 (F) Logged @2012/11/26:22:23:07.010 : [ml:138{69},l:136{68}]"Install (Online) : WMI repository data recovery Failed = -2147024770"

    2012-11-26 23:23:10, Error                 CSI    00000004@2012/11/26:22:23:10.926 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(ERROR_MOD_NOT_FOUND)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-11-26T22:39:53+00:00

    Bill's cbs.log shows that updating wdf01000.sys failed with "sharing violation", which typically means anti-virus program plays a role here.

      Status = STATUS_SHARING_VIOLATION, Operation = HardLinkFile, DiagString = [l:342{171}]"\SystemRoot\WinSxS\x86_microsoft-windows-wdf-kernellibrary_31bf3856ad364e35_6.1.7600.17013_none_767300c37f08da42\Wdf01000.sys, ??\C:\Windows\System32\drivers\Wdf01000.sys"

    Bill confirms that his AVG 2013 did report a virus issue with wdf01000.sys recently. He is going to clean that up first.

    Note: wdf01000.sys is indeed part of KB2685811.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-11-26T19:54:56+00:00

    bilmo / tartans90 / lldaedalusll,

    You can send the cbs.log file to me (email address provided in my first post on Nov 21). I cannot fix all problems out there; but I'll try isolate whether the problem is directly caused by KB2685811 or not. Thanks,

    Thanks Wei - I have sent it to you

    Bill

    Was this answer helpful?

    0 comments