npcap 0.99-r2 breaks corporate proxy on Chrome (Windows)

Observed behaviour

We have a corporate proxy that is configured automatically (WPAD?) and uses the user's login to authenticate against.
After installing the nmap 7.7 bundle (containing npcap 0.99-r2) Chrome couldn't connect to the proxy any more, so no "external" sites could be accessed.

Expected behaviour

npcap 0.99-r2 should not interfere with Chrome accessing a corporate proxy

Steps to reproduce

0. have a corporate proxy with auto configuration ("Automatically detect settings" set in Windows Internet settings)
1. Install nmap-7.70-setup.exe, choose to install npcap 0.99-r2
2. Try to access pages that need the proxy to work with Chrome. "Local" pages that are not accessed trough the proxy still work.
3. Chrome will respond with a DNS resolution error.

Notes

Interestingly both Firefox and IE were not affected by this.
I also have a local proxy running on my machine. I need to use it for software that can't properly detect the corporate proxy. For testing purposes, I configured it in Windows. That didn't fix the problem with Chrome.
I have tried both WinPCAP-API-Mode installation and "normal" installation. As soon as npcap is installed, Chrome doesn't work any more.

Steps to fix

Uninstall npcap 0.99-r2 via the control panel.

Versions

• npcap 0.99-r2
• (from nmap-7.70-setup.exe)
• Chrome Version 65.0.3325.181 (64-Bit)
• Windows 10 Pro Version 1703 Build 15063.909

Start by reproducing the failure with npcap 0.99-r2 from nmap-7.70-setup.exe on Windows 10 using Chrome's automatically detected corporate proxy, then compare the behavior with Firefox and IE. Done means Chrome can reach proxied external pages after npcap is installed while local pages continue to work.