tbird 60.7.2 not printing in win 10 pro ver 1903

[Malcolm11929]

I have two PC's each with Windows 10 Pro Version 1903 and Thunderbird 60.7.2. Neither computer can print or save as. the print box / save box screens do not appear. Just a brief flash. Printer works with all other programs. I have tried with a couple of older versions of TB with same result. i have not found any items by doing a web search.
Suggestions to fix please

[LIMPET235]

Moving this to the Thunderbird Support forum...

Does it function if you roll back/remove the 1903 update?
Might be the cause?

[Malcolm11929]

One is a new computer so no roll back. Another computer with 1809 works OK. !903 is fully up to date. I can print using eM Client on both computers without problems.

[tanstaafl]

I'm on build 1809. I'll update to 1903 later today and see if I have the same problem.

It might help to reset all print* settings using the config editor and restart Thunderbird. For example I have lots of settings such as print.printer_Brother_HL-L2320D_series.print_bgcolor due to last using a Brother HL-L2320D laser printer.

Do you have the same problem with the "Microsoft save to PDF" print queue? The reason I ask is that's generic (not printer specific).

[tanstaafl]

Initially neither Thunderbird or em client would go online (after updating to build 1809) but restarting fixed that. The print settings changed to landscape at 175% but I was able to reset them to portrait at 100% (in Thunderbird) and print a message on the laser printer.

[Malcolm11929]

Re print.printer settings, these changed correctly when either printer is set as default. The settings are portrait at 100%. i will try print to PDF but my thoughts are that wont work. Dont forget I have same problem when trying "Save As" feature. This suggests to me is that the problem is associated with the task in calling the windows functions but I may be wrong. I will comment later after testing.

[Malcolm11929]

I just started the problem computer and said thunderbird update and now all working. Same happened with the second computer as well. so I don't know what fix was
Thanks for your help