Fixing Security Descriptors

[Guest]

Norton Disk Doctor (NDD) reports problems on my 4 drives with Security
Descriptors.

NDD "Fix" is to set CHKDSK /F for each drive, but CHKDSK reported no errors
and did not fix the problem (ran NDD w/Fix 3 times total).

I ran CHKDSK /R from the Repair Console, but it did not list any errors.
According to MS KB the Repair Console CHKDSK /R displays a detailed list and
would have said there were problems with Security Descriptors IF they existed.

Is there a way to fix Security Descriptors?

Of course, the problem could be NDD.

PS: Someone have an alternative to NDD?

 

[Guest]

Update: Found several KB articles on SECEDIT, including one on resetting
policies back to defaults. Problem, at work I did a search for SECEDIT and
all I get is the SDB. No EXE as stated in articles. Yes, my work PC is
running WinXP Pro SP2 (installed as SP2).

I have yet to go back home and see if it has SECEDIT.

Also, questions:

1) Could a problem with SECEDIT.SDB cause a problem with Security
Descriptors? When I go into Admin Tools, Local Security Policy, I get an
error saying a parameter is wrong in SECEDIT.SDB

2) Would it be OK to copy SECEDIT.SDB from my work WinXP Pro to my home
WinXP Pro to fix?

 

[Tecknomage]

UPDATE:

Copying SECEDIT.SDB from my WinXP Pro SP2 at work fixed the problem
below.

Also my Security Descriptors problem was false. The problem was
Norton Disk Doctor (NDD).

I found a improved replacement for Norton Utilities.

TuneUp Utilities 2007
http://www.tune-up.com/products/tuneup-utilities/
Click the "New Features" link at bottom of page to see more.

It does more than Norton Utilities and its Disk Doctor found no
problems with my Security Descriptors. Which is what CHKDSK runs
indicated.

I suggest everyone look at TuneUp Utilities.

Update: Found several KB articles on SECEDIT, including one on resetting
policies back to defaults. Problem, at work I did a search for SECEDIT and
all I get is the SDB. No EXE as stated in articles. Yes, my work PC is
running WinXP Pro SP2 (installed as SP2).

I have yet to go back home and see if it has SECEDIT.

Also, questions:

1) Could a problem with SECEDIT.SDB cause a problem with Security
Descriptors? When I go into Admin Tools, Local Security Policy, I get an
error saying a parameter is wrong in SECEDIT.SDB

2) Would it be OK to copy SECEDIT.SDB from my work WinXP Pro to my home
WinXP Pro to fix?

======= Tecknomage =======
San Diego, CA
The Mage Soapbox
http://magesoapbox.blogspot.com/