How do I repair Path to Executable as I am unable to Update Window

The current problem relates to the SERVICES - AUTOMATIC UPDATES PROPERTIES -
And the Path to Executable. I believe the path is incorrect and the Service
will not start. I receive Error # 0X08007041D.

If you could possibly explain in detail , why a Path to Executable gets
changed, how I would change it / if that would correct the problem. IE: I
see a Path and let us say (for the sake of this argument) it currently says
C:\WINNT\ 3ystem32\services.exe - when we know it should in fact be
C:\WINNT\system 32\services.exe.

The reason I ask this is due to the problem I currently have with this
computer we are working on today and I am also experiencing a very similar
problem with a computer I am working on at another location at a private
residence where I ran into the Background Intelligence Transfer Service and
Event Log Path to Executable both hosed! That is why I ask the question - how
I would change it / if that would correct the problem?

"wcdep" <> wrote in message
news:6CFB4363-BF52-4F17-9433-...
> The current problem relates to the SERVICES - AUTOMATIC UPDATES PROPERTIES -
> And the Path to Executable. I believe the path is incorrect and the Service
> will not start. I receive Error # 0X08007041D.
>
> If you could possibly explain in detail , why a Path to Executable gets
> changed, how I would change it / if that would correct the problem.


It looks like that field is an input field.
What happens if you use that dialog to change it?


> IE: I
> see a Path and let us say (for the sake of this argument) it currently says
> C:\WINNT\ 3ystem32\services.exe - when we know it should in fact be
> C:\WINNT\system 32\services.exe.


Except for the extra spaces (which I assume are typos)
this is a very good example of possible disc corruption.
E.g. in hex character 3 is 0x33 and character s is 0x73
a difference of only one bit (e.g. binary 3 in a nibble is 0011
and binary 7 is 0111)


>
> The reason I ask this is due to the problem I currently have with this
> computer we are working on today and I am also experiencing a very similar
> problem with a computer I am working on at another location at a private
> residence where I ran into the Background Intelligence Transfer Service and
> Event Log Path to Executable both hosed! That is why I ask the question - how
> I would change it / if that would correct the problem?


I think it would depend on why it had happened.
E.g. if it is due to malware expect to see it again
unless you identify and eliminate the cause.
If it is due to failing hardware, you have to wonder
what else was/will be corrupted? Etc.

BTW this is probably not the best newsgroup to be looking for advice
about either (checking for a failing drive or checking for malware)
but you haven't given me sufficient clues about your OS to cross-post for you.
Try reposting in a newsgroup which specializes in hardware or maintenance
and error recovery for your specific OS. For advice about malware
a security newsgroup could be a reasonable starting point.


Good luck

Robert Aldwinckle
---