Quote:
|
Originally Posted by prariepoodle Well I can see no one here knows anything either... Thanks for all who read my post... |
You should leave this post running until someone with expertise in this problem sees it. Every
volunteer on these forums isn't on the net 24/7. Just wait!
Your problem probably indicates a corrupt secedit.sdb file. One way to fix it
MAY BE as follows:
DON'T DO THIS UNTIL SOMEONE WITH MORE EXPERTISE VERIFIES THAT THIS IS THE CORRECT PROCEDURE! As I said, just have a little more patience and wait...
To re-create the Secedit.sdb file:
1. Rename the Secedit.sdb file to "Secedit.old". (On my computer the file is found in C:\WINDOWS\security\Database)
2. Run the secedit /refreshpolicy machine_policy /enforce command to recreate the local database from the local settings.