Npcap Bug Report - error 8007007e

[marcin-gryszkalis]

Trying to install npcap 0.9983 on Windows 10.

C:\Program Files\Npcap>NPFInstall.exe -u
Npcap LWF driver has failed to be uninstalled.

C:\Program Files\Npcap>NPFInstall.exe -i
Unknown error! 8007007e
Npcap LWF driver has failed to be installed.

setupapi.dev.log says:

>>>  [SetupCopyOEMInf - C:\Program Files\Npcap\NPCAP.inf]
>>>  Section start 2019/09/18 10:33:12.266
      cmd: NPFInstall.exe  -i
     inf: Copy style: 0x00000000
!    inf: Driver package is already in driver store
     sto: {Setup Import Driver Package: C:\Program Files\Npcap\NPCAP.inf} 10:33:12.269
     sto:      Driver package already imported as 'oem2.inf'.
     sto: {Setup Import Driver Package - exit (0x00000000)} 10:33:12.274
     inf: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\npcap.inf_amd64_328479d0c4fcaa92\npcap.inf
     inf: Published Inf Path: C:\WINDOWS\INF\oem2.inf
<<<  Section end 2019/09/18 10:33:12.278
<<<  [Exit status: SUCCESS]


>>>  [Install network driver - INSECURE_NPCAP]
>>>  Section start 2019/09/18 10:33:12.283
      cmd: NPFInstall.exe  -i
     dvi: Driver is already installed; no work to do
     dvi: Committing changes to the network graph
<<<  Section end 2019/09/18 10:33:12.322
<<<  [Exit status: FAILURE(0x8007007e)]

DiagReport on the other side says

InstallTimeStamp : {227, 7, 8, 0...}
Characteristics  : 262144
ComponentId      : INSECURE_NPCAP
Description      : @oem95.inf,%npf_desc_standard%;Npcap Packet Driver (NPCAP)
InfPath          : oem95.inf
InfSection       : FilterStandard
LocDescription   : @oem95.inf,%npf_desc_standard%;Npcap Packet Driver (NPCAP)
                   6e974-e325-11ce-bfc1-08002be10318}\{7DAF2AC8-E9F6-4765-A842-F1F5D2501341}
                   6e974-e325-11ce-bfc1-08002be10318}

oem95.inf doesn't exist in Windows\INF, oem2.inf (and .PNF) do exist.

> pnputil -f -d c:\Windows\INF\oem2.inf
Microsoft PnP Utility
Deleting the driver package failed : Parametr jest niepoprawny. [transl.: invalid parameter]

[marcin-gryszkalis]

DiagReport-20190918-122951.txt

[marcin-gryszkalis]

Note: installing nmap with KM-TEST loopback fails too, setupapi.dev.log says:

