That happens to coincide, more or less, with when Microsoft Update started to fail. On machines that get clobbered, when you look at the files C:\WINDOWS\SoftwareDistribution\ AuthCabs\muauth.cab and C:\WINDOWS\SoftwareDistribution\ AuthCabs\authcab.cab you see a suspicious entry: Poster Steve on the SANS ISC thread noted an important detail. Some of the fixes work on some machines, others don't. For most, though, that approach doesn't work.Īlternatives range from deleting the C:\WINDOWS\SoftwareDistribution folder to running wuauclt.exe /detectnow to chasing chicken entrails. Some people have reported that simply setting the system clock back a couple of weeks and re-running the update bypasses whatever devils may be lurking. There are also lengthy discussions on the SANS Internet Storm Center site and on the MSFN site. The options provided below might help you solve the problem. The website has encountered a problem and cannot display the page you are trying to view. The main TechNet thread on the subject says the error looks like this: (Keep in mind that, although Windows XP is no longer supported, Security Essentials updates for XP still go through Microsoft Update, and all old patches for XP are still available - when Microsoft Update is working.) As best I can tell, Microsoft has not responded to the problem, not documented a workaround, and is doing nothing visible to fix it. 18, some Server 2003, Windows Home Server 2003, and Windows XP SP3 machines suddenly refused to connect to Microsoft Update. The causes of the problem remain cloudy, but the symptoms are quite clear.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |