Finally this issue is fixed in V5.3.17
Special thanks to @newuserkantu for his help in recreating this problem on one of our test machines.
Finally this issue is fixed in V5.3.17
Special thanks to @newuserkantu for his help in recreating this problem on one of our test machines.