Re: Automatic Updates Will Not Turn On

No problemo, DCB. You've done the right thing, as painful as it was.
If it all possible, suggest you steer clear of security suites as they tend to get nothing right while attempting to do everything.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


DCB wrote:

Mow,
I was away for the weekend and just saw your reply. As I have been dealing with this for almost a week now I decided to try another route. I re-formated my hard drive and re-installed Windows. It was kind od a pain to have to re-install all of my programs, but at least I know that everthing is fresh now. I really appreciate all of your help. It was just easier for me this way.

"MowGreen [MVP]" wrote:


Either McAfee or malware is preventing the operation from being carried out. The only way you can determine which is the culprit is to rule out one or the other first.
You state that the system was infected with a virus but it was cleaned up by Spyware Doctor. One would assume that McAfee would have cleaned up the virus as that's one of it's functions ... an antivirus.
Spyware Doctor is not an antivirus.

Suggest you first ensure that the system is totally free of malware.
If you've already done that, then either system files have been damaged beyond use by the malware or McAfee is the cause of the file replacement issue.

Consult McAfee's User Guide or web site to learn how to completely disable *all* of Security Center's protections. This includes all running services, script blockers, site blockers, etc.
Learn how the firewall can be disabled and how to enable the native Windows firewall.

After learning the above, disconnect from the network prior to enabling the Windows firewall.
Then see if the system can successfully update.

If not, we'll have elimnated malware and McAfee as the causes of the updating issue.

Then we'll run a new tool to see if it can restore the system's ability to update successfully.
Hang in there.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============




DCB wrote:


I am running McAfee Security Center
That is the antivirus program and firewall.
when I got the virus in the computer I loaded Spyware Doctor with a malware program.
I have a home network setup in my house with 2 other computers on it. There has been no problems with either of the other computers though.

"MowGreen [MVP]" wrote:



2008-05-21 18:46:35:890 2368 a3c Setup WARNING: Could not move C:\WINDOWS\system32\wuapi.dll to
C:\WINDOWS\system32\wuapi.dll.wusetup.1842453.bak due to 0x80070020

Some 'thing' is interfering with the above operation.

What is the installed antivirus\security suite and/or anti-malware software ?
[ An older Version of Spybot is the cause of the 0x80070020 error when TeaTimer is enabled ]

Which firewall is being used ?
Is the system on a network ?

You receive a "0x80070020 The process cannot access the file because it is being used by another process" error message when you try to download an update from Windows Update
http://support.microsoft.com/kb/883825

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


DCB wrote:



Yes the 1058 error occurs after I change the setting to autoatic, then I try to start it and I get the 1058 error. I am not sure what you mean by post the last 50 or so lines. I am not sure where to find the log to copy and paste the lines. Is this what you meant?:

