Windows update problems [RESOLVED]

Comodo, I really like your firewall but continue to have problems using the Express method on the Windows Update site. I keep getting the 0x8024402C error unless I change Comodos settings to Allow All traffic. I’ve added all Windows Update URL’s to my trusted zones and have tried deleting both services.exe application rule and svchost.exe application rules. I’ve also created rules for both that allow all access but am still getting the same errors. Pls let me know how to fix this or I’ll be forced to go back to Zone Alarm. Thanks

I confirm this problem too…

The only way to allow Internet Exploerer is to check “Skip Advanced Securiy Checks”. I assume you already allowed IE to allow TCP/UDP in/out with parent windows/explorer.exe

Regards,

Hi, While I am not sure of your problem, I would like to note, Windows update site has been a bit strange the last couple of months. I had problems with ZA a while back, same thing, unless I disabled it , could not update from MS. I moved to CPF a while back and first had issues as well, thought it was CPF, it wasn’t. I had no firewall at all, still couldn’t update. The last update I did, I had to go to different links just to get it to work. Finally , I slipstreamed :wink: smart move. I am not saying it’s not part CPF, you understand, but the update site has been odd for many users and seems to react differently with different firewalls as well. I used Kerio as well, and had to shut it right down to update. CPF, I got an error, ZA wouldn’t allow me at all either. I don’t know if this is your problem or not, but what I do is simply "allow all"on the firewall when doing Windows updates as long as it’s not too long, 16 minutes or less. I have no choice as it seems Windows won’t update with any firewalls I have used. Even without one I have had problems updating and I run DSL. Do you use a router? Also, you could try to reset your IE settings, these cause issues as well. If you don’t know how to reset IE let me know. :wink: It’s worth a try.

Paul

CK, I tried your workaround and still got the same error.

Paul, I used ZA in the past w/no problems at all. You solution really doesn’t solve my problem anyway. I’d like the updates to run and load in the background (I’m not sure they are even doing this still since when I try the manual method it doesn’t work). It has to be a Comodo issue because when I turn it off everything works ok. It has to have something to do with the firewall blocking svchost.exe and parent services.exe. I can see Access Denied logs being written when I’m trying to update. How can I set the firewall to allow scvhost/services? I tried deleting the entries and creating new ones w/allow all options and both did not work. I also have DSL and a router but did not try your reset IE suggestion yet. I’m also using IE beta 7 if it makes a difference.

PS, what is slipsteaming that you mentioned?

I see now. Ok, one thing at a time then.

1.) You are using IE beta, the beta version is what it is, beta (in testing, no guarantee ) and no softwares can guarantee (including IE7) that all will work right. It may be a CPF \IE beta problem. I have sinced streamed away from IE at all. I leave IE 6 and only use it for updates. Firefox is far more secure and have had no issues with it. So I will be honest and say I haven’t been partial to IE for a while now. Although MS promises IE7 to be the most secure, we’ll see… :wink: Either way, it may be an IE7 issue or as stated, both together.

2.) Did you install IE 7 before or after CPF, I may suggest uninstalling CPF, do a reinstall with auto configuration. Or simply do a reinstall.

3.) If you set them to allow, then it must be another issue. Did you look in component monitor and see if all items are allowed as well?

4.) If it is a CPF issue, I will do a look around the forums to see if anyone else has had this issue.

5.) Slipstreaming is when you have a “legal” copy of windows, non-OEM version, you can create a reinstall disk of your windows OS , only slipstreamed “combined with” all current updates, patches, etc…Now when I install windows, I don’t have to go through 68 update downloads\installs just to have Windows up an running. It installs as normal as my original OS disk, but takes much less time to actually get up and running. Very nice to say the least.

anyway, i’ll do some browsing on this issue unless someone else has an idea.

Paul

Hi mmura,

in addition, this is key!! Please, can you provide the details of those denied logs. It can help us get your rules set up properly to allow updates. The problem could be in your “Network Monitor” rules, maybe a “Block” rule that needs moving down the list.

In addition please post what it says in “WindowsUpdate.log” (found in %SYSTEMROOT%)… just the last update will be fine (rather than the whole log file).

cprtech, sorry but I read your post after I did an uninstall & reinstall which solved the problem. The logs basically said that scvhost was being denied access.

kail, here’s some of my windows update log below. It was hard for me to tell when an event started & stopped so I just pasted a few lines. Let me know if you want more & I’ll provide.

2006-09-30 13:44:24 784 6fc AU # WARNING: Search callback failed, result = 0x8024402C
2006-09-30 13:44:24 784 6fc AU #########
2006-09-30 13:44:24 784 6fc AU ## END ## AU: Search for updates [CallId = {6C6B3ACB-C115-4D29-9D42-B4B633E7A11A}]
2006-09-30 13:44:24 784 6fc AU #############
2006-09-30 13:44:24 784 6fc AU AU setting next detection timeout to 2006-09-30 23:44:24
2006-09-30 13:45:06 784 324 Misc WARNING: Send failed with hr = 80072ee7.
2006-09-30 13:45:06 784 324 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2006-09-30 13:45:06 784 324 PT + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
2006-09-30 13:45:06 784 324 PT + Caller provided credentials = No
2006-09-30 13:45:06 784 324 PT + Impersonate flags = 0
2006-09-30 13:45:06 784 324 PT + Possible authorization schemes used =
2006-09-30 13:45:06 784 324 PT WARNING: GetCookie failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
2006-09-30 13:45:06 784 324 Report Uploading 1 events using cached cookie, reporting URL = http://stats.update.microsoft.com/ReportingWebService/ReportingWebService.asmx
2006-09-30 13:46:06 784 324 Misc WARNING: Send failed with hr = 80072ee7.
2006-09-30 13:46:06 784 324 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2006-09-30 13:46:06 784 324 Report WARNING: Failed to upload events to the server with hr = 80072ee7.
2006-09-30 13:46:06 784 324 PT + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
2006-09-30 13:46:06 784 324 PT + Caller provided credentials = No
2006-09-30 13:46:06 784 324 PT + Impersonate flags = 0
2006-09-30 13:46:06 784 324 PT + Possible authorization schemes used =
2006-09-30 13:46:06 784 324 PT WARNING: ReportEventBatch failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
2006-09-30 13:46:06 784 324 Report WARNING: Reporter failed to upload events with hr = 8024402c.

Thanks to the moderators for your help.

I think we might need more before 13:44:24 (look at the time for reference).

Don’t forget to post the entries in your CPF logs that are relevant to the Windows Update attempt & a nice picture of your Network Monitor rules. Until these are posted, we don’t have the whole picture.

Many thanks…

So the problem is now solved mmura? Unfortunately, svchost requires more than usual access for Windows Updates, unless you decide to manually retrieve them from here

http://www.microsoft.com/downloads/Browse.aspx?displaylang=en&categoryid=7

For Automatic or Custom updtaes, It needs UDP to port 53 and TCP to port 443.

Glad to hear it’s solved. :slight_smile:
My thought was it sometimes matters with firewalls when they were installed after or before another major application to work properly, plus I felt that after you deleted, etc…it was better to start with a “clean slate” in case it didn’t work, so we could get a shot of the system freshly installed\unmodified so it would be easier to deal with the settings. >Then I would leave it to Kail and cprtech, lolll. They know their stuff. :wink:
Cheers,

Paul

kail, let me know if you want more of the update log, otherwise the problem has been solved. Thanks again

If the problem has be resolved, then no more logs are needed. Thanks.