Unable to change parental control settings see system administrato

[keona1995]

Just yesterday I began receiving these message when attempting to change
settings for a standard user. This was after the latest Tuesday OS patches. I
am the system administrator, using the only administrative account on the
Vista Home Edition machine. Event Viewer showing Audit Failures in the
Security logs regarding unknown user or wrong password. These messages
correlate with clicking on the Parental Controls applet, which of course
happens after a normal logon (which by the way is noted as a Success Audit in
the same event log).

I can no longer change any setting, which pretty much renders the computer
useless for this standard user. Does anyone have an idea what recovery steps
I should take?

Thank you in advance.

 

[Mary]

First try a System Restore to go back to before you installed the updates. If
that doesn't work, See if anything here will help:
http://www.neowin.net/forum/index.php?showtopic=537806&st=0

 

[keona1995]

Thank you, Mary, for the effort. Doing a System Restore did not help, but it
might be because the restore points did not go far enough into the past.
Enabling the native Administrator account did not help either, since using
that account resulted in the same message.

One change has occurred. Setting Time Limits resulted in the same "Unable to
change parental control settings. If this situation persists, see the System
Administrator" message, but re-opening the Time Limits applet showed that the
change actually did occur. Where the change absolutely does not take is in
the Allow and Block Specific Programs applet. This is especially serious,
since installing new programs will by default, on this computer anyway,
result in programs being unchecked, and thus the non-administrative user will
not be able to use the program.

Obviously there is some deep corruption somewhere, but where? The fact that
the Security logs are showiing that the administrative user is not being
recognized as an administrative user for certain applications must somehow be
implicated in the problem. Isn't there a Microsoft employee who could help
out?

Thanks.