This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have downloaded the Office Pro Plus 2013 ISO from the download page and when I try to install it, it show me the first screen saying that the setup is preparing and then I get the error message "Microsoft Setup Bootstrapper has stopped working". Could anyone help?
I have also read this article, but I do not have Citrix installed: http://social.technet.microsoft.com/Forums/en-US/officeitpro/thread/88a6f422-0bac-4d0d-8279-95c5afbbc95a/
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
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.
I think there's a problem with your hardware specs.
I had the same problem too and now m using the WPS office 2015 as an alternative to ms office.
Can you tell your hardware specs??
do you have an intel core i5 processor???
Use compatibility mode (windows xp service pack 3) in your setup.exe
Simple way to try isn't it?
PS: It totally works for me.
Folks -
Make sure you can run ose*.exe (ose00000.exe and so on - successive attempts at reinstalling will increment the ose00001.exe, etc.) from your %temp% folder. After CryptoLocker many IT folks put in GPOs that blocked EXEs from launching in the temp folder. Adding those ose00000.exe's as "unrestricted" in a software restriction policy seems to be effective, and Office 2013 setup can continue.
Doug
This is exactly correct for my case. You can verify this is occurring by looking for event ID 866 in the windows logs. We have GPO in place as described. We usually unblock the files on a case by case basis, but I also found that backing the machine out of the domain and into a workgroup allowed for the installation. Big thanks to Doug for associating the bootstrapper error with this GPO. I had become accustomed to other error responses, and now I will add this to my troubleshooting list.
Good stuff!
73's
Chris Closs
yes. I found that the following worked perfectly.
I threw that PC right out the window and got a MacBook. Problem solved.
your instructions do NOT work at all. I still get the same error. Come on Microsoft, can you really not figure yourself out???