This issue could still be a software issue because Windows have installed a later driver than the one you had installed and if so, Little LogBook will not recognize the device. In some cases, certain malware also caused a similar issue.

Try these steps:

  1. Open Device Manager (you can find this by RIGHT clicking “Computer” in your Start Menu and clicking Manage)
  2. In device manager, check firstly if there is an “Other Devices” category. If so and it shows an entry USB-Serial Controller D OR STM32 Virtual Port, then you need to install the driver - see Device not picking up after installing Little LogBook in the knowledge base on how to install the drivers
  3. Otherwise check under the category Ports (COM & LPT)...There should be ONLY ONE entry of the a Prolific USB-to-Serial Comm Port OR ST Microelectronics Virtual Com Port
  4. RIGHT click the entry and click Update driver software.
  • In the box that appears, click the BOTTOM option
  • In the next box, again click the BOTTOM option
  • You might be presented with a list similar to that of Device Manager’s (depends on the Windows) - scroll down to the “Ports (COM & LPT)” category and select it and click Next
  • You could now see up to 3 entries of different drivers you can choose...they have dates in brackets next to them. Click on the oldest date to highlight it and click Next
  • Finish the process to apply the driver and take special note whether it gives any errors during this stage**

Once done, close everything and open Little LogBook and try again. If it still does not work or if it does not show up in Device Manager at all, let us know in order to have a look to ascertain whether its not a hardware fault.

**If you applied the final step under number (4) above and it completes the wizard with an "Access is Denied" message, then it seems you also have been a victim of a security hole in Windows. There seems to have rolled out some form of malware that attacks certain registry hives in Windows and this causes the issue you are experiencing.


We have had a multitude of users with the same issue and after posting the problem to Microsoft (whom were not able to provide a solution), we found that running a scan with software called Malwarebytes resolved the issue every time.


Thus follow these steps:


  • Download and install Malwarebytes Free:
  • Once installed, run the scan and let it clean anything it finds and restart the computer
  • Once restarted, unplug the device and plug it back in and follow the steps as per the Device Manager section in my original solution.


Many users have applied this with success and it resolved the issue.