What to do when the WNIP Driver does not start with Windows

What to do when the WNIP Driver does not start with Windows

We have seen instances of our WNIP audio driver not starting properly with Windows. In these cases, you can go to the Windows | Services applet and find that the driver isn't running. Starting the driver resolves the issue.

The primary reason that the driver might not start automatically with Windows is that the bootup process is happening so fast that when the driver tries to learn the MAC address of the NIC it's configured to use, that information isn't yet available because the networking service isn't fully up and running yet. This could be due to the use of a solid-state drive as boot device, as they load startup modules very quickly. Or there could be other services that need to run before the networking runs.

In any case, the solution is to delay the startup of the WNIP driver. To do this, go to search in the taskbar and start to type Services. Then you can open Services.msc. Once you're there, scroll down to the WheatNet IP Transport Service. Right-click on the Wheatnet IP Transport Service and select Properties. Set the driver's Startup Type to Automatic (Delayed Start):

This image has an empty alt attribute; its file name is image-13.png

If this causes too long of a delay, you can also try setting the Startup Type to Manual and write a simple Powershell or Visual Basic script, or even a startup batch file to start the driver service after a delay that you select and build into the script.

    • Related Articles

    • How To Install The WNIP Audio Driver

      Installing The Audio Driver Before you begin, connect the PC/Server to the WNIP network and set a fixed IP address on the NIC you are using within the WNIP system’s subnet. The default WNIP subnet is 192.168.87.0; your system may be configured ...

    • Configuring Rivendell For The WNIP Driver

      Install The Driver 1. Set up a network card on your computer with a static IP in the WNIP subnet range and connect that card to the network. Ping a blade to ensure you're seeing the WheatNet-IP Network. 2. Open a terminal window in the folder where ...

    • Recording Multitrack With The WNIP Audio Driver

      [UPDATE 3/21/25] An integrator notified us that he had found a utility that will allow both our ASIO and WDM drivers to be used for multitrack recording. The utility is called VBAudioMatrix, the 64-bit "Coconut" variety. We have completed some basic ...

    • How To Test the ASIO Audio Driver

      Unlike the WDM driver, ASIO drivers don’t show up in the Windows Control Panel. When someone can’t use the ASIO driver with an application, how can you verify the driver was installed correctly? If this tester works but the software doesn’t, then the ...

    • Optimizing Windows for AoIP

      This comprehensive document explains how to prepare your Windows PC to work reliably with the WheatNet-IP Audio Driver. Download/View Document