I beleive I have a corrupt group policy/security db that is effecting all PCs on a peer-to-peer network. The manifestation of the problem is a pagefile error that is missing or too small after boot. When the user enters their password and tries to login they hang imeediately. CTRL-ALT-DEL gets them past the hang and XP starts up. Then the pagefile error messages begin to appear. Windows eventually creates a temp page file and life is good until the next boot. This error had me confused for a while until I looked at the event logs. The event log shows numerous errors (423) in the ESENT. This led me to a MS support doc on the corrupt security db. A complete reinstall of the OS will fix the problem. I was hoping to find a better fix. I have a doc that explains how to fix the corrupt db problem but it does not work. It involves renaming the security db in the windows system folder, runnning mmc and adding in a snap-in for security management. Then using the snap in to open/reload the db from a security inf file. This would have reinitialized the db. This all works until the final import of the security inf file. I get an access denied message. The doc I have said this message may appear and to ignore it. But in the end the db is never actually recreated. So the problem continues. How can I restore the security db without a reinstall of the OS? My other issue is how could the db have gotten corrupted in the first place. Yes, I have tried all the tricks related to the pagefile itself including some regediting, deleting/recreating, boot with no page file than add it back and boot again etc. I don’t think it’s simply the page file but is the corrupt security db leading to the pagefile problem. I say this because of how it happens right at login when security policy is usually checked. Also the fact that it impacts all PCs on the network makes sense given it is related to group security.