Altered security descriptors causing problems, a la kb909444

  • Thread starter Thread starter thesingularity
  • Start date Start date
T

thesingularity

After a BSOD corrupted my hard drive and prevented XP from loading, I
ran chkdsk, which fixed the corruption, but in the process reset all
the security descriptors on my files. The changed permissions meant
that the RPC service wouldn't run, and so nearly all programs failed
to function.

I managed to fix this by resetting the security settings back to
default using the secedit command as described here:

http://www.le.ac.uk/cc/dsss/docs/acls3.shtml

However, I am left with the symptoms described in the kb909444
article:

http://support.microsoft.com/kb/909444

The Windows Installer service does not start.
The Network Connections folder is empty.
The computers node in the MMC tree will not expand.

Also, Search doesn't function and clicking on the dependencies tab for
any service results in the error "Win32: Access is denied", symptoms
which also seem to be experienced by those suffering from the same
kb909444 issues.

This is clearly a permissions issue, but I've followed the articles'
solution and given the Windows/registration folder the permissions
described - and the problems still remain, and at this point I'm at a
loss what to do next, other than to reinstall Windows.

Any help would be greatly appreciated.

Thanks.
 
Hi,

Did you ever get this issue resolved? I ask because I have encountered a
similar problem with CHKDSK incorrectly identifying and deleting the security
descriptors in the MFT upon reboot with the /f option. The net effect of
running CHKDSK /f resulted in the same effect on my box. Fortunately I was
able to restore a copy of the volume but the "error" is still reported by
CHKDSK. MS describes this problem in KB 831374. However, since my MFT is only
151 MB with 106,104 records, it doesn't appear that the MS explanation of a
MFT of 4 GB or 4,194,303 files as the cause is correct. Furthermore, their
proposed solution for Win XP (install SP2) doesn't appear to correct the
problem even though MS purports that it does in the fix list for this SP.

Regards

Warren
 
Back
Top