Endpoint Protection

We have an unmanaged Windows 7 Pro 64-bit client running SEP 12.1.4.    We ran a manual LiveUpdate today and noticed that one of the updates was something called the "AP Portal List".   I think this has something to do with SEP Browser Intrusion Prevention.

So, the issue we are trying to shoot is a problem with Windows Update that popped up after the AP Portal List update.  Microsoft Update fails with either error 802440B or 80244016.    We're not say that the AP Portal List update is the issue, but we're trying to rule out causes for the Microsoft Update failure.   Both the 802440B error and the 80244016 error have something to do with an interruption in the internet connection.   However, we can go to other websites with no problems.

The machine has been working perfectly - no other changes other than the Symantec updates.   Again, not blaming Symantec, just trying to rule out potential causes.

It could just be the Microsoft update site having problems....

today liveupdate had some issues and its been fixed, can you try again?

https://www-secure.symantec.com/connect/forums/definitions-not-updating-1

Have you tried recently? Like within the past hour?

If still problem to confirm pl rollback the def to previous revision and try . I have called Symantec since def not updated for the day 4th they said some issue and delay on def . should work now or try roll back and check. also check with Microsoft to do they have problem Note: you can try rollback only IPs.

We don't think it's related to any of the Symantec defs.   We've run the Microsoft Windows Fixit tool - the tool didn't report any problems.   We're getting some connection related error messages.

So, I'm closing this thread as it looks like it's not related to SEP.

Thanks to all for your comments.

Resolution - although it's not related to SEP, I want to share what worked for us.   Don't like threads that don't post their resolution.

Apparently, it's related to the Microsoft Windows Update site but not sure exactly how.   We were getting generic "try later" communications errors.  We went through MS troubleshooting doc.   One suggestion was to set Windows Update to retrieve updates from the Microsoft Update site instead of the Windows Update site.

We used the opt-in for Microsoft Update (in Win 7 it's located mid-way down on the Windows Update page - "Get updates for other Microsoft products".  

We set the client to get updates from Microsoft update and it now works.   Don't know why Windows Update was having problems.

Lastly, be aware that the opt-in for Microsoft Update will set your update preferences to "Automatically check and install".   You can stop Windows Update while it's checking for updates and set your preferences to something else if desired.

We're a small shop and don't use WSUS.