Sql 2000 gives error setup stub has stop working

sir i am installing sql server 2000
but i am gate a error setup stub has stop working so what can u do....

Hi,
Without any error details it is hardly someone can help. So, can you please share more details - the exact version, what is the OS you are installing on, what error message(s) do you get and on which stage of the setup.
Ivan Donev MCT and MCSE Data Platform

Similar Messages

Bridge CC on opening gives "Adobe Bridge CC has stopped working" Uninstalled, re-installed same error, will not run. "check online for a solution" does nothing.

Bridge CC on opening gives "Adobe Bridge CC has stopped working" Uninstalled, re-installed same error, will not run. "check online for a solution" does nothing.
Bridge worked great for a while then started to fail when starting. Old Bridge CS6 still works fine. HELP ... please.

You problem is in the Fault Module MSVCR80.dll
Do a web search for this. Here is one LINK

TS2529 Im am using Windows 7 ,I log onto to itunes and connect my Iphone.When my iphone tries to sync it gives an error message "itunes has stopped working" - this only happens when i connect my iphone and it tries to sync - help please

Im am using Windows 7 ,I log onto to itunes and connect my Iphone.When my iphone tries to sync it gives an error message "itunes has stopped working" - this only happens when i connect my iphone and it tries to sync - help please

Many thanks.
With those symptoms, I'd try the following document:
Apple software on Windows: May see performance issues and blank iTunes Store
(If there's a SpeedBit LSP showing up in Autoruns, it's usually best to just uninstall your SpeedBit Video Accelerator.)

Cannot install BI Publisher 10.1.3 Windows 7 setup.exe has stopped working

Hallo!I am trying to install Oracle BI Publisher 10.1.3.4 on Windows 7 Professional 32 bit.When I click on the setup.exe,the following output appears on the cmd prompt
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be 4.0, 5.0, 5.1, 5.2 or 6.0 . Actual 5.1Passed
Checking monitor: must be configured to display at least 256 colors . Actual 4294967296 Passed
Checking Temp space: must be greater than 500 MB . Actual 252112 MB Passed
Checking swap space: must be greater than 500 MB . Actual 1900MB Passed
All installer requirements met.
Preparing to launch Oracle Universal Installer from C:\Users\jirungu\AppData\Lo
cal\Temp\OraInstall2011-04-13_09-33-57AM. Please wait ...
When the OUI tries to launch,the following error appears
setup.exe has stopped working.
Is this due to an incompatibility problem?Are there any prerequisites for installing BI Publisher?How can I resolve this?
Thanks.
Edited by: 4joey1 on Apr 12, 2011 11:35 PM
Edited by: 4joey1 on Apr 12, 2011 11:36 PM

I am also facing the same issue and i tried with the following modes
xp mode
vista mode
2000 mode
still i am seeing the same error.
My Notebook is Window 7 Home Premium 64bit & have jdk 1.6 32bit.
Edited by: user5345841 on May 26, 2011 12:10 PM
Edited by: user5345841 on May 26, 2011 12:55 PM

WRT400N setup.exe has stopped working

I just got a brand new HP Pavillion desktop with Vista 64 and I am having installation issues. Every time I put the setup disc in the drive it fails to load and I get an error message telling me that setup.exe has stopped working and will be forced to close. I even tried skipping the autorun and going in to my rom drive and manually selecting the setup.exe file. The initial splash screen appears and says please wait loading but I never get any farther than that because the program locks up. I thought maybe the disc was defective but I have tried it on an XP desktop and an XP netbook and the disc works fine on both of those. What gives? I have searched this entire forum and it seems like I am the only person having this problem. Is my new computer defective or is it the user
Solved!
Go to Solution.

Is the new Vista Dekstop is wired computer or wireless computer ?
Are you able to go online with the other wired and wireless computers ? If yes then, you do not need to run the CD anymore on the VIsta Dekstop.
If the new Vista dekstop is wired computer then, just connect the eternet cable from the computer to the router on one of the 4 eternet port and restart the computer and it should be able to go online.
If the new Vista dekstop is wireless computer then, try to locate your network and connect it using the secuity key(if the network is secured)...It should work !!!

