Cannot install office 2016 Error "Microsoft office professional plus 2016 encountered an error during setup"

Question

Have uninstalled in almost all machines save for one. I am failing to install our licensed Microsoft Office 2016, it gives the error "Microsoft office professional plus 2016 encountered an error during setup". Have renamed the Microsoft Help file to no avail. Anyone with another solution?

Answer 1

Verbose does not cause more messages to be displayed externally. All of the messages are captured in the log files I described. You have to manually search through the logs, look for the "middle" one as I described to find the most likely one with the relevant messages.

Answer 2

No problem, I just wanted to be clear.

For other machines, as long as you have licenses, why not go ahead?

You can go on trouble shooting this one specific machine while others are going forward.

As I said before, at this point the best trouble shooting technique I know of for the problem machine is verbose logging.

I managed to follow the instructions on verbose logging but I still get only one "cryptic" message and that is  

Microsoft office professional plus 2016 encountered an error during setup

I am using Windows 10 if that will help and have tried as much as I could to uninstall so may programs that were loaded on this laptop. So far, I still have nothing to smile about.

Answer 3

No problem, I just wanted to be clear.

For other machines, as long as you have licenses, why not go ahead?

You can go on trouble shooting this one specific machine while others are going forward.

As I said before, at this point the best trouble shooting technique I know of for the problem machine is verbose logging.

Answer 4

Ooops!!! Apologies!

I managed to uninstall previous versions on all machines and successfully load the Office 2016 onto all machines save for one! I get that error, 

Microsoft office professional plus 2016 encountered an error during setup

It is a Volume Licensing arrangement so I am not sure what it is I have to do before I proceed to work on other machines as well.

Answer 5

Have uninstalled in almost all machines save for one.

Is that 2nd word supposed to installed or uninstalled?

Unfortunately that is one of the typically useless MS error messages.  It is just a very wordy way of saying "oops".

Check Control Panel > programs and features for any other installed Office programs.

Turn on Verbose Logging, run the install again and then check the logs for better error information.

Verbose logging - Trouble shooting Problems Installing Office 2003/2007/2010/2013

http://support.microsoft.com/kb/2545723 - fix Its to turn logging on and off

---

http://blogs.technet.com/b/odsupport/archive/2010/12/30/trouble shooting-office-installation-failures.aspx Office 2003-2010, analyse log

---

http://support.microsoft.com/kb/826511 - help interpreting logs

---

http://support.microsoft.com/kb/906485 - Enable logging on XP

---

http://technet.microsoft.com/en-us/library/cc978342.aspx

---

http://support.microsoft.com/kb/223300 - Fix it enable XP, Server 2003-8

---

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

---

http://community.office365.com/en-us/blogs/office\_365\_community\_blog/archive/2013/04/04/office-365-proplus-administrator-series-enabling-verbose-logging-for-troubleshooting-office-365-proplus-installations.aspx

---

http://technet.microsoft.com/en-us/library/bb742606 Control Event Logging

---

“Verbose logging” is a setting that exposes more information during the installation process. It will capture “warning” as well as “error” messages that provide us with clues to your problem. 

You can post the generated Logs in Onedrive and give a link to them to your technician if you need technical help.

I found a pattern in one verbose log file set that I have not yet had a chance to confirm in others, but you can give it a try.  The pattern is each log file is for a separate component. If you open the files from the start and jump to the bottom of each file you will see that they report successful install of a component.  There should be an odd number of log files, find the one in the very middle. It is also probably the largest. It is most likely to be the one reporting the error that caused the install to end and back out. All of the log files after that point will be reporting the uninstall of previously installed components in reverse order.

Here is an example of the error message:

<snip>

MSI (s) (48:2C) [18:15:25:059]: Product: Microsoft Office Single Image 2010 -- Installation operation failed.

MSI (s) (48:2C) [18:15:25:059]: Windows Installer installed the product. Product Name: Microsoft Office Single Image 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

</snip>

Do a google search for “error status: 1603”

If you don’t recognize an error, upload the entire log file set to Onedrive.

The thing is, the “useful” part will be very small and very specific and you probably won’t recognize it. So posting extract may catch the problem, but often miss the important info, so it is best to give us access to everything captured.

PS: remember to turn Verbose Logging OFF after you fix the problem. It will continue to generate “excess” logging files during all installations, including Windows updates.

To do onetime verbose logging:

Diagnosing When Setup Stops Responding

At times, Office Setup stops responding (hangs), and you do not receive any error message. The best thing to do in this situation is to restart your computer, and run Office Setup again with complete verbose logging turned on (with one additional option). To do this, start Office Setup. To do so, follow these steps:

1. 1.           Click Start, and then click Run.
2. 2.           In the Open box, type the following command-line, and then click OK:

path\Setup.exe /L*v! C:\Verboselog.txt

Note that Path is the full path of your Office source location.

To enable Windows Installer logging yourself, open the registry with Regedit.exe and create the following path and keys:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Reg_SZ: Logging

Value: voicewarmupx

The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter’s actual function is as follows for MSI version 1.1:

v - Verbose output

o - Out-of-disk-space messages

I - Status messages

c - Initial UI parameters

e - All error messages

w - Non-fatal warnings

a - Start up of actions

r - Action-specific records

m - Out-of-memory or fatal exit information

u - User requests

p - Terminal properties

• • Append to existing file

! - Flush each line to the log

x - Extra debugging information. The “x” flag is available only on Windows Server 2003 and later operating systems, and on the MSI redistributable version 3.0, and on later versions of the MSI redistributable.

”*” - Wildcard, log all information except for the v and the x option. To include the v and the x option, specify “/l*vx”.

Note This should be used only for troubleshooting purposes and should not be left on because it will have adverse effects on system performance and disk space. Each time you use the Add/Remove Programs tool in Control Panel, a new Msi*.log file is created.

When looking through the MSI logs we will typically want to look for a value 3 entry in the logs. Windows installer returns codes during the install which will indicate if a particular function was successful or not.

Value 1 = Success

Value 2 = Cancel

Value 3 = Error

---

Note: make sure to turn off verbose logging after you are done.

Enable verbose logging before collecting the log files.

1. 1.    Click on Start -> All Programs
2. 2.    Accessories -> RUN
3. 3.    Type reg add HKLM\SOFTWARE\Microsoft\ClickToRun\OverRide /v LogLevel /t REG_DWORD /d 3
4. 4.    Click on OK.

Now try to install Microsoft Office 2013 to get the error message so that the log files get created.

Provide the complete error log present in the ‘Temp’ folder to help you better.

Follow the steps below to access the ‘Temp’ folder.

1. 1.    Click on Start -> All Programs
2. 2.    Accessories -> RUN
3. 3.    Type %temp%  -> Click on OK

Following are the log files that may be present in the %windir%\temp folder (c2r is for Click to Run):Bootstrapper*.log

1. 1.    c2r_*.log
2. 2.    C2Rintegrator*.log
3. 3.    Firefly*.log
4. 4.    Integratedoffice.exe_c2r*.log
5. 5.    Interceptor*.log
6. 6.    *.exe.log
7. 7.    *_c2rdll*

MSI, “Normal”, installations the log files will look like MSI****.LOG

---