2

Windows 8.1 and Office 2013

If I try to open an invalid spreadsheet XML file in Excel a pop-up notification gives a brief explanation of the problem and a points to a detailed log file in the Content.MSO folder. However, when I open the detailed log file, it is empty. Earlier versions of Excel and/or Windows populated this log file with each issue encountered.

What is preventing this log file from being populated?

user3749695
  • 31
  • 3
  • I have experienced the same issue, in the beginning I used Git Bash run in Admin mode to visit the specified location - and I saw the logs. But now even that doesn't work for me anymore – ajthewebdev Sep 28 '14 at 15:15

1 Answers1

0

I'm not sure of the KB number but a fix for Office 2013 related to this issue was pushed through Windows Update around 12/12/2014. Error logging appears to be working again.

user3749695
  • 31
  • 3