This is a reposting of a prior (and popular) blog entry that unfortunately was 'chopped' when we migrated to our new platform. Here it is in full:Preface: this article refers to making direct edits to the Windows Registry.
![]() ![]() ![]()
8) Hold down ALT + S to Save Changes to the partition table and then Press CTRL +C to exit out of the program. 9) Reboot your computer and it should now boot normally into Windows. Of course, all these steps should be followed correctly, and if you are not comfortable changing this information you should consult a friend or computer tech that can help you with the problem. Jan 13, 2014 'autochk program not found skipping autocheck' Windows 7 IT Pro. At this thread and tell me if i have any hope in not having to reinstall windows and all my programs.
If you are not experienced with this subject, ask your company's IT Administrator or a computer-expert friend/neighbor for help.Our Tech Support group has seen a few reports of this error (Program not found - skipping AUTOCHECK) from customers when running Diskeeper's bootime defrag. The error starts early in the boot process while the Session Manager process (smss.exe) is busy getting the system up and running. Smss.exe is critical to loading the paging file, initializing the registry and loading kernel components. But, before it does any of that it looks to a registry key called BootExecute. At that location it launches any applications listed.
Session Manager then looks to the Windows system32 folder for particular executables it has been instructed to launch. By default there is only one program listed here - autochk.exe, the boot-time version of chkdsk, which will run if there are any file system inconsistency flags detected (i.e. Volume dirty bit is set).Read on for the solution.Software vendors who need exclusive access to a volume (such as a defragmenter) will name proprietary executables at this registry location (and place the programs in the Windows system32 folder). Using this system is how Diskeeper is able to safely defragment files that could not be defragmented when the system is up and running.However, malware creators have also used this BootExecute location to load their spyware/virus crap.If you uninstall a legitimate program that has written into this BootExecute registry you may see this message. The uninstall will typically delete the executable from the system32 program, but not edit the registry. In most cases, the registry change is only a temporary one. For example: if you set Diskeeper to run a Bootime defrag 'on next reboot' but uninstall it before the reboot, you can create the same issue.
Once the Diskeeper Bootime defrag completes, it removes this string from the registry. Other applications are likely to behave similarly.
It is also possible that a program, during install, writes data into this key, but then does not remove it on uninstall.Another possibility is if you have run an anti-malware program that has removed the referenced executable from the system32 folder, but not changed the BootExecute registry to remove the 'pointer' to that file. In that case you will also see this message.When the program named is from a removed third-party vendor, the message is harmless.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |