As part of our process in troubleshooting Office 2016 issues, we typically have to reinstall office and restart as a step.

Figure 1 The Error: This product installation has been corrupted

Sometimes you may get the above error. This has manifested lately on CSDS machines, the issue stemming from the ccmcache not having the Office16 installation files. For some reason Office16 stores its reinstaller, uninstaller, etc in ccmcache which is normally a temporary file folder for installers. There is no clear reason why this is a problem now but it could be getting removed automatically by Microsoft or Admin Disk Cleanup could be sweeping it up as well.

The fix for this issue is to grab the Office installer folder from the share drive(coming soon when we get more space on there)(For now, here is a link to my OneDrive to download the folder. Please note you need the whole folder, don’t just download the individual files/folders.)

Copy the folder(Office_2016_x86_Collection) from the share:(share drive link to come later) https://purdue0-my.sharepoint.com/:f:/g/personal/cchasta_purdue_edu/ElH8tcNJavRKkWG0UskMIoYBEp-x0kITKqvmGeZT1NjZzQ?e=0WmGd2
C$ into their machine using File Explorer
1. \\CSDS-XXXXX\C$ (For credentials, use your DADMIN credentials)
2. If you cannot C$ into their machine, they may not be on one of the webvpn’s or they haven’t been on them for long enough.
Figure 2 The ccmcache folder
Navigate to their ccmcache folder, if it looks similar to what is above, you are in the right place.
1. Typically going to be: \\Csds-xxxxx\c$\Windows\ccmcache
Paste the folder into the ccmcache folder Note: do not cut and paste it. Do not rename it
After it is on the machine, you can run the reinstall like normal from Control Panel
1. Note: You may need to try it twice

In the event that it does not run, you may need to run it from the ccmcache folder you just made on their machine. It should show the repair option by running the install.vbs script.

In the event that that does not work, you may need to run the "setup.exe" file, let it run for a few minutes, close it in task manager, run it again, hit repair and there's a 50/50 chance that will fail to which you should just need to run it one more time for it to finally work.

Browser not supported