In addition, a review of the update history (click on "Review your update history" in the left side gray stripe) showed no failures at all.I had even checked the system event logs and come up empty.Microsoft Windows is the most widely used desktop operating system in the world. For many of us, supporting it is how we make our living.One of the endearing and annoying features of this ubiquitous OS is the monthly patch update process. It just kind of works in the background when you're not looking. I'll install the updates on a non-critical server during the week to test them. But for the workstations it does a pretty good job - most of the time.
We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions.If you are using Group Policy settings to configure Windows Update, use the Resultant Set of Policy (RSOP) tool (Rsop.msc) to check the computer’s effective configuration.Within RSOP, browse to the Computer Configuration\Administrative Templates\Windows Components\Windows Update node and verify the configuration settings. If you think WSUS is not configured correctly, verify the IIS configuration.So I do a Remote Desktop session to the machine in question and run the process manually. I used to spend hours looking up ways to get around these errors. This process of switching from the newer method to the older one and then back again seems to fix a host of registry errors and other wastes of time.I know something is really messed up when I get a 0x8024001D error or some other stupid hex number. At one time I liked Scott Hanselman's method of renaming the c:\windows\Software Distribution\Download to c:\windows\Software Distribution\ Click on "Disable Microsoft Update software and let me use Windows Update only" and then click on "Apply changes now." After the silly thing asks if you are sure (duh! It is simple and fast and has almost always worked for me.