Using Windows XP-SP2 HE on a Dell Dimension 8200. This problem/bug is something new with V3.4B1. It has not occurred on V3.3 betas or previous versions of PG on my system. I do weekly maintenance to include registry cleaning and defrag. The sequence of events that I use is: 1. Disable Protection on PG. 2. Disable Protection on RegDefend. 3. Using msconfig, I turn off all programs in the Startup tab and reboot with no programs running. 4. Do file cleaning, registry cleaning, and defrag with PerfectDisk V7.0 5. Using msconfig, I turn on all programs in the Startup tab and reboot with all programs to be active. HOWEVER, now with V3.4Beta1, PGAccount's startup entry will not stay active in msconfig startup list. ProcessGuard immediately deactivates it. So when the reboot is "complete", PG finds that PGAccount is not running. To get back to normal, I have to disable protection and close down PG GUI totally and then checkmark the PGAccount entry in msconfig-startup and reboot again. If I do not close down PG before doing this, PG will immediately reset the PGAccount activation/enabler. This bug is 100% repeatable on my system. And has NOT been in previous versions of PG. I am using SHM on the PG GUI. I have "execution protection" and the 4 global options active.