Windows 8.1 updates failing to install error 800F0920

Anonymous
2014-07-02T18:01:45+00:00

My Win 8.1 Pro system was working fine until a few weeks ago when suddenly Windows Updates became broken.  The typical scenario is to choose one or more updates to install, it gets partway through, then reboots, then gets further along (to about 75%), then announces it can't finish the installation and has to roll back the install.  In the end, the update isn't installed.  The whole process takes hours and hours.  The first few times this happened it was in the middle of the work day and I lost use of the computer throughout the whole afternoon.

I researched the many, many similar problems that other people have experience and tried all the suggested solutions involving DSIM, SFC, deleting/renaming the update folder and files, booting "clean", and so on.  I even wrote a simple batch file to do most of this (copy at the end of this post) because I was doing it so often.  I was gradually able to get most of the updates for Windows and Office installed, except for three updates.  For those three, I cannot install them no matter what.  They are (required updates) , KB2955164, KB2966804, and Optional Update KB2962409.  I'll post the full error messages below.

The other new problem I've noticed with this system is that I can no longer change the network properties.  I was doing some tweaking on the network and I wanted to set the PC's IP address to a specific address (instead of using DHCP) and I couldn't change it. That may or may not be related -- I haven't researched it much at this point.

So, does anyone have any suggestions? It's hard to keep trying different ideas that don't work because it's so time consuming.  Since this system is at my office and I don't want to interrupt work again, I can only try doing updates at the end of the work day, and I find out the next morning whether or not it work.

Here are the error messages. You will see that the error codes are  all 800F0920.  Originally, my error codes were all either 80080005 or 80242014 and involved about a dozen updates.  So this is progress of a sorts.

**********************************

**********************************

Update for Windows 8.1 for x64-based Systems (KB2955164)

Installation date: ‎6/‎27/‎2014 6:53 PM

Installation status: Failed

Error details: Code 800F0920

Update type: Important

Install this update to resolve issues in Windows. For a complete listing of

the issues that are included in this update, see the associated Microsoft

Knowledge Base article for more information. After you install this item, you

may have to restart your computer.

More information:

http://support.microsoft.com/kb/2955164

Help and Support:

http://support.microsoft.com

*************************************************

Update for Windows 8.1 for x64-based Systems (KB2966804)

Installation date: ‎6/‎27/‎2014 6:53 PM

Installation status: Failed

Error details: Code 800F0920

Update type: Recommended

Install this update to resolve issues in Windows. For a complete listing of

the issues that are included in this update, see the associated Microsoft

Knowledge Base article for more information. After you install this item, you

may have to restart your computer.

More information:

http://support.microsoft.com/kb/2966804

Help and Support:

http://support.microsoft.com

************************************************

Update for Windows 8.1 for x64-based Systems (KB2962409)

Installation date: ‎6/‎27/‎2014 6:53 PM

Installation status: Failed

Error details: Code 800F0920

Update type: Optional

Install this update to resolve issues in Windows. For a complete listing of

the issues that are included in this update, see the associated Microsoft

Knowledge Base article for more information. After you install this item, you

may have to restart your computer.

More information:

http://support.microsoft.com/kb/2962409

Help and Support:

http://support.microsoft.com

**********************************

**********************************

And here is the batch file I use to reset pretty much everything related to the Windows Update process.  It does not include SFC, which I usually do separately.

**********************************

DISM.exe /Online /Cleanup-image /Restorehealth

pause

net stop bits

net stop wuauserv

net stop appidsvc

net stop cryptsvc

Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

Ren %systemroot%\SoftwareDistribution SoftwareDistribution8.bak

Ren %systemroot%\system32\catroot2 catroot2-4.bak

pause

sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

pause

cd /d %windir%\system32

regsvr32.exe atl.dll

regsvr32.exe urlmon.dll

regsvr32.exe mshtml.dll

regsvr32.exe shdocvw.dll

regsvr32.exe browseui.dll

regsvr32.exe jscript.dll

regsvr32.exe vbscript.dll

regsvr32.exe scrrun.dll

regsvr32.exe msxml.dll

regsvr32.exe msxml3.dll

regsvr32.exe msxml6.dll

regsvr32.exe actxprxy.dll

regsvr32.exe softpub.dll

regsvr32.exe wintrust.dll

regsvr32.exe dssenh.dll

regsvr32.exe rsaenh.dll

regsvr32.exe gpkcsp.dll

regsvr32.exe sccbase.dll

regsvr32.exe slbcsp.dll

regsvr32.exe cryptdlg.dll

regsvr32.exe oleaut32.dll

regsvr32.exe ole32.dll

regsvr32.exe shell32.dll

regsvr32.exe initpki.dll

regsvr32.exe wuapi.dll

regsvr32.exe wuaueng.dll

regsvr32.exe wuaueng1.dll

regsvr32.exe wucltui.dll

regsvr32.exe wups.dll

regsvr32.exe wups2.dll

regsvr32.exe wuweb.dll

regsvr32.exe qmgr.dll

regsvr32.exe qmgrprxy.dll

regsvr32.exe wucltux.dll

regsvr32.exe muweb.dll

regsvr32.exe wuwebv.dll

netsh winsock reset

pause

dism /Online /Cleanup-Image /StartComponentCleanup

**********************************

Thanks,

Ben

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

81 answers

