Path to Executable Wrong in BITS and WUAUSERV

  • Thread starter Thread starter Keneedshelp
  • Start date Start date
K

Keneedshelp

Running XP Proffesional 2002 service pack 3. BITS and WUAUSERV have wrong
path to executable. How do I edit the path in services (local)? This must
have happened when a worm or virus attacked. Receiving urgent messages to
turn on automatic updates but when I try cannot find file message pops up. I
ran "windows-kb890830-v2.8" and am running one care. BITS will not start
because the path is wrong and reads %fystemRoot%\System32\svchost.exe -k
netsvcs. Can you help me to change this as I can not turn on Automatic
Updates or receive from Microsoft?
 
The path to the services are held at their respective keys at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

John
 
John John - MVP said:
The path to the services are held at their respective keys at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

John
Click to expand...

I am also facing the same problem and I am running win Xp service pack 2
 
Hi ju.c

I have the same problem. How do you use your fix.reg.txt file to correct the
problem. Thank you.

hab
 
I am using Win XP SP 2 with NOD32 antirus and windows firewall. I am
unable to update windows and when I did research on it I found that the
Path to executable in AU and BITS in services.msc has been changed to
%fystemRoot%\system32\svchost.exe -k netsvcs which should be
%SystemRoot%\system32\svchost.exe -k netsvcs  and in regedit the image
path has also been changed but I am unable to edit anything .Pls suggest
any solution for this.I found a fix which was been posted by you for
Wind 2000 Can it be usable for Win XP SP 2

--
karthigeyan
------------------------------------------------------------------------
karthigeyan's Profile:http://forums.techarena.in/members/90186.htm
View this thread:http://forums.techarena.in/windows-xp-support/1153012.htm

http://forums.techarena.in
Click to expand...

That fystem stuff is malicious software that has changed that for you
and probably in other places. I can't remember which malicious
entity, but recognize it.

Running a registry file to change those two will fix them, but unless
you have fixed the real problem (malicious software), you have only
fixed a symptom of the problem.

Search your registry for fystem and see how many more you find. Maybe
it is just those two, I can't remember, but if you have not gotten rid
of the malware, you have not fixed your problem.
 
Hi ju.c,

I found out how to import the .reg file, however I am getting the following
message: "Cannot import. Some keys are open by the sustem or other processes."

Please help.
 
The fix file is named "fix.reg" not "fix.reg.txt".

Rename it to "fix.reg" then double-click it or right-click it
and select "Merge".


Regarding your importing error,
Paste these lines into the Run box, one at a time:

reg delete HKLM\SYSTEM\CurrentControlSet\Services\BITS
reg delete HKLM\SYSTEM\CurrentControlSet\Services\wuauserv

and this one, too:
(enter the path to fix.reg)

reg import "C:\Path To\fix.reg"


ju.c
 
Back
Top