NOD32v4 interfering with Windows Update

[Proactive Services]

I'm using Eset NOD32 anti-virus 4.0.437.0 on Windows Vista Ultimate 32-bit SP2. Since I installed NOD32v4 I have noticed that some Windows Updates do not install, causing error 80072F78. When disabling NOD32 the update installs successfully. I most recently had this with update KB973874, a IE8 Compatibility View List. I have noticed this problem affecting the Windows security updates too.

Has anyone else come across this problem?

Detailed NOD32 info:
Virus signature database: 4397 (20090905)
Update module: 1028 (20090302)
Antivirus and antispyware scanner module: 1234 (20090820)
Advanced heuristics module: 1097 (20090809)
Archive support module: 1101 (20090903)
Cleaner module: 1044 (20090826)
Anti-Stealth support module: 1012 (20090526)
SysInspector module: 1213 (20090507)
Self-defense support module : 1005 (20081105)

[Brambb]

I have come a crossed many Windows update related problems. I don't think NOD32 is the one to blame here. Your error means 'ERROR HTTP INVALID SERVER RESPONSE'.

Here (http://www.vistaheads.com/forums/microsoft-public-windowsupdate/181801-vista-error-fixed-80072f78.html) is a topic about the error you have.

I also use this script when encounter Windows update related problems:


Echo This batch file will Force the Update Detection from the AU client:
Echo 1. Stops the Automatic Updates Service (wuauserv)
Echo 2. Deletes the LastWaitTimeout registry key (if it exists)
Echo 3. Deletes the DetectionStartTime registry key (if it exists)
Echo 4. Deletes the NextDetectionTime registry key (if it exists)
Echo 5. Restart the Automatic Updates Service (wuauserv)
Echo 6. Force the detection

@echo on
net stop wuauserv
REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v LastWaitTimeout /f
REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v DetectionStartTime /f
REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v NextDetectionTime /f

regsvr32 /s wuapi.dll
regsvr32 /s wups.dll
regsvr32 /s wuaueng.dll
regsvr32 /s atl.dll
regsvr32 /s msxml3.dll
regsvr32 /s wuapi.dll
regsvr32 /s wuaueng.dll
regsvr32 /s wuaueng1.dll
regsvr32 /s wuauserv.dll
regsvr32 /s wucltui.dll
regsvr32 /s wups.dll
regsvr32 /s wups2.dll
regsvr32 /s wuweb.dll
regsvr32 /s iuengine.dll
regsvr32 /s cdm.dll
regsvr32 /s msxml2r.dll
regsvr32 /s msxml3r.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml2.dll
regsvr32 /s msxml3.dll
regsvr32 /s qmgr.dll
regsvr32 /s qmgrprxy.dll

c:
cd %windir%\SoftwareDistribution
rd /s/q DataStore
mkdir DataStore
rd /s/q Download
mkdir Download

net start wuauserv

net stop "Automatic Updates"
net start "Automatic Updates"

wuauclt.exe /resetauthorization /detectnow

echo echo susid set to unique>c:\wsusfix.txt


Picked it up on a WSUS list once, modified a few things and it has helped me resolving lots of errors I have seen.

[JohnnyDollar]

-{ Quote: "I'm using Eset NOD32 anti-virus 4.0.437.0 on Windows Vista Ultimate 32-bit SP2. Since I installed NOD32v4 I have noticed that some Windows Updates do not install, causing error 80072F78. When disabling NOD32 the update installs successfully. I most recently had this with update KB973874, a IE8 Compatibility View List. I have noticed this problem affecting the Windows security updates too.

Has anyone else come across this problem?

Detailed NOD32 info:
Virus signature database: 4397 (20090905)
Update module: 1028 (20090302)
Antivirus and antispyware scanner module: 1234 (20090820)
Advanced heuristics module: 1097 (20090809)
Archive support module: 1101 (20090903)
Cleaner module: 1044 (20090826)
Anti-Stealth support module: 1012 (20090526)
SysInspector module: 1213 (20090507)
Self-defense support module : 1005 (20081105)" }-

You can also try disabling detection of potentially unsafe/unwanted programs and see if the updates install. It worked for me. Some may argue against doing that, but it has not hurt me, so I leave it turned off.:)

[Proactive Services]

Thanks, I'll give these suggestions a try on Tuesday when the patches come out.

[Proactive Services]

Found the cause - for some reason, svchost.exe was selected in the Web Access Protection Active Mode list. Unchecked it and Windows Update is happy again.