Windows 8.1 updates failing to install error 800F0920

I don't know how to run dism without network access, so how would I do that?

Supposedly you just need another WinSxS at the same level to point to with the /source:  switch.

Since the Killer nic software is completely removed, that would explain why the Killer Bandwidth service is no longer there at all.

Right now, the NIC shows up as "other hardware", meaning that Windows does not recognize it and can't assign any driver to it.

I don't know how to run dism without network access, so how would I do that? I can certainly run sfc.

I am waiting to hear back from the NIC manufacturer (Qualcomm), but that probably won't be until Monday and maybe not even then. I've found them to be pretty slow at responding.

Well that didn't work. Perhaps running sfc/scannow and dism /online /cleanup-image /restorehealth /limitaccess is a worth a shot to see if a system file is corrupt.

I would expect that the wired NIC would try and use the Microsoft driver. Does the device show up unknown in the device manager? If you run those commands then try an install the NIC get me a CBS log so I can see if the failure reason is logged in there.

Maybe the NIC maker has a error log they write to on a failed install that could provide more detail. Another thing that might help is the hardware troubleshooter found in Troubleshooting in the control panel

BTW what is the error you get when the install fails or does it just not work.

If you really want to see what is going on you can use this http://www.microsoft.com/en-US/download/details.aspx?id=39982 to trace everything related to the PC. But it can be a little complicated if you have never used it.

The dam won't start unless you have Always On Always Connected abilities which would be for a tablet or phone. Iggnore that one that was an oversight by me. The other is Killer Bandwidth Control Filter Driver. I wonder if that is a symptom or a cause. If it is trying to start but the NIC is uninstalled that should be removed so it doesn't hang startup. I got those from the systems log file. Was that from a clean boot? Here is the log entry with the time

Log Name:      System

Source:        Service Control Manager

Date:          8/5/2014 2:09:06 PM

Event ID:      7026

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      Ben-Monster

Description:

The following boot-start or system-start driver(s) did not load:

AFD

ahcache

BfLwf

CSC

dam

Dfsc

FPAV_RTP

NetBIOS

NetBT

nsiproxy

Psched

rdbss

tdx

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

    <EventID Qualifiers="49152">7026</EventID>

    <Version>0</Version>

    <Level>4</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2014-08-05T21:09:06.939784100Z" />

    <EventRecordID>15052</EventRecordID>

    <Correlation />

    <Execution ProcessID="532" ThreadID="536" />

    <Channel>System</Channel>

    <Computer>Ben-Monster</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">

AFD

ahcache

BfLwf

CSC

dam

Dfsc

FPAV_RTP

NetBIOS

NetBT

nsiproxy

Psched

rdbss

tdx</Data>

  </EventData>

</Event>

The last part of my message was about services that failed to start for various reasons.

This could be part of the reason everything isn't working. See if the bold services were started if they aren't start them and either try the install of the NIC driver or if it is installed try to change the properties sheet. I don't know if these services and drivers aren't starting on a regular bases or just for updates. They may not start if the are disabled in msconfig you can check it out to make sure they didn't get unchecked by accident

You can check if these are running in sysinfo32 or by trying to start them in the CMD prompt like you did before.

These were drivers that needed to be started to start other services

• Redirected Buffering Sub System = rdbss
• NSI Proxy Service Driver = nsiproxy
• NetIO Legacy TDI Support Driver = tdx
• Ancillary Function Driver for Winsock = AFD ****

These drivers weren't listed other than not starting: ahcache, BfLwf, CSC, dam, Dfsc, FPAV_RTP, NetBIOS, NetBT, Psched. BfLwF and dam shouldn't be required to start so those can be ignored

And these were listed as not starting and are found in Services I listed the dependent drivers for the services to start. There are other dependencies for these Services but I assume they all started if you right click them properties > Dependencies 

• Workstation requires Network Store Interface
• Network Store Interface  **** requires nsiproxy
• TCP/IP NetBIOS Helper requires AFD
• DNS Client requires tdx
• DHCP Client requires AFD

And this one I don't know maybe you can help me with that: WebDav Client Redirector Driver

Did you check to see if those drivers and services were starting and running?

My first guess for the network adapter driver not installing is the registry still has a record from the old one and it is looking up the install.

Do you have a windows basic driver running the network or no network at all?

Look to see if any old registry keys are still present for the old driver and delete these. You can backup of your registry before editing it as I am sure you already know but I like to mention it when I give advice about editing it.

Also try deleting these keys/subkeys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Adapters\ {GUID}

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces{GUID}

To figure out which GUID should stay you can check the network adapters in device manager or delete them all then if it installs recreate the ones that do belong. If you reinstall the other network adapter those keys should be recreated then or on a restart

The first subkey, network/config, didn't exist.  For the other two, I did an export of the entire parameters subkey and then deleted it.  I then did a thorough search of the registry for references to Killer.  A found a few locations, and deleted them, but none stood out as a likely source of problems.

Thanks,

Ben