[Fixed] MS Office 2016: Microsoft Setup Bootstrapper has stopped working

FINALLY, A FIX! YAYYYYYY

I have been given MS Office 2016 Standard to install on my machine for testing/trial use purpose before roll out to Corporate Services guys.
Okay, uninstalled MS Office 2013. No problem.
Reboot.
Run MS Office 2016 setup... *BAMB* Microsoft Setup Bootstrapper has stopped working..

Man, seriously I hate this. I faced the same problem last time when upgrading MS Office 2010 to 2013. I can't find a solution. In the end, I reformatted my machine after wasted countless of hours.. demm.

Anyways FYI, I'm running Windows 10 Pro 64 bit, and installing MS Office Std 2016 32 bit.

The Error

Error popup "Microsoft Setup Bootstrapper has stopped working" while installing.

Here's the error log I found in %temp%:

2015/12/29 15:32:19:992::[3096] Kicking off chained install...
2015/12/29 15:32:19:992::[3096] PERF: TickCount=529687 Name=Job::DoCacheWork Description=Begin function
2015/12/29 15:33:20:854::[3096] Cannot start standalone OSE. from C:\Users\phua0170t\Desktop\MS Office 2016 Standard\standard.ww\ose.exe. Error code: 0x80070102
2015/12/29 15:33:20:854::[3096] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError.
2015/12/29 15:33:20:870::[3096] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError.
2015/12/29 15:33:20:870::[3096] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError.
2015/12/29 15:33:20:875::[8148] WER element [P4] is set to value [UnexpectedError]
2015/12/29 15:33:20:875::[8148] WER element [P7] is set to value [UnexpectedError]
2015/12/29 15:33:20:875::[8148] WER element [P6] is set to value [Unable to select Source Engine process to start, see debug level logs for detail]
2015/12/29 15:33:20:875::[8148] WER element [P6] is converted to [C6F06531]
2015/12/29 15:33:20:875::[8148] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError.
2015/12/29 15:33:20:879::[8148] Catalyst execution finished: 12/29/2015 15:33:20. Return code: 30088. Exception caught: UnexpectedError.
2015/12/29 15:33:20:879::[8148] PERF: TickCount=590562 Name=RunSetup Description=End function

The Solution

