Exchange 2013 Update 6 fails to install pending reboot no matter how many reboots are done

I attempted to apply Update 6 for exchange but the update countinued to claim a reboot was needed.

I found a site that listed keys to delete:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

However those keys did not exist. I did find a reference to pendingfilerenameoperations in a key called Pending Rename Operations that was located in a HKLM\SYSTEM\ControlSet002\Control\BackupRestore \KeysNotToRestore

After removing that reference from the registry the update is not installing.

My question is what hole have I dug for myself in doing this? There didn't seem to be anything on this I could find other then a 2003 site that said absolutely do not remove keys from that location!
LVL 1
dpcsitAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

v_2abhis2Commented:
Try using the sysinternals tool pendmove.exe from the following link

http://technet.microsoft.com/en-us/sysinternals/bb897556

This will tell you why your system shows the reboot is pending and what file needs to be replaced or deleted.

Syntax is given in the link.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dpcsitAuthor Commented:
But it was in the KeysNotToRestore part of the registry so what I think was happening was the update was seeing that key and that it was not empty and thinking it was an actual unresolved update but it was not.

The update worked and fixed one of my other issues with user not sending email with OWA.
0
dpcsitAuthor Commented:
Good tool resource!
0
dpcsitAuthor Commented:
Update 6 blew exchange up installed update 7 seems to work time will tell
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.