Share via

Office Professional Plus 2016 will not install!!

Anonymous
2016-09-30T19:11:00+00:00

I have not been able to install Office Professional Plus 2016  in either the 32 or 64 bit versions

despite exhaustive measures and need the best of help.

My level of techno ability is only that of a good amateur  but I can reasonably follow directions

so bear with me.  However, it is fair to say that I really have no confidence that I know what I am

doing, other than trying suggested cures and crossing my fingers that I do not screw up the

whole computer in my blundering about.

A brief history of what has occurred and what I have tried is in order.

I have a 64 bit Windows PC running Home premium Windows 10 having been upgraded from

my original Windows 7. Previously installed prior to Windows 10 upgrade were Office Enterprise

2007 and Office Home and Student 2010.

When first attempting to install  Office Professional Plus 2016 ("OPP2016") 32 bit, I of course

ran into conflict with these prior versions of Office and I removed them with Revo Uninstaller Plus.

When then attempting to install  OPP 2016 32 bit, the Bootstrap Setup gave me an "Upgrade

Option" thus indicating some prior Office file was hanging around.  I continued to run the installer

but about 1/10th along, setup stopped displaying only an error message that “Microsoft Office

Professional Plus 2016 encountered an error during set up” and would go no further.   It also

gave no information as to what the error might be.

I then tried to install the 64 bit version of Office, I got an error message to the effect that

"Microsoft Single Image 2010" needed to be removed.  I first tried to remove that file by following

 some instructions found on one of the MS support sites and running "015 ctrremove" but when

that did not do the trick I manually went into the registry, used a search tool for the string

"Microsoft Single Image 2010" and deleted what seemed to be over 1 hundred entries.

That seemed to take care of the Single Image conflict, but when I ran  Bootstrap Setup it still gave

me an "Upgrade" Option thus indicating that some legacy Office remnant was around.

Over the next 2 or 3 days, I discovered ran and repeatedly ran Microsoft Easy Fix 50154,

MicrosoftFixit 20055, MicrosoftFixit 20052, Microsoft Program_Install_and_Unistall.meta,

and msicuu.exe to remove all vestiges of Office 2007 or 2010.   I also followed the instructions for

manually removing both Office 2007 and 2010 from the registry but did not find any of the cited

values that were supposed to be changed/deleted.

I met with some success in that Bootstrap set up no longer displays an "Upgrade" option, but

only "Install" and "Custom"  but upon running either the 32 or 64 bit versions of  OPP 2016, 

set up of  32 bit still runs for about 1/10th along before stopping and displaying the 

“Microsoft Office Professional Plus 2016 encountered an error during set up” error message

but the 64 bit version goes almost half the way before stopping and displaying.

I followed the advice of performing a clean boot and then trying to install ("OPP2016") to

no avail, as well as trying to run it as an "net user administrator" with the same results.

I have run the set.up of both versions enough that by reference to the temp files, I seem to

find some references to errors, but do not know how to interpret them.  They include:

On a 32 bit install attempt on the 27th:

2016/09/27 17:01:29:338::[12636] WER element [P4] is set to value [1603]

2016/09/27 17:01:29:338::[12636] WER element [P7] is set to value [1603]

2016/09/27 17:01:29:338::[12636] WER element [P6] is set to value [%s %s]

2016/09/27 17:01:29:338::[12636]  WER element [P6] is converted to [FC73469E]

2016/09/27 17:01:29:338::[12636] Error: Failed to install product:  C:\MSOCache\All Users{90160000-0116-0409-1000-0000000FF1CE}-C\Office64MUI.msi ErrorCode: 1603(0x643).

2016/09/27 17:01:29:338::[12636] Log level changed from: Standard to: Verbose

2016/09/27 17:01:29:338::[12636] Rolling back chain

2016/09/27 17:01:29:338::[12636] Error attaching to OSE, error 0x00000000

2016/09/27 17:01:29:338::[12636] Stopping running ose

and on another day later:

2016/09/28 15:54:47:790::[11916] MSI(INFO): 'Property(S): PrimaryVolumeSpaceRemaining = 0'

2016/09/28 15:54:47:790::[11916] MSI(INFO): 'Property(S): ProductToBeRegistered = 1'

2016/09/28 15:54:47:790::[11916] MSI(INFO): '=== Logging stopped: 9/28/2016  15:54:47 ==='

2016/09/28 15:54:47:920::[11916] MSI(TERMINATE): '<NULL>'

2016/09/28 15:54:47:948::[11916] WER element [P4] is set to value [1603]

2016/09/28 15:54:47:948::[11916] WER element [P7] is set to value [1603]

