Office PP 2013 - Setup bootstrapper has stopped working

Hi Anula ,

I have tried all the options mentioned in this post and replies of the post .After around 50 attempts and wasting one complete day i am still unable to install the software. Still getting the error "Windows setup bootstrapper has stopped working" .The product is become less and less user friendly. I have the same issue trying to use an img file for Microsoft project.This is ridiculous set up for installation .Real waste of time this setup is.

Go into your "Services" in your settings and disable your Print Spooler - just right-click on it and then click stop. My install hung at about 90%, and when I disabled the spooler it finally installed.

Hope it helps.

First of all, I want to thank Kyle for his post. He hit the nail on the head. Once I stopped the spooler, everything went smoothly.

Anytime you install the Office suite, you are installing several programs: Word, Excel, PowerPoint, Outlook, *** AND *** OneNote. With Office 2013, you are also installing a utility called "Send To OneNote" that lives in the notification tray. Apparently, it has an incestuous relationship with the print spooler.

If you've never tried OneNote, you should. It is a fantastic program and worth the price of admission all by itself. I had no problems installing Office 2013 on a new machine but updates through Windows Update would sometimes hang.

By installing only a few updates at a time (a LONG process) I finally identified OneNote updates as the culprits. Before reading Kyle's post, I had three updates for OneNote that would not install because they would all mysteriously just hang about 20% into the process. Additionally, I tried to repair the installation through Control Panel and that also hanged. I came * THIS * close to uninstalling and reinstalling Office when I saw this thread.

The update installer and in Adrian Leong's case, the initial installer, do a good job of ensuring that no Office suite programs are running during the install. It even asked for permission to stop "Send To OneNote". But I think it leaves a portion of it, which may be hooked to the print spooler, still running. This makes sense to me since Send To OneNote runs as a process.

I've never used Office 365, but my guess is that it also contains OneNote and Send To OneNote. When Adrian went to install from the ISO, the installer terminated any running Office applications but, like the updater, left the Send To OneNote process running, thereby hanging the install. I think stopping the Send To OneNote process would have the same effect as stopping the print spooler and allow updates to run smoothly.

To quickly access your running services, press the Windows key and R. A dialog box will open for the Run command. Type in "services.msc" (without the quotes) and click OK. Once the services window opens, scroll down to Print Spooler then follow Kyle's instructions above.

Alternately, you can right-click the Taskbar and select Task Manager. It will show you all the processes running on your machine. Scroll down to either process, or both, and click End Task. You'll have to restart them after the install, but the easiest way to do that is just reboot.

Hope you find this useful.

You are a golden god. Thank you!

I received the same error message and one of our developer's figured it out.

• We removed all previous versions of Office products,
• Ran the Fix-it tool:

Use the Microsoft Fixit tool to remove the older version of Office installed on the computer from the following article.

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

• He discovered that the Task Scheduler service was not enabled. It would not let him enable via the GUI so he had to go into the registry to enable
• He then rebooted the system.
• Once the system was up, he verified the service was running and then I was able to install Office Pro Plus 2013, Visio Pro 2013 and MS Project Pro 2013.

In my case the MDT task sequence was producing this error at the post install section.  It turned out the source files were incomplete/corrupted.  By simply downloading the application again and importing back into the applications node, resolved the issue.