Guest DaleMahalko Posted May 16, 2014 Posted May 16, 2014 This is a report of my long and trying attempts to fix an obscure Windows Update problem, and in the end I did manage to fix it. I'm posting this here, as I hope this information may help someone else who experiences similar problems. This update has been repeatedly failing to install, over and over and over again. Manually installing fails. Various other suggestions related to repairing .NET also doesn't fix it. =========================================== Security Update for Microsoft Office 2007 suites (KB2760415) Installation date: 5/15/2014 4:34 PM Installation status: Failed Error details: Code 80070643 Update type: Important A security vulnerability exists in Microsoft Office 2007 suites that could allow arbitrary code to run when a maliciously modified file is opened. This update resolves that vulnerability. More information: http://support.microsoft.com/kb/2760415 Help and Support: http://support.microsoft.com/?LN=en-us =========================================== , I downloaded the manual installer for this update, and it too failed. Application log says: =========================================== Product: Microsoft Office Shared MUI (English) 2007 - Update 'Security Update for Microsoft Office 2007 suites (KB2760415) 32-Bit Edition ' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\username\AppData\Local\Temp\conv-en-us_MSPLOG.LOG. =========================================== , This error 1603 is also useless for finding a solution. But probing the ridiculously technical log from the KB installer pointed me in the right direction, searching the log for "1603": =========================================== 05/15/14 16:35:49 DDSet_Status: BeginTransaction()->IHxRegisterSession::CreateTransaction() returned 8004036e. 05/15/14 16:35:49 DDSet_Error: BeginTransaction()->Attempt failed because another transaction was running. Trying to Rollback current transaction ({90120000-006E-0409-0000-0000000FF1CE}) 05/15/14 16:35:49 DDSet_Error: BeginTransaction()->Could not restart current transaction; IHxRegisterSession::ContinueTransaction() returned error code 80004005. 05/15/14 16:35:49 DDSet_Status: BeginTransaction()->Registration session {90120000-006E-0409-0000-0000000FF1CE} was *not* created. 05/15/14 16:35:49 DDSet_Exit: CMsHelpObject destructor 05/15/14 16:35:49 DDSet_Exit: BeginTransaction ended CustomAction CA_BeginHelpTransaction.3643236F_FC70_11D3_A536_0090278A1BB8 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) =========================================== , In that log we see "IHxRegisterSession::CreateTransaction() returned 8004036e" and "Attempt failed because another transaction was running." .... this error is not being reported in the previous error messages we've seen. Searching the web for "8004036e" eventually leads me to: http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx , And on there we see: Possible solution(s) http://support.microsoft.com/kb/927153 ========================================= KB927153: The 2007 Office suite or the 2010 Office suite Setup program will not restart after an initial installation is interrupted This problem may occur if the Rgstrtn.lck file is not removed from the computer. If this file is present when you try to install the same Office suite or the Office program that you previously tried to install, the Setup program detects the file. Then, the Setup program stops the installation. ========================================= , Running the Microsoft FixIt utility on that webpage for KB927153 will delete the old lock file, and the update KB2760415 will now install successfully. - Dale Mahalko Continue reading... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.