Excel 2010 crashes when using print preview button and adding headers/footers

Anonymous
2010-12-19T00:28:04+00:00

I am using Office 2010 Professional with Windows 7.  The installation was successful and I have no other issues with any Office programs except Excel 2010.  Whenever I use the print preview button on the Quick Access Toolbar to check the print preview before printing, or use headers/footers to add these before printing, Excel crashes and forces a restart when I next go to save the document.  It may allow me to do up to 3 print previews before I go to save the document and it crashes and attempts to recover the data or just shuts Excel down after a few times.

All other Office program functions work fine and I have checked my printer driver with a Microsoft utility and it reports no issues.

Can anyone help?

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

94 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2011-03-17T23:01:37+00:00

    Have had some success when manually changing the printer to Microsoft XPS prior to calibrating page layout, ensuring to save after each step change.  Once happy with the page layout, I then reselect my HP printer and can happily print.  It's a bit of a work around but so far so good.

    Am in the middle of downloading SP1 - fingers crossed that makes a difference.

    Sean

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-03-19T00:56:36+00:00

    I have all the same problems and more described but thanks to your posts, I now understand that it's my HP printer somehow clashing with Excel 2010.  I have a HP Officejet J6480 All-in-One.

    Just so happened that I've always used a Freeware called CutePDF Writer.  It creates .pdf files and after you install the program, it shows up as a printer.

    My brainstorm was to set Cute Writer as my default printer since I don't have any other printer.  I didn't uninstall or do anything with my HP printer, just left it there.  I did disable loading the HP Solution Center etc. on startup but I don't know if it makes any difference.  In any case, I no longer have any errors when working in Excel.  When I'm all done, then I choose the HP printer to print.  Just make sure it's back to Cute Writer as default before you work in Excel after printing.

    Not a solution, just a work around but at least it's not too difficult or time consuming.  Hope this helps you get around the problems also.

    Cute Printer

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-03-20T02:15:55+00:00

    To add to CutePrinter's work around...

    Add "Print Preview and Print" Command button to your QAT. This is the fastest way to switch printers in Excel 2010. This is the same window that will display when you hit Ctrl+p in Excel 2010. (This window is a new feature of Excel 2010). Please note that on the right side of this window, is the new "Print Preview" interface. Now, try switching printers...(Printer arrow-down) and see for yourself the printer driver that can "print preview" the fastest. Make that printer your Windows Default Printer because Excel 2010 likes to use the printer driver somehow.

    In the case of CutePrinter, Excel 2010 is communicating with the mentioned printer driver seamlessly.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-03-21T10:51:25+00:00

    I have same problem. Any body solve this problem? My printer is Hp F4280.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2011-03-26T01:36:58+00:00

    Bill,

    with respect, HP is NOT THE ISSUE.  All worked fine with MS Office 2003 & 2007.  The problem is with Microsoft release Office 2010.  I have updated my printer driver and like others on this post spent countless frustrating unproductive hours redoing work and recovering excel files.

    There is NO way that Microsoft is not aware of this problem.  I also know other people who experience the same frustrating problems and all Microsoft's lame response is spend money with us to look into it.  That's bullshit and they need to take their head out from where the sun doesn't shine, man up and fix it and treat their customers with respect.

    Was this answer helpful?

    0 comments