none
microsoft office professional 2013 encountered an error during setup

    Question

  • Trying to install the 32 bit version of Office 2013.  Planning to keep all my old versions.  I have Access 2002 and 2003 that I need.  Was not installing Outlook 2013 as Outlook 2010 is the only Office app that I care if I have issues with and my IT dept controls a a bit more.  Getting the error "microsoft office professional 2013 encountered an error during setup" with no other info.  I have Windows 7, full admin rights, and closed all other Office apps.  I Just did a restart which also installed all current Windows patches.  Got the same error. 

    Any ideas or where to look for the cause?

    Tuesday, October 30, 2012 5:16 PM

Answers

  • 2012/12/04 10:51:24:886::[9292] Error: Failed to configure:  {90150000-002A-0409-1000-0000000FF1CE} ErrorCode: 1653(0x675).

    Thank you for emailing me Ken! The issue when you hit a "1653" is that Windows Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653" error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:

    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

     

    ----

    Since I posted my email I have had a few emails for error "1603" and these are the issues I've seen:

    • Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
    • CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old.
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
    • Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
    • Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).

    The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603.

    If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]

    "logging"= "voicewarmup"





    • Marked as answer by Kennethj Thursday, December 06, 2012 6:30 PM
    • Edited by micrey Thursday, February 14, 2013 7:15 PM
    Thursday, December 06, 2012 6:28 PM