2016/09/28 15:54:47:957::[11916] WER element [P6] is set to value [%s %s]

2016/09/28 15:54:47:957::[11916]  WER element [P6] is converted to [FC73469E]

2016/09/28 15:54:47:957::[11916] Log level changed from: Verbose to: Standard

2016/09/28 15:54:47:957::[11916] Error: Failed to install product:  C:\MSOCache\All Users{90160000-0116-0409-1000-0000000FF1CE}-C\Office64MUI.msi ErrorCode: 1603(0x643).

2016/09/28 15:54:47:957::[11916] Log level changed from: Standard to: Verbose

2016/09/28 15:54:47:957::[11916] Rolling back chain

2016/09/28 15:54:47:957::[11916] Error attaching to OSE, error 0x00000000

2016/09/28 15:54:47:957::[11916] Stopping running ose

and on my most recent attempt:

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PROBLEM_PRE = If problem persists, contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see '

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PROBLEM_POST = .'

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PERMISSION_PRE = Verify that you have sufficient permissions to access the registry or contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see '

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PERMISSION_POST = .'

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PRE = Contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see '

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_POST = .'

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT = Contact your computer manufacturer's product support for assistance.'

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT_PERMISSION = Verify that you have sufficient permissions to access the registry or contact your computer manufacturer's product support for assistance.'

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT_PROBLEM = If problem persists, contact your computer manufacturer's product support for assistance.'

2016/09/30 09:12:29:117::[4144] MSI(INFO): 'Property(S): InstalledByClientCatalyst_Ref = 0'

And

/30 09:12:22:728::[4144] MSI(INFO): 'CAQuietExec:  Entering CAQuietExec in C:\WINDOWS\Installer\MSI282E.tmp, version 3.7.2921.0'

2016/09/30 09:12:22:728::[4144] MSI(INFO): 'CAQuietExec:  "schtasks.exe" /create /f /tn "Microsoft\Office\OfficeTelemetryAgentLogOn2016" /xml "C:\Program Files\Microsoft Office\Office16\1033\officeinventoryagentlogon.xml"'

2016/09/30 09:12:28:726::[4144] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the path specified.'

2016/09/30 09:12:28:726::[4144] MSI(INFO): 'CAQuietExec:  '

2016/09/30 09:12:28:726::[4144] MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'

2016/09/30 09:12:28:726::[4144] MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'

2016/09/30 09:12:28:726::[4144] MSI(INFO): 'CustomAction CAOSMRegisterLogonTask.x64.1033 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)'

2016/09/30 09:12:28:726::[4144] MSI(INFO): 'Action ended 9:12:28: InstallExecute. Return value 3.'

2016/09/30 09:12:28:742::[4144] MSI(COMMONDATA): 'Message type:  2, Argument:  0'

2016/09/30 09:12:28:742::[4144] MSI(COMMONDATA): 'Message type:  2, Argument:  0'

2016/09/30 09:12:28:742::[4144] MSI(COMMONDATA): 'Message type:  0, Argument:  1033'

2016/09/30 09:12:28:742::[4144] MSI(COMMONDATA): 'Message type:  1, Argument:  Microsoft Office Shared 64-bit MUI (English) 2016'

2016/09/30 09:12:28:742::[4144] MSI(ACTIONSTART): 'Action 9:12:28: Rollback. Rolling back action:'

2016/09/30 09:12:28:742::[4144] Log level changed from: Standard to: Verbose

2016/09/30 09:12:28:882::[4144] MSI(INFO): 'CAQuietExec:  Entering CAQuietExec in C:\WINDOWS\Installer\MSI4099.tmp, version 3.7.2921.0'

2016/09/30 09:12:28:882::[4144] MSI(INFO): 'CAQuietExec:  "schtasks.exe" /delete /f /tn "Microsoft\Office\OfficeTelemetryAgentFallBack2016"'

2016/09/30 09:12:28:913::[4144] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the file specified.'

2016/09/30 09:12:28:913::[4144] MSI(INFO): 'CAQuietExec:  '

2016/09/30 09:12:28:913::[4144] MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'

2016/09/30 09:12:28:913::[4144] MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'

2016/09/30 09:12:28:913::[4144] MSI(INFO): 'CustomAction CAOSMRegisterFallBackTaskRollback.x64.1033 returned actual error code 1603 but will be translated to success due to continue marking'

2016/09/30 09:12:28:960::[4144] MSI(INFO): 'CAQuietExec:  Entering CAQuietExec in C:\WINDOWS\Installer\MSI4127.tmp, version 3.7.2921.0'

