March 2007 | Main | May 2007

April 27, 2007

Program not found - skipping AUTOCHECK

Preface: this article refers to making direct edits to the Windows Registry. 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. You should only be concerned if the default autochk program itself does not run.

If you do get this error and want to clean it up, here's what you need to do:

Look in the registry at:

"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.

Under normal circumstances only the following would be present:

autocheck autochk *

This is what it might look like with added values:

autocheck autochk * autocheck stera

You can change the value back to the default (as shown in the first example above), but understand that it may possibly impact a legitimate program listed here.

Stera.exe is part of an adware program that pretends to be an anti-adware program!

As always, you need to be very careful editing the registry. If you see anything else listed here other than the executable named in the error message, look at named file's properties in the system32 folder or do a web search on it. A legitimate vendor can advise you on what to do to avoid potential conflict.

For Diskeeper it would look like:
autocheck autochk * autocheck AUTONTFS E: PAGE=KEEP DIRS=NONE MFT=MIN

(where E: represents the drive letter on which to run the bootime).

You can also reset it back to the default (autocheck autochk *) without issue. That is the safest bet with Diskeeper. You'll simply need to go back into Diskeeper and reset the Bootime job.

Diskeeper customers are always welcome to contact our support team for assistance.

Posted by Michael at 10:39 PM | Comments (34)

April 26, 2007

In the Oven in 2007

Here's a quick overview of a few things we have in the works for Diskeeper:

We will have an incremental update for Diskeeper Administrator in the coming weeks that will provide more options to volume license customers with regards to activation.

Just a few of the big things planned for the future are I-FAAST 3.0 (some really cool new performance technologies!), FragShield 2.0, and the evolution (and integration?) of a former technology-pioneering Diskeeper Corporation product.

PS: We have such a FULL feature list planned and designed (the most ever), we just don't have enough developers to code it all. So, if you are a senior (C++ or C#) developer in the Los Angeles area interested in contract work or contract-to-hire (no recruiters please), check out our job openings for more info.

Posted by Michael at 08:36 PM | Comments (0)

April 06, 2007

Software Update - tips and tricks

If you ever need to update (note this does not include full version upgrades), a quick trick is to grab the trialware from the Diskeeper download page, and install it right over the top of existing installation.

Usually the newest build is available via Check For Updates in the software, so you'd never need to consider this. That Check For Updates feature, by the way, also downloads trialware.

Posted by Michael at 11:33 PM | Comments (0)

April 05, 2007

New Diskeeper version every year.

Diskeeper Corporation has released 11 Diskeeper versions for Windows in 11 years. Why is this relevant?

Apart from the fact that Diskeeper regulary keeps it latest technology available to customers, it also means that customers on maintenance really get there money's worth.

Diskeeper Corporation, like many software companies offer what is called Software Maintenance (others may called is Upgrade Assurance or similar). This deal is made available and sold to customers at the time of thier initial license purchase. It is a percentage of the cost of the software license, and is usually purchased by time periods. It is common to offer 1 year, 2 year, and sometimes 3 year maintenance. The longer the Software Maintenance term, the lower the per year cost of the maintenance. At Diskeeper Corporation, Software Maintenance also includes technical support beyond the free 90-day support offered for new purchases for the length of time of the maintenace agreement.

Depending on where you purchase Diskeeper, the maintenance may be easy to find and purchase, but it is always available. If you are purchasing from a reseller, let them know you are interested in purchasing this as well.

Why is this valuable and why did I note that we have a track record of releasing a new Diskeeper version every year? Because, for around 25% of the cost of the license(s), a customer can purchase 1 year maintenance and almost certainly receive the next version for cheap. That's true even if you purchased a Diskeeper edition the first day it is released, as we also have a great track record of releasing a new version of Diskeeper within 12 months (1 year) of the previous release.

Getting that new version out to reward our maintenance customers is one of the big targets we set for ourselves every year. While we can never promise to hit that target, we have an excellent track record.

Posted by Michael at 10:15 PM | Comments (2)

April 04, 2007

What might cause the software to require re-activation?

Diskeeper 2007, as previously mentioned, uses a technology called software (or product) activation. If you want to read more on activation, the Diskeeper FAQ's are a handy source. I regularly post new information into this blog before it makes it into the FAQs or elsewhere; and, I will add one here.

In a nutshell, activation is the process of guaranteeing that the software in use is a genuine copy and is installed only on the number of computers licensed (purchased). Activation technology has been in the Diskeeper software since the release of v2007, though only some users have been required to actually undergo the "process" - such as those purchasing CDs from a retail store.

The activation process involves, in part, Diskeeper identifying your PC as unique. To do this it uses various combinations of your computers hardware. They are (in part); your motherboard, your hard drive, and your BIOS. It is possible (though very rare), where that data is insufficient to uniquely ID the computer, that other hardware must be considered. What is used, and in what combination, varies from computer to computer. As stated in the FAQs, no software data or personal data (to identify you) is ever collected form your PC(s). Apart from the obvious and valid privacy considerations, there simply is no technically legitimate reason to do this as it doesn't make "activation" any more secure or reliable. For anyone interested, the FAQ pages provide more data on the entire process.

So, if you change out the hard drive (where your operating system drive is located) you will very likely need to re-activate. If you change the BIOS or the motherboard, you may also have to re-activate. It depends on the number of metrics used and if the hardware replacement is determined to constitute enough of a change that the computer ID needs to be re-figured. This is, again, very similar to Window's design.

To make the re-activation process as easy as possible for customers, Diskeeper does provide a "grace" number of activation allowances, which are also tied to time-periods. This similar to how Windows works. In other words, if you swap out the hard drive every 6 months for a bigger, faster one, you'll never have a problem with activation. This also makes it easy for you to migrate your Diskeeper license to your new Vista PC.

Please keep in mind that you do need to be legally licensed to install the software on each PC on which you do install and run it. If, you do migrate the license to another PC, and activate it, you will need to uninstall it from your existing PC.

If you find you are re-installing your operating system (or even an new operating system) on the same computer (i.e. same hardware), you have an unlimited number of activation allowances. It is only when the hardware changes that are limited in the number of allowed activations.

We added this leniency as we, as always, do trust our loyal customers to do the right thing. Those who have already been changing components on their PCs, or migrating to Vista, have already found that the Diskeeper grace is very fair. The purpose of activation is, again, to slow down the illegal file sharing that is very rampant on the internet. Sites known as "warez" sites are common locations that facilitate piracy.

The grace allowance is even more lenient for volume license customers, as these customers regularly "retire" and replaced computers. And, as noted in previous blogs, volume license customers can also speak with their Account Managers for a variety of options. There will also be new, and more robust, documentation available for volume customers in the next couple of weeks - as well as new functionality to make the process even easier in a network environment.

We've designed the system to be as seamless and easy to use as possible. If there is anything we can do to help, let us know.

Posted by Michael at 08:50 PM | Comments (1)