I’ve had this happen to me a few times now. Fresh Windows Server 2008 install wants you to go online and get updates. Yet I am faced with this error:
The “dreaded” Code 80244022. OK, I dunno how dreaded that is, but I hate long numeric code errors. They usually correlate to a high p.i.t.a. factor.
If you click on that “Get Help” link and tunnel around the support stuff, eventually you’ll get a hint that maybe the windows firewall is goofing up. Last time I had this happen I just disabled the firewall and it worked fine. But, clearly, that’s not always the right solution — especially outside of the lab.
This time I realized it is a very simple fix. One checkbox in fact:
Just check the box for BITS Peercaching and you’re good to go.
I’ll probably forget this within a few days — but next time I search on it I hope to quickly find the answer here!
Possibly Related posts:
November 9th, 2008 
Tags: 
[...] Update would no longer work. It kept failing with an Error 0×80072EE2. I recalled that I had similar Update issues last month with Server 2008 but how I fixed that one wasn’t an option (no “Bits” exception to [...]