I’m new here, not even certain if I have the right place to ask my question?
I’m using Windows 11 and PSM 7.2.11 (build 9078)
It appears that when the Windows Update “KB 5101650” was installed PDF’s stopped being printed using the PSM postscript driver option (standard or optimized).
Everything in PSM looks as it should, I can import and do all of my normal operations it is only when it goes to print that no PDF’s are actually printed.
Uninstalling the Windows update restored PSM to normal operation. I assume at some point Windows will force me to install that update again and will not allow me to uninstall it.
Is there a known workaround in PSM or a Windows setting to overcome this problem?
To fix PSM classic not printing images, KB5121003 must be uninstalled and the computer rebooted. You can also open a support ticket to be notified of the patched release when it is available.
Thanks for your response.
Will there be any options available for people who don’t have current support contracts?
I’m unable to submit a ticket. Possibly because the “Email For” dropdown is empty, maybe because I don’t have a current support contract?
thx
Ray
I have the same issue, uninstalling Windows Update KB5121003 (as confirmed by jchamel) fixed it for me. Although this is a security update, so not ideal.
I also have the same problem with being unable to open a support ticket!
My team has been dealing with this issue as well (since rolling back Windows updates would require an IT ticket and escalated approvals), so I wanted to drop in a workaround that I found:
If you save the .PDF as a .PNG image, use that instead, and then use Standard Postscript (Edit > Preferences > Print Job > Technology), it usually* comes out fine.
*This really only works for items where the .PDF is fixed and the file has pretty simple formatting, but it’s helped us get those jobs done while we wait for an update.
We have prepared a fix and are currently preparing a build for QA testing. We hope to make the patch available in the coming days, pending successful testing.
It is currently in the hands of QA to validate the fix and certify the general quality of the build, as it has been quite some time since the last release.