I have a customer with an HP Elite computer, Windows 8, and Office 2013 (perpetual license, NOT Office 365).  The first page of a print job to an HP laser printer comes out fine.  However, it will not print another page.  Word or Excel hangs, and then asks to "Restart, or Close".  After the first page, if I go to Task Manager, I see "Windows Host Process (Rundll32) Not Responding".  Also when I close Windows 8, I get the message hpmsn140.dll or hpmsn09.dll "Not Responding".

This problem does not occur with other applications.

This problem does not occur with other non-HP LaserJet printers.

This problem occurs with both USB and network printers.

The only way to clear the problem is rebooting the computer.

I have tried the Windows 8 driver, HP's PCL 6 driver from their website, and HP Universal Print Driver from their website.  All have the same issue.

I have tried logging in as Administrator, as well as, the Standard User.  Both logins have the problem.

Any help would be appreciated.

Michael

• Edited by Michael1000 Tuesday, March 05, 2013 12:18 AM

Jaynet, I tried a clean boot as you described, and, unfortunately, it did not resolve the issue.  I tried printing from Notepad and Wordpad, and those two programs do not have a problem.

Any further ideas to try?

Thanks, Michael

• Edited by Michael1000 Thursday, March 07, 2013 12:39 AM

Same problem here. Office 2013 and HP Laserjet CP1525n. First page after a reboot prints and then the hang. I've tried all four of the current driver offerings from HP, namely PCL5 Universal, PCL6 Universal, Postscript Universal and lastly printer specific. All have the same problem. Interestingly this is only happening with Windows 7 32bit. We also have a few Windows 7 64 bit PCs and they are happy to print with the latest HP drivers and 32 bit Office 2013.

Anyone solutions appreciated!

• Proposed as answer by Arthurfuxake Tuesday, March 26, 2013 8:45 PM
• Unproposed as answer by Arthurfuxake Tuesday, March 26, 2013 8:45 PM

We've managed to fix the problem, but via a fairly unexpected route.

We ran the HP "Scrubber.exe" driver removal tool which is part of the "HP LaserJet Full Feature Software and Driver" download or on the CD that came with the Laserjet.... it's the the "utilities" folder.

We then installed the "HP LaserJet Full Feature Software and Driver" just taking the default options throughout (i.e. installing the extra tools & software too).

Office 2013 now prints perfectly on all affected PCs.

Why there is a difference between the "Basic" and "Full" drivers (both downloaded from the same HP web page and apparantly the same version/date) and why the need to run the Scrubber tool first, even on a PC that's only ever had the above mentioned Basic driver installed... just doesn't make sense... but we've now done the above on 25 PCs and it does certainly fix the problem!

• Edited by Arthurfuxake Tuesday, March 26, 2013 8:57 PM spelling
• Proposed as answer by Arthurfuxake Tuesday, March 26, 2013 8:57 PM
• Marked as answer by Jaynet ZhangMicrosoft contingent staff, Moderator Thursday, March 28, 2013 10:00 AM

Any updates/suggestions on this?

I can confirm this is isolated to Windows 7 32-bit and HP Printers. This is happening on the Office 365 flavor of Office 2013.

-Brad

• Proposed as answer by Stoal76 Monday, April 22, 2013 1:14 AM

After lots of testing I have found a setting that has fixed all my HP CP5520 and HP M4555 printers that were crashing when printing from Office 365's 2013 pro plus.

It's the driver setting in Device settings -> Installable options -> Printer Status notification, this needs to be disabled.

I hope this also fixes other peoples problems.

Shane

• Proposed as answer by Stoal76 Monday, April 22, 2013 1:18 AM
• Marked as answer by Michael1000 Thursday, May 02, 2013 1:09 AM

Same issue here

http://www.techieshelp.com/office-2013-crashes-when-printing-to-hp-printers/

What we did was In the printer driver go to Device settings -> Installable options -> Printer Status notification and select disable.

• Proposed as answer by calvin.enriquez Monday, March 10, 2014 9:08 AM