Cannot install ZEN V -- Setup.exe has stopped working -- CTCABEX.

I cannot install Creative Software for Zen V. Just before the installation finishes, I get the message: "setup.exe has stopped working. A problem with caused the program to stop working correctly. Windows will close the file and notify you if a solution is available."
I also get the following message: CTX Installer-Install Shield Wizard that file CTCABEX.dll not found.
Any ideas on how I can load the creative Zen V software>
Thanks,

I am also facing the same issue and i tried with the following modes
xp mode
vista mode
2000 mode
still i am seeing the same error.
My Notebook is Window 7 Home Premium 64bit & have jdk 1.6 32bit.
Edited by: user5345841 on May 26, 2011 12:10 PM
Edited by: user5345841 on May 26, 2011 12:55 PM

HT201077 my pc gives message that photostream has stopped working it wont upload photos

pc gives message that photostream has stopped working. I have checked settings and read through online support, can't find why.

I was having the same problem. Earlier in the week, I was able to drag a few photos to the upload folder and they synced correctly. Yesteday, I dragged different photos, and I got the "applephotostream.exe has stopped working" error.
The solution - for me, at least! - was to reduce the size of the pictures being uploaded to the photostream. While all of the pictures were jpegs, the first set were ca. 800K (3800 x 2500), and the second set were ca. 2.5 MB (4000 x 2000). When I reduced the resolution of the last set by a factor of 4 (ca. 600 K, 2000 x 1500), they uploaded without a hitch.
Based on this admittedly sketchy experiment, it looks like Apple has a max picture size limit, apparently based on file size rather than picture resolution). Perhaps < 1 MB? To be rigorous, I should complete the experiment - leave the resolution of the second set of pictures alone and reduce file size by reducing jpeg quality.
Has anyone heard about a picture file size limit?

Every time I TRY to start firefox 18-19 I get an error message : Firefox has stopped working - close the program and check online for a solution - or - close th

Every time I TRY to start firefox 18-19 I get an error message : "Firefox has stopped working" - "close the program and check online for a solution" - or - "close the program" this happens TWICE every time I try to start firefox. Eventually after a random number of tries firefox will start normaly. I am useing firefox 19.0.2 now bit I belive it started when I upgraded to firefox 18 but am not sure, it might have been when I upgraded to firefox 19 ... but it has been happening for a very long time and I cannot find any helpfule solutions online.

Certain Firefox problems can be solved by performing a ''Clean reinstall''. This means you remove Firefox program files and then reinstall Firefox. Please follow these steps:
'''Note:''' You might want to print these steps or view them in another browser.
#Download the latest Desktop version of Firefox from http://www.mozilla.org and save the setup file to your computer.
#After the download finishes, close all Firefox windows (click Exit from the Firefox or File menu).
#Delete the Firefox installation folder, which is located in one of these locations, by default:
#*'''Windows:'''
#**C:\Program Files\Mozilla Firefox
#**C:\Program Files (x86)\Mozilla Firefox
#*'''Mac:''' Delete Firefox from the Applications folder.
#*'''Linux:''' If you installed Firefox with the distro-based package manager, you should use the same way to uninstall it - see [[Installing Firefox on Linux]]. If you downloaded and installed the binary package from the [http://www.mozilla.org/firefox#desktop Firefox download page], simply remove the folder ''firefox'' in your home directory.
#Now, go ahead and reinstall Firefox:
##Double-click the downloaded installation file and go through the steps of the installation wizard.
##Once the wizard is finished, choose to directly open Firefox after clicking the Finish button.
Please report back to see if this helped you!

Getting "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine

I am getting a "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine. I already tried running setup.exe as an administrator with the same results. I have Microsoft .NET Framework 4.5.1 installed on the affected machine. Could this be the cause of this issue? Or does someone know the root cause of such error?
Solved!
Go to Solution.

Hi - are you getting it at the start of installation, during or after 100% progress has finished?
Is it just LabVIEW you're installing, or is it drivers too, in which case, what was the last large package that was installing at the time?
This could be caused by the NVIDIA chipset driver :
https://decibel.ni.com/content/message/46299?tstart=-130
Thanks
Sacha
// it takes almost no time to rate an answer

Setup bootstrapper has stopped working Office PP 2013

I have downloaded the Office Pro Plus 2013 ISO from our licensing site. The ISO is good as i was able to install the suite on a 2008R2 XenApp 6.5 server.
However every time i try to install it on my windows 7 SP1 64bit PC i get the error
"Microsoft Setup Bootstrapper has stopped working"
This is in the event viewer:
Fault bucket 3355664129, type 5
Event Name: OfficeClassicSetup
Response: Not available
Cab Id: 0
Problem signature:
P1: 15.0.4420.1017
P2: OSETUP.DLL
P3: 15.0.4420.1017
P4: 0x80004005
P5: Unspecified
P6: 835EB42B
P7: 0x80004005
P8:
P9:
P10:
Analysis symbol:
Rechecking for solution: 0
Report Id: a69e6953-55e2-11e2-b617-d4bed90d8d01
Report Status: 0
I have done some Google searching and tried all the suggestions.
Ran all windows updates. Uninstalled Office 2010. Burned the ISO to CD and tried.
2013 has never been on my computer before as far as im aware. I had someone else try in the office on their laptop with the same results....
Any thoughts?
Systems Administrator