2008-05-21 18:46:35:453 2368 a3c Setup ** START ** Setup: Installing client binaries
2008-05-21 18:46:35:453 2368 a3c Setup *********
2008-05-21 18:46:35:453 2368 a3c Setup * Download directory: C:\WINDOWS\SoftwareDistribution\WebSetup
2008-05-21 18:46:35:453 2368 a3c Setup * Stop and start service: Yes
2008-05-21 18:46:35:531 2368 a3c Setup Starting file operations for section wuapi
2008-05-21 18:46:35:859 2368 a3c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuapi.dll to C:\WINDOWS\system32\wuapi.dll.wusetup.1842406.new
2008-05-21 18:46:35:890 2368 a3c Setup WARNING: Could not move C:\WINDOWS\system32\wuapi.dll to C:\WINDOWS\system32\wuapi.dll.wusetup.1842453.bak due to 0x80070020
2008-05-21 18:46:36:203 2368 a3c Setup File operations for section wuapi completed successfully
2008-05-21 18:46:36:218 2368 a3c Setup Starting file operations for section wuauclt
2008-05-21 18:46:36:515 2368 a3c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauclt.exe to C:\WINDOWS\system32\wuauclt.exe.wusetup.1843046.new
2008-05-21 18:46:36:562 2368 a3c Setup Setup successfullly moved C:\WINDOWS\system32\wuauclt.exe.wusetup.1843046.new to C:\WINDOWS\system32\wuauclt.exe
2008-05-21 18:46:36:562 2368 a3c Setup File operations for section wuauclt completed successfully
2008-05-21 18:46:36:578 2368 a3c Setup Starting file operations for section wuaucpl
2008-05-21 18:46:36:796 2368 a3c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaucpl.cpl to C:\WINDOWS\system32\wuaucpl.cpl.wusetup.1843359.new
2008-05-21 18:46:36:875 2368 a3c Setup Setup successfullly moved C:\WINDOWS\system32\wuaucpl.cpl.wusetup.1843359.new to C:\WINDOWS\system32\wuaucpl.cpl
2008-05-21 18:46:36:875 2368 a3c Setup File operations for section wuaucpl completed successfully
2008-05-21 18:46:36:890 2368 a3c Setup Starting file operations for section wuaueng_WebSetup
2008-05-21 18:46:37:375 2368 a3c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng.dll to C:\WINDOWS\system32\wuaueng.dll.wusetup.1843937.new
2008-05-21 18:46:37:437 2368 a3c Setup Setup successfullly moved C:\WINDOWS\system32\wuaueng.dll.wusetup.1843937.new to C:\WINDOWS\system32\wuaueng.dll
2008-05-21 18:46:37:437 2368 a3c Setup File operations for section wuaueng_WebSetup completed successfully
2008-05-21 18:46:37:453 2368 a3c Setup Starting file operations for section wucltui
2008-05-21 18:46:37:640 2368 a3c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wucltui.dll to C:\WINDOWS\system32\wucltui.dll.wusetup.1844203.new
2008-05-21 18:46:37:765 2368 a3c Setup Setup successfullly moved C:\WINDOWS\system32\wucltui.dll.wusetup.1844203.new to C:\WINDOWS\system32\wucltui.dll
2008-05-21 18:46:38:531 2368 a3c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\en\wuau.adm to C:\WINDOWS\INF\wuau.adm.wusetup.1845109.new
2008-05-21 18:46:38:562 2368 a3c Setup Setup successfullly moved C:\WINDOWS\INF\wuau.adm.wusetup.1845109.new to C:\WINDOWS\INF\wuau.adm
2008-05-21 18:46:38:562 2368 a3c Setup File operations for section wucltui completed successfully
2008-05-21 18:46:38:578 2368 a3c Setup Starting file operations for section wups
2008-05-21 18:46:38:703 2368 a3c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wups.dll to C:\WINDOWS\system32\wups.dll.wusetup.1845265.new
2008-05-21 18:46:38:765 2368 a3c Setup File operations for section wups completed successfully
2008-05-21 18:46:38:765 2368 a3c Setup Starting registry operations for section wuapi
2008-05-21 18:46:38:781 2368 a3c Setup Completed registration operations for section wuapi: status 0
2008-05-21 18:46:38:796 2368 a3c Setup Starting registry operations for section wuauclt
2008-05-21 18:46:38:796 2368 a3c Setup Completed registration operations for section wuauclt: status 0
2008-05-21 18:46:38:796 2368 a3c Setup Starting registry operations for section wuaucpl
2008-05-21 18:46:38:796 2368 a3c Setup Completed registration operations for section wuaucpl: status 0
2008-05-21 18:46:38:796 2368 a3c Setup Starting registry operations for section wuaueng_WebSetup
2008-05-21 18:46:38:812 2368 a3c Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"
2008-05-21 18:46:44:593 2368 a3c Setup Completed registration operations for section wuaueng_WebSetup: status 0
2008-05-21 18:46:44:609 2368 a3c Setup Starting registry operations for section wucltui
2008-05-21 18:46:44:609 2368 a3c Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wucltui.dll"
2008-05-21 18:46:45:562 2368 a3c Setup Completed registration operations for section wucltui: status 0
2008-05-21 18:46:45:578 2368 a3c Setup Starting registry operations for section wups
2008-05-21 18:46:45:578 2368 a3c Setup Completed registration operations for section wups: status 0
2008-05-21 18:46:45:578 2368 a3c Setup Processing registry operations completed. Deleting backup files.
2008-05-21 18:46:45:578 2368 a3c Setup Successfully deleted backup file C:\WINDOWS\system32\wuauclt.exe.wusetup.1843109.bak
2008-05-21 18:46:45:593 2368 a3c Setup Successfully deleted backup file C:\WINDOWS\system32\wuaucpl.cpl.wusetup.1843390.bak
2008-05-21 18:46:45:593 2368 a3c Setup Successfully deleted backup file C:\WINDOWS\system32\wuaueng.dll.wusetup.1843968.bak
2008-05-21 18:46:45:609 2368 a3c Setup Successfully deleted backup file C:\WINDOWS\system32\wucltui.dll.wusetup.1844234.bak
2008-05-21 18:46:45:609 2368 a3c Setup Successfully deleted backup file C:\WINDOWS\INF\wuau.adm.wusetup.1845125.bak
2008-05-21 18:46:45:625 2368 a3c Setup FATAL: Warning: Failed to restart wuauserv service: 0x80070422
2008-05-21 18:46:45:625 2368 a3c Setup * WARNING: Exit code = 0x80070422
2008-05-21 18:46:45:625 2368 a3c Setup *********
2008-05-21 18:46:45:625 2368 a3c Setup ** END ** Setup: Installing client binaries
2008-05-21 18:46:45:625 2368 a3c Setup *************
2008-05-21 18:46:45:625 2368 a3c Setup FATAL: InstallUpdatedBinaries failed with error 0x80070422
2008-05-21 18:46:45:625 2368 a3c WUWeb FATAL: InstallUpdatedBinaries failed with error:0x80070422
2008-05-21 18:46:45:625 2368 a3c WUWeb FATAL: UpdateClientWorker failed: error 0x80070422

Any help is greatly appreciated!

.

Relevant Pages

  • Re: Automatic Updates Will Not Turn On
    ... Suggest you first ensure that the system is totally free of malware. ... Learn how the firewall can be disabled and how to enable the native ... the Windows firewall. ... section wuaucpl ...
    (microsoft.public.windowsupdate)
  • Re: Password vault software
    ... The malware has to target the specific software firewall. ... Windows Firewall with a proper network configuration" but never addresses application control. ... If the malware is there, and since there ARE times when users need admin rights to do something, like installs or manage user profiles or take ownership of files, BOOM, the malware is still there when the user has to go into an admin account. ...
    (alt.computer.security)
  • Re: firewall
    ... I found it under Windows Firewall so,> I ... >> You cannot start the Windows Firewall service in Windows XP Service>> Pack ... then click on the Dependencies tab. ... Since all of this started with what appears to be a malware infection, I would start with doing a thorough check for malware yourself. ...
    (microsoft.public.windowsxp.general)
  • Re: Cant Firewall/Remote
    ... If the Windows Firewall is not running then all ports used on the computer ... your computer for malware since malware is a common cause of problems with ...
    (microsoft.public.windowsxp.security_admin)
Loading