Cannot start office 2013 applications

Environment: Windows 7 Pro X64, Office 2013 Home and Office X64
Office applications are not starting, none of them (outlook, word, excel, powerpoint). There is no error message, just don’t start. I see it in task manager, to appear on the list of running tasks, then quit. Doesn’t start in safe
mode either: word /safe.
I tried to repair, the quick repair was done without error, but did nothing. The online repair says, that the process was unsuccessful.

update：
Please try to update the display card drive. See the below thread:
http://social.technet.microsoft.com/Forums/en-US/34401d63-6c3b-47e6-ab20-9ed9b70d890b/outlook-2013-sp1-unusable-since-sp1-update-?forum=officesetupdep
Thanks
George Zhao
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click "[email protected]"

Similar Messages

Cannot start the source application for this object - Embedded PDF in Excel 2007

I am having a real issue which unfortunately is intermittant and I cannot pinpoint what is causing the problem. Basically I am inserting a PDF object into an Excel worksheet and immediately after I insert it, it will open fine. If you click off into another cell and save the sheet, then try to reopen the embedded PDF, you get the error "cannot start the source application for this object".
Any help would be very much appreciated! Has anyone else run into this?

I got that problem with one of my client after updating from Adobe Reader 8.2 to 9.3.1. Excel version was 2002 and not 2007 but this is Adobe problem.
Check that registry key for you Acrobat Document key points to right AcroRead32.exe path at HKEY_CLASSES_ROOT\CLSID\{B801CA65-A1FC-11D0-85AD-444553540000}\LocalServer32
of whatever key points to your Acrobat Document.
I used Sysinternals Procmon to monitor registry activity and found a line and opened that registry location and found out Adobe Reader 8.0 path there.
9:55:56,9021789 EXCEL.EXE 3236 RegOpenKey HKCR\CLSID\{B801CA65-A1FC-11D0-85AD-444553540000}\LocalServer32 SUCCESS Desired Access: Maximum Allowed
I have seen that Adobe Reader 9.3 doesn't update that registry and leaves Adobe Reader 8.0 values there. Same problem may be in other upgrade scenarios too.
In addition to that my Windows 7 with Office 2007 that has never had anything but Adobe Reader 9.x versions didn't had anything on that registry location and it gave me same "cannot start the source application for this object" error. Putting that path "C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe" to LocalSever Default value fixed that too. Maybe Adobe should do something with this issue?

Cannot open Office 2013 Excel, Word, PPT Files on Network Share

Cannot open Office 2013 Excel, Word, PPT Files on Network Share
I am having a problem opening any Office 2013 file when it is located on a network drive. I immediately get the error:
"Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space.
. To make more memory available, close workbooks or programs you no longer need.
. To free disk space, delete files you no longer need from the disk you are saving to."
It only occurs when I try to access the file when it is stored on a network share. I cannot open any word, excel or PPT files located on my file shares.
I am on Windows 8 (pro), part of a local domain based on Server 2003, and have administrator rights to the domain and the file share where the Excel file resides (and Word files -same problem). If I copy the file locally, I can either open
it directly, or right-click, go to Properties and 'un-block' the file and then open it. But it is impractical to keep doing this, as I edit different files from the directory tree all day.
I have bing'd and google'd this extensively, and the only answers I come up with do not work, such as going into the DCOM config system and changing the user from interactive to launching user, or vice versa, or even using a specific user - mine
with the password. Since the product is so young there aren't a lot of posts on this, and nothing has improved the situation.
Can you add any insight to this? I really want to use Office 2013, but this is such an obstacle I'm going to have to downgrade if this problem cannot be resolved. Thank you very much for any help you can offer.
Evan

Dear Evan,
If DCOM config solution did not work, I'd suggest narrow down the problem by trying to access another network share on another server, try to open an Office file there, do we still have the error? It could help us determine if the issue is on the client
machine or the server side.
Best regards,
Daisy Cao
Forum Support
Please take a moment to "Mark As Answer" if they help.

Office 2013 applications cannot be made to show the "Documents" folder when opening and saving files

(Windows Server 2012R2 and Windows 8.1 PRO)
We are redirecting the user's "Documents" folder to the network (using Folder Redirection). The OS hides this fact however, and most applications simply see the "Documents" folder when opening or saving files, including Office 2003.
Office 2013 however displays the actual path, which in this case is:
\\sever1\redirect$\username\documents
Even if you forcibly set the "Default local file location:" in the Options Save area to the 'Documents' folder in, say, Word, Word immediately converts the local path to the network path.
Is there anyway to get Office 2013 to follow the virtual path? All of other apps follow it and expose the users only to "Documents".
Thank you so much.
Dana

There's nothing in my FAQ concerning screen savers, so I'm unsure why you decided to take that approach. From your description, it looks like you only tried a few of the suggestions before throwing in the towel. That's fine, it's your call.
I don't have the problems you described with 10.4.7. Usually when folks have problems after an update, these are caused by either installing an update on an already-corrutped system or they've installed third-party applications or hardware that have been rendered incompatible by the update.
Before installing software updates, you may wish to consider the advice in my "Installing Software Updates" FAQ. Taking the steps therein before installing an update often helps avert problems and gives you a fallback position in case trouble arises.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Office 2013 Pro - Error Message - I cannot set Office 2013 as the default mail client

I have a number of PCs on a single domain in the same office all running Windows 7 Pro. Some at 64 bit and some are 32 bit depending on their age.
My issue is that on upgrading from Officer 2010 Pro to Office 2013 Pro, the only application I have a problem with is Outlook 2013, and only on the 64 bit machines.   The upgrade on 32 bit machine goes perfectly.   On both I install the
32 bit version of Office 2013 as per the MS notes.
When the 64 bit machines reboot and the user logs on I get the message, sometimes twice:
Either there is no default mail client or the current mail client cannot fulfil the message request. Please run Microsoft Office Outlook and set it as the default mail client.
OK, so this should be straight forward:
I set outlook at the default mail client and associate all file with it from Outlook\File\Option. Nope. That does not work.
I go through default programs and set the default mail client as Office 2013 and associate all file with it from Outlook.   Nope. That does not work.
I check the registry and it shows that the 64 bit or 32 bit reversion is the default mail client. So that does not help.
I install the 64 bit version instead of the 32 bit version. Nope. That does not work.
I clean the registry and temp file. Nope. That does not work.
I set a new mail profile for the user. Nope. That does not work.
Odd that it only upgrades smoothly on the 32 bit machines.
Has anyone got any ideas?   All the suggested fixes on this forum do not fix this issue.

Hello.
Same problem, nothing Works!!!
Help please, really frustrated and angry.
Added written above I tried:
Uninstalled with the Microsoft fix uninstall
and reinstall. This does not work.
Contact the phone technical support. This
does not work.
Addin,s does not work. Adobe, iCloud Addin .... does not work.
'Send email to'   menu does not work.
No application communicates with
Outlook, no Microsoft or third apps.
I can only send and receive emails
from within Outlook.
This program is lousy, any
possibility that my money back.
Thanks

Office 2013 applications crash when opening/saving files in OneDrive for Business folder

My setup:
Windows 7 64-bit
Office 2013 Professional
OneDrive for Business (connected to Office 365)
Issue Description:
Example 1:
1. I create a file in OneDrive for Business using the appropriate web app (Excel web app, for example).
2. I edit the file in the web app, I save the file in my OneDrive for Business
3. I sync OneDrive for Business with it's local folder
4. Now I open the folder in Windows Explorer and double-click the Excel file
5. Excel splash screen shows up for a bit, and then Excel crashes
Example 2:
1. I open Word on my Windows 7 laptop
2. I start from a blank document and create some content in the document
3. I use the Save As option under the File menu to save the file to my local OneDrive for Business folder
4. As soon as I click the Save button on the dialog, Word crashes
The same happens with all the Office applications.
Important Note:
If I run the above examples with Excel/Word in SAFE mode, there is absolutely no issue.
What have I done so far?
1. I have made sure that the DisplayLink driver is the latest version from the manufacturer
2. There is no bluetooth send-to add-in in any of the Office applications
3. No add-ins are enabled in any of the Office applications (not sure if there are "stealth" ones that are not visible in the Options/Add-Ins dialog?)
Any assistance with this would be much appreciated.
JeHarry

Hi JeHarry,
Because I didn't have Windows 7, I did a test with Windows 8.1 based on your description. However, in my testing, everything worked well.
Please repair your Office under Control Panel, compare the result.
This forum is for SharePoint On-premise, as your issue is about Office 365, I suggest you create a new thread on Office 365 forum, more experts will assist you with Office 365.
Office 365 forum:
http://community.office365.com/en-us/f/172.aspx
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Cannot install Office 2013 during task seqeunce after installing R2

Hi,
Since we installed SCCM 2012 R2, I have not been able to install Office in my baseline captures using a task sequence (64-bit OS). Ronni Pederson suggested using an Application rather than a Package but in his example, the application is being pushed rather
than deployed during OSD. Either way, his solution doesn't work for me. Office 2013 does install on my Windows 7 SP1 32-bit capture without any errors (same package).
I saw another suggestion that recommended using a wrapper script in a package. When I tried this, I used Task Manager to verify that application was installing and I could see msiexec running. After about 10 minutes, SCCM seems to be waiting for feedback
from the application which never happens. The task sequence fails and I can see log messages stating that it's Waiting for job status. It repeats this message for about 20 minutes and then fails. The wrapper script seems to have the best results but still
doesn't install Office without errors. When I logged in as administrator, I could see that Office looks to be installed. I tried launching a few of the apps and they are working so I don't really understand why this installation doesn't work properly.
Prior to installing R2 on SCCM 2012, this was not a problem. I installed Office 2013 via my capture task sequences many times without any problems. The only thing I can find through research is to use an Application object or use a Package object with a
wrapper script. I couldn't find any other suggestions.
Does anybody have any other ideas?
Thanks,
Rob

Before I can name any ideas, I need to know what's going wrong. Did you follow all the log files? I would start by looking at the installation log files of Office (%windir%\Temp) and see if it's indeed ending successful. If it does then continue to the
ConfigMgr log files (App*.log for application, or exempt.log for package).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Cannot start Outlook 2013: "name cannot be resolved" / "connection to Microsoft Exchange is unavailable" / "___.ost is not an Outlook data file (.ost)"

My work e-mail has a double-login system, where my credentials for work access are one username and my e-mail is an alias of that first username, so they differ from one another. I suspect that's why I've been having the hardest time with Outlook 2013. I
was able to add my account just fine once but changed my mind about using Outlook and removed the account. Now I can't get back into Outlook for the life of me. The error messages that show up are:
1. It asks me to verify server and Mailbox. I've tried it with both usernames (the official work username and the e-mail alias) as my Mailbox info, followed by the email domain (even tried it without the domain) and it still won't verify when I click "Check
Name".
2. This message comes up: The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
3. Then once I click "OK" another pop-up says: Cannot start Microsoft Outlook. The file C:\Users\FirstLastname\AppData\Local\Microsoft\Outlook\FirstLastname.ost is not an Outlook data file (.ost).
Help?

Hi,
As per this KB article, the issue might occurs when some required registry key does not exist on your computer.
Please try the steps mentioned in it and see if it is helpful to you:
http://support.microsoft.com/kb/2264398/en-us
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.

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

Office 2013 applications crash with Document Information Panel open

I am using Office Professional Plus 2013 to work with documents that reside in SharePoint 2010 document libraries.
The content type(s) in that SharePoint site collection are set to automatically show the Document Information Panel when opened in Office applications. By opening any of these documents in their desktop app (via browser or Skydrive Pro), I am able
to check-out and edit content; but the check-in step always crashes the application, giving a pop-up error: "An unknown errors has caused <office program> to stop working."
By choosing to NOT automatically show the Doc Info Panel for these SharePoint documents, Office 2013 programs can handle everything just fine (editing, versioning, etc.).
If I don't auto-show the Doc Info Panel, but then manually open the panel once I get inside the program, this crashes the program in the same way as before.
If I save a local copy of a document and show the Doc Info Panel in any way (auto or manual), Office 2013 crashes.
I couldn't find any postings on this error and I don't see this incompatibility listed in the
Office 2013 known issues article and was wondering if anyone has had a similar experience?

I am having the exact same issue. I have created a Custom Site Column which is defined as a CHOICE. I do not want to put in a Default so left it blanl but field must be populated. I then put this into a Document Library Content Type.
With documents that are already been uploaded and in the Library when I pull up in Office Web Apps, I can make changes to the document but when I try to save it crashes.   Also, when I pull up document and say edit in Office Web Apps there is no
way to change information in the Document Information Panel since this does not appear.   (I forgot to mention that I required DIF to display in Content Type also).
This only happens on blank column fields when trying to save. If I do a Quick EDIT of the list and change my blank Choice columns to something(I created as radio buttons) and then go through the process it works OK and will save. Not sure
if this pertains to your issue but, I just prepopulate all columns with what the should be, when a brand new document from word, excel etc is created it is created from the Desktop version of Word Excel and when IT saves to SharePoint, I get
a message to choose information to put into properties before it actually saves.
Hope this helps a little.

Printing causes Office 2013 applications to crash

We’ve a fresh installed Windows 8 Pro and Office 2013. Printing works correctly in every application but Office 2013.
Word, Excel, Outlook … printing causes the application to crash.
Any idea if this is a known issue?
Regards.
Peter
Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

This is the answer that fixes the problem every time, based on my experience and that of others. It works for both the 32 & 64-bit versions of Windows (I'm one of those odd ducks who runs 32-bit Windows 8.1 Professional and it worked perfectly for me).
The problem is not Windows, either 7 or 8, it's Office 2013 and a variety of unique HP LaserJet printers. By the way, the glitch occurs whether you use networked printing or a USB cable; I discovered that early-on when I
was trying to troubleshoot the issue. Also (and it should go without saying), always reboot the computer after you make the change to the driver. Thanks to Shane, who apparently was the first one to discover the solution over a year ago, right
after Office 2013 came out and the problem manifested itself.
After lots of testing I have found a setting that has fixed all my HP CP5520 and HP M4555 printers that were crashing when printing from Office 365's 2013 pro plus.
It's the driver setting in Device settings -> Installable options -> Printer Status notification, this needs to be disabled.
I hope this also fixes other peoples problems.
Shane

How to migrate Office 2010 Pro application most recently opened document (MRU) to Office 2013 applications

I am upgrading from Office 2010 Pro to Office 2013 Pro. In my test, we discovered that the MRUs are not getting migrated over from the Office 2010 Pro applications into the Office 2013 Pro applications. I am using the Microsoft
Office 2013 OCT to do the configurations. In the OCT, I have "migrate user settings" checked, but that did not work for the users MRUs. I came across the following link
http://social.technet.microsoft.com/Forums/office/en-US/67b3622f-5b7c-4c57-b71d-c8c7de6f7da9/office-2010-pro-to-2013-not-migrating-settings-and-recent-history?forum=officeitpro
That suggests manually creating the Migration key with sub keys like below
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Common\Migration\Word]
"UpgradeVersion"=dword:0000000d
"Lang"=dword:00000409
On the test machine that I was using and had installed Microsoft Office 2013 Pro on, I found the keys listed as follows
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Common\Migration\Word]
"UpgradeVersion"=dword:0000000e
"Lang"=dword:00000000
1) I would like to know which is correct subkey ("UpgradeVersion" and "Lang") to use?
2) Since I am using the OCT, can I add or import them into the OCT add registry entries section?
Thanks for your help.

Since you are doing an uninstall-upgrade the MRU list will not migrate by default.
"UpgradeVersion"=dword:0000000d means Office 14.0, also known as Office 2010
"UpgradeVersion"=dword:0000000e means Office 15.0, also known as Office 2013
"Lang"=dword:00000409 means Locale ID = English_United_States, and the "Lang"=dword:00000000 means default.
In this case, you plan to migrate Office 2010 to 2013. thus, the correct one is
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Common\Migration\Word]
"UpgradeVersion"=dword:0000000e
"Lang"=dword:00000409 (00000000 is ok as well)
Yes, you may import them into OCT registry entries section, or you may deploy these registry keys before migration.
Tony Chen
TechNet Community Support

SCCM 2012 - Deploying Office 2013 Application - Setup Errors

dear SCCM admins,
i am trying to test deploying office 2013 to users in my company. i made the application and deployments. the application appeared in the software center and in the application catalog.
The problem is whenever a user "which is not a local administrator" tries to install this application, it gives me the setup errors message saying "You must have administrative privileges to install or uninstall this
product."
Is there any specific configuration to make to overcome this behavior???
appreciate your suggesstions
M.Zakaria

As you can see from the screenshot you need to add the ProductID after the uninstall command.
See here for finding the ProductID
http://blogmines.com/blog/2012/07/21/how-to-check-version-of-office-2013-products/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Cannot download Office 2013 Service Pack 1 (KB2850036)

I'm using SCCM 2012 Config Manager. I've created a software update date for Office 2013 - Service Pack 1. It contains only 1 update, and that's the Office 2013 SP1 (KB2850036).
The standalone installer for this KB is around 640MB, according to the following link.
http://support.microsoft.com/kb/2817430/en-us
When I choose to Download this update with SCCM, it starts the normal "Provisioning Update" process but sits at 0%. The deployment package directory grows to 334 folders, 329 files taking 3,707,522,416 bytes on the hard drive, and then eventually
throws the following error in SCCM.
Error: Service pack 1 for Microsoft Office 2013 (KB2850036) 32-Bit Edition. Failed to download content id 16844655. Invalid certificate signature.
I've tried the download a couple of times, and I get the same thing.
Any suggestions?

WSUS does not use the stand-alone installer for any updates. For this update in specific, because I had a battle with it, there are something like 700 different files that are part of the update and something like 800GB of data - those are ballpark numbers
based on my spotty memory; IOW, lots. Your best bet is just to right-click on the update itself and select download again.
If that still doesn't work at all, you can click on the update and go to the content tab, you'll see all of the files listed. You can individually copy the URLs (using Ctrl+C) and download them manually if there are one or two that won't download.
Jason | http://blog.configmgrftw.com

Cannot install Office 2013 - Seup cannot find or validate an installation file

I downloaded the trial version of Office 2013 to evaluate it, but was unable to install it because I kept getting the following error...
Setup cannot find or validate an installation file. Please try reinstalling office from your installation source or if you installed from a downloaded package, please re-download and reinstall. If you continue to haVe problems
contact Microsoft or your system administrator.
I tried re-downloading the program - again I was met with the same problem. I tried running the setup file as administrator - problem remained. I tried copying the program to the hard drive and running it from there as the administrator - problem
remained. I downloaded Microsoft fixit tool for problem installations and ran that - that was no use either. The error message just kept coming back again.
I am assuming the setup file is corrupted in some way but seem unable to get an alternative setup file that will actually INSTALL. Or is there something so blatantly obvious going on that I'm missing it?
Help please!

I deployed Office 2k13 to client machine via SCCM 2012 R2. It did that flawlessly but I got the same error after trying to uninstall Office 2k13.
setup.exe /uninstall ProPlus /config .\ProPlus.ww\Uninstall.xml
Uninstall.xml file:
<Configuration Product=”ProPlus”>
<Display Level=”basic” CompletionNotice=”yes” SuppressModal=”yes” AcceptEula=”yes” />
</Configuration>
I can uninstall Office 2k13 manually by running setup.exe and following wizard but it is not automatic process so it sucks.
I've responded in your other thread:
https://social.technet.microsoft.com/Forums/en-US/fd735611-95bf-46f6-8add-2229a52e3e93/i-can-not-uninstall-office-2013-from-command-line?forum=officeitpro
Hi, your command-line is not valid - you are using a "relative" path for the <config.xml> and that is not supported..
http://technet.microsoft.com/en-us/library/cc178956(v=office.15).aspx#BKMK_config
Note: You must use a fully qualified path. Setup does not recognize relative paths with /config.
Instead, I suggest that you copy your "Uninstall.xml" file to the same folder where setup.exe exists, then, adjust your command-line like this:
setup /uninstall ProPlus /config Uninstall.xml
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Cannot start office 2013 applications

Similar Messages

Maybe you are looking for