That helped me as well - I have the HP Laserjet 100 M175 - I have not seen it hang since I changed the settings!  The best thing to do is to go to 'See What's Printing' which will get you to the print queue, where you can get to the printer properties to change the settings. This should be bookmarked so its more easy to find :)

Thanks again!

• Proposed as answer by JaySel Sunday, June 09, 2013 6:58 PM

Precise and accurate.

Thanks, Shane, you just saved me a lot of troubleshooting time.

  You da MAN Stoal!  (Or, you da WOMAN!)

Wow, thanks, it really worked.  I was about at the limit but it makes sense that it would be hanging at the notification, because that's where it hangs.  I guess it's waiting for a signal it never receives.

Can I come live with you, or at least my computer?

We've been having exactly the same problem on several Win7 x64 machines which have just had Office 2013 x64 installed.

When printing to HP printers (a Laserjet 4050 and a M475), using HP drivers (I tried the PCL 5 and 6 universal drivers, and the full driver install for the M475), the printer would hang after printing from either Word or Excel 2013 (didn't try any other office applications). 

Eventually I disabled the notifications (by chance), and this seems to have fixed the problems.

There's definitely a problem with the notifications for HP printers across all drivers, and with Office 2013.

All,

I have been reading this post, and have tried to reproduce this issue. I would like to investigate this issue further. If you are still experiencing this issue, please reply to this thread.

Best regards,

Dan Eccher

Dan Eccher
AMS Advanced Technical Support
Global Support Engineering

Global Customer Care, PPS CSS

Hewlett-Packard Co.

Dan, this problem continues to occur to this day (20 May 2014) still with no resolution. As noted elsewhere, I've just installed two new Dell computers with Windows 8.1 Professional, Office 2013 Home & Business with a couple of new high-end HP LaserJet printers with the latest Universal PCL 6 drivers and I still had to disable the "Printer Status Notification" to get them to print. When is HP going to respond to this annoying and ongoing bug, which has been around as long as Office 2013 has? Thanks...

We were having similar issues on 10 brand new Dell Optiplex 3010 installed with Windows 7 x64 and Office 2013 x64. After numerous driver reinstallation's, correcting permissions on the print spooler service/ dlls/ and drivers, updating/repairing Office, and a few other "off the wall" attempts to fix. The solution for us ended up being to uninstall Office 2013 x64 and install Office 2013 x32. For whatever reason this solved all of our problems on all 10 systems. My only thought is that there could be some compatibility issue with Office 64 and the spooler, since the spooler is a 32 bit process. Hope this helps and good luck to all.

Although I can't speak specifically to the Office 2013 64-bit installation (Microsoft recommends against it due to ongoing compatibility problems, unless you have a unique need for it) in each & every case I've encountered using the "Shane fix", as noted above, it has solved the problem immediately and without further ado.  It's also light-years easier than uninstalling and reinstalling all of the Office programs.  I would encourage everybody who has this problem to try the "quick fix" first before they go to all the trouble of uninstalling and reinstalling Office.  By the way, that still doesn't let HP off the hook for dragging their feet so long in (not) fixing this; it's criminal that they've ignored it nearly 2 years now when they're fully aware of the problem everybody is having; it certainly has not been kept a secret...

All, my apologies for the delayed response. This issue has not been ignored, and is being addressed with the next roll of the Universal Print Driver (UPD), slated for late Aug 2014. While we haven't been able to repro this issue, we have been able to root-cause from dump files provided by a few customers. As you have all found out, disabling status notifications (SNP) is the work-around, which doesn't get enabled if the driver is being installed in a 100+user domain (USERDNSDOMAIN environment variable set, then LDAP query for # of users). 

I hope this helps, and again, apologies for the delay in response. 

Feel free to contact me directly with any questions/comments. 

Best regards,

Dan 

Daniel.eccher@hp.com

All, my apologies for the delayed response. This issue has not been ignored, and is being addressed with the next roll of the Universal Print Driver (UPD), slated for late Aug 2014. While we haven't been able to repro this issue, we have been able to root-cause from dump files provided by a few customers. As you have all found out, disabling status notifications (SNP) is the work-around, which doesn't get enabled if the driver is being installed in a 100+user domain (USERDNSDOMAIN environment variable set, then LDAP query for # of users). 

I hope this helps, and again, apologies for the delay in response. 

Feel free to contact me directly with any questions/comments. 

Best regards,

Dan 

Daniel.eccher@hp.com

First of all, thanks for the update Dan; it's been an awfully long time in coming.  And now a few questions if I (and many others, I'm sure) may (& I'm not trying to be rude or ungrateful here, just direct):

1. I'm incredulous that HP couldn't reproduce this problem when countless other people have experienced it each time they installed the printer driver; seems like at some point you said you were trying to reproduce it on virtual machines, which apparently still are not like a regular "hardware install" on a standalone computer.  Did you guys in fact try it with individual standalone computers by doing clean installs on them? As mentioned elsewhere, this occurs exclusively with Office 13, regardless of whether it's on Windows 7, Windows 8 or Windows 8.1.  In my broad experience it never happened with Office 2010.

2.  What on Earth took so long after the original problem was identified and reported over a year ago?  That's a really long response time, much more so than HP usually takes to address such a vexing bug.  Remember this was not just a minor annoyance; you could only print one job at a time and then the computer would be useless to print again (often locking up completely) until it was rebooted. This caused my clients untold agony, not to mention me, because I was expected to explain what the problem was and magically fix it.  (Fortunately after the work-around became known I could sort of head it off at the pass on future installations.)

3.  Finally just exactly what, technically, was causing the problem?  After all the turmoil and brain-damage we went through confronting this nightmare, I (and countless others, I'm sure) would like to know exactly what caused it to blow up after printing only one time; I've never seen a bug like that before or after this time.

Thanks and standing by...

• Edited by Travis_Lloyd Friday, May 23, 2014 7:28 AM typo

All, my apologies for the delayed response. This issue has not been ignored, and is being addressed with the next roll of the Universal Print Driver (UPD), slated for late Aug 2014. While we haven't been able to repro this issue, we have been able to root-cause from dump files provided by a few customers. As you have all found out, disabling status notifications (SNP) is the work-around, which doesn't get enabled if the driver is being installed in a 100+user domain (USERDNSDOMAIN environment variable set, then LDAP query for # of users). 

I hope this helps, and again, apologies for the delay in response. 

Feel free to contact me directly with any questions/comments. 

Best regards,

Dan 

Daniel.eccher@hp.com

First of all, thanks for the update Dan; it's been an awfully long time in coming.  And now a few questions if I (and many others, I'm sure) may (& I'm not trying to be rude or ungrateful here, just direct):

1. I'm incredulous that HP couldn't reproduce this problem when countless other people have experienced it each time they installed the printer driver; seems like at some point you said you were trying to reproduce it on virtual machines, which apparently still are not like a regular "hardware install" on a standalone computer.  Did you guys in fact try it with individual standalone computers by doing clean installs on them? As mentioned elsewhere, this occurs exclusively with Office 13, regardless of whether it's on Windows 7, Windows 8 or Windows 8.1.  In my broad experience it never happened with Office 2010.

2.  What on Earth took so long after the original problem was identified and reported over a year ago?  That's a really long response time, much more so than HP usually takes to address such a vexing bug.  Remember this was not just a minor annoyance; you could only print one job at a time and then the computer would be useless to print again (often locking up completely) until it was rebooted. This caused my clients untold agony, not to mention me, because I was expected to explain what the problem was and magically fix it.  (Fortunately after the work-around became known I could sort of head it off at the pass on future installations.)

3.  Finally just exactly what, technically, was causing the problem?  After all the turmoil and brain-damage we went through confronting this nightmare, I (and countless others, I'm sure) would like to know exactly what caused it to blow up after printing only one time; I've never seen a bug like that before or after this time.

Thanks and standing by...

I would like to hear Dan's response to this, since in every situation I have encountered, I have been using HP Elite or EliteDesk computers, and HP LaserJet late model printers.  It seems to happen every time.

Michael

After lots of testing I have found a setting that has fixed all my HP CP5520 and HP M4555 printers that were crashing when printing from Office 365's 2013 pro plus.

It's the driver setting in Device settings -> Installable options -> Printer Status notification, this needs to be disabled.

I hope this also fixes other peoples problems.

Shane

This fixed it for me. HP LaserJet Pro 400 MFP on a Windows 2008 R2 Print Server.

I removed the setting in Printer Preferences > Device Settings > Installable Options > Printer Status Notification: change to Disabled

Then I removed the printer for the client computer, and restarted the client computer.

I then reinstalled the printer from the print server, rebooted, and tested Excel and Word.

• Edited by ATLTEK Thursday, June 19, 2014 9:22 PM

I have had the same problem hp laserprinter 4700dn - windows 7. After installation of Office 2013 only some pages are printed like all the other wrote it before.

After change the setting  Printer Status Notification to Disabled it was working as Shane described above.

Thank you very much for you help help Shane.

Axel

Nice one! Thanks! Cannot believe this is what was causing the issue! It worked for me

Yes indeed! And we are all still awaiting an update from Dan Eccher to confirm exactly when the much-needed (and very belated) Universal Print Driver update will be released which is supposed to fix this nightmarish problem.  "Late August" is getting pretty close, to be sure...

this worked great for me. Thanks so much for this

OMG ! I have been working to fix this problem all day.  Your driver tweek worked like a charm.  thank you so much for posting the fix.  We have a small 10 user network all with old Office 2003.  Decided to buy just Outlook 2013, via key card.  The download went on perfectly from Microsoft. But trying to print anything a 2nd time crashed the program.  Also after dumping Outlook via the task manager. No other application would be able to print. It was difficult finding the fix as well, you really have to just search for certain key words and phrases.

Thanks so much for taking the time to post this fix.

Hmm.  I have Microsoft Office 365 64 bit and Windows 7 Professional 64 bit on 4 computers and having the same problem on HP LaserJet M601.

All,

UPD5.9 has released, and is available on www.hp.com/go/upd. This issue is documented in the UPD5.9 Release Notes as resolved under issue "25348 Office 2013 and Office 365 may hang after printing when status notification pop-ups are enabled."

If you continue to experience issues after updating to UPD5.9, please contact HP Support (800-334-5144) referencing this forum post, and my name. Doing so will ensure we get the issue properly qualified and cases needed for an escalation into the HP Labs. You can also send me a head's-up, informing me of the issues, so I can follow-up on them.

Best regards,

Dan Eccher

daniel.eccher@hp.com

Thanks Shane, It works fine.

Using Office 365 32 bit, Windows 7, fixed and wireless network and just installed a brand new HP MFP M476dw. Same problem as everyone else have reported. One printout works - then printer gets locked up.

Spent an hour and half with HP support yesterday. Uninstalled and reinstalled drivers and tested a bunch of other things. Nothing worked.

Then found this thread. THANKS SHANE! Amazing - the fix worked and seems that HP still hasn't a fix. Or at least hasnt been ablre to distribute it to its support centers. And why do I have to find the solution on a MS support page and not on HP's?? 

(By the way - our Lexmark and Canon printers on the same network work fine)

It's the driver setting in Device settings -> Installable options -> Printer Status notification, this needs to be disabled.

This fixed the problem

Thank you very much Shane

Shane is a genius. I have been fighting this problem for well over a year now and never had time to resolve it. Finally found a post where HP tech support wasn't sending people on a wild goose chase checking all kinds of things that were not the problem. HP driver updates still don't resolve the issue that is solved by Shane here with the quickest fix possible. THANK YOU, THANK YOU, THANK YOU!!

This worked on both my computers which were having the same problem.

1) HP Laptop Win 8.1 64 bit, Office 2010 32 bit.

2) Desktop Win 7-64 bit, Office 2013 64 bit.

• Edited by Cardinal-Bags Friday, November 14, 2014 12:51 PM

This fixed my issue as well.

SD

Thanks , Shane....

Thanks Shane, fixed my M451dn printing issue!