2016/09/30 09:12:28:960::[4144] MSI(INFO): 'CAQuietExec:  "schtasks.exe" /delete /f /tn "Microsoft\Office\OfficeTelemetryAgentLogOn2016"'

2016/09/30 09:12:28:976::[4144] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the file specified.'

And

2016/09/30 10:40:47:587::[7488] MSI(INFO): 'Property(S): ProductToBeRegistered = 1'

2016/09/30 10:40:47:587::[7488] MSI(INFO): '=== Logging stopped: 9/30/2016  10:40:47 ==='

2016/09/30 10:40:47:993::[7488] MSI(TERMINATE): '<NULL>'

2016/09/30 10:40:47:993::[7488] WER element [P4] is set to value [1603]

2016/09/30 10:40:47:993::[7488] WER element [P7] is set to value [1603]

2016/09/30 10:40:47:993::[7488] WER element [P6] is set to value [%s %s]

2016/09/30 10:40:47:993::[7488]  WER element [P6] is converted to [FC73469E]

2016/09/30 10:40:47:993::[7488] Log level changed from: Verbose to: Standard

2016/09/30 10:40:47:993::[7488] Error: Failed to install product:  C:\MSOCache\All Users{90160000-0116-0409-1000-0000000FF1CE}-C\Office64MUI.msi ErrorCode: 1603(0x643).

2016/09/30 10:40:47:993::[7488] Log level changed from: Standard to: Verbose

2016/09/30 10:40:47:993::[7488] Rolling back chain

2016/09/30 10:40:47:993::[7488] Error attaching to OSE, error 0x00000000

2016/09/30 10:40:47:993::[7488] Stopping running ose

As I have indicated, the 64 bit version proceeds much further but prior to shutting down, seems

to encounter a number of installation errors somewhat different from those in the 32 bit version

that may be relevant, such as:

2016/09/27 20:21:15:838::[14632] MSI(ACTIONSTART): 'Action 20:21:15: CAOSMRegisterLogonTask.x64.1033. '

2016/09/27 20:21:16:026::[14632] MSI(INFO): 'CAQuietExec:  Entering CAQuietExec in C:\WINDOWS\Installer\MSI94A6.tmp, version 3.7.2921.0'

2016/09/27 20:21:16:026::[14632] MSI(INFO): 'CAQuietExec:  "schtasks.exe" /create /f /tn "Microsoft\Office\OfficeTelemetryAgentLogOn2016" /xml "C:\Program Files\Microsoft Office\Office16\1033\officeinventoryagentlogon.xml"'

2016/09/27 20:21:35:246::[14632] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the path specified.'

2016/09/27 20:21:35:246::[14632] MSI(INFO): 'CAQuietExec:  '

2016/09/27 20:21:35:246::[14632] MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'

2016/09/27 20:21:35:246::[14632] MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'

2016/09/27 20:21:35:246::[14632] MSI(INFO): 'CustomAction CAOSMRegisterLogonTask.x64.1033 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)'

2016/09/27 20:21:35:246::[14632] MSI(INFO): 'Action ended 20:21:35: InstallExecute. Return value 3.'

2016/09/27 20:21:35:246::[14632] MSI(COMMONDATA): 'Message type:  2, Argument:  0'

2016/09/27 20:21:35:246::[14632] MSI(COMMONDATA): 'Message type:  2, Argument:  0'

2016/09/27 20:21:35:246::[14632] MSI(COMMONDATA): 'Message type:  0, Argument:  1033'

2016/09/27 20:21:35:246::[14632] MSI(COMMONDATA): 'Message type:  1, Argument:  Microsoft Office OSM MUI (English) 2016'

2016/09/27 20:21:35:246::[14632] MSI(ACTIONSTART): 'Action 20:21:35: Rollback. Rolling back action:'

2016/09/27 20:21:35:246::[14632] Log level changed from: Standard to: Verbose

2016/09/27 20:21:35:293::[14632] MSI(INFO): 'CAQuietExec:  Entering CAQuietExec in C:\WINDOWS\Installer\MSIE085.tmp, version 3.7.2921.0'

2016/09/27 20:21:35:293::[14632] MSI(INFO): 'CAQuietExec:  "schtasks.exe" /delete /f /tn "Microsoft\Office\OfficeTelemetryAgentFallBack2016"'

2016/09/27 20:21:35:324::[14632] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the file specified.'

2016/09/27 20:21:35:324::[14632] MSI(INFO): 'CAQuietExec:  '

2016/09/27 20:21:35:324::[14632] MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'

2016/09/27 20:21:35:324::[14632] MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'

