It’s a 28 MB download from Microsoft servers if you’re curious.You can update it online, or do it later via your local update server—once it’s back online.NET Framework 4, failing with the error code 66A (Windows Update encountered an unknown error). At first I wanted to reset the Windows Update components using the official Microsoft Fix it 50202 tool but after thinking for a while, this error code 66A should have nothing to do with a broken Windows Update since other updates were able to install except for . NET Framework 4 Client Profile to its original state”. This time Windows Update reports “The updates were successfully installed” with a checkmark which means the repair fixed the problem and allowed the updates to be installed. An update to WSUS 3.0 SP2 on Windows Server 2008 R2 and Windows Server 2008 (both x64 and x86) seems to break Windows Server Update Services (WSUS) and/or Internet Information Services (IIS) making clients unable to update via WSUS showing error 0x80072EE2.NET Framework 4 with a couple of other updates for Windows.All updates installed without problems except the 3 updates for . NET Framework 4 has somehow got corrupted and needs to be reinstalled. NET Framework 4, I should try the repair option first. NET Framework 4 Client Profile from the list and click on the Uninstall/Change button. NET Framework 4 Client Profile Maintenance window will open and select the “Repair . NET Framework 4, I went to Windows Update again and try to install the 2 updates and 1 security update.
There are three ways you can get these Windows Updates through the tool that is built into your operating system, from Microsoft's website and through Automatic Updates.Either the update is not applicable to this computer or the update no longer exists.Verify that the update still exists and is applicable to this computer from your WSUS server or Windows Update.setting the configuration to Defer Upgrades (1507 & 1511), Defer Feature Upgrades (1607), changing to Current Branch for Business (1703), or even disabling these settings via GPO, the computer will now ALSO download updates directly from Microsoft? I’m frustrated because as mentioned in the beginning of this article, I followed the SCCM configuration steps outlined by Microsoft themselves. Not a single reply was given by Microsoft – and then comments were closed. See here Below are some screen shots our team sent out to the various office IT admins – asking them to never modify these settings when setting up a new machine.Allegedly referred to as a “dual scan” scenario, what this truly is is a terrible bug that was not caught months ago. And despite following them to a T – our company was put into a terrible position where devices were saturating Internet links when Windows 10 updates were released. What’s further frustrating is reading the comment section on the Microsoft Blog that brought this to my attention. The problem here is that once a machine is managed by SCCM (and WSUS/updates are configured) these settings are supposed to be hidden.