Saving .pdf reports

[Orizon-STL]

I have PC-DMIS CAD++ 2018 R2
I recently updated my service pack and now when I save my report as a .pdf a second save menu wants me to save it again. But, this save menu has some crazy symbol after the .pdf
How do I get rid of this second save menu?
PC-DMIS SAVE.PNG

[bfire85]

Do you have the printer checked on the output settings and have your default printer set to an additional PDF writer?

[Orizon-STL]

Here are my setting. I've been saving my reports like this for years. This new "Output File Name" window just started popping up after I updated my PC-Dmis to Service Pack 8.
-FILE
-PRINTING
-REPORT WINDOW PRINT SETUP
PC-DMIS SAVE PDF.PNG
Thanks,
Keith

[RIDER]

Has someone slipped a PRINT command into your program's code?

[Orizon-STL]

I don't see a PRINT command in my EDIT WINDOW. This happens on all my programs now.

[bfire85]

Here are my setting. I've been saving my reports like this for years. This new "Output File Name" window just started popping up after I updated my PC-Dmis to Service Pack 8.
-FILE
-PRINTING
-REPORT WINDOW PRINT SETUP
PC-DMIS SAVE PDF.PNG
Thanks,
Keith

Do you want it to be on PROMPT? That will prompt a dialog box to come up to save into a specific location.

[Orizon-STL]

Yes, I like to be able to name my reports.

[SABarber]

Th second dialog is coming from Amyuni Print Driver. You can tell by the Concatenate on the dialog. A registry setting does not have the correct permissions. There is another thread about this. I think Anders has posted the solution.

[AndersI]

You need full access rights to HKEY_CURRENT_CONFIG\Software\PC-DMIS 50 Converter - it seems a recent Windows Update has caused this problem on a lot of computers. If that sounds like gibberish, or you are not allowed to do the change, you need help from your local IT.

SABarber - doesn't that indicate some error in the installation program? Driver not running as a priviledged user, but under the user account? Login for the driver not correctly setup?

[SABarber]

Amyuni has its own installation. I wonder if an MS update also tried to update the driver? Seems pretty random which makes it harder to determine the cause.
Pcdmis installation checks to see if the driver is already installed and if it is should not re-install it.

[Peter Fuller]

IMO this indicates an issue with computer configuration, not installation. HKCC\* is a replication of a HKLM\SYSTEM\CurrentControlSet\Hardware Profiles\Current\ and should never be restricted. I can see 100 machines in the same domain have no issues all running the exact same install and version of PC-DMIS and one machine be errant and present this issue. Always stems from a user profile configuration issue.

[AndersI]

I don't think a system driver should run under the 'current user' account…

And Another 'interesting' thing was that the latest Windows Update changed computers from working to 'not working any longer', until the access rights were re-set on them.