Digi AnywhereUSB/14 and delayed availability in Win2003 ?

Hello, we’ve latest drivers (v3.60.60) and our Net Admin recently upgraded the Digi Firmware. We turned to using a Digi 2x port group for our 32-bit Win2003 Licensing Server with USB dongles.

I noticed it’s a while before the Digi ‘port owned’ LEDs turn ON after Windows starts, often as long as after user login. Safenet’s Sentinel Drivers for SuperPro are OK with this. However, Wibu’s WIBU-KEY was not. So, I’ve added a task to restart its host’s ‘WIBU-KEY Server’ NT system service, both at login (All Users.…\Startup) and at 7AM.

I’m just wondering if I could tie it to be dependent on another System Service?

Should I expect the same Digi behaviour under Server 2008 R2 or 2012?


I’m not certain if this information will help, but it’s worth sharing with you, if you want to try it. It’s from an internal knowledge article for the AnywhereUSB.


Software services that look for related USB license dongles may start before the AnywhereUSB and attached dongle is enumerated. This is a suggested workaround for that scenario - to make the service in question start later during the boot cycle, hopefully after the AnywhereUSB and attached dongle is enumerated and ready for use.


In order to create a new dependency you will need to open your registry editor and browse to HKLM/System/CurrentControlSet/Services/. Select the subkey containing the service you wish to create the dependency for and create a new “Multi-String” value named “DependOnService” with a data type of REG_MULTI_SZ. In the “Value data” field, type the name of the service or services you wish to start before this service, putting one entry per line. The name of the service is exactly as it appears under the services key.

This Microsoft article covers the subject as well:

The bottom section is most relevant to you (making your USB key-related service run after another one that’s known to start late), particularly “Note If you have a service that needs to start late in the boot cycle but you do not have a specific service dependency, as explained above, then choose one of the services which startup last as the data value for the value “Depends on Service”. Services commonly selected are Spooler and Messenger.”

Since the AnywhereUSB has its own service, we recommend using that as the dependency (instead of Spooler or Messenger). The AnywhereUSB (NT) service is called “awusbsys”. It’s in the same path as Spooler (HKLM/System/CurrentControlSet/Services/).

Note: This information is provided as a courtesy to help users who may be affected by this issue. We have received mixed feedback regarding these instructions. Most users should not need to make these changes.

Worked brilliantly. Thank you.