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

Wow..., that's so convenient....

Now I have the ultimate answer i worked for 4 days and i am successful now...

First of all try the old steps..

Step 1: Run the fix it from the following link to remove traces of Office: http://support.microsoft.com/kb/2739501/en-us

Step 2: Once the fix it process is complete try the step below to rename the Microsoft Help Folder and check if it helps: · Hold Windows key + R. · Copy and paste, or type the following command in the Open box, and then press Enter: %Programdata% Rename the 'Microsoft Help' folder as 'Microsoft Help. OLD'

After coming in the programdata folder delete all files related to  ms office by your own common sense... Ex - PowerPoint publisher , word , excel etc any releated folder....If there are no folders then leave it..

Step 3 : go to program files of your pc and completely delete the ms office folder if there are more folders related to the ms office then  remove them too..ex- msbuild , microsoft office analysis ,  OR any related files by your own common sense.

Step :4  now , Hold Windows key + R. · Copy and paste, or type the following command in the Open box, and then press Enter: %appdata %

After coming to the app data folder.. there  3 more folders will be found more find any ms office related folder among these 3 folders and completely delete the ms office related folders by your own common sense ex - PowerPoint ,excel , publisher , word etc... If there are no folders then leave..

Now comes the last step

Now open the ms office 2013 or 2016  setup with administrator 's privilege... By right clicking on the setup and clicking run as administrator..

Disable any type of antivirus before installation because they can block some features......of the installation...

This worked for me... Now u try

Thank You

Mayank Kr.

I have the same problem. This is my error. Any remedy? Please. I deleted OFFICE and task scheduler, event log, all are enabled.

Problem signature:

Problem Event Name: OfficeClassicSetup

SETUP EXE VERSION: 15.0.4128.1014

SETUP DLL NAME: OSETUP.DLL

SETUP DLL VERSION: 15.0.4128.1014

ERROR CODE: 1603

MSI HRESULT: Unspecified

ERROR DETAILS: FC73469E

FIRST ERROR CODE: 1603

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 16393

Thank you so much this work, Instantly it work thank you so much

There are as many reasons as there are solutions. There is really no reason to keep fiddling with a botched installation. Not that you botch it, it botches itself! I have been fighting these wars since XP, and 2003. And sometimes, no scrubber works. In that case, I just save the data to a folder, or another drive, and go for the reinstall. I usually reformat the HDD, and start anew.

I have to thank you in return for the discussion because it is a very important one. I am not declining there are any issues with Office. In fact there are numerous threads like this one handling the same or similar issues. I've had the issue myself - that's why I found to comment it in the first line. In fact for me the solution was to run ALL available and suitable cleaners that Microsoft has in stock for the affected OS, so I've started with the Office 2007, then 2010 then the 2013 / 2016 cleanup tool in the order of release to get it fixed.

To be honest the ways how computer work or simply refuse to work are so numerous. Basically all that I can repeat is that in some circumstances it might be faster - especially since the appearence of Windows 10 - to reinstall or "refresh" the system instead of fiddling and searching for solutions for hours.

I find it hard myself to refuse to do that just because I am curious and want to learn what's the issue and how to solve it to appreciate people that found a solution or to find the logical solution myself, regardless if the time invested is really worth it or not. That said on my rig, Windows 10 is installed in about 5 minutes, which isn't the standard for anyone and which doesn't mean that I would simply throw anything aboard to skip around errors like this nasty Office installation bug.

The major problem since decades is that Microsoft is saving developing time for proper installation gauges - these might indicate more precisively when an installation fails and eventually also why, then they are cutting ressources to code proper error messages that are additionally well documented in the KBs. Yes of course there are logs but to be honest people simply don't love to browse megabyte sized ascii based logfiles.

Microsoft, however, isn't a lone sample of a developer doing so.

After all, - no offence - if anyone keeps failing to install Office despite having ran all the cleanup tools - I think it's better to start with a clean system instead of bothering with finding possible solutions.

Just yesterday I had one system where the Windows component store was so desperately bugged and destroyed that not even sfc or dism could repair it. There are many dependencies on this component store (WinSxS) also Office and Windows Updates or Store... if such things are damaged and cannot be repaired with usual tools it might be not worth to spent time on the matter any further.

Just my 2 cents.

p.s. I would also advice anyone to avoid inplace upgrades from an older version to a newer version like from 2007 to 2010 or 2010 to 2013 / 2016 but rather uninstall the old version and install the new one - eventually run the cleaners before.

The reason is that I had a lot of troubles with the migration of Outlook (non Exchange based) profiles and you would be surprised that Microsoft still does save these in a Windows NT 4.0 branch in the registry :), just in case you need to backup anything.