Here is the XML view of the event
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider
Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2013-01-22T21:38:37.000000000Z" />
<EventRecordID>21769</EventRecordID>
<Channel>Application</Channel>
<Computer>PC1030016593.domain.com</Computer>
<Security
/>
</System>
<EventData>
<Data>3355664129</Data>
<Data>5</Data>
<Data>OfficeClassicSetup</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>15.0.4420.1017</Data>
<Data>OSETUP.DLL</Data>
<Data>15.0.4420.1017</Data>
<Data>0x80004005</Data>
<Data>Unspecified</Data>
<Data>835EB42B</Data>
<Data>0x80004005</Data>
<Data
/>
<Data
/>
<Data
/>
<Data>C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301221437291E34).log C:\Users\sboudrea\AppData\Local\Temp\MSI115b3.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d07.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI21d08.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d09.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d0a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d0b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d0c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d0d.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI21d0e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d0f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d10.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI21d11.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI2e513.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI4e698.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI523a8.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI523a9.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55ae.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55af.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55b0.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55b1.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI55b2.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55b3.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55b4.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55b5.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55b6.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55b7.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI55b8.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55b9.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55ba.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55bb.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55bc.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55bd.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI55be.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55bf.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55c0.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55c1.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55c2.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55c3.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI55c4.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55c5.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55c6.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI55c7.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI60e82.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbcf.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd0.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd1.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd2.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd3.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd4.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd5.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd6.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd7.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd8.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbd9.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbda.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbdb.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bbdc.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbdd.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbde.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbdf.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe0.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe1.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe2.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe3.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe4.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe5.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe6.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe7.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe8.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbe9.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbea.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbeb.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbec.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbed.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bbee.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbef.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf0.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf1.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf2.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf3.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf4.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf5.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf6.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf7.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf8.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbf9.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bbfa.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbfb.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbfc.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbfd.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbfe.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bbff.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bc00.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc01.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc02.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc03.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc04.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc05.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bc06.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc07.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc08.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc09.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc0a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc0b.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bc0c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc0d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc0e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc0f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc10.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc11.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bc12.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc13.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc14.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc15.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc16.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc17.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bc18.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc19.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc1a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc1b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc1c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI6bc1d.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI6bc1e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8362c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8362d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8362e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8362f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83630.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI83631.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83632.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83633.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83634.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83635.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83636.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI83637.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83638.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83639.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8363a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8363b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8363c.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI8363d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8363e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8363f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83640.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83641.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83642.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI83643.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83644.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83645.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83646.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83647.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83648.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI83649.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8364a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8364b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8364c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8364d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8364e.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI8364f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83650.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83651.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83652.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83653.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83654.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI83655.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83656.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83657.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83658.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83659.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8365a.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI8365b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8365c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8365d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8365e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI8365f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83660.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI83661.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83662.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83663.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83664.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83665.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83666.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI83667.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83668.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI83669.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c59.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c5a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c5b.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI96c5c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c5d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c5e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c5f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c60.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c61.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI96c62.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c63.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c64.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c65.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c66.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c67.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI96c68.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c69.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c6a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c6b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c6c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c6d.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI96c6e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c6f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c70.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c71.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI96c72.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a756.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a757.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a758.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a759.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a75a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a75b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a75c.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a75d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a75e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a75f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a760.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a761.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a762.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a763.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a764.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a765.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a766.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a767.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a768.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a769.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a76a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a76b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a76c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a76d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a76e.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a76f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a770.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a771.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a772.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a773.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a774.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a775.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a776.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a777.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a778.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a779.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a77a.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a77b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a77c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a77d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a77e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a77f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a780.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a781.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a782.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a783.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a784.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a785.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a786.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a787.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a788.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a789.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a78a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a78b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a78c.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a78d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a78e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a78f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a790.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a791.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a792.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a793.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a794.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a795.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a796.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a797.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a798.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a799.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a79a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a79b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a79c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a79d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a79e.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9a79f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a7a0.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a7a1.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a7a2.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a7a3.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9a7a4.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9dca8.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dca9.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dcaa.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dcab.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dcac.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dcad.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSI9dcae.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dcaf.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dcb0.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dcb1.LOG C:\Users\sboudrea\AppData\Local\Temp\MSI9dcb2.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIa4a97.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSIa4a98.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaec99.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaec9a.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaec9b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaec9c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaec9d.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSIaec9e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaec9f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaeca0.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaeca1.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaeca2.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIaeca3.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSIc6c3f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c40.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c41.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c42.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c43.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c44.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSIc6c45.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c46.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c47.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c48.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIc6c49.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe504a.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSIe504b.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe504c.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe504d.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe504e.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe504f.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe5050.LOG
C:\Users\sboudrea\AppData\Local\Temp\MSIe5051.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe5052.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe5053.LOG C:\Users\sboudrea\AppData\Local\Temp\MSIe5054.LOG C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2012062607591512A0).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201207131243253A0).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201207131243441CB4).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20120713125345154C).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20120817091659E34).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201208201402581248).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201208201410551A88).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201212040902031858).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201212040902291A8C).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20121204090322F18).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201212040937031560).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201212040937407E8).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2012120409442915C0).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201212041126311BA0).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201212051339071E6C).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20130102105831408).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20130102144408132C).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301021534031650).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013010215482816C4).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301021549441568).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301030804361988).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013010310272514E0).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301031317511AB8).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301040823261434).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013010815570415EC).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20130109083626500).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20130109084149B7C).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301090848051EE4).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301090852061F50).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301090857581124).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301090903411808).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20130109090417ED0).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013010909254719D8).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013010909285781C).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013010909391014A0).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20130114113354131C).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(20130114120634132C).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301151023281A84).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301151131251C2C).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301211007082750).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013012110105118FC).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013012110313617A4).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(2013012110383211BC).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301211103221640).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301211105061A68).log
C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301211127131B38).log C:\Users\sboudrea\AppData\Local\Temp\SetupExe(201301221437291E34).log</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Report_15.0.4420.1017_f43830efbcb9f3f41549571abd3ae40e31ffbb0_1b195951</Data>
<Data
/>
<Data>0</Data>
<Data>ec82362d-64db-11e2-964c-d4bed90d8d01</Data>
<Data>0</Data>
</EventData>
</Event>
Systems Administrator

Cannot install Office 2013: Microsoft Setup Bootstrapper has stopped working

