Hi,

This month, we are having some issues with our monthly fixes deployment in our Lab environment.

For our monthly updates, we always create a new updategroup of all available security and critical fixes per OS (every month). This month we had a problem that on some servers the available updates were not showing in software center. After running the updates deployment cycle, the following message appears for the assigned updategroup: Assignment({B27D0A77-4F09-4019-8B8B-5B49C9B7098F}) already in progress state (AssignmentStateDetecting). No need to evaluate UpdatesDeploymentAgent 16/06/2015 14:19:00 2716 (0x0A9C). It doesn't ever finish, so updates are not displayed. By creating different updategroups (removing some updates) and deploying them, I found that for 1 servers kb2894854 and KB2898869 were the problem. Once this patches were removed from the list, the deployment worked and I could install the remaining updates. Afterwards, I deployed those fixes seperately but again I got the same message in the updatesdeployment.log (already in progress).

So I manually installed those fixes and all seems fine. I'm afraid that the same will occur next month, as the patches will be in the updategroup again. Even now if I deploy the complete updatelist, it still says in progress, even after all the patches are installed and the machine is compliant with that list.

On a second machine, KB3033929 is the culprit. Other servers are there...

Is this a know issue and/or how can we troubleshoot this? I don't find any errors in the logfiles (updatesdeployement, scanagent, windowsupdate,updatstore). I've searched on this issue for days now, but didn't find a solution.

Maybe it is also not a good idea to deploy all available patches but only deploy what has been released the last (2,3...) month(s) and only use those complete patchlist for compliancy tests?

 

On the second machine, I tried to install kb3033929, but this one is failing. After restart, the system is unable to change the status of this patch to "installed".

Any ideas?

Hi,

There are some known issue with 3033929

https://support.microsoft.com/en-us/kb/3033929

You can also try update component reset

https://support.microsoft.com/en-us/kb/971058

I have two machines where I cannot install this patch 3033929, both are SCCM servers (primary site and secondary site).

These are normal VM's (vmware) without any special bootloaders or dual boot...

I have two machines where I cannot install this patch 3033929, both are SCCM servers (primary site and secondary site).

These are normal VM's (vmware) without any special bootloaders or dual boot...

What does the log say, as to why it can't be installed?

Which log?

I manually install the patch, the server reboots and after reboot the setup.log says that the patch failed to be changed to the installed state

• Edited by WiM8 18 hours 23 minutes ago typo

Which log?

I manually install the patch, the server reboots and after reboot the setup.log says that the patch failed to be changed to the install

It is unclear to me, when you manually install the SU does it install correctly? What make you think that it does? Have you reviewed the log file for the SU itself? What happens when you try to re-apply the SU? What does it's log file say?

BTW, I was talking about he SU itself log file.

When I apply the SU via the downloaded source (msu), after reboot the system is reverting the changes for some reason, the setup.log (eventvwr) says that the state failed to change to installed.

Where can I find the log of the actual installation of the patch?

Thanks

When I apply the SU via the downloaded source (msu), after reboot the system is reverting the changes for some reason, the setup.log (eventvwr) says that the state failed to change to installed.

Where can I find the log of the actual installation of the patch?

So that sound like the SU is not installing correctly. You need to lookup what the command line is to generate the log for.

Which log?

I manually install the patch, the server reboots and after reboot the setup.log says that the patch failed to be changed to the installed state

• Edited by WiM8 Wednesday, September 02, 2015 1:26 PM typo

Issue solved for kb3033929!

Sometimes it is indeed all about finding the correct log. I found some errors related to bootmgr in the cbs.log in c:\windows\logs\cbs. Something could not be validated in the bootmgr. When I checked the bootmgr file in c:\windows\boot\pcat, the file was missing. I took the file from another system, rebooted and installed the fix successfully.

Thanks!

• Marked as answer by WiM8 49 minutes ago

Issue solved for kb3033929!

Sometimes it is indeed all about finding the correct log. I found some errors related to bootmgr in the cbs.log in c:\windows\logs\cbs. Something could not be validated in the bootmgr. When I checked the bootmgr file in c:\windows\boot\pcat, the file was missing. I took the file from another system, rebooted and installed the fix successfully.

Thanks!

• Marked as answer by WiM8 Thursday, September 03, 2015 7:00 AM