HOW TO UNINSTALL WINDOWS UPDATE AGENT PATCH
HOW TO UNINSTALL WINDOWS UPDATE AGENT DOWNLOAD

Restart your computer after the update has been installed. Note: In this case it is possible to completely suppress a restart.If you choose to apply all required changes outside your scheduled business hours : (By default the business hours are set from 5:00 AM to 10:00 PM Monday through Friday) you can view Microsoft should hopefully be putting out more information on troubleshooting/fixing, when/if things do go wrong with this patch.It's much simple and easy-to-use. I think for now, I'm going to hold off on applying KB2938066. Hopefully that will get you on the right track. For instance, are all machines in the environment having issues checking in for updates? Or just certain operating systems? If it's just certain operating systems, what version of the Windows Update Agent do they have? 256? Is their behavior the same? I think the first step would be to try and find the common ground. Do you have any machines that are still at. 320, which I believe is the latest release (depending on the O/S). On the WindowsUpdate.log that you pasted above, what is the operating system on that machine? I see that it's already at Windows Update Agent version.

HOW TO UNINSTALL WINDOWS UPDATE AGENT PATCH

I'm always wary of 'patching the patch infrastructure', because if something goes wrong, the entire environment could be affected. I'm sorry to hear that you're having issues.

HOW TO UNINSTALL WINDOWS UPDATE AGENT DOWNLOAD

Here is part ot the WindowsUpdate.log in case you have some advice for me.ДЄgent ** START ** Agent: Finding updates ДЄgent * Online = Yes Ignore download priority = NoДЄgent * Criteria = 'IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1'ДЄgent * ServiceID = ]

Unfortunatelly, these changes cannot be rolled back.

Most of all, I ran into some issues in our second (an much larger environment), where the WSUS server (WS2008 R2 SP1 with WSUS 3.0 SP2) stopped self-updating and other server clients (mostly WS2008 R2 SP1) have troubles checking in after installing KB2938066.

As you mentioned, the clients need to be updated in different way unless managed by WSUS directly. I installed the update on my SCCM/WSUS machine (fully patched WS2012 R2) and the clients were not checking in for the updates. Just not sure if I should include KB2938066 with this month's updates.ДЄs we have similar environment I would not recommend installing KB2938066 just yet. I want to make sure that if I update the main SCCM/WSUS server, I don't create some sort of 'mismatch', where the clients wouldn't be able to receive updates (until they get the newer Windows Update Agent at a later time.) My Primary/SCCM server is Windows 2012 R2, fully patched as of last month. 256) throughout the environment at this point. My question is, has anyone applied KB2938066 to their WSUS servers yet? If so, are your SCCM clients still checking in and getting Windows updates without any issues? I don't think we're ready to update the Windows Update Agent version on our clients (currently. This blog goes into more depth on that scenario: But in an SCCM environment, most of us have disabled Automatic Updates per best practice recommendations, and the updating of the client WUA version needs to be done via some other method. In this month's list of updates, Microsoft came out with new patch for WSUS servers (3.0 and above.) In a 'normal' WSUS environment, updating the main WSUS server would then automatically/gradually update all of the managed clients to the latest Windows Update Agent.

How to uninstall windows update agent