I have been using the Silverfast Ai 8.8 scanner plugin with Photoshop CC for some years.
It was an expensive piece of Software but it worked ok to begin with.
Since PS CC 2017 it has exhibited a problem that still exists even using the latest version of PS.
If I use the PS plugin to carry out a normal scan using 'Import from Silverfast', it works fine.
However if I quit the Silverfast application (without scanning) and then try to exit Photoshop, Photoshop reports an unhandled exception message:-
"Could not complete your request because of a program error".
Once this happens, the only way to exit Photoshop is to kill the process from Task Manager.
I'm guessing this may be some sort of file permission or memory access problem.
The problem happens in several versions of PS CC I have tried including the latest 2021 versions.
However, it does not happen if I go right back to PS versions before PS CC 2017.
That suggests there was a PS change in 2017 that introduced this problem.
I have reported the problem to Silverfast but received no response. Silverfast support appears to be non-existent these days. Their forum has not been updated since 2018.
I do not want to upgrade to Silverfast Ai 9 because I don't use my scanner that often and the upgrade is expensive, I don't want or need the other changes that were made in Ai 9.
The compatibility information on the Silverfast website indicates that Ai 8.8 should work with ALL versions of PS CC.
I have tried updating the GPU drivers and disabling GPU support in PS - it made no difference.
I have tried installing the PS diagnostics plugin but no error information is written to the clipboard.
Has anyone else seen this problem?
Is it a configuration issue?
Is it a bug or change made in PS 2017?
Is it a change in a Windows 10 update that has upset file permissions etc?
In my view the way PS reports multiple errors as "Could not complete your request because of a program error" is bad programming. It leaves the user without a clue as to the underlying cause of the problem.
There should at least be an event log or trace facility of some sort.
I've run out of ideas.