Corrupted path?

  • Thread starter Thread starter Dave
  • Start date Start date
D

Dave

I believe this may be just part of my pc problems, but I'm having problems
gettting Windows Update to work correctly.

One of the things I found was that the path to svchost for Windows Update is
listed as "%lystemroot%\system32\svchost...." instead of
"%systemroot%\system32\". I don't know how the "s" got replaced with an "l',
but that's what it reads when I look at the properties for Update. I thought
this parameter might be stored in the registry and I could go in and edit it.
But so far I haven't been able to find it. Anyone know where to find this
"%lystemroot%" entry, and how it can be fixed?

It's actually on my best friend's son's pc, with XP and SP2 installed. It
had a lot of registry problems that I cleaned up with an app called
Systemsuite 9 Professional.

Thanks for your help.
 
I believe this may be just part of my pc problems, but I'm having problems
gettting Windows Update to work correctly.

One of the things I found was that the path to svchost for Windows Updateis
listed as "%lystemroot%\system32\svchost...." instead of
"%systemroot%\system32\".  I don't know how the "s" got replaced with an "l',
but that's what it reads when I look at the properties for Update.  I thought
this parameter might be stored in the registry and I could go in and editit.
 But so far I haven't been able to find it.  Anyone know where to find this
"%lystemroot%" entry, and how it can be fixed?

It's actually on my best friend's son's pc, with XP and SP2 installed.  It
had a lot of registry problems that I cleaned up with an app called
Systemsuite 9 Professional.

Thanks for your help.

lystemroot? That's a good one!

Now, fystemroot is well known.

You should start here:

Download, install, update and do a full scan with these free malware
detection programs:

Malwarebytes (MBAM): http://malwarebytes.org/
SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

They can be uninstalled later if desired.

AFTER the scan you need to search your registry for lystemroot and
change them to systemroot by hand. lystemroot is just flat out
wrong. The malware scans won't fix that part, but do the scan first.

Here is a popular, easy and free registry backup tool before you start
editing:

http://www.larshederer.homepage.t-online.de/erunt/

Hold off on (stop) using any registry cleanup/tuneup/fixup/mechanic
type tools.

You are also behind on a Service Pack (3 is current), but I would not
do that yet - it will not fix this problem.
 
Back
Top