NPCAP installation failed with runtime error 255

[b-ono]

I used the NPCAP for the version setup 0.9990.

It crashes first at stopping the npcap driver (i had an older version already installed). If I close the displayed message (Runtime Error 255 at 74F622A2) the installation continues and hangs afterward at "Starting the npcap driver".

The details displayed are:

Stopping the npcap driver
Could not load: C:\Users\username\AppData\Local\Temp\nsx9C25.tmp\SimpleSC.dll
Output folder: C:\Program Files\Npcap
Extract: LICENSE
Extract: DiagReport.bat
Extract: DiagReport.ps1
Extract: FixInstall.bat
Extract: NPFInstall.exe
Output folder: C:\Program Files\Npcap
Extract: npcap.sys
Extract: npcap.cat
Extract: npcap.inf
Extract: npcap_wfp.inf
Output folder: C:\Program Files\Npcap
Extract: Uninstall.exe
Installing NDIS6.x x64 driver for Win7, Win8 and Win10
Output folder: C:\WINDOWS\system32\Npcap
Extract: wpcap.dll
Extract: Packet.dll
Extract: NpcapHelper.exe
Extract: WlanHelper.exe
Output folder: C:\WINDOWS\system32\Npcap
Extract: wpcap.dll
Extract: Packet.dll
Extract: NpcapHelper.exe
Extract: WlanHelper.exe
Npcap driver cache in Driver Store has been successfully cleaned up!
The cache in driver store was cleared
Npcap WFP callout driver has been successfully installed!
Npcap LWF driver has been successfully installed!
The npcap service for Win7, Win8 and Win10 was successfully created
Writing service options to registry
Starting the npcap driver

Installing an older version (like 0.99-r7) works without issues.

[dmiller-nmap]

It looks like there was a problem extracting an installer module that we use to start, stop, and configure Windows services. This would necessarily interfere with installation. Can you try again with Npcap 0.9991, released yesterday, which contains several installer improvements? Thanks.

[urbanhusky]

I solved it for myself. If anyone else experiences this issue and is working remotely via citrix, not using citrix (directly) might help solve it for you.
You'll want the connection to your PC to run via remote desktop, not citrix. If your Citrix Receiver allows for it, establish a connection to a general desktop and then connect via remote desktop to your machine from there.

I was able to reproduce this issue. Worked fine via RDP, failed with error 255 when connected via Citrix.