An update to WSUS 3.0 SP2 on Windows Server 2008 R2 and Windows Server 2008 (both x64 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.To me, the subversive update number is not clear yet.What if you don’t want the number of rows it determines?

updating windows registry-63updating windows registry-77

As many companies have found to their cost, installing security updates can be the difference between a working PC and a desk-sized paperweight.

Thankfully, although Microsoft has long since abandoned support for the operating system, Microsoft is still continuing to develop updates, even if they aren't strictly intended for Windows XP users.

So, if you know for sure the exact update that does this, please comment.

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.

The Charms bar in Windows 8 pops up the second you move your mouse to the top right or bottom right corner of the screen.

I find it annoying because I do this by accident a lot.

The beauty of the two systems being so interlinked is that updates designed for one system should work on the other.

As discovered on Beta News, tricking your home edition of XP into thinking its Windows Embedded POSReady means you get updates for the next five years.

This shows that IIS and its pipings are broken and client computers cannot communicate with the server.

Another symptom and a confirmation of the broken IIS hypothesis is a selection of the following warning and error events listed for Windows Server Update Services: service prior to manipulation.

While most of us have long since consigned Windows XP to the Recycle Bin of history, there are still plenty of PCs out there running Microsoft's long-since-defunct operating system.