We’ve had this problem with other firmware releases, and this issue began again with the latest update, so I suspect it’s deja vu here. Is this a known current problem, and is there an update that addresses it? Or is there a way to revert to an earlier f/w version?
Thanks for any help or insights.