PCAN_ERROR_NODRIVER on Win10 for user without admin rights

[eriks]

Did you test on a completely fresh WIN10 (updated)?

What we saw yesterday on the first pc: eventually we installed the driver after assigning admin-rights to the user. That worked. Then we uninstalled the driver and removed the admin-rights from the user again. Then we tried to reproduce the faulty situation. However then the driver seems to install correctly. So it seems like once the driver has been successfully installed something remains on the system and the problem does not occur anymore.

Regards,
Erik

[M.Heidemann]

Hello Erik,

i tested your scenario on a WIN 10 machine (Win 10 2004), and have now also confirmed the functionality of the driver again on a secondary machine, which is a close to "vanilla" windows 10 installation (Current WIN 20H2), only the Device-Drivers were previsouly installed on this machine.

In both instances i manually and completely removed the drivers (Device mananger - > Advanced remove driver + delete driver files, as well as removing the PEAK-Driver Utility software.)


This bascially resembles your current state (after a reboot):

20H4_After_Driver_Device_Manager.PNG (14.12 KiB) Viewed 5837 times

After confirming none of the drivers were installed, i rebooted and then switched to the local user account (non-admin), to replicate your issue.

PCAN-View does not show any device (like in your case):

20H4_After_Driver_removal.PNG (63.11 KiB) Viewed 5837 times

Then i start a fresh driver install on the local non-admin account, prompting UAC to ask for administrator credentials (No Screenshot for the UAC prompt):

20H4_Fresh_Driver_install.PNG (4.7 KiB) Viewed 5837 times

After Installation PCAN-View recognizes the hardware as expected:

20H4_After_reinstall_PCAN_View.PNG (67.9 KiB) Viewed 5837 times

Like mentioned earlier, this is the first time we hear of an issue like this.

Do you approach the installation differentely in any way?

Best Regards

Marvin

[eriks]

Hi Marvin,

I did some more testing. Apparently something changed in the last driver release(s), because the PCANBasic is now installed by default I just noticed. In earlier versions we had to enable that.

So our way to install the driver is/was: "PeakOEMdrv.exe /exenoui /quiet ADDLOCAL=F_PCANBASIC"

It seems the faulty situation is now generated because of the 'ADDLOCAL=F_PCANBASIC' part. Could that be the problem?

Still testing, but is seems if I only use this "PeakOEMdrv.exe /exenoui /quiet" it is working correctly

I appreciate your time and effort in helping us with this problem!

Regards,
Erik

[M.Heidemann]

Hello Erik,

Well that changes things quite a bit, i was assuming a regular installation via the GUI...

Please consider the following information:

Command-line-doc.PNG (69.31 KiB) Viewed 5827 times

Peak-Device Driver command-line documentation:
https://www.peak-system.com/produktcd/ ... _en-us.pdf


Using "PeakOEMdrv.exe /exenoui /quiet ADDLOCAL=F_PCANBASIC" will not install the driver, as mentioned in the docs.

If possible just use the default installation instead, as it now also installs PCANBasic, as you have mentioned.

Maybe this also explains the beheaviour on the work-machine?


Best Regards

Marvin

[eriks]

"Using "PeakOEMdrv.exe /exenoui /quiet ADDLOCAL=F_PCANBASIC" will not install the driver, as mentioned in the docs."
To be honest, it is not clear from the docs that this is not possible. It was always working and it is still working except for the situation that we now encountered.

Anyway, since the PCANBasic is now default selected, we can omit that part. Using only 'PeakOEMDrv.exe /exenoui /quiet" seems to work, I will do some more testing.

And I'm sorry I forgot to mention that we use some command-line parameters, I was assuming that the problem was not related to that. One more time to realise that assumptions are not always correct.

Thanx for your time and help !

Best regards,
Erik