Windows Update error 80072ee2 generally refers to a problem with your firewall exceptions or “allow” list, but if you’re using your local WSUS, then it’s not a simple case of limited access to. Error(s) found: Code 80072EE2 Windows Update encountered an unknown error. On the surface at least, the server looks OK: It synchronizes with upstream Microsoft servers, displays newly-published updates, approves and declines as been told, and downloads approved updates flawlessly.īut deep inside the WSUS server, things are a mess: The WSUS server is the only computer that can get updates from itself, it cannot communicate with clients, and after a few days, all computers-except for the WSUS server itself-are listed as This computer has not reported status for X or more days.įurther investigations reveals clients (ranging from Windows XP to Windows 7 and Windows 8) fail to update showing Windows could not search for new updates An error occurred while checking for new updates for your computer. So, if you know for sure the exact update that does this, please comment. To me, the subversive update number is not clear yet. An update to WSUS 3.0 SP2 on Windows Server 2008 R2 and Windows Server 2008 (both 圆4 and x86) seems to break Windows Server Update Services (WSUS) and/or Internet Information Services (IIS) making clients unable to update via WSUS showing error 0x80072EE2.
