I did try those, but it did not solved the issue. But searching around I came to know, this was a rare known explorer bug. Which was not resolved ... so that's that.