We are using Adobe Framemaker 2019 with Adobe Professional 2017. For the past week, we have been having issues with the Adobe pdf printer inadvertently disappearing. The only solution we have so far is to uninstall and reinstall Adobe Pro. We cannot keep doing this so I have reached out to Adobe support for a solution but have not heard back yet. This seems to only be happening to those of us in the company using FrameMaker 2019. Is anyone else having this problem that can offer a solution? We don't know if there is a company involved script or something like that causing this.
Are you all patched up? Check Help > Updates to check. Might also be something to do with Windows updates - I've noticed recent updates have messed up my Windows printer instances lately.
Thanks! Sadly, we have not uploaded any patches yet because we are kinda afraid to. We have some plugins installed on our computers that interface with FrameMaker, i.e., Timesavers and Framescript. We also have our maker file configured with some items like a reference to the company dictionary and we have fonts installed as well. We'll have to run the latest update on a test computer to see if it messes anything up.
Our IT is hopefully going to research this. They don't have a clue so far.
Your plugins or FrameScript scripts should not be affected.
Adobe fixed lots of issues in the updates. Therefore I would really do this.
So the printer is vanishing for all applications and in Control Panel?
On just one system?
What is the default printer on this machine?
re: uninstall and reinstall Adobe Pro
It vanishes from the list of available printers in the control panel. We set the default printer as Adobe pdf.
This is starting to sound like a Windows problem. Anyone who can help will need to know
what Windows Edition 7,...,10, home, pro, enterprise, etc.
Version: e.g. 1903
32- or 64-bit
OS build: e.g. 18362.1016
Any notion of the event triggering the vanishing?
I agree this sounds like a Windows problem. We just have to wait on our IT to consider this important enough to work on now.
We have suspicions a Webex script might be causing this when the software updates in the background
Ok, I've definitely heard of that happening then - usually it's messed up on the receiving end of a WebEx connection, not the initiating side, but ymmv!