>>>  [Device Install (DiShowUpdateDevice) - ROOT\NET\0001]
>>>  Section start 2019/09/18 11:38:27.291
      cmd: "C:\WINDOWS\system32\mmc.exe" "C:\WINDOWS\system32\compmgmt.msc" /s
     dvi: {DIF_UPDATEDRIVER_UI} 11:38:27.292
     dvi:      Default installer: Enter 11:38:27.293
     dvi:      Default installer: Exit
     dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 11:38:27.294
     ndv: {Update Driver Software Wizard - ROOT\NET\0001}
     ndv:      Search options: 0x00000203
     ndv:      Searching currently installed INF
     dvi:      {Build Driver List} 11:38:29.275
     dvi:           Searching for hardware ID(s):
     dvi:                *msloop
     dvi:      {Build Driver List - exit(0x00000000)} 11:38:29.278
     ndv:      Searching default INF path
     dvi:      {Build Driver List} 11:38:29.280
     dvi:           Searching for hardware ID(s):
     dvi:                *msloop
     dvi:           Created Driver Node:
     dvi:                HardwareID   - *MSLOOP
     dvi:                InfName      - C:\WINDOWS\System32\DriverStore\FileRepository\netloop.inf_amd64_c53a2ac7a82dcc49\netloop.inf
     dvi:                DevDesc      - Microsoft KM-TEST Loopback Adapter
     dvi:                Section      - kmloop.ndi.NT
     dvi:                Rank         - 0x00ff0000
     dvi:                Signer Score - INBOX
     dvi:                DrvDate      - 06/21/2006
     dvi:                Version      - 10.0.17763.1
     dvi:      {Build Driver List - exit(0x00000000)} 11:38:29.398
     dvi:      {DIF_SELECTBESTCOMPATDRV} 11:38:29.528
     dvi:           Default installer: Enter 11:38:29.529
     dvi:                {Select Best Driver}
     dvi:                     Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:                     Selected Driver:
     dvi:                          Description - Microsoft KM-TEST Loopback Adapter
     dvi:                          InfFile     - c:\windows\system32\driverstore\filerepository\netloop.inf_amd64_c53a2ac7a82dcc49\netloop.inf
     dvi:                          Section     - kmloop.ndi
     dvi:                {Select Best Driver - exit(0x00000000)}
     dvi:           Default installer: Exit
     dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 11:38:29.537
     sto:      {Setup Import Driver Package: C:\WINDOWS\INF\netloop.inf} 11:38:29.545
     sto:           Driver package already imported as 'netloop.inf'.
     sto:      {Setup Import Driver Package - exit (0x00000000)} 11:38:29.549
     dvi:      Searching for hardware ID(s):
     dvi:           *msloop
     dvi:      Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:      {Plug and Play Service: Device Install for ROOT\NET\0001}
     dvi:           Driver INF Path: C:\WINDOWS\INF\netloop.inf
     dvi:           Driver Node Name: netloop.inf:db04a16c8f2dc9fb:kmloop.ndi:10.0.17763.1:*msloop,
     dvi:           Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\netloop.inf_amd64_c53a2ac7a82dcc49\netloop.inf
     dvi:           Searching for hardware ID(s):
     dvi:                *msloop
     dvi:           Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:           {Core Device Install} 11:38:29.621
     dvi:                {Install Device - ROOT\NET\0001} 11:38:29.623
     dvi:                     Device Status: 0x01802401, Problem: 0x1c (0x00000000)
     dvi:                     Parent device: HTREE\ROOT\0
     dvi:                     {Configure Device - ROOT\NET\0001} 11:38:29.630
     dvi:                          Device Status: 0x01802401, Problem: 0x1c (0x00000000)
     dvi:                          Parent device: HTREE\ROOT\0
     sto:                          {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\netloop.inf_amd64_c53a2ac7a82dcc49\netloop.inf}
     sto:                               Source Filter  = *msloop
     inf:                               Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:                               Class Options  = Configurable
     inf:                               {Configure Driver: Microsoft KM-TEST Loopback Adapter}
     inf:                                    Section Name = kmloop.ndi.NT
     inf:                                    {Add Service: kmloop}
     inf:                                         Start Type    = 3
     inf:                                         Service Type  = 1
     inf:                                         Error Control = 1
     inf:                                         Image Path    = \SystemRoot\System32\drivers\loop.sys
     inf:                                         Display Name  = Microsoft KM-TEST Loopback Adapter Driver
     inf:                                         Group         = NDIS
     inf:                                         Updated service 'kmloop'.
     inf:                                    {Add Service: exit(0x00000000)}
     inf:                                    Hardware Id  = *MSLOOP
     inf:                                    {Configure Driver Configuration: kmloop.ndi.NT}
     inf:                                         Service Name  = kmloop
     inf:                                         Config Flags  = 0x00000000
     inf:                                    {Configure Driver Configuration: exit(0x00000000)}
     inf:                               {Configure Driver: exit(0x00000000)}
     flq:                               Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\netloop.inf_amd64_c53a2ac7a82dcc49\loop.sys' to 'C:\WINDOWS\System32\drivers\loop.sys'.
     cpy:                               Existing file 'C:\WINDOWS\System32\drivers\loop.sys' remains unchanged.
     sto:                          {Configure Driver Package: exit(0x00000000)}
     dvi:                          Install Device: Configuring device (netloop.inf:*msloop,kmloop.ndi.NT). 11:38:29.679
     dvi:                          Install Device: Configuring device completed. 11:38:29.683
     dvi:                          Device Status: 0x01802001, Problem: 0x0 (0x00000000)
     dvi:                          Install Device: Starting device 'ROOT\NET\0001'. 11:38:29.685
     dvi:                          Install Device: Starting device completed. 11:38:29.690
!    dvi:                          Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000.
     dvi:                     {Configure Device - exit(0x00000000)} 11:38:29.692
     dvi:                     Device Status: 0x01802401, Problem: 0x38
     dvi:                {Install Device - exit(0x00000000)} 11:38:29.696
     dvi:           {Core Device Install - exit(0x00000000)} 11:38:29.698
     dvi:           Waiting for device post-install to complete. 11:38:29.702
!!!  dvi:           Timed out waiting for device post-install to complete. 11:42:14.705
     ump:      {Plug and Play Service: Device Install exit(000005b4)}
!!!  ndv:      Device install failed for device.
!!!  ndv:      Error 1460: This operation returned because the timeout period expired.
     ndv:      Installing NULL driver.
     dvi:      {Plug and Play Service: Device Install for ROOT\NET\0001}
