"The file is corrupt and cannot be opened" error on office 2010 Excel while opening .xls files

Anonymous
2010-08-07T08:54:12+00:00

I recently upgraded my office to 2010 from 2007 after that i am unable to open any .xls files created by previous version

no issue with the files because i can open it in 2003 sp3 and 2007 sp2 versions

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2010-08-08T06:28:33+00:00

Try the following steps:

  1. Open Excel 2010.

2. Click on File > Options.

  1. Select Trust Center > Trust center settings.
  2. Select Protected view.
  3. Uncheck all the options under Protected View > OK.
  4. Restart Excel 2010 and try to open Excel documents.

Was this answer helpful?

500+ people found this answer helpful.
0 comments

147 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-08-28T16:59:54+00:00

    Thanks, Ruchi - worked like a champ!

    Dan

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-09-06T00:44:31+00:00

    THIS was the only thing that worked for me, Thank you!!!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-10-08T19:38:40+00:00

    Thanks a TON. It worked for me

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-10-21T12:25:24+00:00

    Try the following steps:

     

    1. Open Excel 2010.

    2. Click on File > Options.

    1. Select Trust Center > Trust center settings.
    2. Select Protected view.
    3. Uncheck all the options under Protected View > OK.
    4. Restart Excel 2010 and try to open Excel documents.

     

     

     

    Excellent solution! I was about to give up on this one, my office reported across the board that all files were corrupted after beign saved on a network drive!. Dell support couldnt fix my problem and blamed VMware, who blamed Microsoft. But this solved my problem on all my clients.

    Thank you!

    Was this answer helpful?

    0 comments