Forum Discussion
chutz
2 years agoOccasional Contributor
Thank you 1P_Timothy for the workaround advice.
If it helps, I had this problem a while ago, and then it disappeared for a long time. This bug resurfaced maybe 2 or 3 weeks ago.
Looking at the release timeline, I believe everything was OK on 8.10.12 and most likely the 8.10.16 update broke it.