

- #FUZZMEASURE FIX HANG WITHOUT LOSING DATA HOW TO#
- #FUZZMEASURE FIX HANG WITHOUT LOSING DATA PRO#
- #FUZZMEASURE FIX HANG WITHOUT LOSING DATA SOFTWARE#
- #FUZZMEASURE FIX HANG WITHOUT LOSING DATA PC#
I could understand if, maybe, we've installed some new software between A and B. Printers, even though nothing has changed between "working" and "not working". That's what irritates me, that Office keeps having trouble with these The problem is that the drivers/spoolers on the computers randomly STOP working for no apparent reason, with no rhyme or reason, and almost always while printing from MS Office programs. They work fine, they always print a test page (although I wish there was a "null print" option, where I can just test if the spooler/drivers are working right, but not produce a piece of paper). Installed properly on all the computers, done the right way.
#FUZZMEASURE FIX HANG WITHOUT LOSING DATA HOW TO#
I know how to set up this stuff, and we've done everything by-the-books here.

It's not a problem about "the computers can't connect to the printer" like some kind of "I just read a book and wanted to get started in IT" guy. I just can't understand how this could possibly have left HP's "labs". With the current printer setup") until I exit and re-open all Office programs. if there is a printing problem, I can restart the spooler and it'll fix it for all OTHER programs, but Office often still keeps screwing up ("cannot print due to a problem One worse, it seems that Office 2010 adds an additional layer of problems to the mess. Restarting or detecting it? Either way, it's not mine everything I've been doing here is being done completely by the books. Is it an HP thing because the spooler is hanging, or is it a Microsoft thing for allowing the spooler to hang without

Later that day another person's computer was hanging in MS Word in the "print" menu (not responding) and, as usual, all I had to do was kill splwow64.exe and immediately Word sprang to life and was A few days later the problem came up AGAIN. I connected the printers "directly" (via a direct network connection, not a shared printer) On our president's PC, he was getting the same issues with printing from MS Office 2010, so I got fed up with it and threw the sledgehammer at it. I would love to know the setup of anyone that uses HP printers on their domain and hasn't had these sorts of Tried that too. it didn't)Ĥ HP printers sharing a single HP UPD (Universal Print Driver), a P2015DN, 4050, Color LaserJet 4700, and a P4014.
#FUZZMEASURE FIX HANG WITHOUT LOSING DATA PRO#
Windows 7 Pro 圆4 as the "bug-testing" print server that was supposed to fix these problems (. Windows Server 2003 R2 as the AD domain controller and on the original print server Win7 from the OEM (some preloaded HP systems). The issue occurs nearly randomly for all users that print, even on the computers that came with Every computer was individually installed and configured from retail media, not imaged. Windows 7 Pro 圆4 on all ~25 PCs, clean installs, less than a month old. So the users are left with Windows shrugging and going "I don' see no stinkin' problem", and I'm left with no explanation other than to throw my arms up and shout "MICROOSOOOOOOOFFTTTTT!!!!". it checks that status of the print spooler as one of its "tests" and it never finds a problem with it. I'm mostly frustrated that this is such a common and recurring problem, and yet the Windows "print troubleshooter" is completely and totally worthless. There seems to be absolutely no pattern to the madness.
#FUZZMEASURE FIX HANG WITHOUT LOSING DATA PC#
Up a few times on my own PC at the office as well. And it seems to happen for no apparent reason. Is this acceptable to you?! Am I supposed to walk the users through how to restart the print spooler? I always have to go out to each computer and restart their spooler whenever this happens. (Sometimes also kill the splwow64.exe process which is hanging the applications and/or "problem with the current printer configuration) And it's the ONLY solution that actually works (can't add a printer, removing printer leaves a "ghost" printer behind, etc). And there isĪlways one solution, that always fixes each of these problems.