I have been trying to install Office 2013 and get this error. Microsoft Setup Bootstrapper has stopped working. Full details are below.
The version of office I am installing is
en office professional plus 2013 with sp1 x86 and x64
The error log shows:
2014/11/04 16:10:55:382::[7440] Cannot start standalone OSE. from <path>\en_office_professional_plus_2013_with_sp1_x86_and_x64_dvd_3928186\x86\proplusr.ww\ose.exe. Error code: 0x80070102
2014/11/04 16:10:55:382::[7440] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError.
2014/11/04 16:10:55:398::[7440] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError.
2014/11/04 16:10:55:398::[7440] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError.
2014/11/04 16:10:55:398::[4744] WER element [P4] is set to value [UnexpectedError]
2014/11/04 16:10:55:398::[4744] WER element [P7] is set to value [UnexpectedError]
2014/11/04 16:10:55:398::[4744] WER element [P6] is set to value [Unable to select Source Engine process to start, see debug level logs for detail]
2014/11/04 16:10:55:398::[4744] WER element [P6] is converted to [C6F06531]
2014/11/04 16:10:55:398::[4744] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError.
2014/11/04 16:10:55:413::[4744] Catalyst execution finished: 11/04/2014 16:10:55. Return code: 30088. Exception caught: UnexpectedError.
2014/11/04 16:10:55:413::[4744] PERF: TickCount=4546680 Name=RunSetup Description=End function
The error window shows:
[Window Title]
Microsoft Setup Bootstrapper
[Main Instruction]
Microsoft Setup Bootstrapper has stopped working
[Content]
Windows can check online for a solution to the problem.
[V] View problem details [Check online for a solution and close the program] [Close the program]
Problem signature:
Problem Event Name: OfficeClassicSetup
SETUP EXE VERSION: 15.0.4454.1000
SETUP DLL NAME: OSETUP.DLL
SETUP DLL VERSION: 15.0.4569.1503
ERROR CODE: UnexpectedError
MSI HRESULT: Unspecified
ERROR DETAILS: C6F06531
FIRST ERROR CODE: UnexpectedError
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 2057
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I managed to fix this... here’s what I did:
I extracted the MSDN ISO to my downloads folder
I created an office 2013 config file with logging set to verbose and copied it to the x64 installer directory
I ran the installer and looked in my temp folder (c:\users\rob.henwood\AppData\Local\Temp)
The log file created said “Cannot detect OSE Service”
I found the OSE Service in the setup folder from the ISO
I looked on another machine and found where it is installed then copied the registry settings for the OSE service.
I restarted the machine and found the Office 64 Source Engine service now existed. I started the service.
I ran the Office installer again and it all worked OK!
Steps to fix:
Create a folder for OSE
C:\Program Files\Common Files\microsoft shared\Source Engine
Copy the OSE.exe file to that folder
Open the OSE.reg file (shown below) and apply the registry settings in that file to your registry
Restart your machine
Open services (services.msc) and see that Office 64 Source Engine is installed
Start the service
Try installing Office 2013/Visio 2013.
OSE.reg:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose64]
"DisplayName"="Office 64 Source Engine"
"Description"="Saves installation files used for updates and repairs and is required for the downloading of Setup updates and Watson error reports."
"Type"=dword:00000010
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,\
6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,43,00,6f,00,6d,00,6d,00,6f,\
00,6e,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4d,00,69,00,63,00,72,00,\
6f,00,73,00,6f,00,66,00,74,00,20,00,53,00,68,00,61,00,72,00,65,00,64,00,5c,\
00,53,00,6f,00,75,00,72,00,63,00,65,00,20,00,45,00,6e,00,67,00,69,00,6e,00,\
65,00,5c,00,4f,00,53,00,45,00,2e,00,45,00,58,00,45,00,22,00,00,00
"ObjectName"="LocalSystem"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose64\Security]
"Security"=hex:01,00,14,80,8c,00,00,00,98,00,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,5c,00,04,00,00,00,00,00,14,00,9d,01,00,00,01,01,00,00,00,00,00,\
05,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,\
00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\
00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,01,01,00,00,00,00,\
00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

Microsoft Setup Bootstrapper Has Stopped Working when Trying to Install MS Project Professtional 2013

I cannot get the trial version of MS Project 2013 to load onto my computer.
I keep getting "Microsoft Setup Bootstrapper Has Stopped Working" error message when attempting to download.

What operating system are you attempting to install to?

Microsoft setup bootstraper has stopped working

hi, when i am trying to install microsoft office professional plus 2013 in my windows8.1 based system pc , i can not installed it. there shows a massage " microsoft bootstraper has stopped working" i tried to installed it several time but
it shows same massage . please help me.....

Hi,
"Microsoft Setup Bootstrapper has stopped working" is a generic error for Office installation. It could be caused by lots of reasons, thus the troubleshooting of this issue can be tricky.
You might first check the setup log file and see if there is anything useful there. If you would like us to help analyze the logs, you can send the log file to this email account:
[email protected] and inform us here (the email subject should be the link of this thread).
Also, to troubleshoot the issue, I would sggest we try following steps:
If you have any trial or beta version of Office 2013 ever installed on your computer, please try to run
Microsoft Fix-It tool
to remove any possible traces which might cause the problem.
If you have enabled any real-time scanning feature of your antivirus program or firewall application, temporarily disable them, then try again.
Hope this helps.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Every time I TRY to start firefox 18-19 I get an error message : Firefox has stopped working - close the program and check online for a solution - or - close ..

Every time I TRY to start firefox 18-19 I get an error message : "Firefox has stopped working" - "close the program and check online for a solution" - or - "close the program" this happens TWICE every time I try to start firefox. Eventually after a random number of tries firefox will start normaly. I am useing firefox 19.0.2 now bit I belive it started when I upgraded to firefox 18 but am not sure, it might have been when I upgraded to firefox 19 ... but it has been happening for a very long time and I cannot find any helpfule solutions online.
I have tried a Clean reinstall but it did not help.

Hello,
'''Try Firefox Safe Mode''' to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.
''(If you're not using it, switch to the Default theme.)''
* You can open Firefox 4.0+ in Safe Mode by holding the '''Shift''' key when you open the Firefox desktop or Start menu shortcut.
* Or open the Help menu and click on the '''Restart with Add-ons Disabled...''' menu item while Firefox is running.
''Once you get the pop-up, just select "'Start in Safe Mode"''
'''''If the issue is not present in Firefox Safe Mode''''', your problem is probably caused by an extension, and you need to figure out which one. Please follow the [[Troubleshooting extensions and themes]] article for that.
''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.''
''When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.''
Thank you.

ERROR MESSAGE: ITUNES HAS STOPPED WORKING

Hi guys n girls, i was wondering if antonehas had the same probs as me, and ill try to explain what happens, After buying an ipod classic 120gb, i downloaded itune 8 for the firs time and it installs, then windows installer asks you "wouldyou like to open itune" so, i click yes, i set it all up, sort out a library, sync to ipod which is all fine, ipod works great.. Now if i close itunes, and open it again another time i get an error message,"itune has stopped working and windows is looking for solutions" and this does it evertime i click onto the icon and the quicktime icon aswell. now ive remove all of itune, quicktime, bonjour, apple updater and mobile support includeing a file to do with apple including some of the music that becomes attactched to it and checking system 32.i then download a fresh itues, it installs, works for the first time and thats it, i get the message again. i have uninstalled and installed intune including various products several time but to no sucess with getting itune to work. if anyone can possibly help me with this as ipod dont bounce off of walls very well cheers
bazza
bazdonsop

please sombody help me, apple support are no help, the shop are no help, the only thing i havent tried is delete everything on my laptop and put it back to factory, which is my very last resort

Sql 2000 gives error setup stub has stop working

Similar Messages

Maybe you are looking for