Thanks, I spent a lot of time cleaning and cleaning my pc without effective solution, but now, stera is dead ;-)

josep

hi sorry to be a pain but i also have this issue and it is stopping my cd drives from working,

can you put this solution in a more basic way so i could maybe sort it out.

thanks daz

Hi Daz,
I'd certainly like to help. Please let me know what specific section you'd like more assistance with.

I just upgraded to Diskeeper 2007, and I had problems with boot-time defrag which I did NOT have with Diskeeper 10 and SpySweeper (XP Pro). The first time the defrag at boot seemed to cut off before it finished, and then I got the error message about not finding "ssiefr.E" and skipping autocheck. To get rid of the error, I had to delete the registry value for the bootcheck, before I found your explanation here. ssiefr.EXE is a legitimate SpySweeper file found in the Windows/System32 folder. Reinstalling SpySweeper did NOT reinstate the correct or problem value in the registry, and I replaced the blank value with your suggestion for the default. I have also had problems with Diskeeper 2007 refusing to run a boot-time defrag because Checkdisk was scheduled (when it wasn't); I had to manually set Checkdisk to run, then it removed the greyed-out but checked option in Diskeeper.

Hi Jan,
The registry entry you reference appears to be related to a SpySweeper beta, and may be the cause of the issue you've experienced. Webroot support can likely assist you in a more definitive answer on this. I'm basing this on the following thread: http://www.castlecops.com/t142766-What_is_Ssiefr_e_in_Spy_Sweeper.html

As for Chkdsk issues, that may be related to a device driver from another software product loading prematurely. If the issue continues, our Technical Supprt can help you identify the source of this.

Hi, I was having this same issue, but what WindowsXp is complaining about is thew inability to find AUTONTFS!! So my boot-time defrag never happens.. :( Did DiskKeeper 2007 forget to install AUTONTSF on my system?
Where can I get AUTONTFS so I can actually do a boot-time defrag!?

I'd suggest resetting bootime defrag and trying this again. AutoNTFS should be located either in your Windows/System32 folder (older Diskeeper build prior to 11.0.709) or in the Program Files\Diskeeper folder for new builds. A path in the registry (Session Manager\Environment) will ensure that your computer can find the AutoNTFS file. Please contact Technical Support for help on this if the resetting of bootime does not work.

Every time I started my computer a light blue screen appeared during bootup with "Program not found - skipping AUTOCHECK." After checking out various forums and the Microsoft website I came here and then found "autocheck autochk *" had been deleted from my registry. Adding it back fixed the problem. Many thanks for this info.

hi, i was wondering if you might know if this had something to do with the fact that durring startup my computer says analog???

Hello,
I do have a problem with auto check Program not found - skipping AUTOCHECK.

My computer doesn't restart and I don't know what to do. it doesn't even start in safe mode and not in previous mode where it worked fine.

Anybody who can help me in very simple language.

thanks a lot

Hi Ashley, Vijay,

I recommend trying some of the many online PC support forums for solutions. You'll want to provide more info to the members in those groups so they can assist you.

I finally figured this out and found the AutoNTFS program in the program files\diskeeper directory tree... made a copy of the file and placed it in my wondows\system32 directory and that fixed it all up!!

Hi Khile,

Well done on your solution. The problem is that you should not have had to figure this out in the first place. I'll let the support team know and investigate this - perhaps your situation came from upgrading DK, or the environmental variables were not properly created. Thanks.

Hello ,First of all sorry for my English,

I got the same error one day and I basically I tried everything possible and nothing worked, then I remembered the day before I was messing around with the NTFS permission on the C:/ Drive. so I boot my pc with a WINXP LIVE CD then I went back to the NTFS permission on my C drive and took ownership and set system account back. then I boot the computer and It worked.
so technically the pc was trying to boot up but the system didn't have the permission to access those files.

if you dont have a Windows LIVE CD, try to connect the hard drive as slave in another pc and then set back the NTFS permissions.

I hope this works for you.
good luck.

My computer won't start at all. It begins to start with the window logo then goes to the blue sceen that says "autochk.exe not found skipping Auto Check. Then it won't start up it just keeps trying to reboot.

Hi Duane,

I've not seen this error cause a boot-loop, but if you are using Diskeeper and believe this is related to our software, please contact our Support group.

I would also suggest that you search the net on this issue. There are numerous support sites covering this topic. Given that there is a laundry list of possible causes and the solution you need now is very complicated, they are likely to be a better alternative for you.

I am suffering from the DisKeeper startup issue referred to here, as a result of doing a trial of DiscKeeper and then removing it from my system.

I am running XP, and using RegEdit, I tried to follow the instruction which said:

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager" and remove the string [the name referenced in the message on system startup] from the BootExecute value.

I got down to control manager just fine, but could NOT find anything that mentioned "BootExec". Is it referred to in some other way in some versions of XP?

I also tried reinstalling Diskeeper, but even this step did not prevent the boot time issue.

Please advise as to alternative steps to get rid of this!

Thanks

Hi John,

Please make sure that the spelling is eaxctly as listed, as the Registry is unforgiving to edits.

For example there is also a SessionManager (not the Session Manager one described) key that does not have the space between the words.

If this key does not exist in the place described you can add it, following the instructions posted, or seek out more advice/help in other online forums that include this topic.

Well i was getting this prob in deskeeper 2007 and the registry editing just sorted it out.Thanks,mate.I wasn't getting any solution.

Just installed diskeeper 2008 pro premier and am having the same problem - will follow the steps here - but - is there anything special about 2008

Hi Menteth,

Nothing unique about Diskeeper 2008. You will see this type of meesage if the Bootime defrag is setup but not run - and then Diskeeper is uninstalled prior to the reboot that would kick off the Bootime defag.

If you see this continually, I suggest you contact Technical Support - could be a file permissions issue.

I'm trying to do a boot time defrag and i'm getting and unhandled exception. What can I do. I looked it up and DK says that with normal online defragging, boot time is not needed. I don't agree and want to know how to actually fix the unhandled exception so I can continue doing the boot time defrag. Thanx

Hi scorpiotail,

Please contact Tech Support (tech_support@diskeeper.com) and report this. If a new update of the Diskeeper software is needed, contacting them will add you to the list of customers to get it.

I also encountered this problem after upgrading from DK 2007 Pro Premier to DK 2008 Pro Premier. I'm running Windows XP Pro SP2 with all the latest Microsoft updates and have Administrator rights.

As suggested above, I edited the registry key:

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager"

and removed everything after "autocheck autochk *"

thereby deleting the following:

"autocheck AUTONTFS C: PAGE=KEEP DIRS=NONE MFT=MIN".

I also checked the registry key:
"HKEY_LOCAL MACHINE\SYSTEM\CurrentControlSet001\Control\Session Manager\Environment\Path" string and noted no reference to the Diskeeper directory.

(NOTE: There are two "CurrentControlSet(s)" in my registry: "Set001" and what appears to be a mirror image "Set002").

This string is already a rather lengthy 239 characters. Perhaps (just a guess on my part) there is a limit to the number of characters allowed and the path to the Diskeeper directory exceeded the string limit?

The simple expedient was to copy the file "AutoNTFS.EXE" from "C:\Program Files\Diskeeper Coproration\Diskeeper" to "C:\WINDOWS\system32".

This will work for now, but I'm concerned about the next time I upgrade to DK 2009. By them I will have forgotten what I did to fix the problem.

Wouldn't it be just as easy to copy AutoNTFS.exe into the WINDOWS\system32 directory during installation, as it is to modify the registry?

I found that Iolo System Mechanic leaves a bunch of junk in that key as well. I just deleted that and hopefully now the boot-time defrag will work.

I just experienced this problem after uninstalling Norton System Works, which contains Go Back (with some versions). Go Back is a system recovery tool that you can use at boot time to restore to a previous system config. It's similar to Windows XP's System Restore, but is done at boot time, which is when you really need it, unless you want to get into the Recovery Console (not if there's something easier!).

Anyway, I uninstalled Norton System Works (in order to install Norton 360...thanks for not doing it for me Symantec! When I rebooted, I still noticed that the Go Back boot time program was still running, so I hit the space bar to see my options. I saw that it was still enabled, so I disabled it, the system rebooted and I was able to get past the autochk program not found, skipping autocheck error message. Before that, it was rebooting, getting close to starting Windows, but every time that error message would appear and reboot my system. If you happen to have Go Back installed, try disabling it on boot time and see if that make any difference. It worked for me!

Yo desinstale diskeeper 8 y ahora me sale el aviso y no se que hacer,me pueden ayudar

Hola Santiago,

Pongase en contacto con nuestro personal de apoyo en busca de ayuda.

evil stera I banish you from my computer!!!

doh... guess ill have to do it the hard way...

*opens window, picks up pc, and hurls it out the window!

ahh haa sucker !!!!!

When tring to do a boot time defrag using diskeeper 2008 I get the following message:

Some argument was unrecognized or conflicting, boot-time not running...

Ive checked BootExecute in the registry and the string reads:

autocheck autochk *
autocheck AUTONTFS C: PAGE=MIN DIRS=NONE ENDPAUSE MFT=MIN

Ive tried to modify string so it reads:

autocheck autochk * autocheck AUTONTFS E: PAGE=KEEP DIRS=NONE MFT=MIN

but after attemting yet another failed boot time defrag I checked the reg only to find that PAGE=KEEP had once again become PAGE=MIN.
I also tried with default autocheck autochk * no luck there either.

I dont know if it makes a difference (it shouldn't) but I upgraded from DK 2007 pro.

If anyone can help me nut this one out I would be eternally grateful

Hi,

You can try this:

Copy AutoNTFS.exe from C:\Program Files\Diskeeper
Corporation\Diskeeper to C:\WINDOWS\system32.

Boot-time defrag will work correctly once this is done.

In case the above steps aren't working, you can email our Tech Support staff.

never had this. Program not found - skipping AUTOCHECK .till i got diskeeper have two computers
bouth same problem it is driving me nuts!!

please help

I am getting the skip autocheck error at boot. It

does not seem to cause any problem. Would you

attempt to do a fix if is causing no other problems?

Thanx

Hi,

If you are having issues, please contact our technical support. While this error may not indicate an actual "issue" of any consequence, it may add to longer boot ups (even if only a second or less), so I do recommend working with our technical staff to get it handled - they are here to help you out.

Hi. I am also having this problem and just need to be certain I am doing the right thing. Please follow the link below to view a screenshot of my registry.

http://img55.imageshack.us/img55/2828/bootexects7.jpg

Do I simply delete the selected entry?

Thanks alot.

Hi,

Delete everything after the asterisk and you should be fine. Keep in mind that it is still possible that the application that put those strings there in the first place may try to do so again. You may also need to find and remove the application if you have not already.

Hi - I was getting a lsdelete.exe program not found, skipping autochk.

So I looked for a solution to that - lavasoft apparently left something behind. Perhaps I misunderstood the solutions, but I believed that they were saying to delete that BootExecute line and the problem would disappear. Maybe it did for others, but apparently Diskeeper needs it. Now I do not have this BootExecute command in the registry which you are referencing! Could you please help by giving instructions as to exactly where the WHOLE BootExecute registry should appear and what exactly I need to type in?

Thank you

Hi Cheryl,

The BootExecute value should say (by default):

autocheck autochk *

If you have removed the BootExecute Value, you'll need to recreate it. Navigate to the registry key "Session Manager" described above and right click on the right hand pane where the values are named. Select to create a new "Multi-String Value" and then enter the above text string.

Thank you Michael.

It was awhile before I got back to this. It was also with some trepidation that I paged down to the Session Manager keys and then actually typed in a BootExecute key. However, my computer did boot up again (Hooray!) and I didn't see the skipping autocheck warning come up this time. Thank you for helping out with instructions to replace my missing key.

Cheryl

Thanks for posting this. It was caused (I think) by Iolo software. At least it appeared when I removed the Iolo "System Mechanic". As usual, Diskeeper rocks.

Thanks for the help. I used the the above post: "Posted by: Michael at November 27, 2007 07:25 PM"

I followed your instructions to the letter and now my computer is running much better!

I removed all references except the autochk* and now the "program not found skipping autocheck" no longer appears.

Thank you!

>>>>>>QUOTE/ The simple expedient was to copy the file "AutoNTFS.EXE" from "C:\Program Files\Diskeeper Coproration\Diskeeper" to "C:\WINDOWS\system32". /END QUOTE<<<<<<<

Ive had this problem for a VERY long time, and never figured it out until today. This proceedure fixed the problem. Many thanks for this posting.
AND, no thanks to conglomerate ignorance towards the solution.

Thanks a lot!!!!