Seems like my last successful update was 3/14 at around 9:30am. It was running on a schedule, and I think still tries. When I try to run it manually, I get the following:80072EE2I'm wondering if there is a problem with the update servers maybe? I can't think of anything I installed Saturday or Sunday which would be causing this. A week or more ago, I added a purchased code for my AVG Internet Security software, but that had been running for a month or more with no issues. I have the firewall on, but technically, it's sitting in 'let everything through' mode anyways.Just curious if anyone ran into this recently, or perhaps in the past and has found any solutions for it.

asfaraslarry said: Seems like my last successful update was 3/14 at around 9:30am. It was running on a schedule, and I think still tries. When I try to run it manually, I get the following:80072EE2I'm wondering if there is a problem with the update servers maybe? I can't think of anything I installed Saturday or Sunday which would be causing this. A week or more ago, I added a purchased code for my AVG Internet Security software, but that had been running for a month or more with no issues. I have the firewall on, but technically, it's sitting in 'let everything through' mode anyways.Just curious if anyone ran into this recently, or perhaps in the past and has found any solutions for it. HiThis error code returns as: 0x80072EE2- ERROR_INTERNET_TIMEOUT - The request has timed out.The most common cause is that the update servers are busy. This could be due to heavy traffic, the servers are down for maintenance, or.....?Here are more possible, but less likely issues.You may encounter temporary connection-related errors when you use Windows Update or Microsoft Update to install updatesWindows Update error 80072ee2Hope this helps.Thank You for testing Windows 7 Beta Ronnie Vernon MVP

Thanks Ronnie.You know, I believe it is an issue with my AVG. Something about it changed causing my connection issues. I uninstalled it completely, and I can update again. I'm going to need to take a closer look at why their 'allow all' doesn't really 'allow all', it would seem.