On Tue, Jan 7, 2020 at 08:16 AM, conrad wrote:
I will try that.? Question is why now with v4.16 to v4.18 update?
Let us know if that works.
If it does, perhaps your previous exception was tied to the program, which you replaced when updating. The new program was not (yet) listed as an exception.
