This has been discussed and answered in many threads already.
We finally were able to replicate the problem thanks to the help of some users (we are still unable to replicate it on any of our system), so it will be fixed in the next update that will be out in the next days.