This problem occurs if the zExplorer API was used incorrectly, and should not occur unless the zExplorer was customized by third party plug-ins.