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-30T03:19:17+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.

    Thanks for the help Wei

    Using a CD booted utility I found that the virus (Trojan) still existed in wdf01000.sys but somehow masked from a normal boot virus scan.   I managed to replace wdf01000.sys with a clean version (the new version in fact from another PC) and the update worked.  Hopefully the process cleaned up any errors that may have occurred due to not replacing with the original version.  Now to try SP1 to see if it now works?

    Thanks again for being a great help.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-11-28T18:34:41+00:00

    Having said that, the other updates installed without problem. It was only the KB2685811 that failed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-11-28T18:32:30+00:00

    It's AMD's Radeon Ramdisk.

    But I believe the problem is simple: I had to set it to not save a disk image on shutdown and reload it at startup (I had to due to a bug\problem\whatever). So, everytime it starts, it's empty. That's why I needed to use a standard hdd. Probably it didn't even needed to be the Windows partition; I didn't try, but I suspect any would do, as long as the content of the Temp folder wasn't deleted before the update was over.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-11-28T18:32:15+00:00

    To all who read this thread:

    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".

    Different scenarios as unveiled by cbs.log file are:

     - Some people installed a ramdisk program, and set TEMP environment variable to point to the ramdisk. Look like during updating / reboot cycle, the ramdisk program is not started yet, and thus if updating need to access TEMP folder, it will fail. The solution is to change TEMP to point to its original location, e.g. %LOCALAPPDATA%\temp, or %windir%\temp

        * cbs.log: I've not seen it yet. But people do confirm it solves their problem.

        * cbs.log: 2012-11-26 19:16:09, Error CSI 00000003 (F) Logged @2012/11/27:00:16:09.328 : [ml:138{69},l:136{68}]"Install (Online) : WMI repository data recovery Failed = -2147024770"

    • Some reports wdf01000.sys cannot be moved due to sharing violation. It later was confirmed to be related to anti-virus programs or maybe the system was indeed attacked by virus.

        * cbs.log: 2012-11-25 20:24:09, Error CSI 00000006 (F) Error: ResolvePendingTransactions called after poqexec failure (call 1). 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"

    Also note that none of the above problems are directly related nor caused by the update KB2685811 itself; the KB2685811 is merely a victim of inconsistent system state.

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

    Was this answer helpful?

    0 comments