Benn Schreiber - 2017-02-04

I have a VM set up with Windows 10, Scanner (HP Scanjet flow 7500) is pushed to the VM via Virtualbox. First user (me) can use the scanner just fine, including the Twain Flatbed profile. I set up the profiles the way I wanted, copied the profile.xml file to \Program Files (x86)\NAPS2 and also changed 3 items in appsettings.xml: LockSystemProfiles, NoUserProfiles, and SingleInstance, setting them all to true.

When the second account RDPs into the VM it sees the correct profiles, and can scan just with the Twain ADF profile, but trying to use the Twain Flatbed scan profile fails by timing out. There is another profile that is exactly like the Twain Flatbed profile but has UseNativeUI set true. This profile, which brings up the native scanner UI, is perfectly able to scan from the Flatbed using Twain.

What should I look at that would cause the second account to have a profile that doesn't work, although it works correctly in the first account?

Thanks for any and all suggestions.