![error 1935 policy 8.0 microsoft vc80 atl error 1935 policy 8.0 microsoft vc80 atl](http://www.geekstogo.com/forum/uploads/monthly_01_2014/post-384314-0-17325200-1388971241.png)
- Error 1935 policy 8.0 microsoft vc80 atl how to#
- Error 1935 policy 8.0 microsoft vc80 atl install#
- Error 1935 policy 8.0 microsoft vc80 atl download#
However, this log isn't clear enough to diagnose the issue.
![error 1935 policy 8.0 microsoft vc80 atl error 1935 policy 8.0 microsoft vc80 atl](https://renewcoins.weebly.com/uploads/1/2/5/0/125035688/421480258.jpg)
This log usually has a value 3 entry in it when there is a failure. We recommend that you start with the setup.exe log. Therefore, there are many logs to verify. In a good installation, you'll typically not see any value 3 entries in the logs. Windows installer returns codes during the installation that indicate if a particular function is successful or not. When you look through the MSI logs, we will typically want to look for a value 3 entry in the logs. :::image type="content" source="media/troubleshooting-office-installation-failures/verbose-logs.png" alt-text="Screenshot shows an example of the verbose logs from an installation attempt."::: Here's a screenshot of the verbose logs from an installation attempt.
Error 1935 policy 8.0 microsoft vc80 atl install#
Analyzing logsĪfter your install attempt, you'll find that you have somewhere between 1 and 20 logs from the installation in your temp directory. However, this time, you're ready to capture log files that will be detailed enough to help you diagnose the failure point. It's failed previously, expect it to fail again. Now that you have enabled verbose logging and know where you should look for the logs, just retry your installation. If you're running your installation manually on the computer as a signed-in user by double-clicking setup.exe, the log files will be generated in the %temp% directory of the user who performs the installation.
![error 1935 policy 8.0 microsoft vc80 atl error 1935 policy 8.0 microsoft vc80 atl](https://i.ytimg.com/vi/KR9UfftGA6w/mqdefault.jpg)
Error 1935 policy 8.0 microsoft vc80 atl how to#
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installerįor more information about Windows Installer logging, see How to enable Windows Installer logging. To enable verbose logging, set the following registry keys: You'll have a verbose log for the installation of the Word component, Excel, and so on. With verbose MSI logging enabled, you'll get a verbose log file for each component that Office installs. However, it doesn't give the detail that's usually required to diagnose an installation failure. In Office, there's a setup.exe log file that's created by default. When you troubleshoot Office install failures, make sure that MSI verbose logging is enabled. The techniques can be applied to all Office installations that use Windows Installer (MSI). This article describes techniques on how to determine and fix Microsoft Office installation failures. This article was written by Eric Ashton, Senior Support Escalation Engineer.
![error 1935 policy 8.0 microsoft vc80 atl error 1935 policy 8.0 microsoft vc80 atl](http://i366.photobucket.com/albums/oo104/Generalblood/error.jpg)
Note: is not affiliated with Autodesk or with Microsoft. Use at your own risk.Troubleshooting Office installation failures All products that use 2015 should still function with 2017.