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 No 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 No comments

102 additional answers

Sort by: Oldest
  1. Anonymous
    2012-12-02T11:27:27+00:00

    [210]"Parsing MOF file: C:\Windows\system32\wbem\Wdf01000.mof

    Error 80 in Function CMofLexer::CMofLexer line 615

    C:\Windows\system32\wbem\Wdf01000.mof (1): error SYNTAX 0X8004402f: Error creating temporary file

    Hi,

    did you try to rename/delete the wdf01000.mof file? I think this is how I fix my problem with this update. Details are on page 4 of this thread.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-12-02T12:01:13+00:00

    Thanks for this thread.

     

    billmo -- what CD booted utility did you use to find the virus (Trojan) in wdf01000.sys?  I have pulled the HDD from my HP W7 laptop, connected it to my XP tower, and run both Malwarebytes and SUPERAntiSpyware against the drive. SAS did remove a trojan in a restore file, but when the drive was reconnected to the laptop, KB2685811 still fails to install.  Please update us with your results after you replace the wdf01000.sys file.  BTW, where did you get a clean copy of the file?

     

    Wei -- the error messages I find in cbs.log differ from the messages you outline in your post.  Instead, I see the following messages:

     

    2012-12-01 13:55:52, Error                 CSI    00000001@2012/12/1:21:55:52.751 (F) Logged @2012/12/1:21:55:03.596 : [ml:100{50},l:98{49}]"MOF (install online) $(runtime.wbem)\Wdf01000.mof"

    [gle=0x80004005]

    2012-12-01 13:55:52, Error                 CSI    00000002@2012/12/1:21:55:52.751 (F) CMIADAPTER: Inner Error Message from AI HRESULT = 8004402f [Error,Facility=FACILITY_ITF,Code=16431 (0x402f)]

     [

    [210]"Parsing MOF file: C:\Windows\system32\wbem\Wdf01000.mof

    Error 80 in Function CMofLexer::CMofLexer line 615

    C:\Windows\system32\wbem\Wdf01000.mof (1): error SYNTAX 0X8004402f: Error creating temporary file

     

     

    "

    ]

    [gle=0x80004005]

    2012-12-01 13:55:52, Error                 CSI    00000003@2012/12/1:21:55:52.751 (F) CMIADAPTER: AI failed. HRESULT = 8004402f [Error,Facility=FACILITY_ITF,Code=16431 (0x402f)]

          Element:

          [137]"<mof xmlns="urn:schemas-microsoft-com:asm.v3" name="$(runtime.wbem)\Wdf01000.mof" uninstallmof="$(runtime.wbem)\Wdf01000Uninstall.mof" />"

    [gle=0x80004005]

    2012-12-01 13:55:52, Error                 CSI    00000015@2012/12/1:21:55:52.751 (F) d:\win7sp1_gdr\base\wcp\cmiadapter\installers.cpp(352): Error 8004402f [Error,Facility=FACILITY_ITF,Code=16431 (0x402f)] originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::ResolveAndInvokeInstaller expression: hr

    [gle=0x80004005]

    2012-12-01 13:55:56, Error                 CSI    00000004@2012/12/1:21:55:56.277 (F) CMIADAPTER: Exiting with HRESULT code = 8004402f [Error,Facility=FACILITY_ITF,Code=16431 (0x402f)].

    [gle=0x80004005]

    2012-12-01 13:55:56, Error                 CSI    00000016@2012/12/1:21:55:56.277 (F) d:\win7sp1_gdr\base\wcp\cmiadapter\installers.cpp(123): Error 8004402f [Error,Facility=FACILITY_ITF,Code=16431 (0x402f)] originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::Install expression: hr

    [gle=0x80004005]

     

    I used AVG rescue disc that you can download from AVG site. It runs on Linux and you can therefore scan with AVG without booting the PC.  You then use the file manager utility to rename the file and to copy across the new copy that you need to have ready on a usb card. I got a copy of wdf01000.sys from another PC.

    Hope this makes sense

    Bill

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-12-03T10:18:21+00:00

    I tried to do the same, changing %USERPROFILE%/AppData/Local/Temp to C:/Temp and making sure that C:/Temp existed, but did not work.

    Have also tried the Microsoft FixIt, but still did not work.

    Cannot find a way to manually install it.

    I would like to know what else I can try?

    Was this answer helpful?

    0 comments No 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 No comments