Exchange 2010 Sp3

You can upgrade RU 11 directly. Please provide us the failed error message occur during the installation.

There is no error, it starts the process of stopping the services and then it starts rolling back and says not changes were performed to the system. It nevers goes pass stopping services before it instantly starts the roll back. See attached Exchange Setup logs.
ServiceControl.log
ServiceStartupMode.xml
ServiceState.xml

Numerous hits say to turn UAC back on and to install it from an elevated command prompt: http://www.msdigest.net/2014/03/setup-wizard-for-exchange-update-rollup-ended-prematurely/

Also it could be waiting for reboot from another update.   As Mr. McCarn said try UAC on and from elevated but after that reboot system properly and try update again.

I have rebooted multiple times, and tried again. I have attempted to install with UAC on from and elevated account and that failed also.  I found the following link and i will try this and see what happens and I will update.

https://support.microsoft.com/en-us/kb/2784788#/en-us/kb/2784788

I have attempted the fix on the link but still no luck. See the attached rollup log, maybe there is something there that one of you have seen before that may help.
rollup.txt

Yes; about 95% of the way down your log is CAQuietExec:  Error 0x80070001

According to this, its a machine or user policy which needs to be set to "not configured":
https://support.microsoft.com/en-us/kb/981474

Davis I will try this and update.

Those polices were set to unrestricted but I have made the changes on the GPO, and verified that those userpolicy and machinepolicy are now undefined. I still get the exact same result. I forced the gpupdate and the applied the new undefined policy. I didn't reboot the server though, but I still get the same issue when trying to update. See new log.
rollup3.log

Is this a server that's a member of a database availability group (DAG)?
If it is:
https://technet.microsoft.com/en-gb/library/ee861125(v=exchg.141).aspx

Yes it is a member of the DAG, but the DAG maintenance script doesn't even run, it gives an error. Anytime I update, I manually move the active DB copy to a different DAG member. They had a contractor working on Exchange before I came aboard and he also installed Windows Server 2012 DataCenter on the Exchange Servers along with WMF 4.0, so I have also removed WMF 4.0 from the servers, but the DAG maintenance script has never worked.

Are you a member of the domain admin's group?

Yes I am a member of that group.

"but the DAG maintenance script doesn't even run, it gives an error"  What, EXACTLY, is the error?

Not sure, I haven't run it in about 3 weeks. I would have to try that again later but that script definitely fails.

Then we're stuck until you have that error.

This is the error from DAG maintenance script:

At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\DagCommonLibrary.ps1:494 char:6
+         return $moveSuccessful
+         ~~~~~~~~~~~~~~~~~~~~~~
Control cannot leave a finally block.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\DagCommonLibrary.ps1:926 char:5
+                 return $success
+                 ~~~~~~~~~~~~~~~
Control cannot leave a finally block.
    + CategoryInfo          : ParserError: (:) [], ParseException
    + FullyQualifiedErrorId : ControlLeavingFinally

Test-RsatClusteringInstalled : The term 'Test-RsatClusteringInstalled' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that th
path is correct and try again.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\StartDagServerMaintenance.ps1:78 char:2
+     Test-RsatClusteringInstalled
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Test-RsatClusteringInstalled:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

log-verbose : The term 'log-verbose' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\StartDagServerMaintenance.ps1:232 char:4
+             log-verbose ($StartDagServerMaintenance_LocalizedStrings.res_0015 )
+             ~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (log-verbose:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

log-verbose : The term 'log-verbose' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\StartDagServerMaintenance.ps1:97 char:3
+         log-verbose ($StartDagServerMaintenance_LocalizedStrings.res_0008 -f $shortSer ...
+         ~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (log-verbose:String) [], CommandNotFoundException

Check to see if you have KB2506143 installed.  If you do, uninstall it and try again (It's Powershell 3.0):
https://social.technet.microsoft.com/Forums/exchange/en-US/acc712fd-c4ee-4b56-be55-618990eec9a9/dag-maintenance-scripts-do-not-work-anymore-after-sp2-ur5-upgrade?forum=exchange2010

We are running PS version 3.0 on window server 2012 but I don't show that the KB is installed.

PS 3.0 breaks the scripts for the Exchange rollups.  Its in that thread I posted.

I agree but that shouldn't have anything to do with the RU 11 installing. This installed successfully on the CAS/Hub servers, and they also have PS 3.0

https://social.technet.microsoft.com/Forums/exchange/en-US/acc712fd-c4ee-4b56-be55-618990eec9a9/dag-maintenance-scripts-do-not-work-anymore-after-sp2-ur5-upgrade?forum=exchange2010

Latest roll up is RU12, did you tried that?

KB:
http://support.microsoft.com/kb/3096066

Download:
https://www.microsoft.com/en-us/download/details.aspx?id=50359

Sudeep

Please disregard this ticket. I will be contacting Microsoft about this issue.

I've requested that this question be deleted for the following reason:

Please disregard this ticket. I will be contacting Microsoft about this issue.

This has now been completed. The issue was snap manager was installed and once we uninstalled it from the mailbox servers, all updates were successful.

This has now been completed. The issue was snap manager was installed and once we uninstalled it from the mailbox servers, all updates were successful.