Group Policy propagating slow with errors.

Hello All,

Group Policy isn't propagating correctly. I get SceCli 1202 events with "0x4d2: An extended error has occurred". In the Winlogon.log file I see:

----Configure Registry Keys...
Configure machine\hardware.
[snip]
Configure machine\software\Microsoft.
Warning 6: The handle is invalid.
Error seting security on machine\software\Microsoft\Windows
NT\CurrentVersion\Perflib\009.
Configure machine\software\Mozilla.
[snip]
Configure machine\system\ControlSet002
Error 234: More data is available.
Error enumerating info for machine\system\ControlSet002\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0009.
Error 234: More data is available.
Error setting security for machine\system\ControlSet002\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0009.
Error 234: More data is available.
Error setting security for machine\system\ControlSet002\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}.
Error 234: More data is available.
Error setting security for machine\system\ControlSet002\Control\Class.
Error 234: More data is available.
Error setting security for machine\system\ControlSet002\Control.
Error 234: More data is available.
Error setting security for machine\system\ControlSet002\Control.

Registry keys configuration completed with error.

This happens every seven minutes (when Group Policy propagates) and it causes the system to slow up. I don't know if the system is supposed to slow up when Group Policy propagates or not (it is a 300MHz), but every seven minutes (which is when I get the warning in the Event Logs and the Winlogon.log file) it acts like it's under a DoS attack. I tried to open up the Start button while it was doing this propagating thing and it took about 45 seconds (!) just to see the Shut Down button. I also noticed whenever this happens that SERVICES.EXE CPU usage goes to 99%. Then afterwards System Idle Process takes back over, but it's still slow and the HD sounds like it's having a fit trying to do whatever it's doing. Then it speeds back up and I can use it again.

I'm considering either reinstalling Windows 2000 or getting a newer workstation and transforming it to Windows 2003 Server, but first I wanted your opinion as to what the problem is for two reasons. One, so I might be able to fix it in the meantime, and two, so that I don't do this again. :)

Thank you for your assistance.

Andrew
.