Frequently Asked Questions

Chances are, others have the same questions that you do. Therefore, we have taken the common questions for Diskeeper, Sitekeeper and Undelete and provided the answers (and the questions) below in our Frequently Asked Questions section. Simply select the product below that you have questions about. If you can’t find the answer you’re looking for, you can submit a tech support question here.

Diskeeper | Sitekeeper | Undelete

Question
Program Folder opens when clicking on the Diskeeper Icon.
Answer
The problem is with the MMC and your security settings in the registry. The file system path to the .msc file (SystemDrive:Program FilesExecutive Software Diskeeper(Svr or Ws)Diskeeper.msc'' requires an ''8-dot-3'' translation to launch successfully. The situation you described will occur when the ''8-dot-3'' filename generation has been turned off via the registry key HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \Control \FileSystem, with the value NtfsDisable8dot3NameCreation set to 1. This can also have been set by using the Policy Editor. Set the value to 0 or use the Policy Editor to re-enable the ''8-dot-3'' filename generation, uninstall (make sure the Diskeeper directory has been deleted) and reinstall Diskeeper to solve the problem. Another way of handling the issue is to install Diskeeper to a shorter directory name like the Execsoft\Diskeep that was the default in previous Diskeeper versions. That directory name does not require an ''8-dot-3'' translation. Our developers are aware of this issue and it will be resolved in a later version of Diskeeper.

Question

Program Folder opens when clicking on the Diskeeper Icon.

Answer

The problem is with the MMC and your security settings in the registry. The file system path to the .msc file (SystemDrive:Program FilesExecutive Software Diskeeper(Svr or Ws)Diskeeper.msc'' requires an ''8-dot-3'' translation to launch successfully. The situation you described will occur when the ''8-dot-3'' filename generation has been turned off via the registry key HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \Control \FileSystem, with the value NtfsDisable8dot3NameCreation set to 1. This can also have been set by using the Policy Editor. Set the value to 0 or use the Policy Editor to re-enable the ''8-dot-3'' filename generation, uninstall (make sure the Diskeeper directory has been deleted) and reinstall Diskeeper to solve the problem.

Another way of handling the issue is to install Diskeeper to a shorter directory name like the Execsoft\Diskeep that was the default in previous Diskeeper versions. That directory name does not require an ''8-dot-3'' translation.

Our developers are aware of this issue and it will be resolved in a later version of Diskeeper.

<<Back