SYSTEM32 - do not modify

  • Thread starter Thread starter Gary Walker
  • Start date Start date
G

Gary Walker

Sorry if this is redundant. I couldn't find anything identical.

I'm trying to clean/salvage a Win/XP home system for the
family of a recently deceased owner. The system has/had
a whole lot of useless processes active, that just needed
removal, along with some other family training.

So, I'm finalizing my last clean-up activities with removal
of a lot of AOL trash, and I let a shared .dll removal message get by(answer
yes or yes to all), and a member
was removed from system32, causing an obvious direct-
ory update.

Now, although the XP system operates great, initialization
/reboot produces a system32 directory presentation that
describes something like - "system directory, do not mod-
ify".(I'm returning to the site this weekend for the exact
text description)

Within this system32 directory presentation is an addition-
al description where the date/time of the modification is
noted as 05/11, so I know it was caused by my activities. All of the similar
problems I've found on the net, related to this issue, have been noted as
registry problems. This may well be such a problem also(since there was some
kind of a registry cleaner/monitor product installed/active on this system,
but was removed before this problem occurred).

But, unlike the other related net items found during my
research, I seem to have the cause closely identified. The
simple response to this warning presentation is just to
close the window. However, it needs to be corrected.

I've reviewed:
http://support.microsoft.com/default.aspx?scid=kb;en-us;170086
but haven't taken any actions mentioned within, as yet,
pending some additional opinions.

So does XP really monitor system32 for modifications, or
might anyone else have experienced such a problem.

Any clues?

Thank you,

Gary
 
Do I gather that the system32 folder pops up on startup. If so you
might have said so earlier. As stated in the KB, one of the causes is a
corrupted entry on one or more of the run at startup registry entries.

So: what we need is the contents of the keys mentioned in the KB. And a
list of intsalled programs. And possibly installed hardware devices.





Gary said:
Sorry if this is redundant. I couldn't find anything identical.

I'm trying to clean/salvage a Win/XP home system for the
family of a recently deceased owner. The system has/had
a whole lot of useless processes active, that just needed
removal, along with some other family training.

So, I'm finalizing my last clean-up activities with removal
of a lot of AOL trash, and I let a shared .dll removal message get by(answer
yes or yes to all), and a member
was removed from system32, causing an obvious direct-
ory update.

Now, although the XP system operates great, initialization
/reboot produces a system32 directory presentation that
describes something like - "system directory, do not mod-
ify".(I'm returning to the site this weekend for the exact
text description)

Within this system32 directory presentation is an addition-
al description where the date/time of the modification is
noted as 05/11, so I know it was caused by my activities. All of the similar
problems I've found on the net, related to this issue, have been noted as
registry problems. This may well be such a problem also(since there was some
kind of a registry cleaner/monitor product installed/active on this system,
but was removed before this problem occurred).

But, unlike the other related net items found during my
research, I seem to have the cause closely identified. The
simple response to this warning presentation is just to
close the window. However, it needs to be corrected.
Click to expand...

It's not a warning presentation, if you click on the link it'll display
the contents of the folder. The message is saying more or less not to
muck with the folder unless you know what you're doing.

I've reviewed:
http://support.microsoft.com/default.aspx?scid=kb;en-us;170086
but haven't taken any actions mentioned within, as yet,
pending some additional opinions.

So does XP really monitor system32 for modifications, or
might anyone else have experienced such a problem.
Click to expand...

It's on my dad's machine, he chose to leave it be as machine was
working fine otherwise.
 
Yes, the system32 folder displays on startup, just as has
been described in the 170086 incident, and numerous
other incidents dealing with XP.

I just thought(aka assumed) that my problem was differ-
ent since I was being show a modification to the system32
directory, for which I allowed to occur. Additionally, the
characteristics of this problem seemed to simply note
that the system32 directory modification had been detect-
ed, and will be reported in perpetuity. <g>

But, when I return to the scene of the crime, I will review
the named registry entries for corruption.

Thanks, for your comments....

Gary
 
Gary said:
Yes, the system32 folder displays on startup, just as has
been described in the 170086 incident, and numerous
other incidents dealing with XP.

I just thought(aka assumed) that my problem was differ-
ent since I was being show a modification to the system32
directory, for which I allowed to occur. Additionally, the
characteristics of this problem seemed to simply note
that the system32 directory modification had been detect-
ed, and will be reported in perpetuity. <g>

But, when I return to the scene of the crime, I will review
the named registry entries for corruption.

Thanks, for your comments....

Gary
Click to expand...

Let us know what happens. Also feel free to paste in the entries into
the NG if you can't locate the culprit. maybe someone will recognise
them.
 
Back
Top