2016/09/27 20:21:35:324::[14632] MSI(INFO): 'CustomAction CAOSMRegisterFallBackTaskRollback.x64.1033 returned actual error code 1603 but will be translated to success due to continue marking'

2016/09/27 20:21:35:387::[14632] MSI(INFO): 'CAQuietExec:  Entering CAQuietExec in C:\WINDOWS\Installer\MSIE0C4.tmp, version 3.7.2921.0'

2016/09/27 20:21:35:387::[14632] MSI(INFO): 'CAQuietExec:  "schtasks.exe" /delete /f /tn "Microsoft\Office\OfficeTelemetryAgentLogOn2016"'

2016/09/27 20:21:35:418::[14632] MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the file specified.'

2016/09/27 20:21:35:418::[14632] MSI(INFO): 'CAQuietExec:  '

2016/09/27 20:21:35:418::[14632] MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'

2016/09/27 20:21:35:418::[14632] MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'

2016/09/27 20:21:35:418::[14632] MSI(INFO): 'CustomAction CAOSMRegisterLogonTaskRollback.x64.1033 returned actual error code 1603 but will be translated to success due to continue marking'

2016/09/27 20:21:35:418::[14632] MSI(COMMONDATA): 'Message type:  2, Argument:  1'

2016/09/27 20:21:35:433::[14632] MSI(COMMONDATA): 'Message type:  2, Argument:  1'

And

016/09/27 20:21:35:527::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_PROBLEM = If problem persists, contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see C:\Users\CHEFCR~2\AppData\Local\Temp\Setup00003694\PSS10R.CHM.'

2016/09/27 20:21:35:527::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_PERMISSION = Verify that you have sufficient permissions to access the registry or contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see C:\Users\CHEFCR~2\AppData\Local\Temp\Setup00003694\PSS10R.CHM.'

2016/09/27 20:21:35:527::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT = Contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see C:\Users\CHEFCR~2\AppData\Local\Temp\Setup00003694\PSS10R.CHM.'

2016/09/27 20:21:35:527::[14632] MSI(INFO): 'Property(S): CAOSMRegisterLogonTask.x64.1033 = "schtasks.exe" /create /f /tn "Microsoft\Office\OfficeTelemetryAgentLogOn2016" /xml "C:\Program Files\Microsoft Office\Office16\1033\officeinventoryagentlogon.xml"'

And

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): SetARPINSTALLLOCATIONProperty_Ref = 0'

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): SETUPSUPPORTURL = http://support.microsoft.com/?kbid=xxxxxx'

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PROBLEM_PRE = If problem persists, contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see '

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PROBLEM_POST = .'

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PERMISSION_PRE = Verify that you have sufficient permissions to access the registry or contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see '

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PERMISSION_POST = .'

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PRE = Contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, see '

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_POST = .'

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT = Contact your computer manufacturer's product support for assistance.'

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT_PERMISSION = Verify that you have sufficient permissions to access the registry or contact your computer manufacturer's product support for assistance.'

2016/09/27 20:21:35:543::[14632] MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT_PROBLEM = If problem persists, contact your computer manufacturer's product support for assistan

And finally displaying the same kind of error content as in the 32 bit install log:

2016/09/27 20:21:35:558::[14632] MSI(INFO): '=== Logging stopped: 9/27/2016  20:21:35 ==='

2016/09/27 20:21:35:683::[14632] MSI(TERMINATE): '<NULL>'

2016/09/27 20:21:35:683::[14632] WER element [P4] is set to value [1603]

2016/09/27 20:21:35:683::[14632] WER element [P7] is set to value [1603]

2016/09/27 20:21:35:699::[14632] WER element [P6] is set to value [%s %s]

2016/09/27 20:21:35:699::[14632]  WER element [P6] is converted to [FC73469E]

2016/09/27 20:21:35:699::[14632] Log level changed from: Verbose to: Standard

2016/09/27 20:21:35:699::[14632] Error: Failed to install product:  C:\MSOCache\All Users{90160000-00E1-0409-1000-0000000FF1CE}-C\OSMMUI.msi ErrorCode: 1603(0x643).

2016/09/27 20:21:35:699::[14632] Log level changed from: Standard to: Verbose

2016/09/27 20:21:35:699::[14632] Rolling back chain

2016/09/27 20:21:35:699::[14632] Error attaching to OSE, error 0x00000000

2016/09/27 20:21:35:699::[14632] Stopping running ose

Any advice or other suggestions  you can make to get Office installed would be most appreciated. Please

let me know if I can provide any other information you might need to make a determination of exactly

what is going wrong or how to fix it.

Thanks for your time and trouble,

George Ellis

Microsoft 365 and Office | Install, redeem, activate | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

