The scan engine is saved in an attribute for that user. The attribute is also named after the specific computer that was used. Check for the [Scanning-WindowsUsername]ScanEngine-ComputerName attribute. After launching Laserfiche Scanning, selecting the scan engine, and saving these settings, the attribute should get created for that user. Confirm that it exists. Then the next time this problem occurs, check again for the existence of that attribute and that the actual data in that attribute still corresponds to the correct scan engine or not.

Thanks Alex, I will check that and post the results!

I have a site where a couple of users suffer this also. It seems to be coincide with an upgrade to Windows 10 but that could only be a coincidence. Every so often (1-2 a month) they are prompted to select a scan mode and/or the scan mode reverts back to Universal Capture.

Were there any further findings on this?

We have been at 10 for a while and this also happens continuously for us on our scanning workstations.  Sometimes I have to delete their complete scanning profiles and eventually on a few occasions we have had to delete all their profile and user accounts after days of trying to get their scanning to work again.

What I found out with one client specifically is that this is tied to the Windows account so if a different person logs into the scan station using their Windows account and then logs into Laserfiche using the scan account - it still will lose the scan settings.  I hope this helps!

I would agree.  So do we know if there is any way to prevent this from happening?  Reason why I ask is we got rid of all the scanners in one department and started using the copier because every time someone would set down to scan with their credentials, their settings would not be there.  It was too much of a headache to use a shared workstation.  And that's happening more and more for us.

I checked the attributes for this user when the issue was happening and the data referenced universal capture. I changed that whilst logged in as that user (to ScanConnect) and after closing and opening scanning the attribute was updated. When I logged in to troubleshoot the issue there was a dialog on the screen about selecting the scanning mode (basic or standard) which the user quickly dismissed (it was open whilst the scanning application was already running). Not sure if that is significant or not.