Like the doctor who was told "Doctor, it hurts when I do this?"
My answer is the same. Go find a new way to do what you are attempting to do and stop using software that creates the issues.
After original install had no sleep and hibernation. Followed recommendation and entered registry to correct. Worked flawless for many years. Recently crashed and rebuilt with original disks plus SP2. All programs and text files still on hard disk, but programs to work had to be reinstalled. No sleep and hibernation, but start up and close much faster than before. When depressing power button on PC may or may not start. Usually several trials, even though boot.ini was rebuilt. Followed instruction to enter registry to correct as follows:
Hkey local machine > Software > Policies > Microsoft > Windows OK but then >System > Shutdown does not exist. When using machine sometimes on it's own reboots suddenly. Made several attempts to correct with original disks. Did not help. Just for clarity I reinstalled all the programs required by the motherboard, the Bios is the same and was reinstalled. I use Max. Registry Cleaner.
The reason the machine crashed is due to the following: To back-up I used for many years the old GHOOST program to clone HD0 to identical HD1, which was extremely fast 10 to 15 min. for average hard disk used. When a friend had to use Ghoost in reverse cloning HD1 to HD0 we found out that Ghoost had a problem and scrambled HD1. It indeed was a problem our investigation showed, but by that time the original crew that programmed Ghoost had departed from Symantek. We helped ourselves by mounting the hard drives on drawers and simply switched drawers when needed. We then investigated a new program Drive Clone by Farstone, which was not as flexible as Ghoost, but worked flawless in reverse cloning. The original drive clone program like Ghoost clones at a very high speed and so do the subsequent versions. By admission of Farstone the original program has code that did the cloning after shutdown in the start up period, but was not used anymore in subsequent versions, but remained in the program. For some damned reason, when I cloned that particular day the program started then informed me that a drive was locked and that the cloning had to be done during start up. It did and then stalled out and scrambled both hard disks. So much for the criminal investigation. It would be better for Farstone to remove that section of code, but I do not believe that they want to spend the time in doing so. So the threat remains. I did not know that WINXP knows about locking and unlocking drives, somehow it smells of UNIX.
Well this is a long story. Anyone with me?