Sort by: Newest
  1. Anonymous
    2014-08-05T23:40:39+00:00

    I thought it might be useful to capture some of the events from some of the event logs (not all events).  I downloaded a sample of error events into text files and they can be seen at this link: https://onedrive.live.com/redir?resid=9F39A85E3B815424!130&authkey=!AMd1FAyJ7iSrSA0&ithint=folder%2c.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-08-05T14:02:18+00:00

    Are you familiar with xperf?

    @ Dan

    Synchronicity.   Yesterday I found a page which says instead of using xperf and xbootmgr we (W8.1 users) should be looking at  WPR or WPRUI...

    http://windowswideopen.com/category/wpr/

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-08-05T08:30:52+00:00

    That is true. I figured the netsh commands would fail. But hoping it would have a better explanation why.

    When you brought up the event report it made be think of the event logs. There should have been a failure listed when the update failed at 75%. There may be more helpful info in the event logs about netcfg and WiFi systems driver

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-08-05T07:23:13+00:00

    Looking through the folder for the NIC management suite (Killer e2200), I noticed a diagnostic reporting tool.  Most of it's output was generic stuff describing the hardware (motherboard, video card, etc.), but then it go to the last bit about diagnostics.  I'm not sure if this will help, but here is what is reported:


    Diagnostics


    Windows Error Reporting:

    +++ WER0 +++:

    Fault bucket -471574108, type 5

    Event Name: PnPDriverInstallError

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: 00000002

    P3: nettun.inf

    P4: fd0e248e866e83a11bb3e3800c25d0172a7290df

    P5: TEREDO.ndi

    P6:

    P7:

    P8:

    P9:

    P10:

    +++ WER1 +++:

    Fault bucket , type 0

    Event Name: PnPDriverInstallError

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: 00000002

    P3: nettun.inf

    P4: fd0e248e866e83a11bb3e3800c25d0172a7290df

    P5: TEREDO.ndi

    P6:

    P7:

    P8:

    P9:

    P10:

    +++ WER2 +++:

    Fault bucket 90347178687, type 5

    Event Name: PnPDeviceProblemCode

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: USB\VID_04E8&PID_6860&REV_0400&MS_COMP_MTP&SAMSUNG_Android_SPH-P500

    P3: {eec5ad98-8080-425f-922a-dabf3de3f69a}

    P4: 0000000A

    P5: WUDFRd.sys

    P6: 6.3.9600.17195

    P7: 05-31-2014

    P8:

    P9:

    P10:

    +++ WER3 +++:

    Fault bucket 90347178687, type 5

    Event Name: PnPDeviceProblemCode

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: USB\VID_04E8&PID_6860&REV_0400&MS_COMP_MTP&SAMSUNG_Android_SPH-P500

    P3: {eec5ad98-8080-425f-922a-dabf3de3f69a}

    P4: 0000000A

    P5: WUDFRd.sys

    P6: 6.3.9600.17195

    P7: 05-31-2014

    P8:

    P9:

    P10:

    +++ WER4 +++:

    Fault bucket -741469907, type 5

    Event Name: PnPDriverNotFound

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: PCI\VEN_1969&DEV_E091&SUBSYS_78211462&REV_13

    P3:

    P4:

    P5:

    P6:

    P7:

    P8:

    P9:

    P10:

    +++ WER5 +++:

    Fault bucket -471574108, type 5

    Event Name: PnPDriverInstallError

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: 00000002

    P3: nettun.inf

    P4: fd0e248e866e83a11bb3e3800c25d0172a7290df

    P5: TEREDO.ndi

    P6:

    P7:

    P8:

    P9:

    P10:

    +++ WER6 +++:

    Fault bucket , type 0

    Event Name: PnPDriverInstallError

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: 00000002

    P3: nettun.inf

    P4: fd0e248e866e83a11bb3e3800c25d0172a7290df

    P5: TEREDO.ndi

    P6:

    P7:

    P8:

    P9:

    P10:

    +++ WER7 +++:

    Fault bucket , type 0

    Event Name: PnPDriverNotFound

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: PCI\VEN_1969&DEV_E091&SUBSYS_78211462&REV_13

    P3:

    P4:

    P5:

    P6:

    P7:

    P8:

    P9:

    P10:

    +++ WER8 +++:

    Fault bucket -471574108, type 5

    Event Name: PnPDriverInstallError

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: 00000002

    P3: nettun.inf

    P4: fd0e248e866e83a11bb3e3800c25d0172a7290df

    P5: TEREDO.ndi

    P6:

    P7:

    P8:

    P9:

    P10:

    +++ WER9 +++:

    Fault bucket , type 0

    Event Name: PnPDriverInstallError

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: x64

    P2: 00000002

    P3: nettun.inf

    P4: fd0e248e866e83a11bb3e3800c25d0172a7290df

    P5: TEREDO.ndi

    P6:

    P7:

    P8:

    P9:

    P10:


    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-08-05T07:22:49+00:00

    There seem to be two main possibilities: the networking problems are causing the update problems or there is a third issue that is causing both the networking and update problems.  I'd really like to get the networking issue fixed but I'm at a standoff right now.  I'll admit I didn't try uninstalling in Safe Mode but my guess is that that won't make any difference.  I did try actually turning off the NIc in the motherboard bios but that didn't help.  I'm hoping that Qualcomm, the manufacturer of the NIc chipset, will have some ideas. I didn't try any netsh commands but those won't have any higher priority than the uninstall routines that didn't work.

    Was this answer helpful?

    0 comments No comments