Hi folks,

I wonder could anyone help me with a strange problem I am having!

We use SCCM 2012 R2 and I am trying to roll out updates to a Windows 2008 R2 Standard 64 bit server.  When I deploy the updates to the server they get to the server and install but during the reboot it says Windows Modules Installer for a while then shows the failure configuring Windows Updates, reverting changes screen.

Ive tried the suggestions of disabling 'Windows Management Instrumentation' and 'Windows Modules Installer' and renaming the repository folder but still no joy.

If I use Windows Update to install the updates the updates do go on but then when I add it to the collection in SCCM to push out the patches it sees the server as if the updates arent installed and begins doing the installs.  After the patches installs using SCCM and when the server is rebooted it goes back into the loop of saying Windows Modules Installer and reverts the updates and strips out the patches again.

I was hoping that when the Windows Updates were installed via Windows Update and once I put the server into the collection to push out the updates to the server it would have shown that the updates are already installed on the server and show that server as being compliant in SCCM but unfortunately that isnt happening.

It sights a couple of errors in the Setup event logs on the offending server: -

For multiple patches - Package KBXXXXXXX failed to be changed to the Installed state. Status: 0x80070643

For multiple patches - Initiating changes for package KBXXXXXXX. Current state is Invalid Resolved. Target state is Installed. Client id: WindowsUpdateAgent.

After doing some research, 0x80070643 refers to a .Net Framework issue so Ive ran a .Net Repair tool but that didnt work either so Im running out of ideas so any help would be greatly appreciated on how I can get this sever updated using SCCM and showing as compliant.

Thanks,

Bonemister

• Edited by bonemister 16 hours 38 minutes ago

That's not really a ConfigMgr issue. ConfigMgr installed missing and applicable updates (or to be precise: it told Windows Update Client agent to install them). It did so and the OS is applying them before and after the reboot. Examine the eventlog and WindowsUpdate.log to get an idea which patch is failing and why. You could try installing it manually (most likely with the same result). The only way to tell ConfigMgr not to install that patch is removing it from the software update groups that's deployed.