!    dvi:           Installing NULL driver!
     dvi:           {DIF_ALLOW_INSTALL} 11:42:14.927
     dvi:                Default installer: Enter 11:42:14.928
     dvi:                Default installer: Exit
     dvi:           {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:42:14.930
     dvi:           {DIF_REGISTER_COINSTALLERS} 11:42:14.931
     dvi:                Default installer: Enter 11:42:14.933
     dvi:                Default installer: Exit
     dvi:           {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 11:42:14.934
     dvi:           {DIF_INSTALLDEVICE} 11:42:14.935
     dvi:                Default installer: Enter 11:42:14.936
!    dvi:                     Installing NULL driver!
     dvi:                     Install Null Driver: Removing device sub-tree. 11:42:14.940
     dvi:                     Install Null Driver: Removing device sub-tree completed. 11:42:14.942
     dvi:                     Install Null Driver: Restarting device. 11:42:14.948
     dvi:                     Install Null Driver: Restarting device completed. 11:42:14.954
     dvi:                     Install Device: Configuring device class. 11:42:14.955
     dvi:                     Install Device: Configuring device class completed. 11:42:14.955
     dvi:                     Device Status: 0x01802401, Problem: 0x1c (0x00000000)
     dvi:                     Install Device: Starting device 'ROOT\NET\0001'. 11:42:14.959
     dvi:                     Install Device: Starting device completed. 11:42:14.964
     dvi:                Default installer: Exit
     dvi:           {DIF_INSTALLDEVICE - exit(0x00000000)} 11:42:14.966
     ump:      {Plug and Play Service: Device Install exit(00000000)}
     ndv: {Update Driver Software Wizard exit(000005b4)}
<<<  Section end 2019/09/18 11:42:45.814
<<<  [Exit status: FAILURE(0x000005b4)]

[guyharris]

See also #72.

[pferrucci]

Same error installing 0.9990 on a Win2016 Standard, using a local administrator.
DiagReport-20200406-110220.txt

[dmiller-nmap]

Thanks for these reports. I am consolidating all instances of error 8007007e (ERROR_MOD_NOT_FOUND) during installation into this issue. Please follow the below procedure and report if it resolves your issue or not:

1. Reset networking (Windows 10 1607 and later): Settings -> Network & Internet -> Status -> Network Reset
2. Reboot (if Reset did not already reboot)
3. Download and install Npcap 0.9997 (or latest version)

[Nitaihatr1]

Thanks for these reports. I am consolidating all instances of error 8007007e (ERROR_MOD_NOT_FOUND) during installation into this issue. Please follow the below procedure and report if it resolves your issue or not:

1. Reset networking (Windows 10 1607 and later): Settings -> Network & Internet -> Status -> Network Reset

2. Reboot (if Reset did not already reboot)

3. Download and install Npcap 0.9997 (or latest version)

hello, i had the same issues installing the latest version (1.6) and after following these steps i now have no internet connection. I have no adapters in ncpa.cpl and the adapters that show up in device manager all have the error: "windows is still setting up class configurations for this device. (code 56)."

I tried to reinstall network adapter drivers in multiple ways, tried another network restart, tried clear cmos, tried deleting npcap and reinstalling and after 5 hours of work I'm still unable to restore network connectivity and unable to install npcap successfully. I also tried disabling the group security policy for driver signing and that didn't help.

I'm on windows 10 pro without the 21H1 feature update.

[guyharris]

8007007e (ERROR_MOD_NOT_FOUND)

Presumably that's a result of mapping the Windows error code ERROR_MOD_NOT_FOUND to an HRESULT as per Microsoft's documentation on that mapping.

[koffierombouts]

Trying to install Npcap on Windows 11.

All suggested things result in the same error for me.

Things I've already tried:

• Network reset
• Ran System File Checker (sfc /scannow)
• Checked if my Windows Installer was running correctly

NPFInstall.log

If anyone got any ideas to try, please let me know.

[Socks-N-FLops]

I was able to resolve the issue, and I am curious to see if others are in the same situation. I had recently updated my device drivers with the Dell command update, and after a reboot, I lost all of my onboard network drivers to driver code 56. Well, it turns out that if you have VMware workstation installed with the bridged network configured, it causes this whole nightmare. Here's what I did to resolve it:

1. Open Regedit
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\
3. Right-click on the CLSID directory and select find and enter vmware.
4. The find feature should present the directory, and that path should look something like this: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b}
5. Delete the {3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b} entry
6. Reboot

After the reboot, I was able to install Npcap with no issues. I'm not sure if a bunch of us are in the same boat and don't realize the commonality or this was just a coincidence.

[koffierombouts]

This solved the problem for me, thank you SO much.
I would love to hear how you figured out that this entry caused the problem, as this error itched my brain a lot.

Anyway, thanks again!

[Socks-N-FLops]

4. HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b}.

