Yea, had the same issues, but with almost 260 Citrix servers. Created package using the customization wizard where I turned off the enhanced security "Protected Mode at Startup", EULA, and all the other stuff you don't want your users messing with and deployed to our test farm and it functioned like a dream. Last week I applied the recent security updates 10.11 and 10.12 and everything look fine, however, I will have to admit that I didn't kill a tree testing the printing fuctionality. Well, I'm into day two of updating my production farm with this new version of Reader and it's security updates along with latest updates for Flash and Shockwave. I'm about 85% done when the phone starts ringing off the hook, it's our Help Desk which is getting calls from users stating they can't print. I test and sure enough as soon as I hit the print button, Reader crashes. I checked my test farm and same thing is happening there where I was able to print prior to the security updates. So I spend the next two hours un-installing 10x and re-install the 8.2.6 version we have been using without issue for as long as I can remember till I can get a handle on things. Run through my install again with the custom mst file, it works, install the security patch and it is now broken. Seems the security updates over-write your custom settings. I now have a post install script that sets the application and security settings to the state that I want them.
We didn't upgrade to 9x on our Citrix farm due to all the horror stories I read about on the Citrix and Adobe forums. When is Adobe going to address the original issue with 10x, why does your application crash when you try to print with the default security settings. Please fix-it!
"Can someone suggest another product from another vendor that we can use in place of Reader X?"
"so should we change to another reader ? what alternative do you suggest?"
Yes, as a matter of fact this is exactly what I did - for it's what should always be done when there is a superior or equal alternative (without defect) to an inferior or defective product, I switched. It took about two days of getting used to, and now I know I will never return to Adobe again. The one I switched to, available free or paid (which gives further capabilities), is actually much more awesome than Adobe's product, at least for my uses.
This product allows me to mark up pdf files, along with many other functions that the free version of Adobe does not permit.
It is called pdf-xchange-viewer. It is free (or paid) for both personal and commercial use.
Here is its homepage: http://www.tracker-software.com/product/pdf-xchange-viewer.
I think it blows Adobe out of the water, but at the very least it is an equal, an equal from which at least the user is able to print their documents without issue.
(Also, and this is just a bonus, I use another program called "PDF Split and Merge" to merge various PDFs, which is also free and also a great product offering services that Adobe's free version does not.)
Good luck and happy trails saying goodbye to Adobe.
Lol, this only sounds like an ad, but I promise, it is not!!
There are a couple of workarounds posted here http://forums.adobe.com/message/4142897#4142897.
In short, you can turn on "Sharing" in the printer properties, and give it a "Share Name"...should print OK after that. It worked for me.
Adobe has a hotfix for the 10.1.2 patch which works. Tested on our DEV and UAT farm with a script that does a silent install of the hotfix and re-sets the registry value to Enable Protected Mode. So far so good.
News at 11!
"Failure lies not in falling down. Failure lies in not getting up."
Ran into the same issue you were experiecing, have you checked the Default Printer? Once I defaulted the user's printer to one of the office printers, Adobe X stopped freezing. Switched it back to their home printer, which was not connected, the freezing returned. For giggles, I defaulted to a couple of the non-Adobe PDF Printers, freezing returned.
Even with 'Enable Protected Mode..' unchecked I am getting the below error in my Application event log. I use Adobe Reader 11.0.2 in Windows 7 with IE 9 to view PDF forms -
Faulting application name: AcroRd32.exe, version: 18.104.22.168, time stamp: 0x511eacd6
Faulting module name: AcroRd32.dll, version: 22.214.171.124, time stamp: 0x50d0b924
Exception code: 0xc0000005
Fault offset: 0x0006a4ec
Faulting process id: 0x880
Faulting application start time: 0x01ce218774519977
Faulting application path: C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe
Faulting module path: C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.dll
Report Id: b2649438-8d7a-11e2-89ec-84d7e7c9833f
Our friend the Protected Mode anti-printing bug has returned with the advent of Adobe Reader 11.0.09. The bug must have been fixed at some point after my original problem with this in Reader X, where I found that disabling Protected Mode allowed printing to LAN printers. Tead my posts in the thread above, and you will see that, at least in my experience, the problem was limited to printing to shared printers within the same subnet (i.e. where either the printer or the shared printer host is in the same subnet as the client computer--printing to the same shared printer via the same share host but across a VPN, and thus from a different subnet, did not cause the problem.
At any rate, from some point in the further evolution of Adobe X, the problem disappeared, and I no longer had to disable protected mode to get network printing working correctly. This persisted up through Adobe Reader 11.0.08; however, when I updated some stations to 11.0.09, the problem returned, albeit with a slightly different manifestation. While it does not crash upon attempting to print to a network printer, it simply does nothing; it does not pass the job to the print spooler on the server hosting the printer share, and it never makes it to the printer.
So I am back to creating this .reg value (that disables Protected Mode) on affected computers; so far these are just Windows XP computers, since many of my clienst are simply not going to upgrade or replace all of their still-working XP computers yet:
Windows Registry Editor Version 5.00
Don't know if its connected or not, but reviewing a number of posts below, and trouble shooting some other similar issues on a number of devices, there seems to be an O-S compatibility issue "encouraging" people to upgrade to WIN-10. With FORCED updates coming in WIN-10, and hidden unspecified changes to security and privacy in WIN-10, I'm monitoring some of these things now for potential issues. Just wanted to pass this along.
I had success with the "Compatibility" fixes suggested below, so your solution might lie in that direction.
One caution, tho- with the main justification for ADOBE pushing their latest update being an effort to plug security holes in previous versions, and the only solutions to the resulting crashes being to disable security locks or run in previous modes (I had to go all the way back to win-98/Me to succeed) I see a major RED FLAG with this latest update. That some have been struggling with this since last February, it's clear that if this is a known bug that REMAINS uncorrected for this long, there may be some legitimate cause for concern. That the problem MAY NOT be an ADOBE problem, but a WINDOWS compatibility problem, and not only with ADOBE but with certain suddenly "Incompatible" printer drivers in WIN-7 that can only be corrected by allowing an upgrade from ANY previous windows [ some here are running WIN-XP ~30% market share user base, even nowadays !!! ], Server-2k, 3k, etc) to WIN-10, I see a major red flag. A forced upgrade to WIN-10 is a real concern.
I'd love to be corrected on this. I'm just commenting on what I've noticed. Sincerely- I MAY be missing something.
Best to you and all here,