What version are you running? I believe this is a known issue in the recent version of Explorer . The fix is planned for 6.2.2 but I would contact Support for guidance as they may be able to provide you with an older build that does not exhibit the issue.