Update issues and Error 8024402F

I've just restored my Asus Eee PC and proceeded to install the available updates. This it did, until I got the above error message and the text Windows Update encountered an unknown error. As I hadn't installed anything, I restored and tried again. Same thing happened. I did notice, however, that the last update it installed was the .NET Framework 4 Client, so I uninstalled that and voila, updates were back offering me that which I had just uninstalled.

I then downloaded and installed the standalone version of .Net Framework 4, and unfortunately got the same resultant Update error message. Again, uninstalling it restored update functionality. Note that the standalone installs both Extended and Client, and they need to be uninstalled separately (Extended first, followed by Client).

Needless to say, I set that update (KB982670) as Hidden so that I don't get offered it again. It would seem that there is a serious issue with .NET Framework 4 and Windows Updates on some systems, my Asus Eee PC being one of them, because removing that program restored Update functionality.

Do you actually need .NET 4? if not then don't install it :)
If you do need it, try installing the Redist version, rather than the client version....
Download Microsoft .NET Framework 4 Client Profile (Standalone Installer) from Official Microsoft Download Center

Thanks Noel. That is indeed the link where I obtained the standalone, only for it to have exactly the same results. This is really just a heads up for those who have suddenly lost their update capabilities after downloading and installing this update (KB982670) that their issue could be potentially resolved by uninstalling it as I have.

No - I suspect that there's a conflict between the dross that OEMs like to pre-install and reality :)
Having said that, it doesn't take much to throw a .NET installation off-kilter and start causing problems. It's really the only one I continue to have problems with - and it needs continual nursing.

Hopefully MS will get the thing right eventually (but since the supported version is now 4.5, I don't personally have to worry about this one!<eg>)