Well, it was a weird situation. About two weeks ago, I got the Npcap issue, stumbled upon this thread, and checked in a couple of times to see if someone found a fix. Well, yesterday, I was updating my device drivers and then lost all network functionality. I noticed the driver issue was from the VMware virtual network interfaces or bridging software conflicting with physical network adapters. I did have VMware workstation installed on my device a few months ago, so I was a bit confused as to why an application no longer installed would have a lingering impact after a driver update. Turns out the uninstaller doesn't wholly remove itself from the registry. The most common issue related to a Registry CLSID entry is a program's failure to delete its CLSID from the Registry when the rest of the program is uninstalled. After resolving my driver issue, it dawned on me to see if it resolved the Npcap install failure, which it did.

[AxelFoley17]

@Socks-N-FLops You have my gratitude. Worked for me too.

[guyharris]

I got the Npcap issue, stumbled upon this thread

Note that this is a bug report, rather than a forum post - the ultimate goal isn't just to provide workarounds, the ultimate goal is to find out the root cause and fix it (if it's an Npcap bug) or work around it (if it's a problem with some other software), if possible. If it's not an Npcap bug, and it's not possible for Npcap to attempt to work around the problem, it might be useful to add it a a FAQ entry.

I did a Google search and the results suggest that it might, as per your comment, be related to VMware.

[dcahill-ux]

I got the Npcap issue, stumbled upon this thread

Note that this is a bug report, rather than a forum post - the ultimate goal isn't just to provide workarounds, the ultimate goal is to find out the root cause and fix it (if it's an Npcap bug) or work around it (if it's a problem with some other software), if possible. If it's not an Npcap bug, and it's not possible for Npcap to attempt to work around the problem, it might be useful to add it a a FAQ entry.

I did a Google search and the results suggest that it might, as per your comment, be related to VMware.

It worked for me too. Btw that’s a weird way to thank the only person who’s found a fix.

[AxelFoley17]

I got the Npcap issue, stumbled upon this thread

Note that this is a bug report, rather than a forum post - the ultimate goal isn't just to provide workarounds, the ultimate goal is to find out the root cause and fix it (if it's an Npcap bug) or work around it (if it's a problem with some other software), if possible. If it's not an Npcap bug, and it's not possible for Npcap to attempt to work around the problem, it might be useful to add it a a FAQ entry.

I did a Google search and the results suggest that it might, as per your comment, be related to VMware.

I dont know if there is a fix, but what i do know, is that this is definitely the problem, and also affects other network driver related things, apart from npcap.

For example, i could not use any vpn software on my windows for months. They all dies because of "driver error".
Yesterday after successfuly installing npcap, i tried a vpn too, worked flawlesly.

[guyharris]

I did have VMware workstation installed on my device a few months ago, so I was a bit confused as to why an application no longer installed would have a lingering impact after a driver update.

Please file a bug with VMware on that. I think VMware can be installed on a VMware guest, so I'll try installing and uninstalling it on my Windows 11 VM and, if it makes the same mistake there, I'll file a bug, too. (Hopefully they will have a single bug report and make all others duplicates; a significant number of duplicates may raise its priority.)

I'm not sure whether Npcap could detect this issue and remove the CLSID from the registry.

[mario7codes]

I was able to resolve the issue, and I am curious to see if others are in the same situation. I had recently updated my device drivers with the Dell command update, and after a reboot, I lost all of my onboard network drivers to driver code 56. Well, it turns out that if you have VMware workstation installed with the bridged network configured, it causes this whole nightmare. Here's what I did to resolve it:

1. Open Regedit
2. Navigate to "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID"
3. Right-click on the CLSID directory and select find and enter vmware.
4. The find feature should present the directory, and that path should look something like this: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b}.
5. Delete the {3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b} entry
6. Reboot

After the reboot, I was able to install Npcap with no issues. I'm not sure if a bunch of us are in the same boat and don't realize the commonality or this was just a coincidence.

I tried using this solution but I'm unable to delete the entry. I had administrator privileges and everything but it's not deleting, no matter what I do. I also restarted the computer in Safe Mode.

Edit: Okay so since I wasnt able to manually delete it using the instructions given, I used command prompt instead and now its been deleted and I have successfully been able to install Npcap without any errors. I've been stuck with this for weeks so thank you for the solution!

Heres the command I used btw:

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b}" /f