1. Go to MS Office 2016 Std setup files (be it in a DVD or a folder) "MS Office 2016 Standard\standard.ww"
2. Copy the file ose.exe (Note: this file must be copied from the Installer you using. You cannot copy ose.exe from MS Office Pro installer while your installation is MS Office Standard. It doesn't work)
3. Go to "C:\Program Files\Common Files\microsoft shared\Source Engine" (You may need to create the folder "Source Engine")
4. Paste the ose.exe to "Source Engine" folder
5. Download this reg file: ose.reg
6. Open the ose.reg file to apply the registry settings to your registry
7. Restart your computer
8. Run services.msc
9. Start the service "Office 64 Source Engine" if it is not started. (Note: This service must be started!)
10. Try installing MS Office setup again

GOOD LUCK!

Let me know if there's anything I missed out or something you want to add to this error/solution.

Jo.

EDIT 2017-06-09: Updated ose.reg dropbox link

[Fixed] Access to this web server is disabled by default...

Access to this web server is disabled by default because it is controlled by basic authentication and does not use Secure Sockets Layer (SSL). Do you want to search the Microsoft Online Support Center to view possible solutions?

The Problem

Screenshot says it all: (I do not know what exactly caused the problem)

(This applies to all Microsoft Office products)

The Solution

Download the fix from Microsoft website (Microsoft Fix it 50711), patch, and fingers crossed.

So far I've met 3 same cases and all solved by fix it 50711.

Gd luck,
Jo
Where's my coffee?

[Fixed] Excel 2013: There was a problem sending the command to the program.

So, Excel problem again.

I have one user having this issues for a few days before she decided to approach me.

The Problem

The symptoms was the xlsx file would not open if she double click the file; but it works just fine if she opens it via File - Open (within Excel itself).

Screenshot of the problem attached:

The Fix

Head to File - Options - Advanced - General
Ensure "Ignore other applications that use Dynamic Data Exchange (DDE)" is uncheck

Try to double click the xlsx file as per normal.

If this doesn't work, try this other workaround:

Go to File - Options - Trust Center - Trust Center Settings - Macro Options
Enable all macros & tick Trust access to the VBA project object model

ActiveX Settings
Ensure "Prompt me before enabling all controls with minimal restrictions" is selected.

Privacy Options
Ensure "Check Microsoft Office documents that are from or link to suspicious Web sites" is unchecked.

However, please double check which one of the options are getting your spreadsheets opening again as there might be security risks for you if you select all as above (referring to Trust Center Settings)


Gd luck,
Jo.

[Fixed] Office 2013 has stopped working!

Microsoft Excel has stopped working.
Microsoft Word has stopped working.
Microsoft Outlook has stopped working.
Microsoft PowerPoint has stopped working.

Hi Friends,

Like you, I faced this problem after I upgraded my MS Office 2010 to MS Office 2013 and spent plenty amount of hours trying to fix it.
YES IT'S FRUSTRATED! Just look at the screenshot of me trying to find a solution on this:

Event Viewer Errors:

(might be varies from you, but you get the picture)

Faulting application name: EXCEL.EXE, version: 15.0.4420.1017, time stamp: 0x50673286
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x70c
Faulting application start time: 0x01ce148bae1be7ed
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\EXCEL.EXE
Faulting module path: unknown
Report Id: ec6f1ad1-807e-11e2-ba40-4437e69e70e1

Faulting application name: WINWORD.EXE, version: 15.0.4420.1017, time stamp: 0x5067349a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x588
Faulting application start time: 0x01ce13fb6fe1ad27
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\WINWORD.EXE
Faulting module path: unknown
Report Id: ae8f3bec-7fee-11e2-90f9-4437e69e70e1

Faulting application name: OUTLOOK.EXE, version: 15.0.4420.1017, time stamp: 0x506734e2
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x8cc
Faulting application start time: 0x01ce13f3e5651137
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: unknown
Report Id: 27012797-7fe7-11e2-bcd6-4437e69e70e1

The description for Event ID 0 from source MSOIDSVC.EXE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

InitializeSvcAPI failed with hr = 0x80048883

By the way, just for your information; I'm running Windows 7 Professional 64-bit and Microsoft Office 2013 Standard 32-bit.

The Solutions

I have 2 known fixes here; before trying anything, please make sure you can run excel/winword/powerpoint/outlook in safe mode, otherwise these 2 fixes is not for you. I'll use Excel for example.

Press Win + R for run, then enter excel /safe

If Excel 2013 successful run in safe mode, proceed with the fixes, else go back to Google. Good luck.

Fix 1: If you have an Epson Scanner / ABBYY-FineReader

(ABBYY-FineReader is a software bundled together with Epson Scanner)

Fix 1a
1. Run Excel in safe mode. (Win + R ; "excel /safe")
2. Go to File - Options
3. Go to Add-ins
4. Choose COM Add-ins and press Go...
5. Uncheck every box and press OK.
Try to run Excel normally now.

Fix 1b
1. Go to Control Panel
2. Click on Uninstall a program
3. Right click on ABBYY-FineReader and click uninstall.
4. Restart if necessary.
Try to run Excel normally now.

Update: another fix for ABBYY-FineReader
Open ABBYY-FineReader, go to the help menu and search for new updates. Download the newest update. Uninstall ABBYY-FineReader and then reinstall it with the newly downloaded update. Now ABBYY-FineReader works flawlessly scanning into Word and Excel. Also, the newest update does not use add-ins to do it.
(thanks to Anonymous commenter on August 1, 2015)

Fix 2: Disable hardware acceleration

(This fixed MY problem!)

1. Run regedit (Win + R ; "regedit")
2. Browse to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common
3. Create a New Key and name it "Graphics"
4. Select Graphics, right-click on the right panel and create a New DWORD (32-bit) Value and name it DisableHardwareAcceleration.
5. Enter Value data as 1
Try to run Excel normally now.

For some reason, if you're using any USB docking station with DisplayLink driver, please uninstall or update the driver to atleast version 7.1 M1.
Link to download: http://www.displaylink.com/support/downloads.php

Good luck!

Give me a Like, a +1 or just drop a comment if this fix yours! :D

Regards,
Jo.