Microsoft Setup Bootstrapper has stopped working. 19/2016 10:03:57 AM 11:09:47 AM Welcome to the Office 2013 and Office 365 ProPlus IT Pro General. MDAC 2.81 bootstrapper package can be used with Setup & Deployment projects & ClickOnce applications to redistribute MDAC 2.81. Have a new Surface Pro 64bit, Windows 10 and no Office has ever been installed. Getting the famous Microsoft Bootstrapper has stopped working message. /armenian-font-for-microsoft-word-mac-22663/. I have researched greatly and can't find an answer to this issue. With nothing to clean up and I am at a complete loss as to why Office 2016 will not install.
The Microsoft installer is no longer running. This is an error message that appears when you install MS Office 2007, 2010, 2013, 2016 or upgrade your Office to a newer version.
Microsoft has tried to improve the installation system by using an updated technology. Before seeing it, it was enough to install the executable file and one click was enough to install the product. Today Microsoft used a modern technology called “Bootstrapper” to install Microsoft Office 2013/2016.
Depending on the functionality, “Bootstrapper” initializes the application created with the “Composite Application Library”.
Before you begin to fix this problem, you need to create a recovery point to restore your system.
What is Microsoft Setup Bootstrapper?
What is the Microsoft installation bootloader? In Microsoft Office 2013, 216 and 2019 the loader is used to initialize an application created with the Composite Application Library, which simplifies the dependencies needed during the installation.
Reasons for stopping the Microsoft Bootstrapper installer
You can see that the Microsoft installation loader stopped working when trying to run programs in Microsoft Office package, and the Microsoft installation loader stopped working for various reasons. I now list some of them below:
- Communication between the installer and MS servers is blocked by third-party anti-virus software.
- Registry keys or installation files are damaged.
- Conflict with IObit software.
- The task scheduler is disabled in the registry editor.
- The update process is interrupted by AppComparFlags.
- Office installation is incompatible with Windows version.
Download Microsoft Setup Bootstrapper
Uninstall third-party antivirus software
Some users reported that in their case the problem was solved after removing their third-party antivirus package http://windowsbulletin.com/fix-microsoft-setup-bootstrapper-has-stopped-working/. It turns out that there are several overprotective antivirus programs (McAfee, Avast, possibly others) that block the functionality of Microsoft Office package update and cause an error in Microsoft Setup Boot Trapper that stopped working. .
If this scenario is applicable to your situation, simply disabling real-time protection in your security package may solve the problem. The steps to do this of course depend on the audiovisual package you are using.
Note, however, that some users have reported that the problem has not been solved until they have completely removed a third-party antivirus from their system. When you are ready to go that far, follow this article (here) to remove the security programs and make sure that all the remaining files are also removed.
If after working with a third-party security package you still receive the error message “The installer stopped working when you started the Microsoft installation” or if this method was not applicable, proceed to the following method.
Using the Troubleshooting utility
Step 1. Click the link below to go to the Microsoft support page and download the program installer and troubleshooter:
Depending on your system type (32-bit or 64-bit) click “Download” to download the fix.
For example, my system is 64-bit, so I chose to boot X64. If you are using a 32-bit system, you should choose to boot X86.
Step 2: Now click to start the fix, and check the “Apply the fix automatically” box.
Click Next to continue.
Step 3: Now wait for the Troubleshooter to detect all problems.
Step 4: Select the problem you have encountered. For example, here we have an installation problem. Click on Install.
Step 5: Wait until all installation problems are detected. When you are done, you will see a list of programs that have problems with the installation. Choose if it is on the list and click Next.
Step 6: If the program is not in the list, select “Not in the list” and click “Next”.
Step 7: You will then be asked if you want to remove the program or try other fixes. Choose as you wish.
It’s finally time to work on the actual Office installation. We’ve spent several weeks preparing prerequisites, but now it’s time to get down to business. We’ll assemble all of the needed components, and then next time, we’ll will build our application packages and task sequences in Configuration Manager.
As I stated in the overview, my organization has licensed Microsoft Office Professional Plus 2016. Note that this is not the same thing as “Office 365 ProPlus“, which is a subscription plan. The former is packaged the same way as the previous three versions—as a collection of MSI packages coordinated by an executable installer. The latter is delivered via a streaming model. I will be addressing the former.
My organization has also licensed Microsoft Visio Professional 2016 and Microsoft Project Standard 2016. Since these two products are considered part of the Office family of applications even though they are packaged and licensed separately, there is some overlap in their installation files and those of Office Professional Plus. We’ll take advantage of this to build a single installation source for Configuration Manager, thus decreasing the amount of disk space and network bandwidth required to install all three products. (Machines that don’t have all three installed will still get the entire payload in their Configuration Manager caches, but in my environment, it makes sense to bundle them.)
- Download the ISO files from the Microsoft Volume Licensing Service Center. I downloaded both 32-bit and 64-bit media, so my files were:
- On your application staging file share (wherever you put application source files for Configuration Manager to find), create a folder for the Office, Project, and Visio installation sources. Mine will be fileserversoftware$MicrosoftOffice Professional Plus 2016 (32-bit).
- Mount 32-bit Office ISO in Windows File Explorer by double-clicking it.
- Run the following commands to copy the ISO content to your installation source folder, checking the log file afterward to ensure that all files were copied successfully:
- Eject the Office ISO image, and mount the 32-bit Project ISO.
- Run the following command to copy the ISO content to your installation source folder. The /XC, /XN, and /XO switches prevent Robocopy from overwriting any existing files in the destination.
- Eject the Project ISO image, and mount the 32-bit Visio ISO.
- Run the following commands to copy the ISO content to your installation source folder.
- Repeat steps 2 through 8 for the 64-bit ISOs, copying their contents into a separate installation source folder. Mine will be fileserversoftware$MicrosoftOffice Professional Plus 2016 (64-bit).
- Download the Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool from the Microsoft Download Center. These were released after Office, Project, and Visio, and so contain updated versions of the included files.
- Run the two downloaded executables to extract the files.
- Run the following commands to copy the ISO content to your installation source folder. Note that for product installation, we are only interested in the admin folder.
- Repeat step 12 for the 64-bit Office Customization Tool and the 64-bit installation source admin folder.
We’re going to use the Office Customization Tool to make our Office installations silent and to tweak a few settings. It looks like Microsoft has not revised its documentation for OCT in Office 2016, so please review a little bit of the Office Customization Tool (OCT) reference for Office 2013 if you are unfamiliar with the tool. I will take a step-by-step approach, though, so if you are new to OCT, you should still be able to follow along.
As I mentioned in the overview, my approach to application packaging is to make the installation silent so that it can be deployed with or without user interaction and to minimize or preferably eliminate first-run prompts wherever possible. For example, people that have been using Microsoft Office for years do not want to watch a video about Office or sign in with a Microsoft Account when their version of Office is upgraded; they just want it to work and not get in their way. On the other hand, as a system administrator, I don’t ever want to be too heavy-handed or nitpicky in application of custom settings because unexpected changes to default settings could be surprising or frustrating to users. I want to give users an experience as close as possible to the out-of-box experience designed by Microsoft without compromising the no-first-run-pop-ups rule. You can customize almost any setting in Office by using the Office customization tool, but don’t do it! Most organization-specific setting customizations belong in Group Policy, not in the installation program.
Open an administrative Command Prompt window and run the Office setup program with the /admin switch:
The Microsoft Office Customization Tool window will open and prompt you to select a product. Office, Project, and Visio should be listed. Choose to create a new Setup customization file for Office.
Here are the settings that I used. These settings eliminate most first-run pop-ups. Also, since my organization uses Microsoft Exchange, Outlook will be able to figure out the account settings for the signed-in user automatically, so I include a setting that tells it to just do that and not bother the user with the new account wizard. As is the case with most installers, specifying a silent installation is not enough to prevent a reboot, so a Setup property is specified to make that intention clear. (See Setup properties reference for Office 2013; again, we’re relying on some 2013 documentation because there is no updated version for 2016.)
|Install location and organization name||Leave the default installation path.|
Type your organization’s name in the appropriate box.
|Licensing and user interface||Ensure that Use KMS client key is selected. (This is the default.)|
Ensure that the I accept the terms in the License Agreement checkbox is checked.
Set the display level to None. Then ensure that the subsequent checkboxes have the following states:
|Modify Setup properties||Add the property name SETUP_REBOOT (all capital letters) with the value Never (first letter only capitalized).|
|Modify user settings||Ensure that the Migrate user settings checkbox is checked.|
Configure the following settings:
|Set feature installation states||Set the root node to Run all from my computer.|
Regardless of feature installation settings, everything is copied to disk no matter what. The whole thing is there, and we paid for it, so let’s turn it all on so that people can use it without any hassle.
|Additional content section|
|Add registry entries|| Add a registry entry under HKLM to tag installations of Office with an easy-to-read marker denoting this Setup customization file. I use a registry key with my organization’s name and a value that contains the customization file’s name.|
That last item is just my personal preference and is completely optional. I thought it might come in handy at some point in the future to be able to easily tell whether a given Office installation had been installed using my customization file.
Save the customization file to the root of the Office installation source folder. (It should be in the same location as setup.exe.) It is saved as a Windows Installer patch file (MSP). I use the following formula for naming the customization file; a hyphen separates the individual pieces of information:
- “OCT” for “Office Customization Tool”
- Product name based on its folder name in the installation source (e.g., ProPlus), followed by the version under which it is marketed (e.g., 2016)
- CPU platform (i.e., x86 or x64)
- “Silent-Install” to indicate that the installation requires no user interaction
- The date the customization was created in yyyy-mm-dd format.
Following this naming scheme, the filename for the customization we just built is OCT-ProPlus2016-x86-Silent-Install-2016-02-15.MSP. This, of course, matches the registry value I added.
Project, Visio, and 64-bit Versions of Everything
You will need to create new customization files for each of the other two products. All of my settings for Project and Visio are identical to those for Office with the following exceptions:
- There are obviously no Outlook 2016 settings.
- The added registry value will reflect the name of its own customization file.
Then, when that is done, you can move to your 64-bit Office installation source folder and create three more customization files for 64-bit versions of Office, Project, and Visio. Don’t mix the bitness of customization files and installation files. You must use the 64-bit setup.exe program to build 64-bit customization files, and you must use the 32-bit setup.exe program to build 32-bit customization files. You cannot use the same customization file for both the 32-bit and 64-bit versions of a product. You can, however, import a 32-bit customization file for a given product into the 64-bit OCT and then resave it as a 64-bit customization file for that same product, and vice versa.
When you are done, you should have six customization files. Mine are:
My instructions above specified saving the customization files in the root of the Office installation source folder rather than in the Updates folder. If the customization files were in the Updates folder, they would be applied automatically during any installation. The problem is that only one customization for a given product can exist in the Updates folder. That’s fine for now; we only built a single customization file for each product. If I wanted to support multiple installations from a single installation source, though, this would not work. For example, suppose most users are served well by the installations described above, but for some business reason, some computers can only have Microsoft Word installed. If the customization files were in the Updates folder, I could not reuse this installation source; instead, I would have to have a separate copy of the complete Office installation files. That is clearly ridiculous, and so I planned ahead in case something like that happens by saving the customization files outside of the Updates folder. The consequence of that decision is that I must be explicit about which customization file when running setup. That will be our first command-line argument.
The second command-line argument will tell Setup which product to install. Since there is one setup.exe file in a folder structure of three products, Setup will prompt for which product to install unless we tell it on the command line in advance. To specify the product to install, we must point setup.exe to the config.xml file for the desired product. This file is located in the folder named after the product.
To get a full description of the command line parameters available, run
setup.exe /?. Here are the commands to silently install the 32-bit versions of our three products:
Next time, we’ll revisit the .NET prerequisites.Posts in this series:
- Deploying Microsoft Office 2016: Customizing Setup
Microsoft Setup Bootstrapper Office 2016 Download
<update date=”2016-02-20″>Added setting the SETUP_REBOOT property to “Never”.</update>
<update date=”2016-04-17″>Revised the “Coming Up” section for accuracy.</update>