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
Diskeeper "could not initalise" message when attempting to Analyse or Defragment.
Answer
Typically, this is an indication of a structural problem within the file table for the disk. Diskeeper fails to initialise because it cannot gather the data about the disk that it needs in order to safely begin defragmenting. We suggest that you run a chkdsk /R on the partition from the Command Prompt. You will find the Command Prompt in either the Programs or Programs/Accessories sub menus of the Start menu on your system; depending on your operating system. The proper syntax is: chkdsk disk_name /R example: chkdsk C: /R (the disk_name above means the specific partition designation: C:, D:, E:, etc) After chkdsk has run, try Diskeeper again, it should run fine. If the chkdsk does not fix it, then I suspect the Scheduling file is damaged. Apply the following steps to recreate your Diskeeper scheduling: 1. Close Diskeeper, if it is open 2. In the directory Program Files / Executive Software / Diskeeper directory, 3. delete DISKEEP.CTL 4. Stop and Start the Diskeeper service in Services applet in Control Panel 5. Reopen Diskeeper and reset your SET IT AND FORGET IT settings If you are running Windows XP, check your login security attributes (by right-clicking on my computer \| Manage, then clicking Local Users and Computers\groups) to see if you are a member of the Guest group.If so, remove yourself from Guest.

Question

Diskeeper "could not initalise" message when attempting to Analyse or Defragment.

Answer

Typically, this is an indication of a structural problem within the file table for the disk. Diskeeper fails to initialise because it cannot gather the data about the disk that it needs in order to safely begin defragmenting.

We suggest that you run a chkdsk /R on the partition from the Command Prompt. You will find the Command Prompt in either the Programs or Programs/Accessories sub menus of the Start menu on your system; depending on your operating system. The proper syntax is:

chkdsk disk_name /R
example: chkdsk C: /R

(the disk_name above means the specific partition designation: C:, D:, E:, etc)

After chkdsk has run, try Diskeeper again, it should run fine.

If the chkdsk does not fix it, then I suspect the Scheduling file is damaged. Apply the following steps to recreate your Diskeeper scheduling:

1. Close Diskeeper, if it is open
2. In the directory Program Files / Executive Software / Diskeeper directory,
3. delete DISKEEP.CTL
4. Stop and Start the Diskeeper service in Services applet in Control Panel
5. Reopen Diskeeper and reset your SET IT AND FORGET IT settings

If you are running Windows XP, check your login security attributes (by right-clicking on my computer | Manage, then clicking Local Users and Computers\groups) to see if you are a member of the Guest group.If so, remove yourself from Guest.

<<Back