Dylan Greene dot com

I can't read this site [2cpu.co.kr], but if you go about half-way down there's a link to my blog entry about fixing Windows Update Error 0X800A138F.

This is one of many message boards where Windows users are frustrated beyond belief because when they try to use Windows Update they get error "0x800A138F" without any explanation or suggestions for how to fix it. My blog entry on how to fix it was written in August, about four months ago. Today it has been viewed over 1000 times. There's been over 8000 page views across my entire site in the last 24 hours, so that means 1 out of every 8 visitors has come to see how to fix that Windows Update error.

You'd think Microsoft would realize how many people are getting this error and put some help for fixing it on Windows Update (or fix Windows so it won't happen), but I'm guessing the Windows Update team doesn't even realize how popular this error is because when you use Windows Update no information is sent to Microsoft - for privacy reasons. I think that "privacy reasons" are going to far here, when there's a problem such as Windows Update not working at all (which is the case with this error), there should be an option to let Microsoft know whatever they need to know to learn about the issue and help you fix it.

There's many reasons for this error, and all are easily fixable if you know what's wrong. Popular reasons for why Windows Update won't work include IE's default language not set and the date being wrong, but how would any user know this?

If you are suffering from Windows Update not working, learn how to fix it here.