13 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-10-03T03:29:17+00:00

    Art,

    I sincerely appreciate your time and concern.

    But,

    Ran Malwarebytes..........40 minutes of my life that I won't get back, but at least this was something new to try.  Unfortunately, no results worth mentioning

    Ran the cmd as administrator.......didn't happen to mention that in my litany of attempts that I had done that earlier, but still reran it- results said that it had found no problems but still I can't have Windows boot in normal set up instead of Selective.

    Once again, appreciate your time and consideration, but your solutions seem much like the throwing of darts that I have been doing for the last 8 days.  Was hoping to have a knowledgeable Microsoft Engineer weigh in with more wisdom than the both of us have, but apparently my hopes will go unanswered. 

    Thank you so very, very much for your time and concern, but we both seem to be guessing and hoping rather than knowing.

    Thanks ever so much once again

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2016-10-01T05:28:14+00:00

    The page you reference suggests you run "015 ctrremove.exe" as an Office remover and has been available recently. Although it  specifically pertains to only Office 2013, Office 2016 or Office 365 and not Office 2007 or 2010 which were the legacy versions affecting my system I have run that program at least 3 times over the last week with no beneficial effect on the installation process of Office Professional Plus 2016.  The last time was today, when it ran for just over an hour and reported as the "error corrected" that it could not find Office.

    Thank you for your time spent in review and suggestion.

    You might try downloading the free version of CCleaner and scan the registry.  If it finds any Office references you could delete them.  I couldn't get Office to install and ran CCleaner and at the same time Office was updated and then it installed.  I wasn't sure whether CCleaner fixed it or the Office update.  Since you did what I did except for the CCleaner, it sounds like CCLeaner fixed my problem and not the Office update.  Only run the Registry cleaner portion of CCleaner and save your deletions in case you want to put them back.  I ran the Microsoft uninstall fixers for Office 2007, 2010, 2013 and 2016 yet tons of registry references were left in the registry.

    Please not that even though Office then installed for me with no problems, I am having the other common problem that it cannot recognize its license.  The two issues appear to be unrelated based on many posts.

    One more thing.  Before your run CCLeaner, check for Windows Updates.  There was a big update Tuesday.  If you are not running the anniversary edition and that build gets installed, run it a second time because it too has been updated and that update my help your problem without CCleaner being run.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-10-01T05:25:58+00:00

    The page you reference suggests you run "015 ctrremove.exe" as an Office remover and has been available recently. Although it  specifically pertains to only Office 2013, Office 2016 or Office 365 and not Office 2007 or 2010 which were the legacy versions affecting my system I have run that program at least 3 times over the last week with no beneficial effect on the installation process of Office Professional Plus 2016.  The last time was today, when it ran for just over an hour and reported as the "error corrected" that it could not find Office.

    Thank you for your time spent in review and suggestion.

    You might try downloading the free version of CCleaner and scan the registry.  If it finds any Office references you could delete them.  I couldn't get Office to install and ran CCleaner and at the same time Office was updated and then it installed.  I wasn't sure whether CCleaner fixed it or the Office update.  Since you did what I did except for the CCleaner, it sounds like CCLeaner fixed my problem and not the Office update.  Only run the Registry cleaner portion of CCleaner and save your deletions in case you want to put them back.  I ran the Microsoft uninstall fixers for Office 2007, 2010, 2013 and 2016 yet tons of registry references were left in the registry.

    Please not that even though Office then installed for me with no problems, I am having the other common problem that it cannot recognize its license.  The two issues appear to be unrelated based on many posts.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-10-01T01:06:55+00:00

    The page you reference suggests you run "015 ctrremove.exe" as an Office remover and has been available recently. Although it  specifically pertains to only Office 2013, Office 2016 or Office 365 and not Office 2007 or 2010 which were the legacy versions affecting my system I have run that program at least 3 times over the last week with no beneficial effect on the installation process of Office Professional Plus 2016.  The last time was today, when it ran for just over an hour and reported as the "error corrected" that it could not find Office.

    Thank you for your time spent in review and suggestion.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-09-30T19:44:22+00:00

    Reading your post, I am not sure when your last try to install took place.  But there was an update to Office that I found yesterday that was not there the day before, so if you did not try yesterday, I would uninstall whatever you got, run the various Microsoft uninstalling fix its at

     https://support.office.com/en-us/article/Uninstall-Office-2016-Office-2013-or-Office-365-from-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8?ui=en-US&rs=en-US&ad=US&fromAR=1

    reboot and try again.  However if you already tried late yesterday or today, ignore my post.

    Was this answer helpful?

    0 comments