Support Center

Solo 5 will not initialize

Last Updated: Sep 12, 2017 04:50PM PDT

Some users experience "will not initialize" when launching HoverCamFlex after connecting a Solo 5 document camera.

The most common cause for this is due to a default setting in Windows to search for the best driver.

This can take as long as 30 seconds, depending on your computer. The rule of thumb is to wait approximately 15-20 seconds after connecting the Solo 5 before launching HoverCamFlex. Or, just wait for "The device is ready for use" notification.

After a device is attached, Windows first attempts to locate and install a driver in a trusted system context without user interaction, as follows:

  • Starting with Windows 7 or 8, Windows automatically downloads matching driver packages from Windows Update without prompting the user for permission. If a matching driver package is found, Windows downloads the package and stages it to the driver store.
  • If a matching driver package cannot be downloaded, Windows searches for matching driver packages in the driver store. This includes in-box drivers, installed drivers other than in-box drivers, and preinstalled drivers.
  • Windows also searches for driver packages that were preloaded in the locations that are specified by the Device Path registry value. This value is under the following subkey of the registry.
By default, the DevicePath value specifies the %SystemRoot\INF directory.

If a matching driver package is found either on Windows Update or in a location that is specified by the Device Path value, Windows first stages the driver package to the driver store before the driver is installed. In this way, Windows always installs drivers from the driver store.

Submit a Ticket
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found