Sounds a lot like the problem I had, and still have with 5.2.0.18. Perhaps the workaround I found can help you too:
4 Likes
Sounds a lot like the problem I had, and still have with 5.2.0.18. Perhaps the workaround I found can help you too: