-->
- Microsoft Office Exe Location
- Outlook 2016 Exe Location
- Office 2016 Exe File Location
- Office 2016 Exe File Location Windows 10
- .exe File Mac
- How To Reinstall Office 2016
- Microsoft Word Exe Location
Summary
Jul 29, 2016 Follow these steps to locate PowerPoint 2016 for Windows: Bring up the the Run window, as shown in Figure 1. Figure 1: Run Window; If you don’t know how to bring up the Run window, look at our Launch Run in Different Versions of Windows tutorial. Within the Run window, type “powerpnt.exe” without the quotes as shown in Figure 2, and click OK. Installation Paths. All the applications provided by the Office suite (Word, Excel, Outlook, Access, Powerpoint), if installed, can be found within the given folder(s). The executable files have kept the same names since Office XP, which are the following: Word: WINWORD.EXE. Excel: EXCEL.EXE. Tips & Tricks 147 - Find the Location of Excel.Exe Generally Excel.Exe will be located in C: Program Files (x86) Microsoft Office Office15 in case of Excel 2013 / Windows 7. During installation, if another path is chosen, Excel.Exe's location changes. Sep 10, 2010 Can you find the Word.exe file from this path: C:Program FilesMicrosoft OfficeOffice14? It is properly that Office 2010 is not properly installed. I suggest trying to uninstall the Office programs from the computer and then reinstall Office 2010. To uninstall, you can go to control panel programs and features.
This step-by-step article describes how to use the Microsoft Office installation log files to troubleshoot Office Setup issues.
Occasionally a problem occurs with Office Setup and you may not receive an error message. Even if you receive an error message, you may have to use an installation log file as one of your tools to determine the issue.
This article discusses several techniques to interpret the information in Office installation log files. The topics are listed in the order that you want to use each technique. This article does not cover every situation that you may experience, but it discusses several examples where the Setup issue is resolved by interpreting a Setup log file.
Many articles in the Microsoft Knowledge Base that relate to installation errors also include sections of log files that help you confirm that the article describes the same issue that you are experiencing.
How to create a log file
Office Setup automatically creates log files in your Temp folder. The log files have names that are similar to the following:
Log file for | Log file name |
---|---|
Setup.exe | Microsoft Office Setup(####).txt |
Windows Installer (System Files Update) | Microsoft Office Setup(####)_Task(0001).txt |
Windows Installer (Office installation) | Microsoft Office Setup(####)_Task(0002).txt |
Microsoft Office Exe Location
The #### characters in the log file names are numbers that start with 0001. They increment by one each time that you run Setup. Therefore, the log file that has the highest number is the log file for the most recent time that you ran Setup.
Note You may have only a Microsoft Windows Installer log file for the Office installation. In this situation, the Windows Installer log file for the Office installation has Task(0001) appended to the log file instead of Task(0002).
How to interpret log files
Depending on the problem that you are experiencing, you may have to view the Setup log file or the Windows Installer log file for the Office installation.
Setup log files
The log file for the Setup.exe file is very short because the number of tasks that Setup.exe performs is limited to tasks like the following:
Outlook 2016 Exe Location
- Read the Setup.ini file.
- Parse the command line for properties and switches that have to be passed to the Windows Installer. A common mistake is to include the following on a command line:Transform=path*transform file name*.mstUsing this on the command line does not produce an error message during the installation, but the transform will not be applied to the installation. The correct command line is:Transforms=path*transform file name*.mstThe Setup.exe log file contains the command line that you specified for the installation so that you must check the log file for typographical errors such as the one that is shown in the previous example (the letter 's' is missing from the end of 'Transform' in the first command line).
- Verify that the correct operating system and service pack are being used.
- Check the version of the Msi.dll file.
- Start the Instmsi(w).exe file to install the Windows Installer.
- Check for installed beta versions of Office.
- Check the version of the Tahoma and TahomaBD fonts.
By default, Setup creates a local installation source in Office, but only when you install Office from the CD or a compressed CD image. If sufficient hard disk space exists on the local computer, Setup caches the whole installation source by default. Windows Installer uses this local installation source to install Office, and the local source remains available for repairing, reinstalling, or updating Office later. Users can install features on demand or run Setup in maintenance mode to add new features. Because Setup creates the local installation source by default, you do not have to set any additional options. Setup creates the local installation source in the following hidden folder on users' computers:
driveMsocacheDownloadcode
By default, Setup caches the whole source in Office. If the user's computer does not have sufficient disk space, Setup caches installation file for only the selected features. Setup retains the local installation source after the installation is complete.
The following information may be contained in the Setup log:
- Listing of files to be copied to the MSOCACHE folder: Files to Download:
- Confirmation of Local Install Source settings:
- Confirmation of completed task:
If you suspect problems with the command-line properties and switches that you are using, these items are also listed in the Setup log file. For example, if you use the following command line to run Setup:
The following text is included in the Setup log:
Note
Setup.exe does not actually use these command-line switches and properties; it just passes them to the Msiexec.exe file (the Windows Installer).
If the log file for Setup.exe ends in text that is similar to the following (return code: 1603), there was a problem with the Windows Installer portion of the installation:
In this case, you must review the Windows Installer log files for the Office installation.
Windows Installer log files
The Windows Installer log files are significantly larger than the Setup log file and can appear to be unreadable at first. However, the following guidelines can help you narrow down the issue:
The warning adds that new Bloods members across the nation will be driving around on Friday and Saturday nights as part of this “initiation game”. Thankfully, however, the warning has no factual basis whatsoever. There have been no reports of crimes like the one described in the warning and no such gang initiation ritual is taking place. This is a common 'Bloods' gang member 'initiation game', The new gang member, under initiation, drives along with no headlights on & the 1st car 2 flash their headlights @ them is now his 'target'. He is now required 2 turn around & chase that car, then shoot & kill every individual in the vehicle in order 2 complete his initiation requirements. May 20, 2017 In this video we go through 5 Unbelievable Gang Initiation Rituals. Crips and Bloods Unite with The Game, Snoop Dogg and Problem - Duration: 10:30. Keenan Chapman 2,446,303 views. Blood gang initiation. The main initiation attributed to the 'Bloods' along with the 'Crips,' the 'Black Gorillas' and 'MS-13,' involves prospective gang members bumping the rear of another car to encourage the driver to stop and get out. At this point, the other driver is purportedly robbed, killed or kidnapped.
- If you receive an error message during Setup, search for the error number in the log file. For example, if you receive 'Error 1327' during Setup, search for '1327' in the log. You may find text that is similar to the following:The key text in these log entries is 'Invalid Drive'. The problem in this case is that you used a utility like Disk Administrator to change the drive letter of the location where Windows is installed. Although the drive letter was changed, some registry keys still refer to the original drive letter.
- If the Microsoft Knowledge Base does not have an article that matches your specific error message, follow these steps to diagnose the issue:
- Search the log file for the error number.
- Read each line up from the line with the error number. Typically you see a line that failed, with the ultimate result being a Setup error.For example, a log file was searched for 'error 2737'. The following text was located at or above the line with the 2737 error:Looking at this text, you see that Setup failed on the call to CheckCAServer.
- All log files contain one or more errors that typically can be ignored. The following errors may appear in any log file and typically do not indicate a Setup problem:Info 2898. An internal error has occurred. Contact your Information Technology department for assistance.Info 2743. An internal error has occurred. Contact your Information Technology department for assistance.Info 2726. An internal error has occurred. Contact your Information Technology department for assistance.
- One thing to search for is the string 'Note'. In one case where Setup failed with a 2755 error, the actual resolution for the case was derived from the Note several lines above the error:After the permissions were corrected on this folder, the 2755 error did not occur.Note The line that contains '1632' is the determining factor that this issue deals with permissions.Note In log entries that contain 'Note', the four-digit number that follows 'Note' can be mapped directly to the Windows Installer errors that are listed in the Knowledge Base articles cited earlier in this article.
- Another string to search for in the log file is 'Return Value 3'. If you do not have or remember an error number, but you locate 'Return Value 3' in the log file, this is clearly the area where it is best to focus your troubleshooting. When an action is performed during Setup, the action is noted in the log files. When that action is complete, a return value is subsequently noted. If the return value is 1, the action was successful; however, if the action failed, the return value will be 3.In this case, the SetW2kMill_WFP action succeeds, because the return value is 1. However, the next action, CheckCAServer, fails because its return value is 3.
- Sometimes when you review a log file, you do not find 'Note', 'Return Value 3', or an error number. Instead, you may see text that is similar to the following:In this case, Setup is having a problem applying a transform, because the transform cannot be located on the specified path (C:test.mst). Therefore, Setup also tries to locate the transform on the root of the Office source location. When the transform cannot be located in either place, the installation stops.
Office 2016 Exe File Location
Verbose log files
All the techniques that are listed in the 'Windows Installer Log Files' section can be used on verbose log files. However, verbose logging increases Setup times. Only use verbose logging if you are having Setup problems that cannot be diagnosed with a default log file.
- Generating a Verbose Log FileOn the initial install of Office, verbose logging is not used but if a Setup failure occurs, the second try to install will generate a verbose log file. However, the logging options that are used for these verbose log files are not all the options that are available to the Windows Installer. If you want to create a more detailed Windows Installer log file with all the logging options, you can use the *v parameter combination for the /L switch.Note You can create a verbose log file while you perform an administrative installation of Office by using a command line that is similar to the following:pathsetup.exe /a pathPro11.msi /L*v C:Verboselog.txtDiagnosing When Setup Stops RespondingAt times, Office Setup stops responding (hangs), and you do not receive any error message. The best thing to do in this situation is to restart your computer, and run Office Setup again with complete verbose logging turned on (with one additional option). To do this, start Office Setup. To do so, follow these steps:
- Click Start, and then clickRun.
- In the Open box, type the following command line, and then click OK:pathSetup.exe /L*v! C:Verboselog.txtNote that Path is the full path of your Office source location.
Typically, 19 lines of logging information are cached in memory before being written to the verbose log file. If you do not use the ! option for the /L (logging) switch, you may lose some of the cached information or all the cached information if Setup stops. If you use the ! option, the most you lose is one line, because the ! option forces Setup to write logging information to the log file one line at a time (there is no caching of information).After you create the verbose log file, scroll to the end and look at the last one or two lines. These lines tell you what Setup was trying to do when it stopped. For example, you may see text that is similar to the following:This indicates a problem with the registration (in the Windows registry) of the component (71CE92CC2CB71D119A12000A9CE1A22A), whose key path is OWCDCH11.CHM.The resolution for this particular issue is to repair the Windows registry before you run Office Setup again.In another case, you may see text that is similar to the following in your log file:This indicates a problem with an Office Removal Wizard operation. This problem may occur when Office Setup is having a problem removing your earlier version of Microsoft Office. Try to remove the earlier version of Office, and then run Office 2003 Setup again.Note Office Setup uses the following prefixes for custom actions. If the log file indicates a problem with a custom action, these prefixes indicate where to start your troubleshooting.- OLCA: Outlook Custom Action
- OPC: Office Removal Wizard
- CAG, CaMMC: Associated with Clip Art
- IE: Internet Explorer
Active2 years, 2 months ago
Help!Some months ago i messed around and used Types to change some file type icons without making a system restore. I changed the Excel, Powerpoint, Onenote, Word, Access and Publisher file type icons. They look ugly and I realized how stupid I was so I wanted to change back.
I'm not using Types now, but FileTypesMan. The problem is I can't find the location the dll containing the icons are.
I'm using MS Office 13 and Windows 10.
strugglingstruggling
4 Answers
Nirsoft, who developed FileTypesMan, has another program you could try called IconsExtract. I dont have Office 13, but i tried it out on 14 and was able to locate all the office icons and change them with FileTypesMan.
Using IconsExtact, browse to and search the folder C:/Program Files (x86)/Microsoft Office/Office 13/ (or something similar to that). Hbr articles pdf. It may take a minute but a list of all the office icons should show up.
Select the icons you want to use, right click and save them to your Desktop or another folder as a .ico extension.
You can then use FileTypesMan to edit the extension's icon. Browse to the folder where you saved the icons and choose the appropriate .ico file.
Alternatively you could try to rebuild the icon cache, or reinstall office, but Im not positive these options will work.
If your still stuck, try downloading Office Ico files from the net and loading them with FileTypesMan.
Office 2016 Exe File Location Windows 10
Hope this helps, good luck!
user4922056user4922056
I had the same the problem, but for Outlook 2016. After some searching (with IconsExtract, as mentioned in an answer above) I found several locations which store icons used in the program.
I don't know whether they are the same as in 2013 (and have no way of validating that now), but for those who may have a similar problem in the future, a considerable number of the icons are stored in:
C:Program FilesMicrosoft OfficerootOffice161033OUTLLIBR.DLL
C:Program FilesMicrosoft OfficerootOffice16OUTLOOK.EXE
C:Program FilesMicrosoft OfficerootOffice16OLKFSTUB.dll
C:Program FilesMicrosoft OfficerootOffice16OUTLOOK.EXE
C:Program FilesMicrosoft OfficerootOffice16OLKFSTUB.dll
As for the other microsoft office applications:
For excel:
C:Program FilesMicrosoft OfficerootOffice16EXCEL.EXE
C:Program FilesMicrosoft OfficerootOffice16XLICONS.EXE
C:Program FilesMicrosoft OfficerootOffice16EXCEL.EXE
C:Program FilesMicrosoft OfficerootOffice16XLICONS.EXE
For access:
C:Program FilesMicrosoft OfficerootOffice16ACCICONS.EXE
C:Program FilesMicrosoft OfficerootOffice16MSACCESS.EXE
C:Program FilesMicrosoft OfficerootOffice16ACCICONS.EXE
C:Program FilesMicrosoft OfficerootOffice16MSACCESS.EXE
For word:
C:Program FilesMicrosoft OfficerootOffice16WWLIB.DLL
C:Program FilesMicrosoft OfficerootOffice16WORDICON.EXE
C:Program FilesMicrosoft OfficerootOffice16WINWORD.EXE
C:Program FilesMicrosoft OfficerootOffice16WWLIB.DLL
C:Program FilesMicrosoft OfficerootOffice16WORDICON.EXE
C:Program FilesMicrosoft OfficerootOffice16WINWORD.EXE
For publisher:
C:Program FilesMicrosoft OfficerootOffice161033/PUB6INTL.DLL
C:Program FilesMicrosoft OfficerootOffice16MSPUB.EXE
C:Program FilesMicrosoft OfficerootOffice161033/PUB6INTL.DLL
C:Program FilesMicrosoft OfficerootOffice16MSPUB.EXE
.exe File Mac
For powerpoint:
C:Program FilesMicrosoft OfficerootOffice16PPTICO.EXE
C:Program FilesMicrosoft OfficerootOffice16POWERPNT.EXE
C:Program FilesMicrosoft OfficerootOffice16PPTICO.EXE
C:Program FilesMicrosoft OfficerootOffice16POWERPNT.EXE
For onenote:
I cannot find much for onenote, except its application file(s):
C:Program FilesMicrosoft OfficerootOffice16ONENOTE.EXE
C:Program FilesMicrosoft OfficerootOffice16ONENOTEM.EXE
However, having looked at it, most of the other icons can be found in the other dlls and exes already.
I cannot find much for onenote, except its application file(s):
C:Program FilesMicrosoft OfficerootOffice16ONENOTE.EXE
C:Program FilesMicrosoft OfficerootOffice16ONENOTEM.EXE
However, having looked at it, most of the other icons can be found in the other dlls and exes already.
If you are looking specifically for something that looks like the file icons, then you either need to look in Shell.dll in the Windows32 folder, or in this folder:
C:Program FilesMicrosoft OfficerootOffice16LogoImages
C:Program FilesMicrosoft OfficerootOffice16LogoImages
Harvey EllisHarvey Ellis
Win 10 with Office 2013 user here. Icons found at C:Program FilesMicrosoft OfficeOffice15
How To Reinstall Office 2016
AnonymousAnonymous
Microsoft Word Exe Location
For Office16 I went to the office16 directory (in Program Files x86). There are separate exe (aka Application) files there for each Office component that end with ICO or ICON (ACCICONS, PPTICO, WORDICON) that have the icons. Couldn't find one with all icons. The inconsistencies (ICONS, ICO, ICON) are not mine btw.
GuyGuy