The same code is seen when shutting down using the same methods as you. So I agree there’s something changed recently which causes this error. I’ll post how I got the log tomorrow and perhaps others could see if have same issues.