Office 2013 Click-to-Run Event Logs

Question

_{Tuesday, January 28, 2014 7:20 PM}

Anyone know what the event logs are (Source, Event ID, etc) for Office 2013 Click-to-Run version? Specifically, I'm trying to find out when my installation was last updated (automatic updates are enabled). In general it would also be nice to know what all of the different events are that the program will log.

Shaun

All replies (5)

_{Wednesday, January 29, 2014 7:21 AM}

Hi,

To view the Office updates log, we can just go to Control Panel > All Control Panel Items > Windows Update and click View update history.

If you want to know all the event logs related to Microsoft Office, we can use Event Viewer.

http://windows.microsoft.com/en-in/windows/open-event-viewer#1TC=windows-7

To find Office-related logs, click Event Viewer > Applications and Services Logs > Microsoft Office Alerts in the Event Viewer window.

Regards,

Steve Fan

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 here

_{Wednesday, January 29, 2014 3:52 PM}

Thanks for the input, but updates for click-to-run installations are not shown in Control Panel under the Update History. Also, the "Microsoft Office Alerts" log only shows a history of pop-up messages from the various applications. Any one else care to weight in?

Shaun

_{Sunday, February 2, 2014 2:24 PM}

Sorry for my mistake. I don't have a Click-to-Run version of Office installed in my test environment. I'm doing research on this problem now, and I may involve someone familiar with this topic to further look at this issue.

Thank you for your understanding and support.

Steve Fan

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 here

_{Monday, February 3, 2014 9:29 PM}

http://technet.microsoft.com/en-us/library/jj219420.aspx

_{Tuesday, February 4, 2014 3:11 PM}

Thanks for the link, although I didn't see any mention of log files or their locations in the article.

Shaun