Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Netscreen Remote failed to install DNE drivers.



Article ID: KB8971 KB Last Updated: 10 Jun 2010Version: 3.0

Netscreen Remote 8.7 failed to install Deterministic Networking (DNE) drivers.  Seeing "No Driver Installed" message on task bar icon.


When installing Netscreen Remote 8.7 you will get an error when the Setup attempts to install the DNE drivers.  You will see an error similar to below:

"The specific path does not contain any applicable device INFs"

NSR version 8.5 and 8.6 also fails to install.  Following the DNE uninstall process fails to correct the issue.  The issue was occurring on brand new out-of-the-box PCs with no other VPN applications installed.


For the record, the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath value should be a REG_EXPAND_SZ value. The machine that was failing install was configured with a REG_SZ value, and so environment variable expansion was not performed.

Apparently, the DevicePath value was updated for some sort of Smartcard support package, and this resulted in the bad type.

The tell-tale symptom (outside of the install failure) was that the Network Control Panel applet would report the error "The specific path does not contain any applicable device INFs" when an attempt is made to initiate installation of any network Client, Service, or Protocol.

By re-creating the DevicePath with a REG_EXPAND_SZ type, the install worked.  The above noted modified registry key was the reason the client could not install correctly. The correction should allow the client to install properly.  So it appears the issue was a change made by Microsoft. To resolve the issue you will need to go to Regedit or something similar and make the necessary change to the Windows Registry as outlined above.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search