All replies

  • I decided to wipe out all of my Office 2010, 2002, and 2003.  2013 still won't install.  Same error, completely useless error at that.  A little more info would be helpful.
    Tuesday, October 30, 2012 8:07 PM
  • This error could happen when the Rgstrtn.lck file is present in the computer.

    To work around this problem, delete the Rgstrtn.lck file follow the instructions in the following support article:

    http://support.microsoft.com/kb/927153

     

    Also try:

    • Rename "%Programdata%\Microsoft Help" folder and and try to run setup again
    • Unregister/Reregister installer
      Start > Run > msiexec /unregister
      Start > Run > msiexec /regserver
      restart system and try to run setup again

    Max Meng
    TechNet Community Support
    A new Office has arrived, try it now.
    A beautiful Start. It begins here. Windows 8 and Windows RT.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, October 31, 2012 6:32 AM
  • I tried all 3 of those solutions.  None worked.  The third solution of unregistering the misexec never gave me any confirmation of unregsiter or re-register.  I found that odd.  Also I was never able to get the preview installed on this machine.  It failed with the same error.  I finally put it on a VM but that just meant I barely tested it.
    Wednesday, October 31, 2012 12:43 PM
  • I tried the idea from Tony here

    http://social.technet.microsoft.com/Forums/en-US/officeitpro/thread/bad50332-4410-4cf2-a7f9-1ddba5b7a671

    as well.  backed up the keys and deleted the AppCompatFlags.  No luck.

    Wednesday, October 31, 2012 12:50 PM
  • Just

    1) copy all files from DVD to disc

    2) give all permissions to Administrators in file Setup.exe

    3) Uncheck "read only" in Setup.exe properties

    4) Run Setup.exe as Administrator

    That´s all.

    Fredr

    Monday, November 05, 2012 11:37 PM
  • I've had the files on my local drive and tried that several times.  I flagged it as admin mode.  I set permissions and tried confusing it with different compatibility modes as I read in a few places about getting 2010 installed.  Nothing works.  As of right now I have no Office and none will install.  I'm getting a new hard drive this morning with a fresh install of Windows 7.  That had better fix it. 
    Tuesday, November 06, 2012 1:14 PM
  • I am having the same problem and am dead in the water. 

    Just in case one of the suggestions might have worked, I went through all of those above with no luck.  At first the issue was that the preview version of the OSE was left behind by the uninstall, but I replaced it with the 2010 version, no dice.  I then uninstalled all office products to get the OSE uninstalled, and setup now gets beyond that hangup, but still fails.  Following is the section of the log with the errors (MS email me for the full log):

    2012/11/07 15:38:25:897::[5980] MSI(ACTIONSTART): 'Action 15:38:25: PublishProduct. Publishing product information'
    2012/11/07 15:38:25:897::[5980] MSI(INFO): 'Action start 15:38:25: PublishProduct.'
    2012/11/07 15:38:25:901::[5980] MSI(INFO): 'Action ended 15:38:25: PublishProduct. Return value 1.'
    2012/11/07 15:38:25:901::[5980] MSI(ACTIONSTART): 'Action 15:38:25: InstallExecute. '
    2012/11/07 15:38:25:901::[5980] MSI(INFO): 'Action start 15:38:25: InstallExecute.'
    2012/11/07 15:38:25:921::[5980] MSI(COMMONDATA): 'Message type:  0, Argument:  1033'
    2012/11/07 15:38:25:921::[5980] MSI(COMMONDATA): 'Message type:  1, Argument:  Microsoft Office Shared 64-bit MUI (English) 2013'
    2012/11/07 15:38:25:922::[5980] MSI(ACTIONSTART): 'Action 15:38:25: AllocateRegistrySpace. Allocating registry space'
    2012/11/07 15:38:25:923::[5980] MSI(ACTIONSTART): 'Action 15:38:25: ProcessComponents. Updating component registration'
    2012/11/07 15:38:25:934::[5980] MSI(ACTIONSTART): 'Action 15:38:25: CAOSMRegisterLogonTaskRollback.x64.1033. '
    2012/11/07 15:38:25:935::[5980] MSI(ACTIONSTART): 'Action 15:38:25: CAOSMRegisterFallBackTaskRollback.x64.1033. '
    2012/11/07 15:38:25:937::[5980] MSI(ACTIONSTART): 'Action 15:38:25: RemoveODBC. Removing ODBC components'
    2012/11/07 15:38:25:937::[5980] MSI(ACTIONSTART): 'Action 15:38:25: InstallFiles. Copying new files'
    2012/11/07 15:38:26:142::[5980] MSI(ACTIONSTART): 'Action 15:38:26: CAOSMRegisterLogonTask.x64.1033. '
    2012/11/07 15:38:26:247::[5980] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the file specified.'
    2012/11/07 15:38:26:247::[5980] MSI(INFO): 'CAQuietExec:  '
    2012/11/07 15:38:26:248::[5980] MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'
    2012/11/07 15:38:26:249::[5980] MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'
    2012/11/07 15:38:26:250::[5980] MSI(INFO): 'CustomAction CAOSMRegisterLogonTask.x64.1033 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)'
    2012/11/07 15:38:26:253::[5980] MSI(INFO): 'Action ended 15:38:26: InstallExecute. Return value 3.'
    2012/11/07 15:38:26:322::[5980] MSI(COMMONDATA): 'Message type:  2, Argument:  0'
    2012/11/07 15:38:26:323::[5980] MSI(COMMONDATA): 'Message type:  2, Argument:  0'
    2012/11/07 15:38:26:324::[5980] MSI(COMMONDATA): 'Message type:  0, Argument:  1033'
    2012/11/07 15:38:26:324::[5980] MSI(COMMONDATA): 'Message type:  1, Argument:  Microsoft Office Shared 64-bit MUI (English) 2013'
    2012/11/07 15:38:26:325::[5980] MSI(ACTIONSTART): 'Action 15:38:26: Rollback. Rolling back action:'
    2012/11/07 15:38:26:325::[5980] Log level changed from: Standard to: Verbose
    2012/11/07 15:38:26:465::[5980] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the file specified.'
    2012/11/07 15:38:26:466::[5980] MSI(INFO): 'CAQuietExec:  '
    2012/11/07 15:38:26:467::[5980] MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'
    2012/11/07 15:38:26:468::[5980] MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'
    2012/11/07 15:38:26:469::[5980] MSI(INFO): 'CustomAction CAOSMRegisterFallBackTaskRollback.x64.1033 returned actual error code 1603 but will be translated to success due to continue marking'
    2012/11/07 15:38:26:524::[5980] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the file specified.'
    2012/11/07 15:38:26:525::[5980] MSI(INFO): 'CAQuietExec:  '
    2012/11/07 15:38:26:526::[5980] MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'
    2012/11/07 15:38:26:527::[5980] MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'
    2012/11/07 15:38:26:527::[5980] MSI(INFO): 'CustomAction CAOSMRegisterLogonTaskRollback.x64.1033 returned actual error code 1603 but will be translated to success due to continue marking'
    2012/11/07 15:38:26:537::[5980] MSI(COMMONDATA): 'Message type:  2, Argument:  1'
    2012/11/07 15:38:26:542::[5980] MSI(COMMONDATA): 'Message type:  2, Argument:  1'
    2012/11/07 15:38:26:546::[5980] MSI(INFO): 'Action ended 15:38:26: INSTALL. Return value 3.'

    -Ingram
    • Edited by Ingram Barclay Thursday, November 08, 2012 1:13 PM
    • Proposed as answer by micrey Tuesday, November 20, 2012 7:00 PM
    • Unproposed as answer by micrey Tuesday, November 20, 2012 7:00 PM
    Wednesday, November 07, 2012 9:56 PM
  • Ultimately I found that the source of my problems was a corrupted task scheduler database.  I was receiving the following error when viewing scheduled tasks (Windows 8 RTM ENT) along with the office issues, and correlating it with the above log info (see the line at 15:38:26:250) it became obvious what was going on, although there's no obvious fix: the selected task "{0}" no longer exists. to see the current task, click refresh

    I ended up having to take ownership of the %system%\tasks folder and contents and delete all the contents (after backing up of course) to get the scheduler happy.  I have remaining the unhappy task of importing the 160 previously scheduled tasks to get my system back to normal, however, I may just putt along until I get my Asus Taichi with W8 and then format this one.  A reinstall would have cost me a week of productivity, so this solution works for me, hope it helps someone else.

    -Ingram

        
    • Proposed as answer by Ingram Barclay Thursday, November 08, 2012 1:24 PM
    • Unproposed as answer by Kennethj Thursday, November 08, 2012 1:27 PM
    • Proposed as answer by micrey Tuesday, November 20, 2012 7:00 PM
    • Unproposed as answer by micrey Monday, November 26, 2012 4:50 PM
    Thursday, November 08, 2012 1:23 PM
  • The new hard drive didn't help.  Finally my PC tech had to install it.  It worked.  he has the same permissions I do.  This is a huge failure MS.  Most people don't want to or won't deal with a failure of this magnitude.  First of all fix the installer and return better messages when it does fail. 
    Thursday, November 08, 2012 1:29 PM
  • Since I posted my email I have had a few emails for error "1603" and these are the issues I've seen:

    • Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
    • CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old.
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
    • Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.

    The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603.




    • Proposed as answer by micrey Monday, November 26, 2012 4:49 PM
    • Edited by micrey Thursday, February 14, 2013 7:16 PM
    Wednesday, November 21, 2012 8:34 PM
  • Now I can't get Visio 2013 to install.  I doubt it's any scheduler as I don't use this, I get the same issue with 2010 Office apps, and I tried starting it (it was already running).  I don't have an autorun value in either of the registry keys.  Here is what I get in my log from the error on:

    2012/12/04 10:51:24:886::[9292] Error: Failed to configure:  {90150000-002A-0409-1000-0000000FF1CE} ErrorCode: 1653(0x675).
    2012/12/04 10:51:24:886::[9292] Log level changed from: Standard to: Verbose
    2012/12/04 10:51:24:886::[9292] Rolling back chain
    2012/12/04 10:51:24:886::[9292] Error attaching to OSE, error 0x00000000
    2012/12/04 10:51:24:886::[9292] Stopping running ose
    2012/12/04 10:51:25:464::[9292] Cannot start standalone OSE from path D:\Software Downloads\Visio 2013\x86\vispror.ww\ose.exe. Error code 0x800706b5. Skipping uncache for this product
    2012/12/04 10:51:25:464::[9292] 12/04/2012 10:51:25 Rolling back MSI transaction.
    2012/12/04 10:51:25:464::[9292] MSI(INITIALIZE): '<NULL>'
    2012/12/04 10:51:25:464::[9292] MSI(COMMONDATA): '1: 2 2: 0 '
    2012/12/04 10:51:25:464::[9292] MSI(COMMONDATA): '1: 2 2: 1 '
    2012/12/04 10:51:25:464::[9292] MSI(TERMINATE): '<NULL>'
    2012/12/04 10:51:25:464::[9292] 12/04/2012 10:51:25 MSI transaction rolled back.
    2012/12/04 10:51:25:464::[9292] Unable to cancel a system restore point.
    2012/12/04 10:51:25:479::[8348] Showing completion dialog.
    2012/12/04 10:51:27:055::[8348] Reboot requested if needed.
    2012/12/04 10:51:27:055::[8348] No reboot is needed.
    2012/12/04 10:51:27:086::[8348] Catalyst execution finished: 12/04/2012 10:51:27.  Return code: 1653.
    2012/12/04 10:51:27:086::[8348] PERF: TickCount=527122776 Name=RunSetup Description=End function

    I researched this heavily when I got the previous issues with 2013 professional plus. All fixes got me no where. I still say that this whole process is a failure.

    Tuesday, December 04, 2012 3:57 PM
  • 2012/12/04 10:51:24:886::[9292] Error: Failed to configure:  {90150000-002A-0409-1000-0000000FF1CE} ErrorCode: 1653(0x675).

    Thank you for emailing me Ken! The issue when you hit a "1653" is that Windows Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653" error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:

    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

     

    ----

    Since I posted my email I have had a few emails for error "1603" and these are the issues I've seen:

    • Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
    • CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old.
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
    • Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
    • Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).

    The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603.

    If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]

    "logging"= "voicewarmup"





    • Marked as answer by Kennethj Thursday, December 06, 2012 6:30 PM
    • Edited by micrey Thursday, February 14, 2013 7:15 PM
    Thursday, December 06, 2012 6:28 PM
  • Hey all. I encountered this problem when I was trying to install from a shared network drive. I had to add "modify" permissions to the network folder and it worked ok after that. Odd, because dvd/cd media is not writable! Thanks.
    Wednesday, December 12, 2012 7:02 PM
  • Nothing here (or in any of the other sites I have scanned) has resolved my problem. I have tried multiple versions including streamed, Home Use and licensed copy from my ELA. 32-bit or 64-bit. All the suggestions and to no avail. I now have a machine with no copy of Office and no way to load any version (2010 fails in the same way). What now? (BTW - We have 6000 machine we are considering pushing this to and I am now VERY nervous about any update to Office.
    Sunday, January 27, 2013 6:18 PM
  • Kennethj.....I had same problem

    The solution for this problem is:

    1.Go to C:\ProgramData\Microsoft Help\

    2.In Microsoft Help folder delete all the files present there.

    3.Then try installing Ms Office 2013

    This helped me to get rid of "office 13 encountered a problem" thing!

    Hope you got rid of your problem... :)

    Sunday, February 10, 2013 9:15 AM
  • FYI if the issue is that your "Task Scheduler" is in a bad state then the "extra" proposed solution in the following post has resolved the issue for some people:

    http://serverfault.com/questions/350374/transaction-support-within-the-specified-resource-manager-is-not-started-or-was


    Michael Reynolds

    Thursday, February 14, 2013 7:34 PM
  • Kenneth,

    I had a similar issue while installing MS Office 2013 on Windows 7. But the error was "setup cannot find proplus.ww\ose.exe while installing Office 2013" . I did the following to resolve the issue.

    1) Right click the setup.exe file and click on "Run as administrator".

    2) The installation did stop with an error stating, the file "Setup.dll" was not found. I pointed the installation to  the setup directory and the installation continued without any problems.

    Hope this helps you.

    • Proposed as answer by Avinash.Rao Tuesday, March 19, 2013 1:03 PM
    • Unproposed as answer by Kennethj Tuesday, March 19, 2013 1:12 PM
    • Proposed as answer by LAN-Serve Thursday, January 02, 2014 6:50 PM
    Tuesday, March 19, 2013 1:03 PM
  • This is unbelievable. I am trying to install Visio Professional 2013 as the only (so far) Office 2013 component on a Windows 7 Pro 32-bit computer and am repeatedly getting the "encountered an error during setup" status. I successfully used the same disk to install the same program on a 64 bit Windows 7 laptop.

    I do not have either of the two software policies keys in my registry so they aren't the problem. I've renamed my Windows Help folder to no avail. I've tried running as administrator, I've copied the disk contents to the drive. I tried net start scheduler only to be given error 5 access denied (I'm the administrator of the machine). And I am not going to go fishing in the dark with a gazzillion key settings and speculative modivications.

    The only new information I am getting is that my Setupexe.log file's first mention of "Error" is early in the log with "Error attaching to OSE, error 0x00000000". Much later, almost to the bottom I get "Error: Failed to install product" with the 1603 code.

    If a product requires the obscure fishing around to successfully install suggested above then this is a problem. And I didn't just climb on the technology truck yesterday. While I'm not a computer scientist or computer engineer I do have a Ph.D. in Management Information Systems and have been teaching systems development since we used CPM on PCs and COBOL on mainframes and I've owned every version of Visio ever created including from before Microsoft bought the company. And to make matters worse I need Visio because I'm teaching systems analysis and design to fifty graduate students with varying degrees of technical sophistication and just cannot deal with the multitude of problems their individual configurations are going to create.

    We get our software through the Microsoft Academic Alliance (Dream Spark program) and I'm going to have to revert to Visio 2010. But I'll say here, in case anyone from Microsoft sees it, that this situation is stupid beyond belief.


    Larry West University of Central Florida

    Wednesday, August 28, 2013 6:14 PM
  • thanks Raag123 this worked for me
    Friday, September 06, 2013 3:38 AM
  • Great suggestion MS - Fix the installer so that it doesn't just say "Failed - fuck off" to people. Getting the setup to output an error code or message would make things easier to diagnose. Also getting the Eventlog to record a code or some other useful information would be nice as it currently records the failure but doesn't provide anything useful for troubleshooting it, not a crumb. The things you take for granted these days...
    Monday, February 10, 2014 12:11 PM
  • Been working in IT for over 10 years and nothing on this page has worked for me. And a rebuild is not an option, so thanks Microsoft, for yet another shitty piece of software that I can't use.
    Monday, February 10, 2014 12:17 PM
  • Hi,

    I have the same problem before, in my situation because Windows Event Collector and Windows Event Log are disabled. Try to check yours:

    Run Msconfig > Services > and make sure Windows Event Collector and Windows Event Log are enabled > then restart your PC.

    It works for me.

    I just remember I disabled both events to avoid lag while playing GTA IV :)

    Thanks,


    Sunday, March 23, 2014 4:01 PM
  • Solved my problem. 

    Thanks dude.

    The solution for this problem is:

    1.Go to C:\ProgramData\Microsoft Help\

    2.In Microsoft Help folder delete all the files present there.

    3.Then try installing Ms Office 2013

    This helped me to get rid of "office 13 encountered a problem" thing!

    Hope you got rid of your problem... :)

    Tuesday, April 22, 2014 6:03 AM
  • I've tried everything listed on this site and I cannot get Office 2013 to install.  I get the Office64Mui.msi 1603 error.  Scheduler is running, no "autorun" key to rename to "old".. no permissions issues, I'm installing off the DVD. "ComSpec" looks fine..

    Any other ideas out there? this is ridiculous

    Thursday, May 08, 2014 12:35 AM
  • I spent most of yesterday trying to get the 32-bit version installed at work.

    In my case the problem appears to have been a corrupt WMI repository. Browsing the logs I found an error of the form "An error occurred while opening the namespace for object 1 defined on lines..." I think I'd already tried the recompilations and checks and repairs by the time I ended up here: http://katyscode.wordpress.com/2007/02/03/tutorial-how-to-fix-wmi-corruption/

    Ultimately I blew it away and recreated it using the detail towards the end of the page.  This allowed the installation to complete.

    c:
    cd \windows\system32\wbem
    net stop winmgmt
    rename Repository Repository.old
    net start winmgmt

    At this point there will be no repository at all. In order to create one, you’ll have to run a WMI-using application. The simplest way to do this is to go back to Computer Management and open Services & Applications -> WMI Control, then right-click and choose Properties

    Saturday, June 07, 2014 12:26 PM
  • It does really helpful to my problem here.

    5 stars to Fredr

    Saturday, July 12, 2014 11:49 AM