I am trying to download Microsoft Office Pro Plus 2013 but keep getting the message that I am missing file Microsoft Office 15/clientx86/integratedoffice.exe
I have no idea what to do next, any suggestions please
Technology Tips and News
I am trying to download Microsoft Office Pro Plus 2013 but keep getting the message that I am missing file Microsoft Office 15/clientx86/integratedoffice.exe
I have no idea what to do next, any suggestions please
I have the same problem on Win 7 Professional 32 Bit.
It's no good referring people to links that ask you to remove Office via control panel when this is a vanilla Pc with the only microsoft product installed is the operating system.
I'm installing the Office 2013 Plus suite under a volume licensing agreement on my Home Pc as i work for a microsoft partner.
This is not the preview version so i'm not expecting testing problems. Is this product from the microsofthup.com site not a fully fledged product yet?
The 32 bit exe i downloaded from microsofthup is about 500mb and obviously is the initiator of downloads for the full install but it is not working....
So i expect any mvp reading this to apply a bit of logic to this problem and not to ask to uninstall a failed install but test the installers and perhaps reissue the 500mb installer exe as a patch or issue a FixIt exe to clean the directories and registry?
Have exact same issue using Win 8 64 bit on laptop installing MS Office Pro Plus Home Use Program, will check into Stefan's post and will
Stefan,
Yes i'm seeing the exact same error message: missing Office 15/clientx86/integratedoffice.exe, followed by asking if the HDD has enough space or does the Pc have internet access, both of which it has.
The directory mentioned does exists so i deleted it in the hope a retry would work but i get the same error. the directory was recreated with a few files. Unfortunately i'm at work not on the Home PC to verify the actual files deployed in the directory.
I've been programming windows & databases since VB5 with 10 years previous experience on mainframes and have to script installers using Installshield so i fully understand the problems.
It looks to me like the EXE downloaded from microsofthup site that initiates the full install download or click-once install is flawed.
2 of my work colleagues installed it last night at home on 64 bit windows 7 without issue. Mine as i said is 32 bit Windows 7 so perhaps testing the process more on this flavour of windows will lead to the cause of the issue?
Regards
Martin
yes as i downloaded both 32/64 bit installers to different folders and the exe is named:
setup.x86.en-US_ProPlusRetail_xxxxx-xxxxx-xxxxx-xxxxx-xxxxx_act_1.exe
whereas the 64 bit begins setup.x64.en_US_Pro.......
yes as i downloaded both 32/64 bit installers to different folders and the exe is named:
setup.x86.en-US_ProPlusRetail_xxxxx-xxxxx-xxxxx-xxxxx-xxxxx_act_1.exe
whereas the 64 bit begins setup.x64.en_US_Pro.
Thinking about it, have you tried contacting the HUP Customer Service Representative for help?
http://www.microsofthup.com/hupus/contactus.aspx?culture=en-US
Hello. I've had a similar error to you with my fresh vanilla install of Windows 7 on a PC that I built. I finally found a fix that worked for me.
I just went into regedit and drilled down to "HKEY_LOCAL_MACHINE\Software\Microsoft\Office\15". I deleted the 15 folder, as well as the Outlook folder. Left everything else alone.
I know that the article I'm linking below mentions to delete the HKEY_CURRENT_USER...(and so on)but I left that alone. It worked for me. Hopefully it works for all the other people having the same problem. Here is the link (ignore the fix it and go to the "More information" section):
http://support.microsoft.com/kb/2809219
Dan you are the man!
After hours on this, trying to work out why this error when trying to install MS University on windows 8, trying Microsoft tech support page suggestion - which didn't work - your suggestion worked a treat! Who knows why. I hope Microsoft fix the glitch soon for other users so they don't go through the frustration.
Thanks again for sharing your fix.
:)